unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: Re: The display margin
Date: Sun, 23 Nov 2003 22:53:17 +0000	[thread overview]
Message-ID: <16321.14941.117864.117597@nick.uklinux.net> (raw)
In-Reply-To: <m3d6bjq1k6.fsf@kfs-l.imdomain.dk>


 > I have just checked in fixes to improve event handling for mouse
 > clicks in the marginal areas and on the fringes.  Events now have
 > additional information:
 > 
 >    (WINDOW AREA-OR-POS (X . Y) TIMESTAMP OBJECT POS (COL . ROW))
 > 
 > AREA-OR-POS is not changed as such -- but it may now contain
 > left-fringe and right-fringe.
 > 
 > For clicks in the text area, POS is the same as AREA-OR-POS (the
 > buffer position clicked on).  For clicks in other areas, POS is the
 > buffer position of the first visible glyph on the corresponding row.
 > 
 > As an example, try M-x gdba and click mouse-1 on the left margin or
 > fringe of a source window [it should toggle breakpoint on that line].

Kim,

I like this very much. This means that at some stage the unintuitive tool bar
buttons for gud-break and gud-remove could go. Well for M-x gdba, at least.
Other debuggers in GUD would still need them. I will try to arrange for the
source buffer to always display the margin so that this feature can be used
when there are no prior breakpoints. Also the GDB command 'info line' says
which lines contain code. When I have time, I will try to work this in so
that breakpoints can only be set on those lines.

Thanks,

Nick

  reply	other threads:[~2003-11-23 22:53 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
2003-05-26 23:42   ` Nick Roberts
2003-11-23  2:08     ` Kim F. Storm
2003-11-23 22:53       ` Nick Roberts [this message]
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=16321.14941.117864.117597@nick.uklinux.net \
    --to=nick@nick.uklinux.net \
    --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).