From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: David Kastrup <dak@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Working with one buffer in two frames/windows
Date: Sun, 13 Jul 2008 05:40:27 +0900 [thread overview]
Message-ID: <877ibq7s5g.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <85lk07pdpx.fsf@lola.goethe.zz>
David Kastrup writes:
> martin rudalics <rudalics@gmx.at> writes:
>
> >> I don't think that the solution lies in user commands. The behavior for
> >> temporary screens like help screens and gnus screens and other stuff is
> >> far too egregiously annoying to make it reasonable to require the user
> >> to fight for his window configuration each time.
> >
> > If you have problems with `View-quit' when viewing a help buffer please
> > report here. I have tried to handle that case but might have failed.
>
> I just tried for 10-seconds and it might do the right thing. However,
> killing the view buffer with C-x k RET does not.
(add-hook 'kill-buffer-hook 'View-quit 'append 'local)
?
Yeah, I know, if somebody else does (add-hook ... 'append 'local)
later they will be hosed; maybe `add-hook' needs a MUST-BE-LAST-P
argument and error or warn if 'must-be-last has already been used?
Or view-mode could rebind C-x k to something that does the equivalent
of a before advice which checks if the buffer to kill is the current
buffer, and if so does an add-one-shot-hook.
next prev parent reply other threads:[~2008-07-12 20:40 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 [this message]
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
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=877ibq7s5g.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).