unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: emacs-devel@gnu.org
Subject: Re: Working with one buffer in two frames/windows
Date: Tue, 22 Jul 2008 07:45:32 +0200	[thread overview]
Message-ID: <488573FC.8020008@hotmail.fr> (raw)
In-Reply-To: <jwv8ww5dyvp.fsf-monnier+emacs@gnu.org>

Hello,

Just to throw a comment into this discussion from a non-developper : 
something that is quite disturbing to the user is that when you have 
several windows on the same buffer, and you switch on/off narrowing 
(which is quite often the case when you want to limit the scope of some 
search and replace), then you loose the point position on the other 
window after switching narrowing off again.

If this has been changed in Emacs version 23, then forget this mail (I 
am with 22.2).

It is disturbing because all windows are about is looking at several 
point of the same buffer at the same time, and narrowing on/off looses 
this multiplicity of points of view.

My suggestion is that:
1) when going to narrowing on a buffer, points in other windows of the 
same buffer should be stored if they are outside the narrowed region,
2) if during narrowing mode, the user goes to the other window, and 
moves the point, then the other window's before-narrowing-stored-point 
should be erased, and
3) when the user is going out of the narrowing mode, then for each other 
window on the same buffer, if there is before-narrowing-stored-point 
available, it should be restored.

Surely this restoring of the window configuration prior to narrowing 
should be made a defcustom choice (always, never, ask-user). Maybe point 
2 above is not that much needed.

Ideally, narrowing should concern only one window, and not the full 
buffer (in any windows), but maybe this is too much change because 
narrowing has to do with the current buffer mode and making an indirect 
buffer is a better response.

At least this point save&restore thing would be quite useful, especially 
as using a couple of windows is often more practical than using 
registers to store a point, even though more ephemeral, just as window 
handling command (C-x 2, C-x 1, C-x 0) are of quite easy access.

BR,
  Vincent.







      reply	other threads:[~2008-07-22  5:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 10:55 Working with one buffer in two frames/windows David Kastrup
2008-07-11 11:28 ` David Hansen
2008-07-12  2:24 ` Stefan Monnier
2008-07-12  8:21   ` David Kastrup
2008-07-12 10:40     ` martin rudalics
2008-07-12 11:02       ` David Kastrup
2008-07-12 12:22         ` martin rudalics
2008-07-12 20:40         ` Stephen J. Turnbull
2008-07-12 20:41           ` David Kastrup
2008-07-12 22:53             ` Stephen J. Turnbull
2008-07-12 21:20     ` Stefan Monnier
2008-07-13 13:06 ` Alan Mackenzie
2008-07-14  1:44   ` Stefan Monnier
2008-07-22  5:45     ` Vincent Belaïche [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=488573FC.8020008@hotmail.fr \
    --to=vincent.b.1@hotmail.fr \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).