From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: Phil Sainty <psainty@orcon.net.nz>, Eli Zaretskii <eliz@gnu.org>,
50959@debbugs.gnu.org, Richard Stallman <rms@gnu.org>
Subject: bug#50959: [PATCH] Re: bug#50959: 28.0.50; Shorthand symbols are unknown to Emacs
Date: Wed, 06 Oct 2021 15:59:05 -0400 [thread overview]
Message-ID: <jwvsfxe3p3o.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CALDnm53h=UzpbEA8MMd=ds7xZU3-ztDPvy8g2zZtN4ArvQGpNw@mail.gmail.com> ("João Távora"'s message of "Wed, 6 Oct 2021 13:53:10 +0100")
> In this thread, we've described many ways how that can be done.
> C-x o already "pays attention" to them, from day one, but that attention
> is somehow deemed insufficient. So you'll have to be clearer about
> what you're suggesting exactly, i.e., "what happens when".
As an ELisp programmer, I'd want (and expect) that if I can successfully
use `st-bar` and `st-foo` in the current buffer, I will see them in the
possible completions at least when I complete `st-` and ideally in other
cases (e.g. it would be good for completion of `sba` to take `st-bar`
into account if `flex` completion style).
Stefan
next prev parent reply other threads:[~2021-10-06 19:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16338bdc2497fc51c6fb6d54ab370bfb@webmail.orcon.net.nz>
[not found] ` <831r59kyhf.fsf@gnu.org>
[not found] ` <YVNQJF/7tbJYPyXu@ACM>
[not found] ` <834ka4k15m.fsf@gnu.org>
[not found] ` <YVNnjl9OTy3xCxGI@ACM>
[not found] ` <83y27gijmz.fsf@gnu.org>
[not found] ` <a63044a034174dc3c6432d06f9f5e448@webmail.orcon.net.nz>
[not found] ` <8335pmgnjy.fsf@gnu.org>
[not found] ` <604da2cb10ac61f2b8b89a02c89056be@webmail.orcon.net.nz>
[not found] ` <83a6jtff87.fsf@gnu.org>
[not found] ` <5ac7a31cf2959c31c262a3377c736a5a@webmail.orcon.net.nz>
[not found] ` <83ilygew7p.fsf@gnu.org>
[not found] ` <c021a0357644e1659882cc49138eab7e@webmail.orcon.net.nz>
[not found] ` <83fstjdiwl.fsf@gnu.org>
[not found] ` <f2196bb4bf4e70c33d2418cca87b629d@webmail.orcon.net.nz>
[not found] ` <837devdcz0.fsf@gnu.org>
2021-10-02 9:20 ` bug#50959: 28.0.50; Shorthand symbols are unknown to Emacs Phil Sainty
2021-10-02 10:15 ` Eli Zaretskii
2021-10-02 11:02 ` João Távora
2021-10-02 11:09 ` Eli Zaretskii
2021-10-02 11:14 ` João Távora
2021-10-02 11:54 ` João Távora
2021-10-02 12:29 ` Eli Zaretskii
2021-10-02 14:02 ` João Távora
2021-10-02 14:20 ` Eli Zaretskii
2021-10-02 14:43 ` João Távora
2021-10-02 14:56 ` Eli Zaretskii
2021-10-02 15:22 ` João Távora
2021-10-02 15:53 ` Eli Zaretskii
2021-10-02 17:46 ` João Távora
2021-10-02 17:58 ` Eli Zaretskii
2021-10-02 18:03 ` João Távora
2021-10-02 18:28 ` Eli Zaretskii
2021-10-04 0:14 ` Richard Stallman
2021-10-04 0:14 ` Richard Stallman
2021-10-04 0:14 ` Richard Stallman
2021-10-04 11:55 ` Eli Zaretskii
2021-10-06 10:45 ` bug#50959: [PATCH] " João Távora
2021-10-06 12:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-06 12:34 ` João Távora
2021-10-06 12:50 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-06 12:53 ` João Távora
2021-10-06 19:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-10-06 20:19 ` João Távora
2021-10-10 10:46 ` João Távora
2021-10-10 11:08 ` Eli Zaretskii
2021-10-10 13:39 ` João Távora
2021-10-10 14:23 ` Eli Zaretskii
2021-10-04 0:14 ` Richard Stallman
2021-10-02 11:53 ` Phil Sainty
2021-10-02 12:10 ` Eli Zaretskii
2021-10-02 12:37 ` Phil Sainty
2021-10-02 14:17 ` João Távora
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=jwvsfxe3p3o.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=50959@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=psainty@orcon.net.nz \
--cc=rms@gnu.org \
/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).