Changing this would require internal changes. Followups to
xemacs-beta.
>>>> "Yoichi" == Yoichi NAKAYAMA
<yoichi(a)eken.phys.nagoya-u.ac.jp> writes:
Yoichi> (make-local-variable 'truncate-partial-width-windows)
Yoichi> (setq truncate-partial-width-windows nil)
Yoichi> on buffer B. Then it is possible to control truncation in
Yoichi> buffer B by truncate-lines, I thought.
Yoichi> With GNU Emacs, it is possible regardless of the position
Yoichi> of cursor. But on XEmacs, it shows different behavior.
[I.e., in XEmacs t-p-w-w gets the value for the current buffer, so
when the cursor is in B, truncate-lines rules, when it is not, t-p-w-w
in the other buffer determines whether truncate-lines has an effect or
not.]
I think the GNU behavior (and the traditional behavior of
truncate-lines, for that matter) is an abuse of the term
"buffer-local", although the GNU behavior is desirable in these cases.
The current buffer should determine the value of a buffer-local
variable in Lisp, not the current focus of the redisplay engine.
Ben? Should these variables be specifiers? Can we reasonably draw
the distinction that local variables used to control redisplay should
be specifiers, and buffer-locals should be used to control Lisp?
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.