From: "Stefan Monnier" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu>
Subject: Re: Controling modifications and cuting invisible ?
Date: 23 May 2003 10:58:06 -0400 [thread overview]
Message-ID: <5lk7chaewx.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: 87u1blc3fr.fsf@noos.fr
>>>>> "FF" == François Fleuret <francois.fleuret@noos.fr> writes:
> It seems that what people usually do to control how the buffer cna be
> altered (after a quick look at gnus, vm, rmail etc.) consists in
> remaping all key one by one ...
You got the relation going in the wrong way: they do the rebinding because
the default ones don't work anyway (because they made the buffer
read-only), so they replace them with something more useful.
Stefan
next prev parent reply other threads:[~2003-05-23 14:58 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
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 [this message]
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=5lk7chaewx.fsf@rum.cs.yale.edu \
--to=monnier+gnu.emacs.help/news/@flint.cs.yale.edu \
/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).