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: Fri, 07 May 2021 04:26:29 +0300 [thread overview]
Message-ID: <m2sg2zl4fu.fsf@fastmail.fm> (raw)
In-Reply-To: <20210506232308.cd6dfmj566mbzczz@E15-2016.optimum.net> (Boruch Baum's message of "Thu, 6 May 2021 19:23:08 -0400")
On 06/05/2021 19:23 -0400, Boruch Baum wrote:
> GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24,
> cairo version 1.16.0) of 2021-03-27, modified by Debian
>
> ref: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47784#45
>
> 1] Attempting to run function log-edit-generate-changelog-from-diff
> returns an error message: 'Diff functionality has not been setup.'
>
> 2] The docstring for function log-edit-generate-changelog-from-diff
> gives no indication how to set up 'diff functionality' or otherwise
> guidance on how to use the function.
>
> 3] The source of the error message is function log-edit-show-diff. It,
> too, lacks a useful docstring.
>
> 4] The code in function log-edit-show-diff indicates that the
> configuration is performed via variable log-edit-diff-function.
> However:
>
> 4.1] That variable lacks a docstring.
>
> 4.2] Setting it to a 'reasonable' value of 'ediff returns an error
> (wrong-number-of-arguments (2 . 3) 0)
Give an emacs -Q recipe?
next prev parent reply other threads:[~2021-05-07 1:26 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2sg2zl4fu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.