From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: James Cloos <cloos@jhcloos.com>
Cc: emacs-devel@gnu.org
Subject: Re: Inhibiting read-only
Date: Wed, 19 Jun 2013 16:25:38 -0400 [thread overview]
Message-ID: <jwv4nct7srr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3k3lp282b.fsf@carbon.jhcloos.org> (James Cloos's message of "Wed, 19 Jun 2013 15:50:43 -0400")
LMI> I'd like to make the eww buffers read-only, but leave text input
LMI> fields editable. (And then do processing of the alterations with
LMI> `insert-behind-hooks' or `after-change-functions'.)
> That sounds like how the Customize buffers work, yes?
Exactly, they set buffer-read-only to nil but then use
a before-change-function to signal an error when trying to modify
a non-text-widget area.
Stefan
next prev parent reply other threads:[~2013-06-19 20:25 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 [this message]
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
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=jwv4nct7srr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cloos@jhcloos.com \
--cc=emacs-devel@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.
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).