From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: No Wayman Newsgroups: gmane.emacs.bugs Subject: bug#50842: Fwd: bug#50842: 28.0.50; problem with fill-paragraph Date: Wed, 29 Sep 2021 10:48:00 -0400 Message-ID: <871r572xj3.fsf@gmail.com> References: <87zgrw9067.fsf@gmail.com> <87v92k8yce.fsf@gmail.com> <87lf3fdium.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22403"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.0; emacs 28.0.50 Cc: 50842@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 29 17:49:18 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mVbpd-0005d8-T9 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Sep 2021 17:49:17 +0200 Original-Received: from localhost ([::1]:58698 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mVbpb-0002Lw-TR for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Sep 2021 11:49:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53782) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVbpO-0002KV-4J for bug-gnu-emacs@gnu.org; Wed, 29 Sep 2021 11:49:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38390) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mVbpN-0003eU-Ql for bug-gnu-emacs@gnu.org; Wed, 29 Sep 2021 11:49:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mVbpN-0002KL-Ng for bug-gnu-emacs@gnu.org; Wed, 29 Sep 2021 11:49:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: No Wayman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 29 Sep 2021 15:49:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50842 X-GNU-PR-Package: emacs Original-Received: via spool by 50842-submit@debbugs.gnu.org id=B50842.16329305068889 (code B ref 50842); Wed, 29 Sep 2021 15:49:01 +0000 Original-Received: (at 50842) by debbugs.gnu.org; 29 Sep 2021 15:48:26 +0000 Original-Received: from localhost ([127.0.0.1]:49936 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mVbon-0002JJ-Tx for submit@debbugs.gnu.org; Wed, 29 Sep 2021 11:48:26 -0400 Original-Received: from mail-qk1-f172.google.com ([209.85.222.172]:41960) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mVbom-0002J7-Ak for 50842@debbugs.gnu.org; Wed, 29 Sep 2021 11:48:24 -0400 Original-Received: by mail-qk1-f172.google.com with SMTP id m7so2740543qke.8 for <50842@debbugs.gnu.org>; Wed, 29 Sep 2021 08:48:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version; bh=ScJiBcSrpXJLlsSG3IpHkXbyW8G/ms/Spz7lCluboXM=; b=Mn9M8okF2CtIOYaSIaAIKJ4UiO/hz9l6AoFiRENkwxqJLP1XFYra++XE2LAw5JXWrN +mmNj3SWYCcyqJYvSVYTDKcq6KB9gg3Apa2Cy/mQI10nddlo7DEat4PPdJJB/XHWaZ/F NjSHfEwnpltKge0rWX+mLtZObz1Yc6Hke6vCbE3y4SdDrKy3sVdjWZo3Yb8lWG4heRm7 /6NP+0uH9MkIWWUwk7B4wCfcTosCisI38MrAIRJ6bvnT8RhUHjlZWjmD+hKe6jPCOL/s 0Z0m+EE19wQ8ZJ+ejDn2Z6f9Dlg76fwrds5Ow9AjKSP9pWRikITZ/kpEfEv0CLCewGuS G/dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:cc:subject:date :in-reply-to:message-id:mime-version; bh=ScJiBcSrpXJLlsSG3IpHkXbyW8G/ms/Spz7lCluboXM=; b=qcb4Fzuokmn0/ZRrbbQOB78SQyr2qAPzKW0NvYMEraeRHGVuV1bcA0PvlTPCV44Vjk NbyF/JLOeJjI4qJjVawFZSfE2IebatN11KksyqdpBRC7o0WT6AgtYXWUoSwI5FYZ7/9u LSRwLHxXwmpUdtBQ5csZeGgueoreaZXjVmBgF/jZKP/bmd4huzAkJFBWG+xXhAKPsiUd pQS9KX3lcDb/MX51CDBHt/FPNeBNQFJYhs+EYfsoaR/wctLkQEi9cJufUmSt0VmA+6+f fMP7Vy+BIgxl2FDhK4nV4K/8sjZ5Eq+J2qFu6I/c5U7MDE0XPQYmZQpcloUvsECGgoY4 nGmQ== X-Gm-Message-State: AOAM530f0hYJDT2VnVP2KuVabcR7Sjb2H6EiWeNtchWGpdWamlaHpOMV ViDkBzCidHmQujl163OVYRRI+256C1o= X-Google-Smtp-Source: ABdhPJzlOcrl9aKx5N3l4+eS8qFAL1xEgMXN89Ou1XQT9RhBwtycI+ITzGjOvk3CxgQaN4D/PJlMww== X-Received: by 2002:a37:8287:: with SMTP id e129mr419839qkd.415.1632930498264; Wed, 29 Sep 2021 08:48:18 -0700 (PDT) Original-Received: from arch ([2601:82:c200:166d:afae:ebe6:a0e2:409e]) by smtp.gmail.com with ESMTPSA id b1sm114747qka.34.2021.09.29.08.48.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Sep 2021 08:48:17 -0700 (PDT) In-reply-to: <87lf3fdium.fsf@gnus.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:215861 Archived-At: Lars Ingebrigtsen writes: > No Wayman writes: > >> The basic idea is to provide macros which make declaring a >> reproduction case easier. > > It's an interesting idea, but I think it's unlikely that we'd > get many > people to submit bug reports using something as complicated as > this, > really. I agree that elisp novices probably wouldn't author many reports themselves. However, there's benefit beyond that. We use a similar macro for diagnosing bugs with straight.el and there are users who know enough elisp to write reports. The first thing I do when I get a bug report is encode it via that macro and have the user who reported it run it/share results. That confirms that there is actually a bug and we're on the same page about what is expected/happening. It reduces the time wasted on "Oh yeah, I forgot to mention a step" or "Oh yeah, I forgot to do that step", etc. It's even more beneficial when you have multiple users effected by the same bug. IME, It's a lot more efficient to ask someone "please paste this in your *scratch* buffer, eval, and copy back the results". Once the bug is closed, the body of the macro is often still useful as a regression test, too. Again, just food for thought.