From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: "If you're still seeing problems, please reopen." [Was: bug#25148:] Date: Tue, 31 Dec 2019 21:32:09 -0800 (PST) Message-ID: <0437774b-b3b5-4a0b-8b54-63fe1a70af05@default> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="67418"; mail-complaints-to="usenet@blaine.gmane.org" Cc: ofv@wanadoo.es, larsi@gnus.org, Dmitry Gutov , Ihor Radchenko , emacs-devel@gnu.org To: Michael Heerdegen , Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 01 06:33:55 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 1imWdm-000HOL-QO for ged-emacs-devel@m.gmane.org; Wed, 01 Jan 2020 06:33:54 +0100 Original-Received: from localhost ([::1]:48582 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imWdl-0003lo-Iu for ged-emacs-devel@m.gmane.org; Wed, 01 Jan 2020 00:33:53 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49947) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imWcG-00034V-5I for emacs-devel@gnu.org; Wed, 01 Jan 2020 00:32:21 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1imWcE-0005Il-5P for emacs-devel@gnu.org; Wed, 01 Jan 2020 00:32:19 -0500 Original-Received: from aserp2120.oracle.com ([141.146.126.78]:56542) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1imWcD-0005Gc-14; Wed, 01 Jan 2020 00:32:18 -0500 Original-Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id 0015VUl0044472; Wed, 1 Jan 2020 05:32:15 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2019-08-05; bh=qX9agefkT0oMgkU9uwTTnf92IG2Jv69vt0L2uXoWxRk=; b=olw1zWD/ZQiJCAjqWesTZp+tt9cPDiSOB9hMP0kTmqf2sJHuiY6SKRDJ1Dv8nlcAq63l C5exZ7xWRHZg8rrRaT96BwHz+lgrbNh950JBPVgFUhwCPfxOTVBwmPvjOas/BP5d/mEo kDiHkQvV9pI1V976jQAi9RFIUliwiY6l+ysldHfBXrTNpyxTqdhn7QJr6jPSRjcpmp5E 7CYTiM7weUHDAA4d3p0GoqhGM7pEsmj66XZe8BcxZU8G3bCCAlgZmxl5PXxFWmbrK5Bd K/V8wdJ71+Lky/VVKdjwpEeDkIV3iRaWTIcHijse3Na07EEgptGvrBpulFRI/770E/yd nw== Original-Received: from userp3030.oracle.com (userp3030.oracle.com [156.151.31.80]) by aserp2120.oracle.com with ESMTP id 2x5y0pk99a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 01 Jan 2020 05:32:14 +0000 Original-Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.27/8.16.0.27) with SMTP id 0015TRCC119450; Wed, 1 Jan 2020 05:32:14 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userp3030.oracle.com with ESMTP id 2x8gj96udj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 01 Jan 2020 05:32:14 +0000 Original-Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 0015WA76020725; Wed, 1 Jan 2020 05:32:10 GMT In-Reply-To: <87woacotw1.fsf@web.de> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4939.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9487 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=18 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2001010049 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9487 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=18 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2001010049 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 141.146.126.78 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:243827 Archived-At: > > What exactly would it be good for users to know? > > When and how can we tell them? >=20 > There is another, related problem (it was already posted to this group > but got no answers): >=20 > M-x report-emacs-bug is not even always a good way to file Emacs bug > reports. For example, the org developers wish that org related bug > reports appear in their own list - org-mode bugs reported to > gnu.emacs.bug get no attention for years. >=20 > This works automatically when you use M-x org-submit-bug-report - but I > didn't find that command, even though I searched for it, because the > name doesn't fit the naming scheme report-.*-bug. Other users will not > even know that some packages may have special commands for bug > reporting. >=20 > And other Emacs packages use even different naming schemes: >=20 > calc-report-bug > reftex-report-bug > eshell-report-bug > gnuplot-bug-report > c-submit-bug-report >=20 > Though several modes are also using the naming similar to > org-submit-bug-report: >=20 > c-submit-bug-report > diredp-send-bug-report > org-edna-submit-bug-report >=20 > Oh, and a happy New Year to all of you! Ditto - Happy new year, to all. --- You ask how a user can find out how to submit a bug report for a given library/package. Good question. It's not so easy - there are several places a user might look for such info. To be helpful, you have to cover a few of them. --- Here's what I do, FWIW: 1. `C-h m' gives the mode doc (many libraries have one or more main modes, major or minor). That help prominently tells you how to submit a bug report. E.g.: Send a Dired+ bug report: 'M-x diredp-send-bug-report' (For my libraries I use "send" as the verb, not "submit" or "report", because you send me an email to report the bug.) 2. For a customize group (many libraries have one), `M-x customize-group' shows a Customize buffer for the group. A title/description of the group is just above the `State' button. Just under the `State' button are some links, one of which is, for my libraries, `Send Bug Report'. That's provided by :link with a `url-link' of "mailto:" with template text that fills out email address, library name, and instructions. 3. Similarly, each global `define-minor-mode' I define has a bug-report email :link. (Not that many people will actually use Customize for the mode, but why not?) 4. I mention the command to send a bug report in the library doc. If I had to guess, I'd guess that users come across the info most often in the doc (which is also on the web) or from `C-h m'. --- It's also possible to add a menu item to the `Help' menu for help on the major mode of a buffer, i.e., for `C-h m'. It might even be good for Emacs to do that systematically.