> BTW, in case nobody's noticed the current gud/gdba routinely gets
> completely confused by multiple debugging sessions already...
It's come up at least twice before. I rarely debug two programs at the same
time and when I do, I can do it with two instances of Emacs. For those that
need multi
2005/10/20, Ryan Yeske <[EMAIL PROTECTED]>:
> gdb could use a *gud* buffer local variable. That way multiple
> instances of gud wouldn't steal the arrow from eachother.
BTW, in case nobody's noticed the current gud/gdba routinely gets
completely confused by multiple debugging sessions already...
Ryan Yeske <[EMAIL PROTECTED]> writes:
>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 modif
>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.
>
> g
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* buf
Since the restriction seems to have been lifted, I think we
should remove the paragraph that Ryan quoted from the manual
and make the variable automatically become buffer-local.
It isn't worth bothering with, given overlay-arrow-variable-list.
I recently noticed when adding an overlay arrow to rcirc that making
it `overlay-arrow-position' buffer local *does* work (you can get an
arrow in multiple buffers), even though (elisp)Overlay Arrow says:
I will fix the manual.
___
Emacs-de
Daniel Brockman <[EMAIL PROTECTED]> writes:
> I believe the variable `overlay-arrow-position' should
> automatically become buffer-local whenever it is set.
>
> It appears that Gnus fails to do this manually, instead
> ending up setting the global value to a marker that refers
> to the Gnus summar
> Well, the following doesn't work in 21.3 but does in recent cvs
> versions (I get an arrow in each buffer in the latter):
>
> (progn
> (switch-to-buffer "buf1")
> (delete-other-windows)
> (make-variable-buffer-local 'overlay-arrow-position)
> (setq overlay-arrow-position (make-ma
I think you've always been able to make overlay-arrow-position buffer-local.
The problem arises when two arrows try to display in the _same_ buffer, then
the local value masks the global value. Perhaps this will never happen in
Gnus, but in case it does, a good way is to use overlay-ar
>I believe the variable `overlay-arrow-position' should
>automatically become buffer-local whenever it is set.
>
>It appears that Gnus fails to do this manually, instead
>ending up setting the global value to a marker that refers
>to the Gnus summary buffer, which doesn't
Ryan Yeske <[EMAIL PROTECTED]> writes:
> - Variable: overlay-arrow-position
>
> [...]
>
> The overlay string is displayed only in the buffer
> that this marker points into. Thus, only one buffer
> can have an overlay arrow at any given time.
>
> Which I think was true in 21.
I believe the variable `overlay-arrow-position' should
automatically become buffer-local whenever it is set.
It appears that Gnus fails to do this manually, instead
ending up setting the global value to a marker that refers
to the Gnus summary buffer, which doesn't make sense.
I believe the variable `overlay-arrow-position' should
automatically become buffer-local whenever it is set.
It appears that Gnus fails to do this manually, instead
ending up setting the global value to a marker that refers
to the Gnus summary buffer, which doesn't make sense.
In fact, I see no r
14 matches
Mail list logo
