From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org, daniel@brockman.se, "Kim F. Storm" <storm@cua.dk>
Subject: Re: `overlay-arrow-position' should be automatically buffer-local
Date: Thu, 20 Oct 2005 10:02:51 +1300 [thread overview]
Message-ID: <17238.46203.678461.245113@kahikatea.snap.net.nz> (raw)
In-Reply-To: <871x2hck3a.fsf@cut.bc.hsia.telus.net>
> In principle, there is only one overlay-arrow-position variable,
> and since its value is a marker, its value includes the buffer
> in which it occurs.
>
> This is how e.g. gdb can easily move the overlay arrow between buffers
> -- just modify the global variable.
>
> gdb could use a *gud* buffer local variable. That way multiple
> instances of gud wouldn't steal the arrow from eachother.
Its not about multiple instances of GUD. The overlay arrow is displayed in
the _source_ buffer, not the GUD buffer. As execution proceeds it can move
from file to file and hence, buffer to buffer i.e it would have the same
problem as Edebug. Incidentally, GUD does have its own overlay arrow now and
it seems to work fine.
Nick
next prev parent reply other threads:[~2005-10-19 21:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 2:37 `overlay-arrow-position' should be automatically buffer-local Daniel Brockman
2005-10-19 2:48 ` Ryan Yeske
2005-10-19 4:22 ` Daniel Brockman
2005-10-19 20:16 ` Richard M. Stallman
2005-10-19 6:13 ` Nick Roberts
2005-10-19 6:34 ` Ryan Yeske
2005-10-19 7:33 ` Nick Roberts
2005-10-19 20:15 ` Richard M. Stallman
2005-10-19 8:44 ` Kim F. Storm
2005-10-19 20:44 ` Ryan Yeske
2005-10-19 21:02 ` Nick Roberts [this message]
2005-10-19 21:29 ` Kim F. Storm
2005-10-20 1:43 ` Miles Bader
2005-10-20 4:45 ` Nick Roberts
2005-11-10 4:48 ` Miles Bader
2005-11-10 6:51 ` Multiple debugging sessions [was Re: `overlay-arrow-position' should be automatically buffer-local] Nick Roberts
2005-11-10 8:39 ` Multiple debugging sessions Kim F. Storm
2005-11-10 11:06 ` Miles Bader
2005-11-10 12:34 ` Kim F. Storm
2005-11-10 12:43 ` Miles Bader
2005-11-10 11:19 ` Multiple debugging sessions [was Re: `overlay-arrow-position' should be automatically buffer-local] Miles Bader
2005-11-10 18:08 ` Multiple debugging sessions Stefan Monnier
2005-11-11 1:00 ` Nick Roberts
2005-11-11 4:34 ` Stefan Monnier
2005-11-10 19:12 ` Nick Roberts
2005-11-10 22:10 ` Andreas Schwab
2005-11-12 3:38 ` Richard M. Stallman
2005-11-12 4:56 ` Nick Roberts
2005-11-12 5:53 ` Miles Bader
2005-11-12 6:50 ` Eli Zaretskii
2005-11-12 21:23 ` Richard M. Stallman
2005-11-12 22:15 ` Nick Roberts
2005-11-11 0:31 ` Miles Bader
2005-11-11 1:03 ` Miles Bader
2005-11-11 9:12 ` Kim F. Storm
2005-11-11 19:34 ` Juri Linkov
2005-11-11 3:50 ` Nick Roberts
2005-11-11 4:36 ` Stefan Monnier
2005-11-11 7:41 ` Richard M. Stallman
2005-11-11 9:22 ` Eli Zaretskii
2005-11-12 3:38 ` Richard M. Stallman
2005-11-11 8:30 ` Kim F. Storm
2005-11-11 9:46 ` David Kastrup
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=17238.46203.678461.245113@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=daniel@brockman.se \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).