unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Spencer Baugh via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74772@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#74772: [PATCH] Consistently add wildcards for completion-pcm-leading-wildcard
Date: Tue, 10 Dec 2024 14:14:15 -0500	[thread overview]
Message-ID: <ier5xnr4ago.fsf@janestreet.com> (raw)
In-Reply-To: <86zfl39xaj.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Dec 2024 21:02:12 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>
>> Date: Tue, 10 Dec 2024 12:48:23 -0500
>> From:  Spencer Baugh via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>>  (defcustom completion-pcm-leading-wildcard nil
>> -  "If non-nil, partial-completion completes as if there's a leading wildcard.
>> +  "If non-nil, partial-completion adds a leading wildcard for each word.
>
> The modified wording is misleading, because it says something that
> doesn't really happen (as the rest of the doc string reveals).

Okay, how about:

If non-nil, PCM completes as if there's a wildcard before each word.





  reply	other threads:[~2024-12-10 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 17:48 bug#74772: [PATCH] Consistently add wildcards for completion-pcm-leading-wildcard Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-10 19:02 ` Eli Zaretskii
2024-12-10 19:14   ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-10 19:40     ` Eli Zaretskii
2024-12-10 20:05       ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=ier5xnr4ago.fsf@janestreet.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74772@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).