guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs and URLs in Git commit messages


From: Bengt Richter
Subject: Re: Emacs and URLs in Git commit messages
Date: Thu, 4 Feb 2021 20:12:57 +0100
User-agent: Mutt/1.10.1 (2018-07-13)

Hi Chris,

On +2021-02-04 00:38:18 -0800, Chris Marusich wrote:
> Hi,
> 
> Many Guix commits look like this:
> 
>   commit f9978346e73359ac1d8b88c9ed874edc7225582b
>   Author: Ludovic Courtès <ludo@gnu.org>
>   Date:   Fri Dec 18 18:10:04 2020 +0100
> 
>       avahi: Remove poll timeout when possible.
> 
>       Fixes <https://issues.guix.gnu.org/45314>.
> 
>       * guix/avahi.scm (avahi-browse-service-thread): Change timeout default 
> value
>       to false when no "stop-loop?" procedure is passed. Adapt 
> "iterate-simple-poll"
>       call accordingly.
> 
>       Signed-off-by: Mathieu Othacehe <othacehe@gnu.org>
> 
> Regarding the URL, do people just type it all out, including the opening
> and closing brackets (<>)?  Or is there an Emacs command that does it
> for you?  I've briefly looked on the Internet, but this is the kind of
> thing that seems difficult to search for.
>
I am not sure I understand your context or goal in searching ;/

I.e., what did you briefly look for on the internet?
Did you search for an instance of "<https://issues.guix.gnu.org/45314>"
hoping to find discussion of it elsehere than at the URL itself?

What were you referring to with the "this" in
"...this is the kind of thing that seems difficult to search for." ?

If you were looking for alternate site discussion of bug#45314, duckduckgo
seems to respond better without the '#' and narrowed by a last search term
specifying the year, like
    duckduckgo "bug 45314" 2020
(don't leave out the quotes, and don't put the year inside them)

NB: there are lots of bug trackers out there, so you will probably
want to Ctl-f to ask your browser to walk through all the 45314's just by 
hitting Enter
after that (firefox example).

Not so many hits for 2021 yet, so I can show the result: (2 irrelevant hits :)
--8<---------------cut here---------------start------------->8---
DuckDuckGo
[...]
FreeNAS - Bug #45314
[Search domain redmine.ixsystems.com/issues/45314.pdf] 
https://redmine.ixsystems.com/issues/45314.pdf
FreeNAS - Bug #45314 Add the ability to set the password on first login if user 
left password blank during installation 09/07/2018 07:54 AM - Bonnie Follweiler
Possible IPad/1.7 bug - Unity Forum
[Search domain forum.unity.com/threads/possible-ipad-1-7-bug.45314/] 
https://forum.unity.com/threads/possible-ipad-1-7-bug.45314/
Unity ID. A Unity ID allows you to buy and/or subscribe to Unity products and 
services, shop in the Asset Store and participate in the Unity community.

No more results found for "bug 45314" 2021.
[...]
--8<---------------cut here---------------end--------------->8---

If your context is in emacs editing a git commit, and you just want an easy 
command to insert
a line like
    Fixes <https://issues.guix.gnu.org/45314>.
... I'm sure you can handle that yourself if you want to, hence my confusion 
about what you were up to ;)

But maybe you are lazy like me, and wanted to see what was available. For me, 
that brings up the question
of what form of solution would be most helpful to the most people if I offered 
one. E.g., I could

1. point you to the others' elisp solutions,
2. offer a bash script that formats the line based on clipboard-captured number 
(e.g., using xclip or wl-paste)
   which you can easily invoke from emacs by "Esc 1 Esc ! bash-script"
3. offer a guile script to do the same
4. offer a bash script that will compile and link a C program (source and 
commands all in script) that will do the same,
   assuming you have a usual x86_64 tool chain at hand, or
5. write it in some other interesting language (rash? :)

I am not sure having the solution be dependent on emacs' (or any limiting 
entity's) internals
is the most generally useful, but it's something I think about.

I'd be interested in what you all think, though maybe it ought to be a new 
thread ;)

> -- 
> Chris
--
Regards,
Bengt Richter



reply via email to

[Prev in Thread] Current Thread [Next in Thread]