From: Juri Linkov <juri@jurta.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Christoph Scholtes <cschol2112@googlemail.com>,
Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org
Subject: Re: Fundamental mode vs. special mode
Date: Tue, 25 Oct 2011 07:30:18 +0300 [thread overview]
Message-ID: <8739ehzst9.fsf@mail.jurta.org> (raw)
In-Reply-To: <20111024171725.GA5094@acm.acm> (Alan Mackenzie's message of "Mon, 24 Oct 2011 17:17:25 +0000")
> In any mode, each key-sequence should do one well established thing, not
> performing alternate commands based on read-onlyness. Exceptions should
> be justified individually.
But in read-only buffers, self-inserting characters are useless,
they can't do what they are intended for. So why not allow them
to do more useful things, e.g. `q' to run `quit-window'?
Actually this is what `view-read-only' does when set to non-nil.
I don't propose to change its default value to non-nil now,
but at least it's worth thinking about.
next prev parent reply other threads:[~2011-10-25 4:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 20:13 Fundamental mode vs. special mode Christoph Scholtes
2011-10-23 7:21 ` Chong Yidong
2011-10-23 9:19 ` martin rudalics
2011-10-23 13:28 ` Juri Linkov
2011-10-23 18:59 ` martin rudalics
2011-10-24 5:07 ` Juri Linkov
2011-10-24 16:39 ` Richard Stallman
2011-10-23 13:14 ` Johan Bockgård
2011-10-25 2:38 ` Chong Yidong
2011-10-25 3:51 ` Chong Yidong
2011-10-25 12:30 ` Stefan Monnier
2011-10-25 13:53 ` Juanma Barranquero
2011-10-25 15:11 ` Paul Eggert
2011-10-25 20:02 ` Stefan Monnier
2011-10-25 20:30 ` Alan Mackenzie
2011-10-26 1:11 ` Chong Yidong
2011-10-26 12:11 ` Nix
2011-10-26 11:50 ` Richard Stallman
2011-10-27 2:25 ` Chong Yidong
2011-10-23 14:58 ` Christoph Scholtes
2011-10-24 5:11 ` Juri Linkov
2011-10-24 12:46 ` Stefan Monnier
2011-10-24 17:17 ` Alan Mackenzie
2011-10-25 4:30 ` Juri Linkov [this message]
2011-10-25 20:49 ` Alan Mackenzie
2011-10-26 1:18 ` Chong Yidong
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=8739ehzst9.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=acm@muc.de \
--cc=cschol2112@googlemail.com \
--cc=cyd@stupidchicken.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).