all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: jidanni@jidanni.org
Cc: 9641@debbugs.gnu.org
Subject: bug#9641: Man-notify-method 'bully does not remember how windows were
Date: Sat, 01 Oct 2011 12:05:46 +0200	[thread overview]
Message-ID: <4E86E5FA.4040203@gmx.at> (raw)
In-Reply-To: <87fwjdf4gh.fsf@jidanni.org>

 > mr> Do you mean you have a frame with two windows, invoke man, type q in the
 > mr> window used by man and get a frame with one window?
 >
 > I think so. I never learned "frames". The problem I see is the same in
 > "emacs -nw" too.

Basically "bully" (in `Man-notify-when-ready') means

      (bully
       (and (frame-live-p saved-frame)
	   (select-frame saved-frame))
       (pop-to-buffer man-buffer)
       (delete-other-windows))

to pop to the man buffer in some window and to delete all other windows
on that frame.  No command bound to `q' can restore any windows killed
by the `delete-other-windows' call.  So if `q' earlier restored the
two-windows layout something strange must have happened.  Maybe someone
can clarify ...

martin





  reply	other threads:[~2011-10-01 10:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 22:29 bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
2011-10-01  9:08 ` martin rudalics
2011-10-01  9:26 ` jidanni
2011-10-01 10:05   ` martin rudalics [this message]
2011-10-01 10:14 ` jidanni
2011-10-01 10:58   ` martin rudalics
2011-09-30 22:26     ` bug#9640: compilation bully mode jidanni
2011-10-01  3:04       ` Stefan Monnier
2011-10-01  3:49       ` jidanni
2011-10-01  4:00         ` Stefan Monnier
2011-10-01  4:16       ` jidanni
2011-10-01 14:44         ` Stefan Monnier
2011-10-01 14:22       ` bug#9640: I'll try pop-up-frames jidanni
2011-10-01 11:55 ` bug#9641: Man-notify-method 'bully does not remember how windows were jidanni

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=4E86E5FA.4040203@gmx.at \
    --to=rudalics@gmx.at \
    --cc=9641@debbugs.gnu.org \
    --cc=jidanni@jidanni.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 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.