From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] use-mail branch and other work
Date: Mon, 31 Mar 2014 14:02:46 +0200 [thread overview]
Message-ID: <1396267296-sup-756@qwerzila> (raw)
In-Reply-To: <9CF97884-262B-4CAA-951C-D359C331AC3F@schmeiser.org>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
Excerpts from Steven Schmeiser's message of 2014-03-30 22:47:37 +0200:
> Then I use the async edit mode when replying to messages. It would be
> nice for sup to have an option to always use async edit, but this gets
> me by.
I added an option in #283 as a response to your old request in #118.
Please try it out. Probably needs some testing in regular mode first as
well..
- gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-31 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 9:51 Martin Bähr
2014-03-30 20:47 ` Steven Schmeiser
2014-03-31 12:02 ` Gaute Hope [this message]
2014-03-31 12:09 ` Gaute Hope
2014-04-01 4:13 ` Martin Bähr
2014-03-31 19:42 ` Matthieu Rakotojaona
2014-03-31 20:57 ` Gaute Hope
2014-04-01 3:55 ` Martin Bähr
2014-04-01 3:46 ` Martin Bähr
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=1396267296-sup-756@qwerzila \
--to=eg@gaute.vetsj.com \
--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