From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 48269@debbugs.gnu.org
Subject: bug#48269: 27.1: log-edit-generate-changelog-from-diff FAILURE
Date: Mon, 10 May 2021 01:58:25 +0300 [thread overview]
Message-ID: <m2sg2v5xbi.fsf@fastmail.fm> (raw)
In-Reply-To: <20210509184443.h2jvva6enamdegwd@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 9 May 2021 14:44:43 -0400")
On 09/05/2021 14:44 -0400, Boruch Baum wrote:
>> I was just trying to help you (and all the other Emacs users) to find
>> the information more efficiently next time. No matter how hard we
>> work on it, there will always be deficiencies in Emacs documentation
>> (as in any other software documentation), so relying on the developers
>> to get everything 110% correct is impractical, assuming we all have
>> something else to do other than read the documentation.
>
> The most efficent way seems to me to add the sanity-check to the code.
Frankly, I don't get it: the function we talk about starts with its
mode's prefix (log-edit), is bound to key in that (and derived) modes,
so why would a user just randomly call it in an unprepared buffer? I
mean, the sanity check will be an over-defense, IMO.
Filipp
next prev parent reply other threads:[~2021-05-09 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 23:23 bug#48269: 27.1: log-edit-generate-changelog-from-diff FAILURE Boruch Baum
2021-05-07 1:26 ` Filipp Gunbin
2021-05-07 2:47 ` Boruch Baum
2021-05-07 6:20 ` Eli Zaretskii
2021-05-09 16:55 ` Boruch Baum
2021-05-09 17:15 ` Eli Zaretskii
2021-05-09 18:44 ` Boruch Baum
2021-05-09 18:54 ` Eli Zaretskii
2021-05-09 22:58 ` Filipp Gunbin [this message]
2021-05-10 0:13 ` Boruch Baum
2021-05-11 13:34 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2sg2v5xbi.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=48269@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).