From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Subject: Re: Controling modifications and cuting invisible ?
Date: Thu, 22 May 2003 01:12:51 +0200 [thread overview]
Message-ID: <sgdiss3ao7g.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <87d6icj5kk.fsf@noos.fr> (François Fleuret's message of "22 May 2003 00:30:35 +0200")
François Fleuret <francois.fleuret@noos.fr> writes:
[...]
> The first one is: how to control precisely how the buffer can be
> modified ? So far, the only way I found was to clear the keymap with
> make-sparse-keymap, and redefine any single key remaining that can
> change something (i.e. ^j ^d etc.). This seems pretty dumb to me. What
> would be the "stylish" way ?
Make the buffer read only?
(setq buffer-read-only t)
Lute.
--
(spook) => "smuggle anarchy NATO"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")
next prev parent reply other threads:[~2003-05-21 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 22:30 Controling modifications and cuting invisible ? François Fleuret
2003-05-21 23:08 ` Stefan Monnier
2003-05-21 23:12 ` Lute Kamstra [this message]
2003-05-22 16:33 ` Kai Großjohann
2003-05-23 11:23 ` François Fleuret
2003-05-23 11:40 ` Oliver Scholz
2003-05-23 14:58 ` Stefan Monnier
2003-05-23 12:07 ` Oliver Scholz
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=sgdiss3ao7g.fsf@occarina.pna.cwi.nl \
--to=lute.kamstra@cwi.nl \
/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).