From: David Kastrup <dak@gnu.org>
To: "Tobias C. Rittweiler" <tcr@freebits.de>
Cc: emacs-devel@gnu.org
Subject: Re: [RfC] Saving narrowing information within window configuration
Date: Mon, 13 Aug 2007 14:44:57 +0200 [thread overview]
Message-ID: <86vebjioxi.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <87zm0vd40s.fsf@freebits.de> (Tobias C. Rittweiler's message of "Mon\, 13 Aug 2007 14\:15\:31 +0200")
"Tobias C. Rittweiler" <tcr@freebits.de> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> "Tobias C. Rittweiler" <tcr@freebits.de> writes:
>>
>> > As far as I can see (Emacs v22.0.91.1), narrowed regions are not
>> > restored by saved window configurations. I propose to change that.
>> >
>> > Comments?
>>
>> Don't like it. This is not about what parts of a buffer are
>> displayed, but which parts are accessible.
>
> I think window configurations are mostly used for saving and
> restoring the state as seen by the user, aren't they? So restoring
> narrowing just seems to be the right thing.
Narrowing is not a part of the window configuration. Strictly
speaking, I already find that restoring point and mark is a mistake
here: window-point is the only thing that should be restored in each
window (if there is a currently active window, this will incidentally
also restore point, but that can't be avoided).
> (If restoring narrowing by default is a change that is too invasive,
> I'd have nothing against making it optionally.)
It is simply a mistake to do so. Narrowing is not a feature of the
display, but of buffer accessibility. You would not think of doing
"undo" until the state of the window configuration is reached, even
though buffer changes affected the state as seen by the user, would
you?
In my opinion, narrowing is of a similar degree.
--
David Kastrup
next prev parent reply other threads:[~2007-08-13 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 10:57 [RfC] Saving narrowing information within window configuration Tobias C. Rittweiler
2007-08-13 11:11 ` David Kastrup
2007-08-13 12:15 ` Tobias C. Rittweiler
2007-08-13 12:44 ` David Kastrup [this message]
2007-08-13 13:23 ` Tobias C. Rittweiler
2007-08-14 0:28 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86vebjioxi.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tcr@freebits.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.