From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: isearch-yank-char
Date: Tue, 27 Apr 2004 11:09:52 +0300 [thread overview]
Message-ID: <87ad0xvo33.fsf@mail.jurta.org> (raw)
In-Reply-To: <877jw2cq4f.fsf@floss.red-bean.com> (Karl Fogel's message of "26 Apr 2004 17:48:32 -0500")
Karl Fogel <kfogel@floss.red-bean.com> writes:
> Miles Bader <miles@gnu.org> writes:
>> It's a shame, because it would be nice to use more "normal" bindings in
>> isearch to do "isearchey variants", but it's probably necessary to be pretty
>> conservative.
>
> In this case, I wonder if we're not being overly conservative.
Here is an idea: to create a special mode, say, conservative-mode,
where default values and key bindings will never change from version
to version. Users upset by constant changes will set it once and for
all in own .emacs and will not worry about further changes. Users who
don't set this mode (as well as novices who have no preferences) will
be ready for changes, and Emacs development will not be restricted by
care for backward compatibility anymore. So everyone will be happy.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-04-27 8:09 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 ` Juri Linkov [this message]
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 ` isearch-yank-char Karl Fogel
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=87ad0xvo33.fsf@mail.jurta.org \
--to=juri@jurta.org \
--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).