From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id qB3SBjOetF91EgAA0tVLHw (envelope-from ) for ; Wed, 18 Nov 2020 04:08:19 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id YGQ0AjOetF8EDwAA1q6Kng (envelope-from ) for ; Wed, 18 Nov 2020 04:08:19 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 16BC99400D3 for ; Wed, 18 Nov 2020 04:08:17 +0000 (UTC) Received: from localhost ([::1]:44126 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfElU-0008Ce-QX for larch@yhetil.org; Tue, 17 Nov 2020 23:08:16 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:44016) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfEj7-0007KO-J3 for emacs-orgmode@gnu.org; Tue, 17 Nov 2020 23:05:49 -0500 Received: from mail-pf1-x42c.google.com ([2607:f8b0:4864:20::42c]:38704) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kfEj4-0002gZ-10 for emacs-orgmode@gnu.org; Tue, 17 Nov 2020 23:05:48 -0500 Received: by mail-pf1-x42c.google.com with SMTP id 10so578466pfp.5 for ; Tue, 17 Nov 2020 20:05:45 -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=QD1GQk9wXXyt3Am0uuJbNu56AKjfEVE99goAOGPBtsU=; b=N86RPcBMLukOGrLavFNRIg2bqykhUG6VIW2Mg0I3hF08+QFmLdlcgpBbq6Uy1uKkcJ R49wLi3LTswf/FeXM8jVbNDzTdvTiY1O3IXLygjspisEvswcZLiA7wW1mIIwuMxQXSBt ikPJchNrahLHFycTWaVD0+vONy8MixikC0rRyij4H5msxxJ21NE7XJk7tgBKhwkR3XM1 3uvupc+e93dAn2/BOvlS202zWBxbxtlfIzLwCDyO9wKHKW8UVWDKutl8J8GzKKzlD/uu P9N6bSV1lqr9lhTUnKdHQIaELUFp2jxQUELs0+tCnevG0b5fIPASL2NJpxj6A0ilveuW 9HjQ== 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=QD1GQk9wXXyt3Am0uuJbNu56AKjfEVE99goAOGPBtsU=; b=cUibtQQj3fTO+xN1m6dLYaJIOFk64D15xzoDa71K1fQNPniM1e8QiYIw1P8VPFdHay STOppVFWd2a1zPZTfYUXoPKuX74LugpdmMFn7LpidK1JI0AbWvyCcWUAnfIUfXenczno UU67HF2I3hq3/KyED4KfHLjhPWrK4I6No0n/1x85ZujfGAksWOc31t1EzAdLBUXwKXaS N8JyNNVwfDstPK5LmxSVlkLsiqzKuWEnvnEizJ6fWeQBrQOuaC5zouNK9wxtaXU8NUel fdUqKR4pDCKnYtoG4Op32+jmhs9PxyASyquqB4EXJ195DGpXq7Crmse+J+E9BtzzV8Hi ToNQ== X-Gm-Message-State: AOAM530ZiLWTlzCurC7fvkCT7sXormVN/SJ1X/y+KsM0Kradvk5A+LuK yQ/fmtiC+HbnyLE+Q2P8F9w= X-Google-Smtp-Source: ABdhPJyM5/cMqDPRPvhTztvovCixS6OnDg603cPYWwB4+HAw87rdBJy2r4Nycc9StErJdIO01k67gQ== X-Received: by 2002:a63:1026:: with SMTP id f38mr6236099pgl.181.1605672343753; Tue, 17 Nov 2020 20:05:43 -0800 (PST) Received: from localhost ([107.155.105.218]) by smtp.gmail.com with ESMTPSA id k21sm21486275pfu.7.2020.11.17.20.05.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Nov 2020 20:05:42 -0800 (PST) From: Ihor Radchenko To: Jean Louis , Boruch Baum Subject: Re: Ignored bugs In-Reply-To: References: <20201117184130.t67oqxhnkw5rwozx@E15-2016.optimum.net> <7ef0ec5a-276e-ace7-5316-e168373295ec@grinta.net> <20201117201554.y5pz2blxiklq673m@E15-2016.optimum.net> <6e794a47-b58f-df7a-7420-e0c74174ac16@grinta.net> <20201117205419.l2mzatdu3fkiwgwt@E15-2016.optimum.net> Date: Wed, 18 Nov 2020 12:04:39 +0800 Message-ID: <871rgrnwdk.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::42c; envelope-from=yantar92@gmail.com; helo=mail-pf1-x42c.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -6 X-Spam_score: -0.7 X-Spam_bar: / X-Spam_report: (-0.7 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Daniele Nicolodi , emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=fail (headers rsa verify failed) header.d=gmail.com header.s=20161025 header.b=N86RPcBM; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: 0.59 X-TUID: xcFVKXgVToxy > As if that it not acceptable I would then propose these functions: > > M-x report-org-bug > > and > > M-x report-emacs-bug This issue has been discussed in the past in this maillist as well as in the emacs-devel: https://orgmode.org/list/87zhfntkwm.fsf@gmail.com/ https://lists.gnu.org/archive/html/emacs-devel/2020-01/msg00011.html I think making the alias you proposed was in Bastein's todo-list, according to that earlier discussion. I guess, there should be no issue accepting relevant patches here (not sure about emacs-devel) if you provide them. Best, Ihor Jean Louis writes: > * Boruch Baum [2020-11-17 23:57]: >> On 2020-11-17 21:27, Daniele Nicolodi wrote: >> > The page that introduces the Emacs bug tracker already reports that this >> > ... >> >> The way emacs users behave isn't to go search and find and read that web >> page. It's to perform M-x report-emacs-bug. For people using a command >> completion program, while they type they see similar alternatives but >> org-mode has gone its own way also in its naming convention for >> report-*-bug so its 'submit' function would not appear (nor c nor ffap). >> >> > mailing list is the right place where to report Org bugs (or feature >> > request, as is the case for at least one of the bug you reported), and >> > not the Emacs bug tracker. >> >> That cuts off anyone not wanting to be a subscriber to your mailing list >> / not wanting all the clutter of all the other conversations and threads >> of your mailing list (I certainly don't). That imposes upon them the >> burden of taking the steps to apply to join the list, confirm, post, and >> then unsubscribe any time they want to make a contribution or submit a >> report. > > As Org is part of Emacs one has to understand Boruch's point as > valid. This means it is part of Emacs and M-x report-emacs-bug should > not be ignored. Managers of the mailing list or Org developers could > make sure to read those bug reports as well. A cron job to grep report > for Org bugs can help there. > > It is quite clear when user finds out about M-x org-submit-bug-report > that such will rather use that. But there is plethora of users who may > not find that option and they will simply reach to Help menu to submit > the bug. > > There is menu item Org and Submit bug report. But user may not find > that menu item as first thing to reach could be simply "Help" and > submit bug report. > >> But, let's try out your suggested method of reporting. Here I am on your >> mailing list, reporting that function org-submit-bug-report should >> either be renamed or aliased to something more consistent with function >> report-emacs-bug, possibly report-emacs-org-bug. > > I may join and say I support that alignment with the other function. > > Personally as Org is part of Emacs, I think it should not have special > bug reporting, but it should rather be in M-x report-emacs-bug > together. I say this as I see that bugs sent to mailing list may not > have its proper action cycles, or proper tracking. But I am unsure of > it. You could develop the function report-emacs-bug to have users say > clearly it is Org bug. > > One could detect if user is invoking report-emacs-bug from Org mode > and only then ask user "Is this Org mode bug?" and provide that little > different instructions for Org mode. > > As if that it not acceptable I would then propose these functions: > > M-x report-org-bug > > and > > M-x report-emacs-bug > > As those are more aligned to each other or just as Boruch said. > >> > You are deliberately ignoring these instructions. What do you expect? >> >> For one, I expect you to not unjustly impute to me motive, and not to >> take that 'what do you expect' attitude with me (or with anyone else). > > It is good to be considerate for reason that we should be, and to > consider good faith especially by those reporting bugs. > > GNU Kind Communications Guidelines > https://www.gnu.org/philosophy/kind-communication.html