From: Steve <steve.goldman@gmail.com>
To: sup-devel@rubyforge.org, Michael Hamann <michael@content-space.de>
Subject: [sup-devel] Bug report: temp file commit breaks my emacs hook
Date: Mon, 10 Jan 2011 15:11:35 -0500 [thread overview]
Message-ID: <AANLkTi=ZtdvYyBgKTMzj_DzwQP0xjRmWWzuEouZwW8Bs@mail.gmail.com> (raw)
Hi all,
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?
My emacs hook looks like this.
(add-to-list 'auto-mode-alist
'("sup\\.\\(compose\\|forward\\|reply\\|resume\\)-mode$" . mail-mode))
Thoughts?
Thanks.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-01-10 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 20:11 Steve [this message]
2011-01-10 20:48 ` Michael Hamann
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='AANLkTi=ZtdvYyBgKTMzj_DzwQP0xjRmWWzuEouZwW8Bs@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