From: storm@cua.dk (Kim F. Storm)
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [PATCH] find-file-noselect-1
Date: Fri, 11 Feb 2005 11:30:40 +0100 [thread overview]
Message-ID: <m3sm432xtb.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <16908.32927.36112.410112@farnswood.snap.net.nz> (Nick Roberts's message of "Fri, 11 Feb 2005 22:53:35 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> > I agree with you that we need to have this feature.
> >
> > But can't gdb-ui just bind [left-fringe mouse-1] to a gdb-ui specific
> > command in global-map? That command could check if the buffer is
> > a source file and set breakpoints accordingly (if gdb is running
> > and in a state that allows it to set a breakpoint), and just
> > do mouse-set-point otherwise.
>
> That would be fine with me, but what if later someone else wants to use
> [left-fringe mouse-1] for another purpose?
You got there first :-)
Other modes can bind it in their mode specific local keymap or whatever...
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-02-11 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 20:36 [PATCH] find-file-noselect-1 Nick Roberts
2005-02-11 0:19 ` Miles Bader
2005-02-11 2:49 ` Nick Roberts
2005-02-11 3:03 ` Nick Roberts
2005-02-12 8:38 ` Richard Stallman
2005-02-12 10:30 ` Nick Roberts
2005-02-12 16:50 ` Stefan Monnier
2005-02-13 5:31 ` Nick Roberts
2005-02-13 16:14 ` Stefan Monnier
2005-02-13 12:38 ` Richard Stallman
2005-02-13 20:49 ` Nick Roberts
2005-02-15 6:15 ` Richard Stallman
2005-02-11 3:16 ` Stefan Monnier
2005-02-11 3:19 ` Stefan Monnier
2005-02-11 8:08 ` Nick Roberts
2005-02-11 8:51 ` Kim F. Storm
2005-02-11 9:53 ` Nick Roberts
2005-02-11 10:30 ` Kim F. Storm [this message]
2005-02-11 10:05 ` Miles Bader
2005-02-11 10:29 ` Kim F. Storm
2005-02-11 10:44 ` Nick Roberts
2005-02-11 13:05 ` Kim F. Storm
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=m3sm432xtb.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).