From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: michael_heerdegen@web.de, 59559@debbugs.gnu.org
Subject: bug#59559: 28.1; `minibuffer-with-setup-hook' with :append
Date: Sat, 21 Jan 2023 21:26:28 +0200 [thread overview]
Message-ID: <838rhvlme3.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54885A2330447065D7371AFFF3CA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sat, 21 Jan 2023 18:57:45 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "59559@debbugs.gnu.org" <59559@debbugs.gnu.org>
> Date: Sat, 21 Jan 2023 18:57:45 +0000
>
> > > 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,
>
> Precisely. And we don't say that here.
Yes, we do:
But if FUN is of the form ‘(:append FUN1)’ [...]
> That's _one_
> of the possible forms of the argument sexp. IF
> it has that form (:append F) THEN F is evaluated
> to give the function that's added. OTHERWISE
> the whole sexp arg is evaluated to give the
> function that's added.
>
> This kind of thing is _not_ done in a gazillion
> places.
It's a macro. That's how macros are handled in Emacs.
> > I already did.
>
> I don't think what you suggested changes/adds anything.
> You just changed "FUN" to "function FUN", no?
Yes, because that's the only part that is not crystal clear there.
I don't see what else needs to be discussed here. We should close
this bug.
next prev parent reply other threads:[~2023-01-21 19:26 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
2023-01-21 18:57 ` Drew Adams
2023-01-21 19:26 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rhvlme3.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 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.