From: "Juanma Barranquero" <lekktu@gmail.com>
To: "David Kastrup" <dak@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, Richard Stallman <rms@gnu.org>,
emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; M-( and M-) should not be bound in ESC map
Date: Fri, 11 Apr 2008 00:34:51 +0200 [thread overview]
Message-ID: <f7ccd24b0804101534q4e818eb5ldcb09e499af5bdd7@mail.gmail.com> (raw)
In-Reply-To: <85d4ox1kop.fsf@lola.goethe.zz>
On Thu, Apr 10, 2008 at 11:09 PM, David Kastrup <dak@gnu.org> wrote:
> And those few decisions which
> caused long threads, all in all, tended to be decisions in the need of
> cooking.
Obviously, we disagree in at least two points: the number (you say
"those few decisions", I've got the feeling they have been plenty) and
the final state (you [seem to] think most of them end by reaching a
decision, I think most of them just die out of participant's boredom,
to be reborn a few weeks/months/years later).
But we're out in subjective land. There's no much point discussing this, IMO.
Juanma
next prev parent reply other threads:[~2008-04-10 22:34 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 [this message]
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
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=f7ccd24b0804101534q4e818eb5ldcb09e499af5bdd7@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=acm@muc.de \
--cc=dak@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=rms@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).