unofficial mirror of bug-gnu-emacs@gnu.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:58:18 +0200	[thread overview]
Message-ID: <4E86F24A.8070706@gmx.at> (raw)
In-Reply-To: <87bou1f27b.fsf@jidanni.org>

 > I was hoping to be able to see a man page and then have it go away
 > without side effects... Of course I never learned frames so I suppose
 > this is not a problem for most people.

Indeed.  You could try by setting `pop-up-frames' to t and see whether
it breaks too many of your earlier editing habits.  If it does, you
might want to add all relevant buffer names (or suitable regexps) to
`special-display-buffer-names' (`special-display-regexps') and look
whether that solves your problems.

 > I was also hoping to get a M-x compile command that would act like
 > 'bully... I mentioned that in another bug.

Same here.  You don't really want to use the same frame.  You want to
use another frame and that should intuitively work well for text-only
terminals too.

martin





  reply	other threads:[~2011-10-01 10:58 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
2011-10-01 10:14 ` jidanni
2011-10-01 10:58   ` martin rudalics [this message]
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

  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=4E86F24A.8070706@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 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).