From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: did syntax for setq auto-mode-alist or regexp change with 21.3.1?
Date: Thu, 30 Jun 2005 23:00:43 +0200 [thread overview]
Message-ID: <7eekaj4l1g.fsf@ada2.unipv.it> (raw)
In-Reply-To: 1120154956.527628.38170@f14g2000cwb.googlegroups.com
"Tom" <tmarinus@yahoo.com> writes:
> This worked with emacs 20.7.1 on Linux
>
> (setq auto-mode-alist (cons
> `("makefile\\(\\.aix\\|\\.hp\\|\\.sol\\|\\.linux\\|\\.gcc\\)\\'".makefile-mode)
>
> Any ideas why the first form no longer works?
it is sufficient to add a space around the dot, and use a
forward-single-quote (instead of backtick), resulting in:
'("makefile\\(\\.aix\\|\\.hp\\|\\.sol\\|\\.linux\\|\\.gcc\\)\\'"
. makefile-mode)
here, i added a newline and some more spaces as well -- how many
isn't as important as the presence of at least one. this form
will work for both old and new emacs. that the form w/o spaces
worked at all for old emacs is probably a fluke.
thi
prev parent reply other threads:[~2005-06-30 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 18:09 did syntax for setq auto-mode-alist or regexp change with 21.3.1? Tom
2005-06-30 20:48 ` Kevin Rodgers
2005-06-30 21:00 ` Thien-Thi Nguyen [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=7eekaj4l1g.fsf@ada2.unipv.it \
--to=ttn@glug.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.
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).