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: Fri, 31 Jan 2014 16:12:34 +0000 [thread overview]
Message-ID: <87y51wm8p9.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <jwvfvo42s9w.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Fri, 31 Jan 2014 08:35:04 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Having a buffer automatically do this when a new window is displayed
>> might be difficult; I think it would need an awful lot of DWIM
>> semantics, and I am not sure what these would be.
>
> Stashing point when undisplaying a buffer can be done automatically
> without harming anyone. The DWIM semantics would only show up if/when
> the user wants to use one of those stashed points.
>
>> Indeed. I shall look at these solutions before I go further; but
>> fiddling with major modes to make them work together is also
>> a costly exercise.
>
> I know, but that's what needs to happen: someone should take the
> experience of mmm-mode, mumamo, and friends and come up with some set of
> "rules" which major modes should follow so that these things can
> work reliably.
>
> Once that's done, it's only a matter of going around and adapting the
> existing major modes to those rules, and providing some infrastructure
> so that new major modes can follow those rules easily.
I'd agree. I need to get a clear idea of how these modes work. I am not
even sure what "two modes in one buffer" looks like.
Phil
next prev parent reply other threads:[~2014-01-31 16:12 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 [this message]
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
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=87y51wm8p9.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.
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).