From: Steve <steve.goldman@gmail.com>
To: Michael Hamann <michael@content-space.de>
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 16:09:10 -0500 [thread overview]
Message-ID: <AANLkTikWwbXcGx-9ZyKhyTOJ2a9JOd9CscPnSzphTAVV@mail.gmail.com> (raw)
In-Reply-To: <1294691658-sup-2474@mithink>
On Mon, Jan 10, 2011 at 3:48 PM, Michael Hamann
<michael@content-space.de> wrote:
> 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.
Makes sense. I have corrected my emacs pattern. No need to patch.
Thanks!
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-01-10 21:18 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
2011-01-10 21:09 ` Steve [this message]
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=AANLkTikWwbXcGx-9ZyKhyTOJ2a9JOd9CscPnSzphTAVV@mail.gmail.com \
--to=steve.goldman@gmail.com \
--cc=michael@content-space.de \
--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