From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:] Date: Wed, 01 Jan 2020 23:45:15 +0800 Message-ID: <87png3tc38.fsf@localhost> 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> <83zhf7jisj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="15402"; mail-complaints-to="usenet@blaine.gmane.org" Cc: ofv@wanadoo.es, larsi@gnus.org, dgutov@yandex.ru, rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii , Michael Heerdegen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 01 16:47:48 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 1imgDq-0003q0-Rg for ged-emacs-devel@m.gmane.org; Wed, 01 Jan 2020 16:47:46 +0100 Original-Received: from localhost ([::1]:59368 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imgDp-0000uI-NP for ged-emacs-devel@m.gmane.org; Wed, 01 Jan 2020 10:47:45 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47232) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imgDg-0000r8-QZ for emacs-devel@gnu.org; Wed, 01 Jan 2020 10:47:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1imgDf-00034V-Ef for emacs-devel@gnu.org; Wed, 01 Jan 2020 10:47:36 -0500 Original-Received: from mail-yb1-xb44.google.com ([2607:f8b0:4864:20::b44]:43400) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1imgDa-0002n4-Tn; Wed, 01 Jan 2020 10:47:31 -0500 Original-Received: by mail-yb1-xb44.google.com with SMTP id v24so16346064ybd.10; Wed, 01 Jan 2020 07:47:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=lyyxzDwpZHlw1di0tUTASXP3QnGZH6FvsRcRRErBlKg=; b=O1+xMi6J+jzW/OvBx3m/jWgxajIbNGLE/KuMNiZyz40tnvh5EC61LJ9IPIl47eI9TC XjLCayayItLnPLfj9Nq7+3qbERp0FxAeS5vPP5hHgmcIjjTKUEhANEy+kNSYC/Rj7Ju5 HzTifqB+CwEZAcunGEomKYLZrdsjd5AEJIEqH5HQUnnMUzmJ45EE2CVu3QMaib05k3Xv Rb2PnuXX0gn+dR4IZVoBoBFrJbIBO68HTSJEtU3+a+UHHIgFm7oMSYele0bZPNsqi9SK 0wpdL7nuk1hoiWSBofYg8h2cb/gUDwvaZEWrIQ5Q/td+tzuTDYWya5uHQq7mRfDbzDa7 EpEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=lyyxzDwpZHlw1di0tUTASXP3QnGZH6FvsRcRRErBlKg=; b=Igfbq2/gaGRFBmzYxaDzxqcl4l8DO/ZyEFn3wPDuw07PCdIjkBSUvYTuaZKmecPw19 ncNrJyceRy6dUdjUzy6qEwR+vPfVQ3YFW05TseV7VcSwCaKTw6BJsTA1nN9RybSFXYjw Nx2esGHcxLmXLnHcj+r68vfwEM18PdOvThkOX5i8hQpJFtSXdhAFfmCQ98fuzBJeSkab 7ez0yShH8ErU37EO6GR4/xrtjhQhM4A9xHrPJsSMuiDPnOJ364boHdyID/Ij/Y6N5Snj WoDeoHHefcS9SVL6MaVoCGm9M9Hk0QAjROxH6hkWjrT1ul+8SYOeZXSmHvWrZ/gccdvc oYAw== X-Gm-Message-State: APjAAAUCEZPCurqi1U/LX1V431Vl9LVh4D1u4pcCG2YxWclg+yiu1jc4 ajuUOV7ZSGQy6WrqTOvM7ksHrIBozuQ= X-Google-Smtp-Source: APXvYqyXGqjt6Fo1DINFactyg4ux2zOWIG0tr3mvuVnj9she+OSkaYPDYvyu9SQdYzWKpyILVtnSWw== X-Received: by 2002:a25:ca10:: with SMTP id a16mr44213232ybg.280.1577893649696; Wed, 01 Jan 2020 07:47:29 -0800 (PST) Original-Received: from localhost ([5.226.137.4]) by smtp.gmail.com with ESMTPSA id u136sm20646203ywf.101.2020.01.01.07.47.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Jan 2020 07:47:29 -0800 (PST) In-Reply-To: <83zhf7jisj.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::b44 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:243838 Archived-At: > 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. This sounds reasonable. Eli Zaretskii writes: >> 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. -- Ihor Radchenko, PhD, Center for Advancing Materials Performance from the Nanoscale (CAMP-nano) State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg