From: David Engster <deng@randomsample.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Harald Maier <harald@maierh.de>, 2375@emacsbugs.donarmstrong.com
Subject: bug#2375: 23.0.90; ^ in gnus summary buffer does not work in the nextstep build
Date: Thu, 19 Feb 2009 13:35:17 +0100 [thread overview]
Message-ID: <m2ocwy7gfu.fsf@engster.org> (raw)
In-Reply-To: <jwv8wo3uwzn.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Wed, 18 Feb 2009 18:51:01 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I think the bug is in the definition of ns-unput-working-text (or in
> the way ns-unput-working-text and ns-unput-working-text (both events
> and functions) interact).
>
> Not sure why ns-working-overlay was nil in your case, so either
> ns-unput-working-text should be careful to handle the case where that
> variable is nil, or some other code should make sure that it can't be
> nil when we reach ns-unput-working-text.
It seems this is a bug in ns-insert-working-text, and it's already
mentioned there in a FIXME comment:
;; FIXME: if buffer is read-only, don't try to insert anything
;; and if text is bound to a command, execute that instead (Bug#1453)
The Gnus group and summary buffers are read only, so what we're dealing
here seems to be a duplicate of Bug #1453.
-David
next prev parent reply other threads:[~2009-02-19 12:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 18:27 bug#2375: 23.0.90; ^ in gnus summary buffer does not work in the nextstep build Harald Maier
2009-02-18 21:15 ` David Engster
2009-02-18 23:51 ` Stefan Monnier
2009-02-19 12:35 ` David Engster [this message]
2009-02-19 18:29 ` Stefan Monnier
2009-02-20 3:46 ` Harald Maier
2009-02-20 13:03 ` David Engster
2009-02-20 15:18 ` Stefan Monnier
2009-02-20 15:41 ` David Engster
2009-02-20 21:14 ` Stefan Monnier
2009-02-21 0:45 ` David Engster
2009-02-21 4:56 ` Harald Maier
2009-02-21 6:38 ` YAMAMOTO Mitsuharu
2009-02-21 9:30 ` Harald Maier
2009-02-22 1:39 ` YAMAMOTO Mitsuharu
2009-02-24 5:00 ` Harald Maier
2009-02-24 5:09 ` YAMAMOTO Mitsuharu
2009-02-25 16:25 ` Stefan Monnier
2009-02-26 0:04 ` YAMAMOTO Mitsuharu
2009-02-26 15:21 ` Stefan Monnier
2009-02-27 0:09 ` YAMAMOTO Mitsuharu
2009-03-09 13:25 ` Stefan Monnier
2009-03-10 0:05 ` YAMAMOTO Mitsuharu
2009-03-10 17:18 ` Stefan Monnier
2015-02-13 7:18 ` Lars Ingebrigtsen
2016-01-21 23:31 ` Alan Third
2009-02-26 16:49 ` David Engster
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ocwy7gfu.fsf@engster.org \
--to=deng@randomsample.de \
--cc=2375@emacsbugs.donarmstrong.com \
--cc=harald@maierh.de \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).