unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Ryde <user42_kevin@yahoo.com.au>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 18117@debbugs.gnu.org
Subject: bug#18117: 24.3; tex-mode.el tex-font-lock-verb docstring backslash
Date: Mon, 28 Jul 2014 16:20:43 +1000	[thread overview]
Message-ID: <87egx6ovgk.fsf@blah.blah> (raw)
In-Reply-To: <87ppgrt4f3.fsf@igel.home> (Andreas Schwab's message of "Sun, 27 Jul 2014 13:41:20 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:
>
> There is no need for \= though, since \v isn't special to
> substitute-command-keys.

Would it be prudent to protect against potential new kinds of \
expansions?  Or anything new would not be alphabeticals?

(I pondered even a checkdoc.el test which could ask for no backslashing
except the defined key seq etc forms.  Leaving room for new kinds of
expansions in the future could be good, but maybe they would never be
alnums.)





      reply	other threads:[~2014-07-28  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 10:54 bug#18117: 24.3; tex-mode.el tex-font-lock-verb docstring backslash Kevin Ryde
2014-07-27 11:41 ` Andreas Schwab
2014-07-28  6:20   ` Kevin Ryde [this message]

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=87egx6ovgk.fsf@blah.blah \
    --to=user42_kevin@yahoo.com.au \
    --cc=18117@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).