From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:] Date: Wed, 01 Jan 2020 17:30:36 +0200 Message-ID: <83zhf7jisj.fsf@gnu.org> References: <20191117113054.49837.qmail@mail.muc.de> <87pnhq7mxg.fsf@gnus.org> <87bltaz9g4.fsf@telefonica.net> <877e3y5r6x.fsf@gnus.org> <0b8f8b31-29aa-1a33-f70d-38bdaeefc6e5@yandex.ru> <87y2we4boo.fsf@gnus.org> <7c8e41f2-23e1-868b-4db9-e4f800675ee2@yandex.ru> <87woacotw1.fsf@web.de> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="221257"; mail-complaints-to="usenet@blaine.gmane.org" Cc: ofv@wanadoo.es, rms@gnu.org, yantar92@gmail.com, emacs-devel@gnu.org, dgutov@yandex.ru, larsi@gnus.org To: Michael Heerdegen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 01 16:31:32 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1imfy4-000vLA-Pw for ged-emacs-devel@m.gmane.org; Wed, 01 Jan 2020 16:31:28 +0100 Original-Received: from localhost ([::1]:59236 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imfy3-00035J-Ne for ged-emacs-devel@m.gmane.org; Wed, 01 Jan 2020 10:31:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46349) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imfxU-0002Zg-2b for emacs-devel@gnu.org; Wed, 01 Jan 2020 10:30:53 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37468) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1imfxS-0001CF-RI; Wed, 01 Jan 2020 10:30:50 -0500 Original-Received: from [176.228.60.248] (port=1200 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1imfx2-0003pD-5o; Wed, 01 Jan 2020 10:30:34 -0500 In-reply-to: <87woacotw1.fsf@web.de> (message from Michael Heerdegen on Wed, 01 Jan 2020 02:19:42 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243836 Archived-At: > From: Michael Heerdegen > Date: Wed, 01 Jan 2020 02:19:42 +0100 > Cc: ofv@wanadoo.es, larsi@gnus.org, emacs-devel@gnu.org, > Ihor Radchenko , Dmitry Gutov > > | I am thinking if it would make sense to develop more standardised > | command name conventions for bug reporting and add them to > | (elisp)Emacs Lisp:Preparing Lisp code for distribution > | > | Then, the built-in emacs packages might be changed to follow those > | conventions and improve discoverability of bug reporting capabilities. > | > | Also, an information that different major modes may have they own bug > | reporting tools might be mentioned in the default template shown in > | report-emacs-bug. > | > | What do you think? > > I think this is a problem that also confuses and discourages users to > make bug reports, so - any opinions? I don't really believe on relying on discoverability in this case. Even if users will discover the various commands, they might not know which one to invoke. 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.