unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: sbaugh@catern.com, 64425-done@debbugs.gnu.org
Subject: bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help
Date: Sat, 08 Jul 2023 12:53:25 +0300	[thread overview]
Message-ID: <83ilaud90q.fsf@gnu.org> (raw)
In-Reply-To: <ierv8exi49j.fsf@janestreet.com> (message from Spencer Baugh on Thu, 06 Jul 2023 09:00:24 -0400)

> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: sbaugh@catern.com,  64425@debbugs.gnu.org
> Date: Thu, 06 Jul 2023 09:00:24 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Spencer Baugh <sbaugh@janestreet.com>
> >> Cc: sbaugh@catern.com,  64425@debbugs.gnu.org
> >> Date: Mon, 03 Jul 2023 10:00:01 -0400
> >> 
> >> >> They are also available in regular buffers after triggering completion-at-point. Should we note that too?
> >> >
> >> > Yes, but in another place, where completion-at-point is documented.
> >> 
> >> OK, fair enough.  Actually, that part is already done, in (info "(emacs)
> >> Symbol Completion").
> >> 
> >> So revised patch updating the minibuffer completion documentation:
> >
> > Thanks, this LGTM, but please don't use 'kbd' in simple.el.  With that
> > change, we can install this, I think.
> 
> Fixed.

Thanks, installed on the master branch, and closing the bug.





  reply	other threads:[~2023-07-08  9:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4beb74b6-6bbc-4e0f-9b95-f95b7edf79b9@email.android.com>
2023-07-03 13:28 ` bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help Eli Zaretskii
2023-07-03 13:31   ` Spencer Baugh
2023-07-03 13:43     ` Eli Zaretskii
2023-07-03 14:00       ` Spencer Baugh
2023-07-06  7:43         ` Eli Zaretskii
2023-07-06 13:00           ` Spencer Baugh
2023-07-08  9:53             ` Eli Zaretskii [this message]
     [not found] <e7933bfa-c6e1-4586-b9f0-8bc3555329ef@email.android.com>
2023-07-08 13:51 ` Eli Zaretskii
2023-07-02 16:31 sbaugh
2023-07-02 17:16 ` Eli Zaretskii
2023-07-02 19:14   ` sbaugh
2023-07-03 11:21     ` Eli Zaretskii
2023-07-03 12:53       ` Spencer Baugh
2023-07-03 13:16         ` 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=83ilaud90q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64425-done@debbugs.gnu.org \
    --cc=sbaugh@catern.com \
    --cc=sbaugh@janestreet.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 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).