unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: The display margin
Date: Sun, 25 May 2003 12:36:01 -0400	[thread overview]
Message-ID: <200305251636.h4PGa1ll021935@rum.cs.yale.edu> (raw)
In-Reply-To: 16080.60869.212521.952911@nick.uklinux.net

> 
> Following Kim's changes, I thought it might be timely to ask a question
> about the display margin.
> 
> When a breakpoint is set, using M-x gdba as debugger, an icon is placed in the
> margin. The toolbar can be used to do this but the cursor must be placed on the
> appropriate line beforehand. I would like to be able to do this directly with a
> binding like:
> 
> (define-key gud-minor-mode-map [left-margin mouse-1] 'gud-break)
> 
> This does work but currently only if cursor is placed on the appropriate line
> beforehand as with the toolbar.
> 
> Q: Could this binding be made to work, so that the breakpoint is set where
> the click is made in the margin, regardless of the location of the cursor?

You might try something like:

	(defun gud-break (&optional event)
	  "Set break point."
	  (interactive (list last-input-event))
	  ;; Go to wherever the event happened.
	  (if event (ignore-errors (mouse-set-point event)))
	  ...)

I haven't tried it, tho.  Also you might need to use separate functions
for gud-break-from-toolbar than gud-break-from-margin.


	Stefan

  reply	other threads:[~2003-05-25 16:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 16:22 The display margin Nick Roberts
2003-05-25 16:36 ` Stefan Monnier [this message]
2003-05-26 23:42   ` Nick Roberts
2003-11-23  2:08     ` Kim F. Storm
2003-11-23 22:53       ` Nick Roberts
2003-11-23 23:12         ` David Kastrup
2003-11-24  9:52           ` Kim F. Storm
2003-11-24 15:33             ` Kim F. Storm
2003-11-27 23:08           ` Kim F. Storm
2003-11-27 22:30             ` David Kastrup
2003-11-27 23:17               ` Stefan Monnier
2003-11-28 11:09               ` Kim F. Storm
2003-11-28 10:53                 ` David Kastrup
2003-11-28 14:23                   ` Thien-Thi Nguyen
2003-11-28 16:02                     ` David Kastrup
2003-11-28 17:01                       ` Thien-Thi Nguyen
2003-11-29  3:15                   ` Kim F. Storm
2003-11-29 11:37                     ` David Kastrup
2003-12-01 10:15                       ` Kim F. Storm
2003-12-01 13:08                         ` David Kastrup
2003-12-28  1:43                           ` Kim F. Storm
2003-12-29 11:54                             ` Richard Stallman
2003-11-24  0:09         ` Kim F. Storm
2003-11-25 21:11           ` Nick Roberts
2003-11-25 22:42             ` Kim F. Storm
  -- strict thread matches above, loose matches on Subject: below --
2003-11-28 12:47 David PONCE

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=200305251636.h4PGa1ll021935@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --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 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).