From: Stefano Zacchiroli <zack@upsilon.cc>
To: Chong Yidong <cyd@gnu.org>
Cc: Michael Kifer <kifer@cs.stonybrook.edu>, 9146@debbugs.gnu.org
Subject: bug#9146: M-x broken in console mode with viper (always gives: "viper bell"))
Date: Mon, 27 Feb 2012 15:17:41 +0100 [thread overview]
Message-ID: <20120227141741.GB9931@upsilon.cc> (raw)
In-Reply-To: <87d3901kqn.fsf@gnu.org>
On Mon, Feb 27, 2012 at 09:14:40PM +0800, Chong Yidong wrote:
> Stefano Zacchiroli <zack@upsilon.cc> writes:
>
> > That seems to have done the trick for me.
> > Applying the patch M-x works properly again.
>
> Committed to trunk. Thanks for testing.
Great, thank you for the fix!
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences ...... http://upsilon.cc/zack ...... . . o
Debian Project Leader ....... @zack on identi.ca ....... o o o
« the first rule of tautology club is the first rule of tautology club »
next prev parent reply other threads:[~2012-02-27 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 10:45 bug#9146: 24.0.50; M-x broken in console mode with viper (always gives: "viper bell") Stefano Zacchiroli
[not found] ` <handler.9146.B.131133154717743.ack@debbugs.gnu.org>
2011-09-28 7:25 ` bug#9146: Acknowledgement (24.0.50; M-x broken in console mode with viper (always gives: "viper bell")) Stefano Zacchiroli
2011-09-28 16:44 ` bug#9146: 24.0.50; M-x broken in console mode with viper (always gives: "viper bell") Glenn Morris
2011-09-28 16:48 ` Glenn Morris
2011-09-30 8:50 ` Stefano Zacchiroli
2011-09-30 9:14 ` Julien Danjou
2011-11-04 22:43 ` bug#9146: M-x broken in console mode with viper (always gives: "viper bell")) Stefan Monnier
2012-02-27 10:12 ` Chong Yidong
2012-02-27 12:08 ` Stefano Zacchiroli
2012-02-27 13:14 ` Chong Yidong
2012-02-27 14:17 ` Stefano Zacchiroli [this message]
2012-02-28 1:32 ` Michael Kifer
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=20120227141741.GB9931@upsilon.cc \
--to=zack@upsilon.cc \
--cc=9146@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=kifer@cs.stonybrook.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.