Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Michael Hamann <michael@content-space.de>
To: Steve <steve.goldman@gmail.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Bug report: temp file commit breaks my emacs hook
Date: Mon, 10 Jan 2011 21:48:05 +0100	[thread overview]
Message-ID: <1294691658-sup-2474@mithink> (raw)
In-Reply-To: <AANLkTi=ZtdvYyBgKTMzj_DzwQP0xjRmWWzuEouZwW8Bs@mail.gmail.com>

Hi,

Excerpts from Steve's message of 2011-01-10 21:11:35 +0100:
> This commit has broken part of the interaction between sup and my emacs.
> 
> commit 60573298a2258c101a85b3de8121f73d7aec2d51
> Author: Michael Hamann <michael@content-space.de>
> Date:   Fri Oct 8 10:03:36 2010 -0400
> 
>     Fix monkey-patching of Tempfile
> 
> 
> Did you change the name of the temp file that gets passed to emacs?

Yes. Now sup can and must use the syntax for Tempfile creation that is
available in Ruby version 1.8.7 and newer. It allows to set both a
prefix and a suffix. I didn't care about the filename because I had the
experience that with the old filename my Vim didn't recognize the
content as email and without the extension it recognizes it which gives
me nice syntax highlighting even without configuring anything.

> My emacs hook looks like this.
> 
> (add-to-list 'auto-mode-alist
> '("sup\\.\\(compose\\|forward\\|reply\\|resume\\)-mode$" . mail-mode))

The string you are looking for is now at the beginning of the filename
so you could change your hook to match the beginning of the filename
instead of the end.

The following simple change will change the end of the filenames to
.EXTENSION, so if you think it makes sense to add an extension again I
could provide a proper patch.

diff --git a/lib/sup/modes/edit-message-mode.rb b/lib/sup/modes/edit-message-mode.rb
index 86aef4b..052421d 100644
--- a/lib/sup/modes/edit-message-mode.rb
+++ b/lib/sup/modes/edit-message-mode.rb
@@ -162,7 +162,7 @@ EOS
   def edit_subject; edit_field "Subject" end
 
   def edit_message
-    @file = Tempfile.new "sup.#{self.class.name.gsub(/.*::/, '').camel_to_hyphy}"
+    @file = Tempfile.new ["sup.#{self.class.name.gsub(/.*::/, '').camel_to_hyphy}", ".EXTENSION"]
     @file.puts format_headers(@header - NON_EDITABLE_HEADERS).first
     @file.puts
     @file.puts @body.join("\n")


Regards,
Michael Hamann
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-01-10 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 20:11 Steve
2011-01-10 20:48 ` Michael Hamann [this message]
2011-01-10 21:09   ` Steve

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1294691658-sup-2474@mithink \
    --to=michael@content-space.de \
    --cc=steve.goldman@gmail.com \
    --cc=sup-devel@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox