From: Steven Schmeiser <steven@schmeiser.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] always use async editing?
Date: Tue, 09 Jul 2013 19:00:39 -0400 [thread overview]
Message-ID: <1373410624-sup-1657@indy.local> (raw)
Is there a way to always use async editing when composing a reply or new
message? Right now, when I reply to a message, I hit 'E' then 'H' to
launch my async editor. Can this be configured as the default
behavior and can asyn mode be used to compose new messages (without
going back and editing a draft?)
Steve
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2013-08-02 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1373410624-sup-1657@indy.local \
--to=steven@schmeiser.org \
--cc=sup-talk@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