From: martin rudalics <rudalics@gmx.at>
To: dev.null@caeruleus.net
Cc: help-gnu-emacs@gnu.org
Subject: Re: file/local variables (and auctex?)
Date: Thu, 12 Apr 2007 10:34:21 +0200 [thread overview]
Message-ID: <461DEF0D.3020104@gmx.at> (raw)
> I actually got this very error when copying the lines above to a file
> and opening it.
Indeed - I was confused because the OP didn't mention it the first time.
It's due to the "$" in
(let ((suffix
(concat
(regexp-quote (buffer-substring (point)
(line-end-position)))
"$"))
and I stand corrected. Maybe we should write
(let ((suffix
(concat
(regexp-quote (buffer-substring (point)
(line-end-position)))
"[ \t]*$"))
instead.
next reply other threads:[~2007-04-12 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 8:34 martin rudalics [this message]
[not found] <mailman.1938.1176270970.7795.help-gnu-emacs@gnu.org>
2007-04-11 16:55 ` file/local variables (and auctex?) Ralf Angeli
-- strict thread matches above, loose matches on Subject: below --
2007-04-11 5:53 martin rudalics
2007-04-10 10:35 thorne
2007-04-10 17:33 ` Ralf Angeli
2007-04-11 0:40 ` thorne
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=461DEF0D.3020104@gmx.at \
--to=rudalics@gmx.at \
--cc=dev.null@caeruleus.net \
--cc=help-gnu-emacs@gnu.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).