all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 57250@debbugs.gnu.org
Subject: bug#57250: emacs-lisp-mode not highlighting single characters `k' in comments
Date: Tue, 16 Aug 2022 18:57:36 +0000	[thread overview]
Message-ID: <--US8agB7fi34DerSNWvKWbwIMvb88DEFplpFaTyzeOTM82fSgcZ6skhy2cs4o2XI63RFSfbJ-ATOBqM5NknTVU5GY0BiJHCN4Lr2lDLiMM=@proton.me> (raw)

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

With emacs-lisp-mode make a comment that includes character sequences enclosed
by tick ` and a single quote ' .

The character sequence within gets highlighted with a different colour than the
usual typeface for comments.

Example:

;; Insert `cog', `col', `com', `con', `cor', `coun', `cum'.

The character sequences cog, col, com, con, cor, coun, and cum get highlighted

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.

[-- Attachment #2: Type: text/html, Size: 3446 bytes --]

             reply	other threads:[~2022-08-16 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 18:57 uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-16 19:11 ` bug#57250: emacs-lisp-mode not highlighting single characters `k' in comments Stefan Kangas
2022-08-16 19:17   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='--US8agB7fi34DerSNWvKWbwIMvb88DEFplpFaTyzeOTM82fSgcZ6skhy2cs4o2XI63RFSfbJ-ATOBqM5NknTVU5GY0BiJHCN4Lr2lDLiMM=@proton.me' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57250@debbugs.gnu.org \
    --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.