From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 59559@debbugs.gnu.org, drew.adams@oracle.com
Subject: bug#59559: 28.1; `minibuffer-with-setup-hook' with :append
Date: Sat, 21 Jan 2023 20:43:46 +0200 [thread overview]
Message-ID: <83bkmrlod9.fsf@gnu.org> (raw)
In-Reply-To: <87a62b7txl.fsf@web.de> (message from Michael Heerdegen on Sat, 21 Jan 2023 17:07:18 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: drew.adams@oracle.com, 59559@debbugs.gnu.org
> Date: Sat, 21 Jan 2023 17:07:18 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > How about just adding the obvious to the first sentence:
> >
> > Temporarily add function FUN to `minibuffer-setup-hook' while
> > executing BODY.
> >
> > All the rest sounds clear to me, and I find the original text less
> > confusing than your proposed change ("expression that should evaluate
> > to a function"?).
>
> The (valid, IMO) request was about the (:append FUN1) part: is this the
> s-expr to specify, or should the FUN arg evaluate to such a list? Not
> clear from the original docstring.
I don't see why. We say stuff like "argument of the form (FOO BAR)"
in gazillion places, and I see no reason why this one place should be
singled out.
> I'm happy if you or Drew want to suggest a better wording.
I already did.
next prev parent reply other threads:[~2023-01-21 18:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 2:55 bug#59559: 28.1; `minibuffer-with-setup-hook' with :append Drew Adams
2022-11-25 3:07 ` Drew Adams
2023-01-10 17:37 ` Michael Heerdegen
2023-01-10 18:37 ` Drew Adams
2023-01-10 19:34 ` Michael Heerdegen
2023-01-10 19:53 ` Michael Heerdegen
2023-01-10 20:56 ` Drew Adams
2023-01-10 20:45 ` Drew Adams
2023-01-21 14:36 ` Michael Heerdegen
2023-01-21 15:35 ` Eli Zaretskii
2023-01-21 16:07 ` Michael Heerdegen
2023-01-21 18:43 ` Eli Zaretskii [this message]
2023-01-21 18:57 ` Drew Adams
2023-01-21 19:26 ` Eli Zaretskii
2023-01-21 18:51 ` Drew Adams
2023-01-21 19:23 ` Eli Zaretskii
2023-01-21 20:57 ` Drew Adams
2023-01-21 18:41 ` Drew Adams
2023-01-21 19:29 ` Eli Zaretskii
2023-01-21 20:27 ` Michael Heerdegen
2023-01-22 5:58 ` Eli Zaretskii
2023-01-22 22:10 ` Drew Adams
2023-01-22 22:19 ` Drew Adams
2023-01-23 0:15 ` Michael Heerdegen
2023-01-23 3:14 ` Drew Adams
2023-01-23 3:21 ` Drew Adams
2023-01-23 14:11 ` Michael Heerdegen
2023-01-23 16:38 ` Drew Adams
2023-01-23 12:15 ` 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=83bkmrlod9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59559@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=michael_heerdegen@web.de \
/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).