indicate-buffer-boundaries

indicate-buffer-boundaries

[Andreas Schwab]

When indicate-buffer-boundaries is non-nil but neither 'left nor 'right
nor an alist, that does not show any boundary indicators any more.  Is
that intented?  The doc string suggests that any non-nil value should have
an effect, and I would expect setting it to t would choose some default.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: indicate-buffer-boundaries

[Lars Hansen]

Andreas Schwab wrote:

> When indicate-buffer-boundaries is non-nil but neither 'left nor 'right
> nor an alist, that does not show any boundary indicators any more.  Is
> that intented?  The doc string suggests that any non-nil value should have
> an effect, and I would expect setting it to t would choose some default.

I asked the same question 10 days ago (this thread).
And I think the variable should be made customizable and should be added 
to the Options->Show/Hide menu.

Re: indicate-buffer-boundaries

[Andreas Schwab]

Lars Hansen <larsh@math.ku.dk> writes:

> Andreas Schwab wrote:
>
>> When indicate-buffer-boundaries is non-nil but neither 'left nor 'right
>> nor an alist, that does not show any boundary indicators any more.  Is
>> that intented?  The doc string suggests that any non-nil value should have
>> an effect, and I would expect setting it to t would choose some default.
>
> I asked the same question 10 days ago (this thread).

Sorry, I missed that.

> And I think the variable should be made customizable

I agree, but first we should agree upon the acceptable values.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: indicate-buffer-boundaries

[Kim F. Storm]

Lars Hansen <larsh@math.ku.dk> writes:

> Andreas Schwab wrote:
>
>> When indicate-buffer-boundaries is non-nil but neither 'left nor 'right
>> nor an alist, that does not show any boundary indicators any more.  Is
>> that intented?  The doc string suggests that any non-nil value should have
>> an effect, and I would expect setting it to t would choose some default.
>
> I asked the same question 10 days ago (this thread).
> And I think the variable should be made customizable and should be
> added to the Options->Show/Hide menu.

Done.  See  Options > Show/Hide > Fringe > Indicators

--
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: indicate-buffer-boundaries

[Richard Stallman]

    When indicate-buffer-boundaries is non-nil but neither `left' nor `right'
    nor an alist, that does not show any boundary indicators any more.

When I try setting it to t, it shows the boundary indicators on the left,
as the comments in the code say.

I will clarify this in the doc string.

Re: indicate-buffer-boundaries

[Lars Hansen]

Richard Stallman wrote:

>    When indicate-buffer-boundaries is non-nil but neither `left' nor `right'
>    nor an alist, that does not show any boundary indicators any more.
>
>When I try setting it to t, it shows the boundary indicators on the left,
>as the comments in the code say.
>  
>
Yes, now it works as documented, Kim fixed it 3 days ago (2004-11-22).

indicate-buffer-boundaries

[Richard Stallman]

The interface for indicate-buffer-boundaries is really kludgy.
I cleaned up the doc for it, but I would really rather make
it simpler.

A good way to make it simpler is to use an alist.  Pick four suitable
symbols, one for each of these icons.  I suggest `top', `bottom', `up'
and `down'.  t can serve as a default for all four.  In the alist,
associate these symbols with either `left', `right' or `nil'.

Instead of current (t .  right), we would use ((top . left) (t . right))
or ((top . left) (bottom . right) (up . right) (down . right))
Instead of current (left . nil), we would use ((top . left) (bottom . left)).

Isn't that clearer?  It is much less ad-hoc.

Re: indicate-buffer-boundaries

[Kim F. Storm]

Richard Stallman <rms@gnu.org> writes:

> The interface for indicate-buffer-boundaries is really kludgy.
> I cleaned up the doc for it, but I would really rather make
> it simpler.
>
> A good way to make it simpler is to use an alist.  Pick four suitable
> symbols, one for each of these icons.  I suggest `top', `bottom', `up'
> and `down'.  t can serve as a default for all four.  In the alist,
> associate these symbols with either `left', `right' or `nil'.
>
> Instead of current (t .  right), we would use ((top . left) (t . right))
> or ((top . left) (bottom . right) (up . right) (down . right))
> Instead of current (left . nil), we would use ((top . left) (bottom . left)).
>
> Isn't that clearer?  It is much less ad-hoc.

That would be cleaner, yes.  

I will change it.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: indicate-buffer-boundaries

[Lars Hansen]

It seems to me that indicate-buffer-boundaries does not work as 
documented. According to the docstring marks should be visible if if the 
value is non-nil. But actually the value has to be 'left, 'right or a cons.

BTW, shouldn't this variable be customizable?