From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 57250@debbugs.gnu.org
Subject: bug#57250: emacs-lisp-mode not highlighting single characters `k' in comments
Date: Tue, 16 Aug 2022 19:17:14 +0000 [thread overview]
Message-ID: <XEBR3zfoWjlWvOqV7Ks5_Y2Zg7sYBZq4MvMmZ-GoXhZGX0t94Fy2gyysliVipEToFmx8is5S_QMt4onMhaZ56YMdHIKMCm2ol13vRLqCFDw=@proton.me> (raw)
In-Reply-To: <CADwFkm=8HsBkoeFJ6TDnBtUPR3nTyG7Vt5XV4hCNpCOyxreVog@mail.gmail.com>
------- Original Message -------
On Tuesday, August 16th, 2022 at 7:11 PM, Stefan Kangas <stefankangas@gmail.com> wrote:
> uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" bug-gnu-emacs@gnu.org writes:
>
> > But if the character sequence within tick ` and a single quote ' is a single
> > character, the character does not get highlighted.
> >
> > Example:
> >
> > ;; Insert `k' for words with initial values.
> >
> > The character k does not get highlighted.
>
>
> That's because k here is more likely to be a key than a Lisp symbol.
>
> So I think this is expected.
What is the reason for the highlight for more than a single character?
next prev parent reply other threads:[~2022-08-16 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 18:57 bug#57250: emacs-lisp-mode not highlighting single characters `k' in comments uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 19:11 ` Stefan Kangas
2022-08-16 19:17 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-16 19:23 ` Drew Adams
2022-08-16 20:31 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-17 11:16 ` Lars Ingebrigtsen
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='XEBR3zfoWjlWvOqV7Ks5_Y2Zg7sYBZq4MvMmZ-GoXhZGX0t94Fy2gyysliVipEToFmx8is5S_QMt4onMhaZ56YMdHIKMCm2ol13vRLqCFDw=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=57250@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
--cc=uzibalqa@proton.me \
/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.