Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!topaz!ll-xn!mit-amt!mit-eddie!liberte
From: liberte@b.CS.UIUC.EDU
Newsgroups: net.emacs
Subject: Buffer vs. Window specific variables
Message-ID: <2578@mit-eddie.MIT.EDU>
Date: Thu, 17-Jul-86 17:42:32 EDT
Article-I.D.: mit-eddi.2578
Posted: Thu Jul 17 17:42:32 1986
Date-Received: Sat, 19-Jul-86 00:47:50 EDT
Sender: dca@mit-eddie.MIT.EDU
Organization: M.I.T. EE/CS Computer Facility, Cambridge MA
Lines: 27

From: liberte@b.CS.UIUC.EDU (Daniel LaLiberte)

There are several buffer-local variables that might be more
useful as window-local variables.  In general, any variable
that affects the display only (and movement within the display)
should be part of the window structure so that the user would be
allowed to view a single buffer in more than one way.  

As an example, I would like to view a buffer with selective-display in
one window while simultaneously viewing the buffer with no
selective-display in another window.  With a lisp extension, I could
move the point in the selective-display window and then "pass" that point
to the non-selective-display window for fast procedure hopping.

Is there a good reason to have the following variables buffer-local
as opposed to window-local?  Maybe we need a window-local list too.

	tab-width
	truncate-lines
	ctl-arrow
	selective-display


Dan LaLiberte
liberte@b.cs.uiuc.edu
liberte@uiuc.csnet
ihnp4!uiucdcs!liberte