From: benoit.pierre@gmail.com (Benoît PIERRE)
Subject: [sup-talk] [PATCH run-mailcap 2/2] Use BufferManager.shell_out to call run-mailcap instead of system.
Date: Sat, 15 Aug 2009 00:37:21 +0200 [thread overview]
Message-ID: <1250289386-sup-7331@localdomain> (raw)
In-Reply-To: <1250281039-sup-2788@masanjin.net>
Excerpts from William Morgan's message of Fri Aug 14 22:17:38 +0200 2009:
> Reformatted excerpts from Beno?t PIERRE's message of 2009-08-11:
> > This ensure ncurses state is correctly restored upon command completion.
>
> Both patches applies to branch run-mailcap-fixes, merged into next.
Great!
One problem though, I tested next, and 3478e400ae31b459b2875cc226796a6d4bba11f9
(rewrap getch in select, handle sigwinch manually) introduced a regression: I
get some 'key not handled' errors after run-mail has been called when sup is
getting back control if I press for example an arrow... ;(
Arrows become usable again after I press a "normal" key (like 'a').
Cheers,
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?
next prev parent reply other threads:[~2009-08-14 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 15:23 [sup-talk] [PATCH] run-mailcap fix Benoît PIERRE
2009-08-11 20:28 ` William Morgan
2009-08-11 22:09 ` [sup-talk] [PATCH run-mailcap 1/2] Don't redirect stderr to /dev/null when calling run-mailcap Benoît PIERRE
2009-08-11 22:09 ` [sup-talk] [PATCH run-mailcap 2/2] Use BufferManager.shell_out to call run-mailcap instead of system Benoît PIERRE
2009-08-14 20:17 ` William Morgan
2009-08-14 22:37 ` Benoît PIERRE [this message]
2009-08-14 23:08 ` [sup-talk] [PATCH] Restore keypad mode after we force ncurses to refresh the whole screen Benoît PIERRE
2009-08-16 22:00 ` William Morgan
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=1250289386-sup-7331@localdomain \
--to=benoit.pierre@gmail.com \
/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