all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lassi Kortela <lassi@lassi.io>
To: Stefan Kangas <stefankangas@gmail.com>, 66660@debbugs.gnu.org
Subject: bug#66660: [PATCH] Fix dns-mode-syntax-table
Date: Sat, 21 Oct 2023 12:31:40 +0300	[thread overview]
Message-ID: <7fe6185c-2dac-7464-1394-0bf4dd3b652f@lassi.io> (raw)
In-Reply-To: <CADwFkm=VmRSJ1soJUoUjEsPG2tYeAjoLx8UHzwo2tr-zykmUqg@mail.gmail.com>

> Could you provide an example of something which is incorrectly
> highlighted, briefly explain what is wrong before your patch, and what
> your patch does?  Thanks again.

Sure. Here is the DNS zone for the domain schemers.org:

https://raw.githubusercontent.com/schemeorg/schemeorg/master/dns/schemers.org.zone

On the following two lines, the text in double quotes was not
highlighted.

@ IN TXT "v=spf1 include:simplelists.com -all"

srfi IN TXT "v=spf1 include:simplelists.com -all"

On the following line, the part "k=rsa was not highlighted, and the
rest of the line ;p=MIGf[...]QAB" starting at the semicolon was
incorrectly highlighted as a comment instead of a string literal.

selector1._domainkey.srfi IN TXT "k=rsa;p=MIGf[...]QAB"

The patch causes the parts in double quotes to be highlighted as string 
literals. Since the part starting at the semicolon is inside a string, 
it is no longer incorrectly highlighted as a comment.

Motion commands such as forward-sexp are likewise fixed.





  reply	other threads:[~2023-10-21  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 16:21 bug#66660: [PATCH] Fix dns-mode-syntax-table Lassi Kortela
2023-10-21  9:15 ` Stefan Kangas
2023-10-21  9:31   ` Lassi Kortela [this message]
2023-10-21  9:41     ` Stefan Kangas
2023-10-21  9:49       ` Lassi Kortela
2023-10-21  9:58         ` Stefan Kangas
2023-10-21 10:15           ` Lassi Kortela
2023-10-21 10:30             ` Stefan Kangas

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=7fe6185c-2dac-7464-1394-0bf4dd3b652f@lassi.io \
    --to=lassi@lassi.io \
    --cc=66660@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    /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.