From: <klaus.berndl@sdm.de>
Cc: emacs-devel@gnu.org
Subject: RE: Please review: Small fix for window.c
Date: Thu, 9 Mar 2006 08:52:33 +0100 [thread overview]
Message-ID: <A47B192B0358794C958615D788BF7FB701A2A0EE@mucmail1.sdm.de> (raw)
Kim F. Storm wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> A softly dedicated window is a window that's been created
>> specifically
>> to display a particular buffer, but whose allegiance to this buffer
>> may not be eternal. More specifically if the user decides to do
>> switch-to-buffer, no error will be signalled and instead the
>> dedication flag will simply be set to nil. This way, when the buffer
>> gets deleted the window also gets deleted but only if the user hasn't
>> used that window for some other purpose in the mean time.
>>
>> With this scheme, pop-to-buffer would typically set the dedicated
>> flag
>> of windows it creates to `soft', so many/most windows start out as
>> being softly dedicated.
>>
>> I hope I'll get enough time and motivation at some point to try and
>> convince Emacs's maintainers that this is a good idea and should be
>> installed.
>
> I think it sounds like an excellent idea!
I second this...
>
>> With soft-dedication, the use of set-window-configuration to try and
>> undo what display-buffer has done is replaced by a call to
>> kill-buffer
>> or bury-buffer.
>
> Nice!
>
>
> I was thinking about another kind of "hard" dedication -- where a
> window cannot be deleted unless you kill the associated buffer. It
> seems useful for stuff like ECB which don't want _anything_ to mess
> with its windows.
Yes, sounds like an excellent idea, different levels of dedication could
solve the problems of tools like ECB and would allow to throw away a lot
of advices currently necessary for ECB!
next reply other threads:[~2006-03-09 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 7:52 klaus.berndl [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 15:52 Please review: Small fix for window.c Kim F. Storm
2006-03-08 16:11 ` Stefan Monnier
2006-03-08 20:23 ` Kim F. Storm
2006-03-09 4:48 ` Miles Bader
2006-03-09 17:14 ` 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
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=A47B192B0358794C958615D788BF7FB701A2A0EE@mucmail1.sdm.de \
--to=klaus.berndl@sdm.de \
--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).