From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>, "'Andreas Schwab'" <schwab@suse.de>
Cc: emacs-pretest-bug@gnu.org
Subject: RE: 23.0.60; M-( and M-) should not be bound in ESC map
Date: Thu, 10 Apr 2008 09:18:41 -0700 [thread overview]
Message-ID: <008d01c89b26$8aacebb0$c2b22382@us.oracle.com> (raw)
In-Reply-To: <E1JjwJ0-0001WK-Q3@fencepost.gnu.org>
> > This is is not a good idea. `insert-parentheses' and
> > `move-past-close-and-reindent' should be bound only for
> > programming modes for which they actually make sense.
>
> Inserting pairs of parentheses makes sense pretty much everywhere.
>
> Yes. And error messages that a beginner doesn't totally understand
> can happen in many ways in Emacs. I think this change is too much
> just to eliminate a few cases of them.
>
> Leaving well enough alone seems best to me.
Even leaving aside the opaque error messages and the waste of useful global
keys, this makes no more sense for non-programming modes than would
`blink-matching-paren' or `show-paren-mode'. Should we add those everywhere, as
well?
And we have `insert-pair' as well. If inserting matched parens is so appropriate
for text mode and all other modes, then surely the same must be true for {}, <>,
[], "", '', and `'. The same logic says we should bind `insert-pair'. Matching
"" is at least as important as matching ().
Don't argue only to support personal habits. If your argument makes sense, then
it makes sense also for `insert-pair', `blink-matching-paren', and
`show-paren-mode'.
It's no accident that this is defined in lisp.el. It's appropriate for
programming modes with nested parens.
> People are proposing lots of changes in long-settled aspects of Emacs,
> and I think this is a bad habit. Each such proposal leads to a long
> discussion, which takes up lots of people's time. And usually it
> doesn't achieve anything.
You're opening a general discussion not specific to this bug report.
Just because a decision was made long ago does not mean that it is the right
decision now or even that it was the right decision then.
I filed a bug report. The discussion is yours. Do as you like about the report.
next prev parent reply other threads:[~2008-04-10 16:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 21:09 23.0.60; M-( and M-) should not be bound in ESC map Drew Adams
2008-04-09 21:32 ` Andreas Schwab
2008-04-09 22:15 ` Drew Adams
2008-04-10 6:33 ` David Hansen
2008-04-10 9:20 ` Reiner Steib
2008-04-10 8:31 ` Andreas Schwab
2008-04-10 12:55 ` Richard Stallman
2008-04-10 13:45 ` Paul R
2008-04-10 15:49 ` Alan Mackenzie
2008-04-10 15:45 ` Juanma Barranquero
2008-04-10 16:24 ` Alan Mackenzie
2008-04-10 16:15 ` Juanma Barranquero
2008-04-10 21:09 ` David Kastrup
2008-04-10 22:34 ` Juanma Barranquero
2008-04-11 2:23 ` Glenn Morris
2008-04-11 5:03 ` Thomas Lord
2008-04-11 8:03 ` tomas
2008-04-12 0:11 ` Richard Stallman
2008-04-12 1:13 ` Thomas Lord
2008-04-12 5:49 ` David Kastrup
2008-04-12 7:31 ` Alan Mackenzie
2008-04-12 14:03 ` Thomas Lord
2008-04-12 20:07 ` David Kastrup
2008-04-12 21:24 ` Thomas Lord
2008-04-12 20:34 ` Stephen J. Turnbull
2008-04-11 8:41 ` Paul R
2008-04-11 9:40 ` Juanma Barranquero
2008-04-10 17:10 ` Thomas Lord
2008-04-10 17:10 ` Paul R
2008-04-10 19:21 ` Stephen J. Turnbull
2008-04-12 0:11 ` Richard Stallman
2008-04-10 16:18 ` Drew Adams [this message]
2008-04-12 0:09 ` Richard Stallman
2008-04-12 0:09 ` Richard Stallman
2008-04-12 8:40 ` Nit-picking (was: 23.0.60; M-( and M-) should not be bound in ESC map) Eli Zaretskii
2008-04-12 9:35 ` Nit-picking Alan Mackenzie
2008-04-12 10:30 ` Nit-picking Eli Zaretskii
2008-04-12 11:46 ` Being constructive [Was: Nit-picking] Alan Mackenzie
2008-04-12 13:17 ` Eli Zaretskii
2008-04-12 14:14 ` Jason Rumney
2008-04-12 16:51 ` Eli Zaretskii
2008-04-12 17:16 ` Eli Zaretskii
2008-04-12 21:38 ` Mike Mattie
2008-04-12 15:06 ` 23.0.60; M-( and M-) should not be bound in ESC map Drew Adams
2008-04-13 1:58 ` 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='008d01c89b26$8aacebb0$c2b22382@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@suse.de \
/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).