From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25046-done@debbugs.gnu.org
Subject: bug#25046: 26.0.50; Arguments of `ediff-janitor' undocumented
Date: Fri, 02 Dec 2016 13:47:33 +0000 [thread overview]
Message-ID: <CAArVCkR=V4tV3SOQeE=3AWekX8Gtq5bCtbFwRsm_QogZRROqow@mail.gmail.com> (raw)
In-Reply-To: <837f7ioez6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Fr., 2. Dez. 2016 um 10:30 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Sun, 27 Nov 2016 21:30:18 +0100
> >
> > The function `ediff-janitor' has two required arguments, ASK and
> > KEEP-JANITOR, which are not documented in the docstring.
>
> Thanks, fixed on the emacs-25 branch.
>
Thanks, however I'm still not quite sure about the meaning.
"ASK non-nil means ask the user whether to keep each unmodified buffer,
unless KEEP-VARIANTS is non-nil, in which case buffers are killed
unconditionally."
So if ASK = nil, KEEP-VARIANTS = nil: kill buffers, don't ask about any
buffer
ASK = (nil or non-nil), KEEP-VARIANTS = non-nil: don't kill any buffer,
don't ask
ASK = non-nil, KEEP-VARIANTS = nil: ask about each buffer
If that's the case, shouldn't the documentation rather be something like:
"If KEEP-VARIANTS is non-nil, only indirect buffers are killed [what does
that mean for the user?], and ASK is ignored. Otherwise, if ASK is non-nil,
ask the user for each unmodified buffer whether it should be killed.
Otherwise (both ASK and KEEP-VARIANTS) are nil, all unmodified buffers are
killed without confirmation."
WDYT?
[-- Attachment #2: Type: text/html, Size: 1826 bytes --]
next prev parent reply other threads:[~2016-12-02 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 20:30 bug#25046: 26.0.50; Arguments of `ediff-janitor' undocumented Philipp Stephani
2016-12-02 9:30 ` Eli Zaretskii
2016-12-02 13:47 ` Philipp Stephani [this message]
2016-12-02 14:37 ` Eli Zaretskii
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='CAArVCkR=V4tV3SOQeE=3AWekX8Gtq5bCtbFwRsm_QogZRROqow@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=25046-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).