From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Defining session for emacs as mutt editor
Date: Fri, 22 Mar 2013 15:35:19 -0600 [thread overview]
Message-ID: <20130322213519.GA9386@hysteria.proulx.com> (raw)
In-Reply-To: <87a9pvbjz8.fsf@engels.HistoricalMaterialism.info>
Haines Brown wrote:
> I want to have mutt (which is started from terminal) use emacs as its
> editor with its own initialization file. So in .muttrc I put:
>
> set editor="emacs -q -l ~/.emacsMutt"
Seems reasonable. Alternatively you might consider setting
emacsserver and running emacsclient to connect to the running emacs.
> This defines an emacs session located on right half of my screen. My
> objective is to have the editor displayed to right of screen and the
> mutt messages remain displayed to its left.
I do not think that is possible. Because mutt is going to invoke
emacs and then wait for it to exit before continuing. Effectively
the editor process is stacked on top of mutt and mutt will only become
active again once the emacs process is popped off the stack.
> However, when the emacsMutt window starts, the mutt messages window is
> replaced by an empty emacs window, and as the result I no longer see the
> mutt messages. An -nw option only makes the emacsMutt session full
> screen.
What do you mean by an empty emacs window? I think it should be an
empty mutt window. Mutt cleared the display in preparation for
running the editor. Then mutt is waiting for the editor to exit so
that it can continue. In this case you told emacs in your .emacsMutt
file to open a graphics window and so the original terminal is empty
and waiting.
The issues are mutt specific. I would take up the discussion on the
mutt-users mailing list. Over here on the emacs side of things I
expect the suggesions will be to use vm or gnus where this is already
possible. FWIW the ability to fork off an edit task asynchronously
from the mutt index is something I have also wanted. But I don't
think anyone has written a way in mutt to do this yet.
Bob
next prev parent reply other threads:[~2013-03-22 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 14:13 Defining session for emacs as mutt editor Haines Brown
2013-03-22 21:35 ` Bob Proulx [this message]
2013-03-23 9:43 ` XeCycle
2013-03-31 23:53 ` Suvayu Ali
[not found] ` <mailman.23192.1364774017.855.help-gnu-emacs@gnu.org>
2013-04-01 11:58 ` Haines Brown
2013-04-02 18:55 ` Suvayu Ali
[not found] ` <mailman.23325.1364928968.855.help-gnu-emacs@gnu.org>
2013-04-03 10:32 ` Haines Brown
2013-04-04 20:30 ` Bob Proulx
[not found] ` <mailman.23551.1365107426.855.help-gnu-emacs@gnu.org>
2013-04-05 10:03 ` Haines Brown
2013-04-01 18:28 ` W. Greenhouse
2013-04-01 18:43 ` Mark Skilbeck
2013-04-01 18:57 ` W. Greenhouse
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130322213519.GA9386@hysteria.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).