Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Tassilo Horn <tsdh@gnu.org>
Cc: ding@gnus.org
Subject: Re: Summary minor mode for Emacs-hacking groups?
Date: Thu, 07 May 2020 12:03:32 -0700	[thread overview]
Message-ID: <875zd7h8jf.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871ro2n6sh.fsf@gnu.org> (Tassilo Horn's message of "Sat, 02 May 2020 09:18:54 +0200")

Tassilo Horn <tsdh@gnu.org> writes:

> Tassilo Horn <tsdh@gnu.org> writes:
>
>> Wouldn't just activating bug-reference-mode in gnus-article-mode with
>>
>>   (setq-local bug-reference-url-format
>>               "https://debbugs.gnu.org/cgi/bugreport.cgi?bug=%s")
>>
>> deal with at least emacs bug numbers (including all GNU package bug
>> reports who also use GNU debbugs)?  Of course, that would just produce
>> clickable links and not Gnus buttons but it is readily available...
>>
>> I'm gonna try that out...
>
> I did so, and it works just fine.  Things like bug#19199 are rendered as
> links and invoking bug-reference-push-button (C-c RET by default) opens
> the debbugs bug page in your browser.  Some adjustments could be made:
>
>   * Tabbing through the article just recognizes Gnus buttons and not
>     those bug-reference links so you have to navigate to them manually.
>
>   * Maybe you'd want to open debbugs bugs using the debbugs emacs
>     package rather than your browser (but this is nothing Gnus-related).

Looks like you've been busy! So number two now works correctly, but
still not number one? I wonder if there's a way to get buttons and links
to be treated the same by Gnus. It would also be useful to have the bug
links be accessible to "w" in the Summary buffer.

Thanks for all the work,
Eric


  parent reply	other threads:[~2020-05-07 19:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 19:06 Eric Abrahamsen
2020-05-01 19:24 ` Andreas Schwab
2020-05-01 19:32   ` Eric Abrahamsen
2020-05-01 22:34 ` Emanuel Berg
2020-05-01 23:31   ` Eric Abrahamsen
2020-05-05  2:44     ` Emanuel Berg
2020-05-02  6:58 ` Tassilo Horn
2020-05-02  7:18   ` Tassilo Horn
2020-05-02 15:15     ` Eric Abrahamsen
2020-05-02 21:21     ` Eric Abrahamsen
2020-05-07 19:03     ` Eric Abrahamsen [this message]
2020-05-11 16:09       ` Tassilo Horn
2020-05-14  0:28         ` Eric Abrahamsen

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=875zd7h8jf.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=tsdh@gnu.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.
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 NNTP newsgroup(s).