[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: please change default value of truncate-partial-width-windows to nil
From: |
Miles Bader |
Subject: |
Re: please change default value of truncate-partial-width-windows to nil |
Date: |
Thu, 16 Jul 2009 11:59:44 +0900 |
Stefan Monnier <address@hidden> writes:
>> nil - never truncate lines in the current buffer
>> t - always truncate lines in the current buffer
>> integer - do what integer `truncate-partial-width-windows' does today
>
> I think this would make a lot of sense.
> I.e. first extend truncate-lines so it can take an integer value, then
> mark truncate-partial-width-windows as obsolete.
Eh, why is that better?
`truncate-partial-width-windows' has always[*] been essentially an
"exception for a funny situation", and wedging its functionality into
`truncate-lines' merely complicates things for typical code which really
only cares about the normal case, not the exceptional one.
Currently a mode only needs to worry about setting truncate-lines to t
(or toggling between nil and t in the case of Gnus, etc), if truncating
lines is somehow better for that mode. I your suggestion is followed,
such modes will suddenly have to worry about such details as the proper
width at which point "emergency truncation" goes into effect -- and I
would argue that most modes just don't care about such detail (if a mode
_does_ care about that, it's easy enough to set both variables).
[*] and of course `truncate-partial-width-windows' has been around for
decades, with a non-nil default; I dunno why Drew is freaking out about
it _now_...
-Miles
--
Logic, n. The art of thinking and reasoning in strict accordance with the
limitations and incapacities of the human misunderstanding.
n