From: Jonas Bernoulli via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 67390@debbugs.gnu.org
Cc: "Joseph Turner" <joseph@ushin.org>,
"Adam Porter" <adam@alphapapa.net>,
"João Távora" <joaotavora@gmail.com>
Subject: bug#67390: 28; shorthands-font-lock-shorthands assumes shorthand uses same separator
Date: Wed, 22 Nov 2023 23:18:18 +0100 [thread overview]
Message-ID: <87a5r5ph3p.fsf@bernoul.li> (raw)
Hello,
`shorthands-font-lock-shorthands' assumes that the shorthand uses the
same separator as the real symbol name, e.g., "s-" instead of "long-".
This causes an additional character to be highlighted when an
alternative separator is used, e.g., when using "s/" instead of "long-".
`shorthands--mismatch-from-end' returns the length of the common suffix,
of the shorthand and the long name.
(shorthands--mismatch-from-end "s-tail" "long-tail") => 5
"s-" is highlighted in this case.
Since `shorthands-font-lock-shorthands' also wants to highlight the
separator, "-" in this case, it corrects this off-by-one, but when
different separators are in use, this causes an additional character
to be highlighted
(shorthands--mismatch-from-end "s/tail" "long-tail") => 4
"s/t" is highlighted in this case.
Could we add support for using an alternative separator in shorthands?
IMO it is okay to use another separator for *shorthand* prefixes. They
won't show up in M-x completion candidates, for example. Shorthands are
confined to the file where they are being used, and I think authors
should be free to use whatever prefix they fancy.
Cheers,
Jonas
next reply other threads:[~2023-11-22 22:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 22:18 Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-23 12:57 ` bug#67390: 28; shorthands-font-lock-shorthands assumes shorthand uses same separator João Távora
2023-11-24 21:51 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 0:03 ` João Távora
2023-11-25 3:26 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 16:01 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 22:42 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-26 13:52 ` João Távora
2023-11-26 20:35 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-26 22:02 ` João Távora
2023-11-27 3:48 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-27 12:10 ` Eli Zaretskii
2023-11-29 8:21 ` João Távora
2023-11-29 9:12 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-29 13:56 ` João Távora
2023-11-29 13:30 ` João Távora
2023-11-29 23:27 ` João Távora
2023-11-30 14:16 ` João Távora
2023-11-30 15:23 ` Eli Zaretskii
2023-11-30 15:29 ` João Távora
2023-12-09 18:50 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-03 7:10 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-03 14:50 ` João Távora
2024-02-03 19:43 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-03 22:25 ` João Távora
2024-02-03 23:48 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-21 22:05 ` Joseph Turner 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5r5ph3p.fsf@bernoul.li \
--to=bug-gnu-emacs@gnu.org \
--cc=67390@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=joaotavora@gmail.com \
--cc=jonas@bernoul.li \
--cc=joseph@ushin.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 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.