From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: bug-gnu-emacs@gnu.org, dashteacup@insightbb.com
Subject: Re: View-quit in *Help* restores wrong window when display-buffer-reuse-frames is t
Date: Fri, 19 Oct 2007 10:23:44 +0200 [thread overview]
Message-ID: <47186990.3030007@gmx.at> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICEELDEAAA.drew.adams@oracle.com>
>>What is the semantics of a "dedicated frame"?
>
>
> I should have said "special-display".
>
> (add-to-list
> 'special-display-buffer-names
> (list "*Help*" 'my-display-*Help*-frame...))
I did understand you the first time. The Elisp manual tells me:
By default, special display means to give the buffer a dedicated
frame.
No special semantics for "quitting" or "deleting" dedicated frames are
given. There's a short remark in the Emacs manual
"Killing the special buffer deletes its frame automatically."
but I'm not sure whether you want to kill the Help buffer and I don't
know what to do when you manually switched to another buffer in that
frame in between.
>>If you "dedicate" a frame to the Help buffer why do you want to switch
>>to a different buffer in that frame? Why do you want to split that
>>frame's window?
>
>
> I don't; I never said I did. I was describing my overall use, including my
> use of `pop-up-frames', not my use of *Help*. You expressed some assumptions
> about users with non-nil `pop-up-frames' and their never reusing a window
> and never splitting a window. I was explaining that although I have
> `pop-up-frames' non-nil, I still sometimes reuse or split some windows (not
> *Help*, but others).
>
If you do not "reuse" Help windows I don't understand why the proposed
patch doesn't work for you. You would have to give me a recipe to
reproduce the incorrect behavior. Problems may arise if and only if a
Help window was reused to display another buffer.
>>I already explained that by default Help buffers are not dedicated thus
>>`quit-window' won't necessarily delete the associated frame.
>
>
> And I explained that I don't personally need you to delete the frame - I do
> that myself. Deleting the window is sufficient (for *Help* or any other
> buffer).
Your personal modifications won't be of any help to other Emacs users.
Let's make this generally usable.
> If there was a buffer in the window before the view-mode buffer is placed in
> it, then it's OK to show that buffer after quitting the view-mode buffer. If
> there was no other buffer in the window before the view-mode buffer, then
> there is no reason to display any buffer at all there - just delete the
> window.
I already explained that tracking the appearance of buffers in a window
is non-trivial and has to be done in `window-configuration-change-hook'.
So far the decision about how to quit view-mode must be established when
_entering_ view-mode.
> And if the view-mode buffer is `one-window-p', then delete the frame
> also.
If people agree that typing `q' should be allowed to unequivocally
delete a frame.
next prev parent reply other threads:[~2007-10-19 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D64B7FD7-2C5F-4A87-8F0B-61EB47217262@insightbb.com>
2007-10-13 17:28 ` View-quit in *Help* restores wrong window when display-buffer-reuse-frames is t David Reitter
2007-10-14 8:42 ` martin rudalics
2007-10-17 20:58 ` Glenn Morris
2007-10-18 8:20 ` martin rudalics
2007-10-18 16:05 ` Drew Adams
2007-10-18 22:01 ` martin rudalics
2007-10-18 22:58 ` Drew Adams
2007-10-19 8:23 ` martin rudalics [this message]
2007-10-19 15:17 ` Drew Adams
2007-10-20 9:45 ` martin rudalics
2007-10-18 18:27 ` Glenn Morris
2007-10-18 22:03 ` martin rudalics
2007-10-18 23:44 ` Glenn Morris
2007-10-19 8:14 ` martin rudalics
2007-10-19 17:52 ` Glenn Morris
2007-10-20 9:45 ` martin rudalics
2007-10-23 23:30 ` Glenn Morris
2007-10-24 6:32 ` martin rudalics
2007-10-22 21:45 ` David Reitter
2007-11-29 9:05 ` David Reitter
2007-11-29 10:22 ` martin rudalics
[not found] ` <mailman.4303.1196332542.18990.bug-gnu-emacs@gnu.org>
2007-12-01 8:01 ` David Reitter
2007-12-01 9:20 ` martin rudalics
2007-12-01 14:44 ` David Reitter
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=47186990.3030007@gmx.at \
--to=rudalics@gmx.at \
--cc=bug-gnu-emacs@gnu.org \
--cc=dashteacup@insightbb.com \
--cc=drew.adams@oracle.com \
/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.