unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 48269@debbugs.gnu.org, fgunbin@fastmail.fm
Subject: bug#48269: 27.1: log-edit-generate-changelog-from-diff FAILURE
Date: Fri, 07 May 2021 09:20:52 +0300	[thread overview]
Message-ID: <83im3vcbej.fsf@gnu.org> (raw)
In-Reply-To: <20210507024717.rvxxe7fkbf2iloag@E15-2016.optimum.net> (message from Boruch Baum on Thu, 6 May 2021 22:47:17 -0400)

> Date: Thu, 6 May 2021 22:47:17 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: 48269@debbugs.gnu.org
> 
> Revving up \emacs -Q -nw ...
> Performing now C-x f on a pre-existing elisp file ...

You mean, "C-x C-f", I presume?

> Adding a few blank lines ...
> M-x log-edit-generate-changelog-from-diff
> 
> Yep. Same result as reported.

So the problem seems to be that the doc strings don't say the command
should be invoked from a *vc-log* buffer, is that right?  The user
manual explains that, so next time when the doc string is not enough,
may I suggest to try looking up the command/variable in the manual?

> You don't want me to check the docstrings with "\emacs -Q", do you?

Please don't mock people when they ask clarifying questions about your
bug reports.  It probably means there's some misunderstanding or lack
of information, and clearing that would help use fix the problems you
report.

Thanks.





  reply	other threads:[~2021-05-07  6:20 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 [this message]
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
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=83im3vcbej.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48269@debbugs.gnu.org \
    --cc=boruch_baum@gmx.com \
    --cc=fgunbin@fastmail.fm \
    /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).