[Top][All Lists]

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

Re: "If you're still seeing problems, please reopen." [Was: bug#25148:]

From: Michael Welsh Duggan
Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:]
Date: Thu, 02 Jan 2020 18:45:34 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Michael Heerdegen <address@hidden> writes:

> Eli Zaretskii <address@hidden> writes:
>> How about if we add a bug-reporting-function, to be set by any mode
>> that wants to override the default one (which sends email to debbugs)?
>> Then report-emacs-bug could be modified to detect the modes active in
>> the buffer, and suggest the possible alternatives to the user.  I
>> think adding to our coding conventions a single variable that in most
>> cases doesn't even have to be set will be easier to propagate to the
>> few modes which want their own bug-tracking.  And users will benefit
>> from not having to search high and low for the relevant command.
> Sounds good, yes.  But as you describe it, it doesn't cover those cases
> where people invoke the command from an unrelated buffer (*scratch* or
> so), e.g. because they needed to restart Emacs.  Adding some
> explanations to the initial text in the bug report buffer of the default
> reporting command would thus be good I think.

Another possibility is that at some point in the bug reporting process
Emacs could query as to which mode is having problems.  This could
default to the current major mode (if there is a bug reporting function
specific to that mode) and could contain generic categories such as
"emacs" or "other".  If the selected mode has a specific bug-reporting
function associated with it, that bug-reporting function could be called
instead of the generic function.  As a bonus, even with a generic
bug report, we might get a possibly useful user-selected mode field.

Michael Welsh Duggan

reply via email to

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