From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: TAB for non-editing modes
Date: Sun, 23 Sep 2007 17:33:22 -0700 [thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACGEAICDAA.drew.adams@oracle.com> (raw)
In-Reply-To: <yoij1wcohqh7.fsf@gamma02.me.chalmers.se>
> >> Doing this with kill commands would take away a feature: you can use
> >> them in read-only buffers to copy text to the kill ring. That feature
> >> may not be very useful in read-only buffers, but I am not convinced it
> >> is an improvement to make it entirely unavailable there.
> >
> > Granted. But it could be argued that this "feature" is really a
> > bug that we exploit (because it seems useful) ;-). Because it is
> > inconsistent with normal use (killing) of those commands/keys,
> > it promotes user error and possibly confusion. The user does not
> > even get proper feedback about this "trick" - s?he still gets
> > the read-only error message/reminder, and there is no indication
> > that anything was copied. I don't know if this "feature" is
> > even documented.
>
> Of course it is. There even exists an option to remove the read-only
> error--`kill-read-only-ok'.
Cough; hack.
Why is this better than using the corresponding standard copy commands? What do we gain by this complexity and inconsistency?
next prev parent reply other threads:[~2007-09-24 0:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 1:18 TAB for non-editing modes Dan Nicolaescu
2007-09-22 8:22 ` Lennart Borgman (gmail)
2007-09-25 20:29 ` S-SPC for non-editing modes (was: TAB for non-editing modes) Juri Linkov
2007-09-25 21:14 ` Drew Adams
2007-09-25 21:59 ` S-SPC for non-editing modes Juri Linkov
2007-09-25 22:12 ` Drew Adams
2007-09-25 22:09 ` S-SPC for non-editing modes (was: TAB for non-editing modes) Andreas Schwab
2007-09-22 15:47 ` TAB for non-editing modes Richard Stallman
2007-09-22 16:35 ` Dan Nicolaescu
2007-09-22 19:01 ` Drew Adams
2007-09-22 21:23 ` Lennart Borgman (gmail)
2007-09-22 21:40 ` Drew Adams
2007-09-22 21:51 ` Dan Nicolaescu
2007-09-22 22:16 ` bind commands that change buffer contents to `undefined' when read-only? Drew Adams
2007-09-23 0:37 ` bind commands that change buffer contents to `undefined' whenread-only? Drew Adams
2007-09-23 1:20 ` bind commands that change buffer contents to `undefined'whenread-only? Drew Adams
2007-09-23 1:49 ` Stefan Monnier
2007-09-23 2:18 ` bind commands that change buffer contents to `undefined' when read-only? Drew Adams
2007-09-23 18:16 ` Stefan Monnier
2007-09-23 20:42 ` Drew Adams
2007-09-24 1:25 ` Stefan Monnier
2007-09-24 2:02 ` Drew Adams
2007-09-24 15:24 ` Davis Herring
2007-09-24 16:12 ` Drew Adams
2007-09-24 17:38 ` Davis Herring
2007-09-24 21:49 ` Drew Adams
2007-09-24 18:14 ` Stefan Monnier
2007-09-25 10:44 ` Richard Stallman
2007-09-25 18:00 ` bind commands that change buffer contents to `undefined' whenread-only? Drew Adams
2007-09-24 18:19 ` bind commands that change buffer contents to `undefined' when read-only? Richard Stallman
2007-09-25 14:15 ` Stefan Monnier
2007-09-22 22:44 ` TAB for non-editing modes Drew Adams
2007-09-23 14:48 ` Bastien
2007-09-23 23:59 ` Juri Linkov
2007-09-23 15:05 ` Richard Stallman
2007-09-23 16:43 ` Drew Adams
2007-09-24 0:11 ` Johan Bockgård
2007-09-24 0:33 ` Drew Adams [this message]
2007-09-24 0:46 ` Johan Bockgård
2007-09-23 15:04 ` Richard Stallman
2007-09-24 0:56 ` Dan Nicolaescu
2007-09-24 18:20 ` Richard Stallman
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=BNELLINCGFJLDJIKDGACGEAICDAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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).