From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: indirect-buffers and text-properties
Date: Thu, 30 Jan 2014 16:33:22 +0100 [thread overview]
Message-ID: <52EA70C2.9080507@easy-emacs.de> (raw)
In-Reply-To: <jwv4n4l7ga7.fsf-monnier+gmane.emacs.help@gnu.org>
Am 30.01.2014 14:27, schrieb Stefan Monnier:
>> So, question, anyone know why the text-properties get shared with
>> indirect-buffers and is it possible to stop?
>
> To change that, you'd have to change the underlying C code.
> Probably a non-trivial change.
>
> My recommendation: stay away from indirect-buffers.
> They are an attractive-nuisance.
>
It might be of interest how org-mode, resp. org-babel handles this.
M-x org-edit-src-code
uses an indirect buffer, but fontifies correctly.
next prev parent reply other threads:[~2014-01-30 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 12:29 indirect-buffers and text-properties Phillip Lord
2014-01-30 13:27 ` Stefan Monnier
2014-01-30 14:13 ` Phillip Lord
2014-01-30 15:03 ` Stefan Monnier
2014-01-30 15:45 ` Phillip Lord
2014-01-30 16:17 ` Stefan Monnier
2014-01-31 9:52 ` Phillip Lord
2014-01-31 13:35 ` Stefan Monnier
2014-01-31 16:12 ` Phillip Lord
2014-01-30 15:33 ` Andreas Röhler [this message]
2014-01-30 15:36 ` Nicolas Richard
2014-01-30 16:43 ` Andreas Röhler
2014-01-31 9:46 ` Phillip Lord
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=52EA70C2.9080507@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--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).