GNU bug report logs - #72735
31.0.50; [PATCH] Make more bug-reference variables customizeable

Previous Next

Full log

View this message in rfc822 format

From: Tassilo Horn <tsdh <at> gnu.org>
To: Björn Bidar <bjorn.bidar <at> thaodan.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 72735 <at> debbugs.gnu.org
Subject: bug#72735: 31.0.50; [PATCH] Make more bug-reference variables customizeable
Date: Thu, 13 Feb 2025 17:05:10 +0100

Björn Bidar <bjorn.bidar <at> thaodan.de> writes:

Hi Björn,

>> No, bug-reference should work out-of-the-box for every project
>> checked out of the forges in bug-reference-forge-alist.  Well, unless
>> you've set bug-reference-url-format globally which would turn off the
>> auto-setup.
>
> I get that point however not all or none, depending on one's usecase,
> might use forges to track bugs.

Sure, that's where .dir-locals.el or the three variables come into play.

>>> Or is the purpose of bug-reference mode GNU specific and not
>>> intended to be used for anything but GNU?
>>
>> As said, it works out-of-the-box for Github, several Gitlab
>> instances, codeberg, framagit, salsa.debian.org, and sr.ht.
>
> I know these where the where a customize variable works the easiest
> similar to Forge's forge-alist.

Sorry, cannot parse this sentence.

> Would it make sense to include common instances of FOSS projects such
> as for example Freedesktop, KDE and GNOME in to the
> bug-reference-forge-alist by default?

Yes, absolutely.

> I will try to send some patches in a few days.

As said, I'm positive about the three variables
bug-reference-setup-from-*-alist becoming defcustoms.  But for any other
defcustomization, especially those where additional "default" variables
need to be introduced, I don't think it's worth it.

Bye,
Tassilo

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.