From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: indirect-buffers and text-properties
Date: Thu, 30 Jan 2014 14:13:11 +0000 [thread overview]
Message-ID: <8761p1r214.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <jwv4n4l7ga7.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Thu, 30 Jan 2014 08:27:11 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 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.
That was my impression. Ah, well, unfortunate.
> My recommendation: stay away from indirect-buffers.
> They are an attractive-nuisance.
Really? I've started using them because they enable me to have the point
in two places at once; for example, in the pre-amble and the body of a
latex documented. Of course, you can do this with two windows, but this
is too sensitive to window configuration; if you remove one of the
windows, then you lose the position of point (in favour of the still
visible window). Indirect buffers seem to be a nice solution for this.
Even as it stands, having the same content in two different modes seems
very powerful; instead of using one of the various multi-mode options, I
was thinking of having a single document in two side-by-side windows,
one for changing the code (in one mode) and one for changing the
comments (in another).
Phil
next prev parent reply other threads:[~2014-01-30 14:13 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761p1r214.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.