unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Juri Linkov <juri@jurta.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 12396@debbugs.gnu.org
Subject: bug#12396: 24.2.50; [PATCH] extend usability of gnus-read-ephemeral-emacs-bug-group
Date: Fri, 14 Sep 2012 17:37:05 +0200	[thread overview]
Message-ID: <87txv01uqm.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <87392lee3g.fsf@mail.jurta.org> (Juri Linkov's message of "Fri, 14 Sep 2012 02:35:55 +0300")

On Fri, 14 Sep 2012 02:35:55 +0300 Juri Linkov <juri@jurta.org> wrote:

>> When I use it it does grab the bug number, at least in the types of
>> cases I had in mind (however, I didn't think of URLs like this one...).
>> Can you provide a recipe showing the failure?
>
> A recipe is just to put point anywhere in the message body and
> evaluate M-: (gnus-get-emacs-bug-number) RET It doesn't grab a bug
> number in the subject line, but returns nil.  Please clarify where you
> intended point to be to be able to grab a bug number from the subject
> line.

This is a use case I didn't have in mind.  I use the default window
configuration of Gnus, where when you visit a mail or news group, the
frame is split into two windows: one with the Summary buffer and one
with the Article buffer, and the Summary buffer is selected.  Each line
of the Summary buffer contains by default at least the subject line of
an article in the group, and typing SPC or RET opens, in the Article
buffer, the article listed at point in the Summary buffer.  In this
scenario, it suffices for the search space for gnus-get-emacs-bug-number
to be just the current line, that's why it doesn't work in your case.

> Actually there already exist similar functionality
> in `Info-follow-reference'.  If you type in an Info node
> `f TAB' it allows you to select one of the links to other nodes.
> Since bug references are similar to links, you could do the same
> and to collect bug references from the current buffer for completion.
> Of course, the bug reference under point should be prefered over
> all other bug references in the buffer and should be provided as
> the first default value.

This certainly is a better approach for your scenario, though for mine
it's probably too heavy, since there are may well be numerous bug
numbers in the Summary buffer, but when I call
gnus-read-ephemeral-emacs-bug-group, I most likely want to visit the
thread of the bug mentioned in the subject line at point, not that of
another subject line.  I suppose, though, if I did want to go to a bug
thread from a different subject, it would be useful to cycle through the
completions.  Even better would be if the bug numbers in the buffer are
highlighted as you cycle, so you can see their context.

Steve Berman





  reply	other threads:[~2012-09-14 15:37 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
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 [this message]
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

  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=87txv01uqm.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=12396@debbugs.gnu.org \
    --cc=juri@jurta.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 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).