From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: can a command specify overwrite selection behavior?
Date: Tue, 28 Dec 2010 09:18:27 -0500 [thread overview]
Message-ID: <jwvipyem180.fsf-monnier+inbox@gnu.org> (raw)
In-Reply-To: <E73E0B131BEF4AD7808D65C4F1A1A82F@us.oracle.com> (Drew Adams's message of "Mon, 27 Dec 2010 21:34:49 -0800")
> Arguing that a different approach would have been or would now be
> better could be a legitimate argument.
I prefer it, but both approaches have their advantages, so I have no
intention to claim that one is better than the other.
> It is not legitimate to argue that this is somehow an implementation
> bug, something unexpected or not understood by those who built it the
> way they did.
Neither did I say it was an implementation bug. What I said is that it
is a limitation due to the implementation technique, as opposed to
an explicit goal of the design.
Stefan
prev parent reply other threads:[~2010-12-28 14:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 5:33 can a command specify overwrite selection behavior? Xah Lee
2010-09-01 8:11 ` Xah Lee
2010-12-10 23:37 ` Drew Adams
[not found] ` <mailman.4.1292024249.16140.help-gnu-emacs@gnu.org>
2010-12-12 15:16 ` Xah Lee
2010-12-13 17:16 ` Drew Adams
[not found] ` <mailman.1.1292262212.1009.help-gnu-emacs@gnu.org>
2010-12-22 14:49 ` Xah Lee
2010-12-22 17:12 ` Drew Adams
[not found] ` <mailman.0.1293037975.895.help-gnu-emacs@gnu.org>
2010-12-23 2:33 ` Xah Lee
2010-12-25 0:17 ` Ilya Zakharevich
2010-12-25 17:00 ` Drew Adams
[not found] ` <mailman.8.1293296501.5624.help-gnu-emacs@gnu.org>
2010-12-25 18:54 ` Ilya Zakharevich
2010-12-26 0:32 ` Drew Adams
2010-12-26 2:20 ` Xah Lee
2010-12-26 16:19 ` Drew Adams
2010-12-28 2:46 ` Stefan Monnier
2010-12-28 5:34 ` Drew Adams
2010-12-28 14:18 ` Stefan Monnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvipyem180.fsf-monnier+inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.