On 5/24/07, Andre Poenitz <[EMAIL PROTECTED]> wrote:
On Thu, May 24, 2007 at 10:34:26AM +0300, Elazar Leibovich wrote:
> On 5/22/07, Andre Poenitz <[EMAIL PROTECTED]> wrote:
> >On Tue, May 22, 2007 at 05:41:22PM +0300, Elazar Leibovich wrote:
> >> Well, I'm in cursorX() so I'm having
> >> BufferView bv,
> >> CursorSlice sl,
> >> and finally boundary. Which does nothing AFAIK, it's just always FALSE.
> >> I suspect that it's supposed to tell you whether or not the cursor is
> >> right in front of an inset, but not in it, apparently it's broken.
> >
> >Your suspicion is wrong.
> >
> >I case you'd stop top-posting I might even be tempted to give a longer
> >explanation.
>
> One guy says "be louder", other say "stop top posting", what should I do
> then?
There is a non-empty intersection.
> Anyhow I'd love a longer explanation.
There are cases where this information is useful.
E.g. if you have /italics/[Cursor]BOLD, it is interesting whether
typing 'x' gives you an italics x or a bold one.
Also there is a visual difference between the last position in a
display row and the first position in the row below, although there is
only one logical position. The boundary flag tell you which one is
meant.
Granted. However how do you determine that? Is it by the last cursor
the user has clicked (if he pressed <-, he'll be after character X, if
he typed -> he'll be before character Y)?
Andre'
