From: Stephen Berman <stephen.berman@gmx.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 12396@debbugs.gnu.org
Subject: bug#12396: 24.2.50; [PATCH] extend usability of gnus-read-ephemeral-emacs-bug-group
Date: Sun, 09 Sep 2012 21:49:05 +0200 [thread overview]
Message-ID: <878vcjt1se.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <87txv7yqwa.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 09 Sep 2012 20:47:49 +0200")
On Sun, 09 Sep 2012 20:47:49 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> It would be more convenient if the bug number in the current line in
>> the Group buffer were offered as default regardless of where point is
>> in the line.
>
> It makes sense, but it's kinda not the way these function in Emacs
> usually work. `M-x find-file-at-point', `M-x man', etc, all react to
> the thing under point. And that's a very self-evident user interface.
> Put point at the thing you're interested in, and then issue a command.
I think there are significant differences between these three cases.
With ffap, the UI is already announced in the name, and any other
behavior would contradict it. With man, the list of items naming man
pages is large and could always be augmented, i.e., pretty much any word
could be a potential target, so it makes sense to default to the word at
point. But with g-r-e-e-b-g, even though bug numbers are in principle
unbounded, the context for identifying them can be narrowly specified,
as I tried to show; e.g., it won't grab a number in a subject line like
"Bug in forward-sexp starting with revision 340958". In other words,
for g-r-e-e-b-g the typical use case will have a natural default (or
several, as I noted), which it therefore makes sense to use regardless
of where point is. If this doesn't convince you, all I can add is that
I was annoyed enough times by having to navigate to the bug number to
avoid typing it in that I decided to code up a way to avoid having to do
that; having it in Emacs might spare others such annoyance. :-)
Steve Berman
next prev parent reply other threads:[~2012-09-09 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 16:00 bug#12396: 24.2.50; [PATCH] extend usability of gnus-read-ephemeral-emacs-bug-group Stephen Berman
2012-09-09 18:47 ` Lars Ingebrigtsen
2012-09-09 19:49 ` Stephen Berman [this message]
2012-09-10 21:02 ` Stephen Berman
2012-09-11 19:01 ` Juri Linkov
2012-09-11 23:11 ` Stephen Berman
2012-09-12 20:54 ` Juri Linkov
2012-09-13 20:38 ` Stephen Berman
2012-09-13 23:35 ` Juri Linkov
2012-09-14 15:37 ` Stephen Berman
2012-09-14 22:54 ` Juri Linkov
2012-12-25 21:54 ` Lars Ingebrigtsen
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=878vcjt1se.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=12396@debbugs.gnu.org \
--cc=larsi@gnus.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.
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.