From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Summary minor mode for Emacs-hacking groups?
Date: Fri, 01 May 2020 16:31:24 -0700 [thread overview]
Message-ID: <87d07n8c6r.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <875zdfuvw7.fsf@ebih.ebihd> (Emanuel Berg's message of "Sat, 02 May 2020 00:34:48 +0200")
Emanuel Berg <moasenwood@zoho.eu> writes:
> Eric Abrahamsen wrote:
>
>> I'd like a minor-mode that can be activated in
>> certain Gnus groups, that buttonizes references to
>> Emacs commit hashes, and bug-report numbers.
>
> Does it have to be a minor-mode?
>
> What about a function that parses the `thing-at-point'
> and acts accordingly? Because the commit hashes and
> bug-report numbers look a certain uniform way, right,
> and can thus be recognized and acted upon, DWIM style?
Right, a function that is only run when the minor-mode is turned on :)
The minor mode is just because the behavior would be specific to one's
local Emacs installation. I'm subscribed to other groups where commit
hashes are referenced, entirely unrelated to Emacs, and this function
would do the wrong thing there.
>> Has anyone seen or made anything like this?
>
> I always thought Emacs would benefit from more
> interconnectivity - which could be automated, generated
> on the fly, and opted-in with an option variable so not
> to enrage conservative users. (Or DWIM as above.) The
> docstrings, the source code, the manuals, the info
> pages including their sources, the man page(s), the web
> archives and other resources, the [M]ELPA packs, it
> should all be interconnected IMO to all extents
> that's reasonable.
I'm into it in principle, but not really sure what "interconnected"
means here!
next prev parent reply other threads:[~2020-05-01 23:32 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 [this message]
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
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=87d07n8c6r.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@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.
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).