all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Binding a command to the down-event of a toolbar button
Date: Thu, 06 Apr 2006 11:37:27 -0400	[thread overview]
Message-ID: <E1FRWY3-0006yi-Id@fencepost.gnu.org> (raw)
In-Reply-To: <e129jh$eju$1@sea.gmane.org> (message from M Jared Finder on Wed,  05 Apr 2006 22:40:01 -0700)

    I feel like you are evading my questions.  The original post I replied 
    to was about down events, not drag events.  I brought up drag events as 
    a similar extension that would be useful in addition.

We were discussing one subject and you brought up another.  I am
keeping these discussions separate, which is the only way I can deal
with them properly.  Please stop mixing them up.

    Why are you against adding the necessary code to allow alternate mouse 
    keys, distinguishing between down and up events, and drag events to be 
    added?  I can think of multiple reasons why you *might* not want to add 
    these events:

    * It'd take too much time and be too complicated to implement.
    * It'd be difficult to integrate into the existing code base.
    * I don't like it; it's not a proven UI style.

All of them.  I don't say it would be "too complicated to implement",
but it would be a little complicated.  I don't say it would be too
difficult to integrate, but it would make things more complex.
The first question is, "do we really need this"?

    * We're trying to get to a release of Emacs 22.

That's not a factor, because if we do this, it will certainly be after
the release.

  reply	other threads:[~2006-04-06 15:37 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26  5:10 Binding a command to the down-event of a toolbar button Stefan Monnier
2006-03-28 19:33 ` Richard Stallman
2006-03-30  9:56   ` Mathias Dahl
2006-03-30 22:39     ` Stefan Monnier
2006-03-30 23:03       ` Drew Adams
2006-03-31  7:58         ` Eli Zaretskii
2006-03-31 20:20           ` Richard Stallman
2006-04-01 11:43             ` Eli Zaretskii
2006-03-31 17:28         ` Richard Stallman
2006-03-31 18:35           ` Drew Adams
2006-04-01 11:45             ` Eli Zaretskii
2006-04-01 16:21               ` Drew Adams
2006-04-02 20:38                 ` Richard Stallman
2006-04-01 13:46             ` Richard Stallman
2006-04-01  3:12           ` M Jared Finder
2006-04-01 20:28             ` Richard Stallman
2006-04-01 20:58               ` M Jared Finder
2006-04-03  1:09                 ` Richard Stallman
2006-04-03  4:14                   ` M Jared Finder
2006-04-03 18:24                     ` Richard Stallman
2006-04-04  2:13                       ` M Jared Finder
2006-04-04 19:57                         ` Richard Stallman
2006-04-05  6:04                           ` M Jared Finder
2006-04-05 19:06                             ` Richard Stallman
2006-04-06  5:40                               ` M Jared Finder
2006-04-06 15:37                                 ` Richard Stallman [this message]
2006-03-31 10:18       ` Jason Rumney
2006-03-31 11:01         ` David Kastrup
2006-03-31 14:34         ` Stefan Monnier
2006-04-01 13:45           ` Richard Stallman
2006-04-01 16:27             ` Stefan Monnier
2006-04-01 13:45         ` Richard Stallman
2006-04-01 19:01           ` Jason Rumney
2006-04-02 20:38             ` Richard Stallman
2006-04-02 21:29               ` Jason Rumney
2006-04-03  3:24                 ` Richard Stallman
2006-03-31 17:28     ` Richard Stallman
2006-04-01  0:55       ` Kevin Rodgers
2006-04-01  1:12         ` Robert J. Chassell
2006-04-01  3:59         ` Stefan Monnier
2006-04-01 20:28           ` Richard Stallman
2006-04-03  2:01             ` Stefan Monnier
2006-04-03 13:51               ` Richard Stallman
2006-04-03 18:24                 ` Richard Stallman
2006-04-01 20:28         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1FRWY3-0006yi-Id@fencepost.gnu.org \
    --to=rms@gnu.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 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.