From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Is it obvious that string-match syntax matching is affected by the current buffer?
Date: Sun, 13 Mar 2016 20:13:35 -0400 [thread overview]
Message-ID: <jwvy49lapf3.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: loom.20160313T201129-47@post.gmane.org
> When I work with a string then I feel it should not be affected
> by settings of the current buffer, because it's not buffer text
> anymore, but a separate object.
I agree, yet at the same time this begs the question: which setting to
use, if not the current buffer's?
Using some global setting for them instead would be wrong just as often,
if not more.
Stefan
next prev parent reply other threads:[~2016-03-14 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 16:31 Is it obvious that string-match syntax matching is affected by the current buffer? Tom
2016-03-13 16:52 ` Andreas Röhler
2016-03-13 16:56 ` Tom
2016-03-13 17:23 ` Eli Zaretskii
2016-03-13 19:19 ` Tom
2016-03-13 19:36 ` Eli Zaretskii
2016-03-14 0:13 ` Stefan Monnier [this message]
2016-03-14 0:40 ` Drew Adams
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=jwvy49lapf3.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).