Re: overlay-arrow-variable-list

"Ben Wing" <[email protected]> Wed, 3 May 2006 00:42:06 -0500
Newsgroups gmane.emacs.xemacs.design
Message-ID <[email protected]>
------=_Part_6729_30499327.1146634926634
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 5/2/06, Jerry James <[email protected]> wrote:
>
> I'm still chasing my Holy Grail: the newer Emacs debugger interfaces.
> I'll soon send in the changes to comint.el that I needed to make some of
> this stuff work.  However, I'm facing another problem where I could use
> the help of my fellow designers.
>
> We support overlay-arrow-position and overlay-arrow-string, which are
> used by our GDB support to show which line control has reached.  The
> newer Emacs stuff draws multiple overlaid arrows and things to show
> various bits of information in debugger buffers.  To support this, they
> have introduced overlay-arrow-variable-list, which has the following
> docstring:
>
>   List of variables (symbols) which hold markers for overlay arrows.
>   The symbols on this list are examined during redisplay to determine
>   where to display overlay arrows.
>
> They modified their redisplay engine to support this list.  The newer
> debugger support uses this variable.
>
> I could attempt to modify our redisplay engine to support
> overlay-arrow-variable-list as well, but that doesn't help.  The
> debugger changes are going to go into packages, so I can't use
> capabilities that aren't already present in released XEmacsen.
>
> What do we have in place that I might be able to use instead?


the only thing i know of that might help is `annotations', i.e. marginal
extents.  these are designed for exactly this sort of thing (although they
won't exactly overlay the text).

------=_Part_6729_30499327.1146634926634
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div><span class=3D"gmail_quote">On 5/2/06, <b class=3D"gmail_sendername">J=
erry James</b> &lt;<a href=3D"mailto:[email protected]">[email protected]</a>=
&gt; wrote:</span><blockquote class=3D"gmail_quote" style=3D"border-left: 1=
px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"=
>
I'm still chasing my Holy Grail: the newer Emacs debugger interfaces.<br>I'=
ll soon send in the changes to comint.el that I needed to make some of<br>t=
his stuff work.&nbsp;&nbsp;However, I'm facing another problem where I coul=
d use<br>
the help of my fellow designers.<br><br>We support overlay-arrow-position a=
nd overlay-arrow-string, which are<br>used by our GDB support to show which=
 line control has reached.&nbsp;&nbsp;The<br>newer Emacs stuff draws multip=
le overlaid arrows and things to show
<br>various bits of information in debugger buffers.&nbsp;&nbsp;To support =
this, they<br>have introduced overlay-arrow-variable-list, which has the fo=
llowing<br>docstring:<br><br>&nbsp;&nbsp;List of variables (symbols) which =
hold markers for overlay arrows.
<br>&nbsp;&nbsp;The symbols on this list are examined during redisplay to d=
etermine<br>&nbsp;&nbsp;where to display overlay arrows.<br><br>They modifi=
ed their redisplay engine to support this list.&nbsp;&nbsp;The newer<br>deb=
ugger support uses this variable.
<br><br>I could attempt to modify our redisplay engine to support<br>overla=
y-arrow-variable-list as well, but that doesn't help.&nbsp;&nbsp;The<br>deb=
ugger changes are going to go into packages, so I can't use<br>capabilities=
 that aren't already present in released XEmacsen.
<br><br>What do we have in place that I might be able to use instead?</bloc=
kquote><div><br>
the only thing i know of that might help is `annotations', i.e.
marginal extents.&nbsp; these are designed for exactly this sort of
thing (although they won't exactly overlay the text).<br>
</div><br></div><br>

------=_Part_6729_30499327.1146634926634--