From: Hamish D <dmishd@gmail.com>
To: Mark Alexander <marka@pobox.com>
Cc: sup-talk <sup-talk@rubyforge.org>,
Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] Preparing for sup 0.13
Date: Tue, 18 Oct 2011 18:58:40 +0100 [thread overview]
Message-ID: <CAOxvSbchWGomtdFSv1yATD1=PvQ0zHZjfrdYx1uJk7RgTqb=CA@mail.gmail.com> (raw)
In-Reply-To: <1318945224-sup-126@bloovis.org>
On 18 October 2011 14:46, Mark Alexander <marka@pobox.com> wrote:
> Excerpts from Hamish D's message of Sun Oct 16 08:09:41 -0400 2011:
>> * added an asynchronous edit mode - this allows you to carry on using
>> sup while composing a message in an external editor
>
> I'm not having much luck with this feature. I was able to write an
> async-edit hook that spawned my editor in a separate gnome-terminal
> window. But when I exited async-edit mode, sup started responding to
> keystrokes weirdly. I tried to discard the message I had just
> composed using 'x', so sup asked if I wanted to discard the message,
> and when I hit 'y', it sent the message instead of discarding it.
> After that, sup behaved as if every other keystroke was being
> discarded, and I had to quit and restart.
Could you email me your hook so I can check if there is anything in it
that might cause trouble? I've used the mode myself a bit and not hit
that issue.
I guess it's not really a regression as the feature didn't exist in
sup 0.12, but would still be good to sort it out ...
Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-10-18 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 12:09 Hamish D
2011-10-18 13:46 ` [sup-devel] " Mark Alexander
2011-10-18 17:58 ` Hamish D [this message]
2011-10-19 14:31 ` Mark Alexander
2011-10-20 13:18 ` Mark Alexander
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='CAOxvSbchWGomtdFSv1yATD1=PvQ0zHZjfrdYx1uJk7RgTqb=CA@mail.gmail.com' \
--to=dmishd@gmail.com \
--cc=marka@pobox.com \
--cc=sup-devel@rubyforge.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