From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@IRO.UMontreal.CA, cloos@jhcloos.com, emacs-devel@gnu.org
Subject: Re: Inhibiting read-only
Date: Thu, 20 Jun 2013 19:58:04 +0200 [thread overview]
Message-ID: <m3ppvg1x77.fsf@stories.gnus.org> (raw)
In-Reply-To: <83wqpooew1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Jun 2013 20:45:02 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> But the read-only buffer doesn't fit your bill, it requires that you
> develop a non-trivial infrastructure we currently lack. Isn't it
> better to use existing features instead?
The "existing way" to do this now is to use `before-change-function',
which is what Customize does. And it sucks.
>> Having to re-apply properties to ensure that we still are read-only
>> after inserting text (modulo stickiness) is pretty annoying.
>
> I don't see the annoyance. Can you elaborate the difficulties you
> envision?
Re-applying text properties after massaging the buffer (from some
command) is an annoyance.
> But marking the entire buffer read-only and then using text properties
> to inhibit that for some portions of the text sounds wrong to me.
> Especially when we already have facilities for making only part of the
> text read-only.
Well, we could have facilities for the opposite very easily. The
commands already look up the `read-only' text property, so all we have
to do is add the proper action for a special value, and Bob should be a
quite close relative soon.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-06-20 17:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 15:49 Inhibiting read-only Lars Magne Ingebrigtsen
2013-06-19 16:06 ` Juanma Barranquero
2013-06-19 16:07 ` Jambunathan K
2013-06-19 16:10 ` Juanma Barranquero
2013-06-19 16:24 ` Jambunathan K
2013-06-19 16:29 ` Lars Magne Ingebrigtsen
2013-06-19 17:17 ` Jambunathan K
2013-06-19 16:30 ` Juanma Barranquero
2013-06-19 16:48 ` Jambunathan K
2013-06-19 16:49 ` Juanma Barranquero
2013-06-19 17:11 ` Lars Magne Ingebrigtsen
2013-06-19 17:16 ` Juanma Barranquero
2013-06-19 19:32 ` Lars Magne Ingebrigtsen
2013-06-19 17:44 ` Jambunathan K
2013-06-19 19:50 ` James Cloos
2013-06-19 20:16 ` Lars Magne Ingebrigtsen
2013-06-19 21:29 ` James Cloos
2013-06-19 20:25 ` Stefan Monnier
2013-06-20 8:44 ` Lars Magne Ingebrigtsen
2013-06-20 9:11 ` Andreas Schwab
2013-06-20 9:16 ` Lars Magne Ingebrigtsen
2013-06-20 15:56 ` Eli Zaretskii
2013-06-20 15:59 ` Lars Magne Ingebrigtsen
2013-06-20 17:04 ` Eli Zaretskii
2013-06-20 17:09 ` Lars Magne Ingebrigtsen
2013-06-20 17:45 ` Eli Zaretskii
2013-06-20 17:58 ` Lars Magne Ingebrigtsen [this message]
2013-06-20 18:18 ` Eli Zaretskii
2013-06-21 6:33 ` Stephen J. Turnbull
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=m3ppvg1x77.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=cloos@jhcloos.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).