bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

window configuration bug


From: John H Palmieri
Subject: window configuration bug
Date: Tue, 28 May 2002 15:07:05 -0700

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.2 (alphaev5-dec-osf5.1, X toolkit)
 of 2002-04-03 on goedel1.math.washington.edu
configured using `configure  --prefix=/scratch/palmieri'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:


I start Emacs with 'emacs -q'.  I define this function (by typing it
into the *scratch* buffer and hitting C-j):

(defun test ()
  (interactive)
  (let ((config (current-window-configuration)))
    (insert "hello")
    (set-window-configuration config)))

I type 'M-x test', and "hello" gets inserted into the buffer, with the
point after the "o".  Good.

I type 'C-x 2 M-x test', and "hello" gets inserted into the buffer,
with the point at the "h".  Bad: the documentation for
current-window-configuration says

   An exception is made for point in the current buffer:
   its value is -not- saved.

I interpret this to mean that the function set-window-configuration
should not alter the point.  It does, and that's a bug.

It's almost as if, even though the point in the current buffer is not
saved, the point in the other window (which contains the same buffer)
*is* saved, and this is messing up the position of the point.
However, the value of the variable split-window-keep-point appears to
be irrelevant: toggling this variable, hitting C-x 2, and running
'M-x test' still causes the misplaced point.  Hitting C-x 2 and
switching between the windows, (in case one of them is viewed as the
"current buffer" and the other is something else in which the point
deserves to be saved) still results in the misplaced point.

-- 
J. H. Palmieri
Dept of Mathematics, Box 354350    mailto:palmieri@math.washington.edu
University of Washington           http://www.math.washington.edu/~palmieri/
Seattle, WA 98195-4350



reply via email to

[Prev in Thread] Current Thread [Next in Thread]