From: Shynur Xie <one.last.kiss@outlook.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: "64351@debbugs.gnu.org" <64351@debbugs.gnu.org>
Subject: bug#64351: probabe bug associated with “completion-regexp-list”
Date: Fri, 30 Jun 2023 18:45:04 +0000 [thread overview]
Message-ID: <PH0PR11MB7470DC8F7966FAFAE0B8DCD7D72AA@PH0PR11MB7470.namprd11.prod.outlook.com> (raw)
In-Reply-To: <jwvttuodcpb.fsf-monnier+emacs@gnu.org>
> Shynur> Evaluate this:
> Shynur> (setq completion-regexp-list '("^[^-]"))
> Stefan> Bad idea.
I have to say that it is not a bad idea to write this _meaningless_
and _short_ expression. I just want to find a short enough expression
to show the issue. If I post a _long_ code snippet and say “Hey,
there’s a bug”, nobody wants to see it. :-)
next prev parent reply other threads:[~2023-06-30 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 18:53 bug#64351: probabe bug associated with “completion-regexp-list” Shynur Xie
2023-06-30 6:21 ` Eli Zaretskii
2023-06-30 12:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 13:15 ` Eli Zaretskii
2023-06-30 14:17 ` Shynur Xie
2023-06-30 14:27 ` Andreas Schwab
2023-06-30 15:23 ` Shynur Xie
2023-06-30 18:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 18:45 ` Shynur Xie [this message]
2023-06-30 19:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 19:36 ` Shynur Xie
2023-06-30 23:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 19:52 ` Shynur Xie
2023-06-30 19:08 ` Eli Zaretskii
2023-07-01 14:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02 6:18 ` Eli Zaretskii
2023-07-01 8:21 ` 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=PH0PR11MB7470DC8F7966FAFAE0B8DCD7D72AA@PH0PR11MB7470.namprd11.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=64351@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).