From: Karl Fogel <kfogel@floss.red-bean.com>
Cc: Juri Linkov <juri@jurta.org>, emacs-devel@gnu.org
Subject: Re: isearch-yank-char
Date: 27 Apr 2004 17:49:30 -0500 [thread overview]
Message-ID: <87n04x9gud.fsf@floss.red-bean.com> (raw)
In-Reply-To: <x5y8oh7o6c.fsf@lola.goethe.zz>
I don't think a 'conservative-mode' is the direction to go. Adding
more choices is not helpful. Conservative-mode would be an endless
source of future decision avoidance. For any given new feature or
binding, someone would say "Well, we can't figure out what to do, so
let's add the feature, but disable it in conservative-mode." Is that
really what we want?
Anyone who knows enough about Emacs to know to look for and/or tweak a
hypothetical conservative-mode, knows enough to simply adjust their
isearch bindings directly. The target audience for conservative mode
would not be helped in reality, because they'd probably never even
know the mode existed.
We should either do the new isearch bindings or not do them, instead
of growing Yet Another Choice Mechanism in Emacs.
-Karl
next prev parent reply other threads:[~2004-04-27 22:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 4:42 isearch-yank-char Juri Linkov
2004-04-25 23:03 ` isearch-yank-char Karl Fogel
2004-04-25 23:17 ` isearch-yank-char Karl Fogel
2004-04-26 6:15 ` isearch-yank-char Juri Linkov
2004-04-26 14:10 ` isearch-yank-char Richard Stallman
2004-04-26 22:42 ` isearch-yank-char Stefan Monnier
2004-04-26 23:03 ` isearch-yank-char Miles Bader
2004-04-26 22:48 ` isearch-yank-char Karl Fogel
2004-04-27 8:09 ` isearch-yank-char Juri Linkov
2004-04-27 9:11 ` isearch-yank-char Juri Linkov
2004-04-27 9:41 ` isearch-yank-char David Kastrup
2004-04-27 22:49 ` Karl Fogel [this message]
2004-04-28 5:04 ` isearch-yank-char Juri Linkov
2004-04-29 22:08 ` isearch-yank-char Karl Fogel
2004-04-30 4:48 ` isearch-yank-char Juri Linkov
2004-04-29 22:53 ` isearch-yank-char Karl Fogel
2004-04-30 8:27 ` isearch-yank-char Juri Linkov
2004-04-30 11:23 ` isearch-yank-char Romain Francoise
2004-04-30 13:47 ` isearch-yank-char Karl Fogel
2004-04-30 20:55 ` isearch-yank-char Juri Linkov
2004-04-30 17:34 ` isearch-yank-char Karl Fogel
2004-05-01 0:15 ` isearch-yank-char Juri Linkov
2004-04-30 18:57 ` isearch-yank-char Karl Fogel
2004-05-01 1:04 ` isearch-yank-char Juri Linkov
2004-05-01 20:02 ` isearch-yank-char Kim F. Storm
2004-05-02 11:32 ` isearch-yank-char Juri Linkov
2004-05-03 12:40 ` isearch-yank-char Robert J. Chassell
2004-05-02 11:19 ` isearch-yank-char Richard Stallman
2004-05-03 19:24 ` isearch-yank-char Karl Fogel
2004-05-04 20:08 ` isearch-yank-char Richard Stallman
2004-04-30 8:31 ` isearch-yank-char Alan Mackenzie
2004-04-30 9:52 ` isearch-yank-char Juri Linkov
2004-04-30 10:12 ` isearch-yank-char Miles Bader
2004-04-30 13:58 ` isearch-yank-char Karl Fogel
2004-04-27 9:36 ` isearch-yank-char Kim F. Storm
2004-04-28 5:02 ` isearch-yank-char Juri Linkov
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=87n04x9gud.fsf@floss.red-bean.com \
--to=kfogel@floss.red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=kfogel@red-bean.com \
/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).