Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] Can't get emacs to open in flyspell-mode
Date: Fri, 07 Nov 2008 16:03:06 -0600	[thread overview]
Message-ID: <C53A173A.2EA6%chrisw@rice.edu> (raw)
In-Reply-To: <1226009080-sup-663@sgoldmanlinux.tower-research.com>

"Steve Goldman" <sgoldman at tower-research.com> @ 2008-11-6 4:07 PM:
> I set my editor in config.yaml to:
> 
> emacs -f flyspell-mode -nw +8
> 
> This command works correctly from the command line, but when sup opens
> emacs for composing, it uses -nw and +8 correctly but does not use
> flyspell-mode.  Anyone have any luck with this?

I set my editor to be emacsclient and added this to my .emacs:

; disable longlines-mode for e-mail
; mail-mode runs text-mode first.
(add-to-list 'auto-mode-alist
'("sup\\.\\(compose\\|forward\\|reply\\|resume\\)-mode$" . mail-mode))
(add-hook 'mail-mode-hook (function (lambda ()
                                      (longlines-mode 0)
                                      (auto-fill-mode 1))))

Using emacsclient keeps one copy of emacs open, but each invocation of
emacsclient opens a new buffer with the given file. I always used sup while
using a windowing environment at the same time.
http://www.emacswiki.org/emacs-en/EmacsClient

Even if you don't use a windowing environment, the mail-mode modification
should work. It will also give you some nice features like quote
highlighting while editing (assuming font-lock is on).

-- 
Christopher Warrington <chrisw at rice.edu>




  parent reply	other threads:[~2008-11-07 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 22:07 Steve Goldman
2008-11-07  1:02 ` William Morgan
2008-11-07 14:23   ` Steve Goldman
2008-11-07 22:03 ` Christopher Warrington [this message]
2008-11-07 22:24   ` Steve Goldman
2008-11-10  5:13     ` William Morgan

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=C53A173A.2EA6%chrisw@rice.edu \
    --to=chrisw@rice.edu \
    /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