Mutt, Emacs and post-mode

[downtime]

I'm not having much luck using post-mode. When I start an email from mutt
and load emacs, I get the error "File mode specification error: (void-
function post-mode)"

I have post.el in ~/.emacs-modes and (load "~/.emacs-modes/post") in
my .emacs file.

Google searches found similar errors, but I didn't find anything that
relates to problems specific to post-mode.

I can provide other info on request. Any help is appreciated.

[downtime]

Post by downtime
I'm not having much luck using post-mode. When I start an email from
(void- function post-mode)"
I have post.el in ~/.emacs-modes and (load "~/.emacs-modes/post") in my
.emacs file.
Google searches found similar errors, but I didn't find anything that
relates to problems specific to post-mode.
I can provide other info on request. Any help is appreciated.

So. Yeah. I was going off of a configuration off the internet that I
didn't totally understand. I start emacs and did m-x post-mode, and it
loaded fine. So that's weird. Then I look in my .mutt/muttrc, and there's
the crazy 'set editor=' line that has way more than necessary. The
details aren't important there, but I changed it to 'set editor=emacs -nw'
and voila! post-mode loads fine now.

The end.

[Ian Zimmerman]

Post by downtime
So. Yeah. I was going off of a configuration off the internet that I
didn't totally understand. I start emacs and did m-x post-mode, and it
loaded fine. So that's weird. Then I look in my .mutt/muttrc, and
there's the crazy 'set editor=' line that has way more than
necessary. The details aren't important there, but I changed it to
'set editor=emacs -nw' and voila! post-mode loads fine now.

That is quite inefficient, and it also means that you cannot use the
context from your emacs work in composing the message (such as the kill
ring, command history etc). Clearly the "right" way is to run a main
emacs in server mode and let mutt just connect to it, like this:

set editor="emacsclient -c"

(I marked and copied this line from my main emacs window where I opened
a muttrc buffer, and yanked it into the message composing window [1].
See what I mean?)

BTW, I fail to see the advantage of this newfangled "post-mode" over
message-mode which has been in emacs for decades.

[1] oh yeah, I use mutt for posting news, go figure.

[Jorgen Grahn]

Post by Ian Zimmerman

Post by downtime
So. Yeah. I was going off of a configuration off the internet that I
didn't totally understand. I start emacs and did m-x post-mode, and it
loaded fine. So that's weird. Then I look in my .mutt/muttrc, and
there's the crazy 'set editor=' line that has way more than
necessary. The details aren't important there, but I changed it to
'set editor=emacs -nw' and voila! post-mode loads fine now.

[emacsclient]

Post by Ian Zimmerman
BTW, I fail to see the advantage of this newfangled "post-mode" over
message-mode which has been in emacs for decades.

I'm using mail-mode (for both mail and Usenet postings), for no
particular reason. Should I be using message-mode instead?

/Jorgen

[Ian Zimmerman]

Post by Jorgen Grahn

Post by Ian Zimmerman
BTW, I fail to see the advantage of this newfangled "post-mode" over
message-mode which has been in emacs for decades.

I'm using mail-mode (for both mail and Usenet postings), for no
particular reason. Should I be using message-mode instead?

I think it depends on your edit_headers setting. I have it on because I
like to always see the headers of the message I'm composing; and
message-mode has commands and key bindings to navigate the headers. If
you're used to just seeing the body of the message, another mode may be
better for you.

[Jorgen Grahn]

Post by Ian Zimmerman

Post by Jorgen Grahn

Post by Ian Zimmerman
BTW, I fail to see the advantage of this newfangled "post-mode" over
message-mode which has been in emacs for decades.

I'm using mail-mode (for both mail and Usenet postings), for no
particular reason. Should I be using message-mode instead?

I think it depends on your edit_headers setting. I have it on because I
like to always see the headers of the message I'm composing; and
message-mode has commands and key bindings to navigate the headers. If
you're used to just seeing the body of the message, another mode may be
better for you.

I keep edit_headers set and mostly modify headers inside the editor.
But I like seeing mail headers as text and don't mind editing them
that way, without more help than the syntax highlighting provided by
mail-mode.

Syntax highlighting and M-x fill-paragraph honoring '>'-quoted text
are the reasons I use mail-mode instead of plain text mode.

/Jorgen

[downtime null]

post-mode is just a major mode for Emacs, and once I simplified the
set_editor line to just 'emacs -nw', post-mode started working fine.
It's also working right now with Emacs as the editor for slrn. But I've
changed my mutt editor to vim for now. lol

Post by Jorgen Grahn

Post by Ian Zimmerman

Post by Jorgen Grahn

Post by Ian Zimmerman
BTW, I fail to see the advantage of this newfangled "post-mode" over
message-mode which has been in emacs for decades.

I'm using mail-mode (for both mail and Usenet postings), for no
particular reason. Should I be using message-mode instead?

I think it depends on your edit_headers setting. I have it on because I
like to always see the headers of the message I'm composing; and
message-mode has commands and key bindings to navigate the headers. If
you're used to just seeing the body of the message, another mode may be
better for you.

I keep edit_headers set and mostly modify headers inside the editor.
But I like seeing mail headers as text and don't mind editing them
that way, without more help than the syntax highlighting provided by
mail-mode.
Syntax highlighting and M-x fill-paragraph honoring '>'-quoted text
are the reasons I use mail-mode instead of plain text mode.
/Jorgen