unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
Subject: RE: another newbie question -- auto-mode-alist regexp
Date: Mon, 23 Sep 2002 19:34:00 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209231932110.11057-100000@dell> (raw)
In-Reply-To: <Pine.LNX.4.44.0209231925150.11003-100000@dell>

On Mon, 23 Sep 2002, Robert P. J. Day wrote:

> On Mon, 23 Sep 2002, Bingham, Jay wrote:
> 
> > 1. The \\ means make the next character literal.  Two are required
> > because the string is parsed before it is placed in the variable if
> > there are not two then the single \ gets stripped out and the
> > literalness is lost.  So \. becomes just . (which means match any
> > character) while \\. becomes \. (which means find a dot).
> 
> i knew that part.  what i didn't understand was the function of
> the double-escaped sinqle quote: \\'.  what does *that* represent?
> the way it's used suggests something related to end-of-string,
> but doesn't the "$" already serve that purpose?

never mind, i finally found it in the elisp info manual.
apparently, \' matches the empty string, but only at the end
of the buffer or string being matched.

so, AFAICT, it appears to serve the same purpose as a trailing
$ to match end of string.

rday

  reply	other threads:[~2002-09-23 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 22:59 another newbie question -- auto-mode-alist regexp Bingham, Jay
2002-09-23 23:27 ` Robert P. J. Day
2002-09-23 23:34   ` Robert P. J. Day [this message]
     [not found] <mailman.1032823999.4821.help-gnu-emacs@gnu.org>
2002-09-23 23:56 ` Barry Margolin
     [not found] <mailman.1032821006.2883.help-gnu-emacs@gnu.org>
2002-09-23 23:15 ` Michael Slass
2002-09-23 23:17   ` Michael Slass
  -- strict thread matches above, loose matches on Subject: below --
2002-09-23 22:43 Robert P. J. Day

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=Pine.LNX.4.44.0209231932110.11057-100000@dell \
    --to=rpjday@mindspring.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.
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).