unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Should killing a help or compile buffer also delete the window?
Date: Tue, 26 Apr 2005 16:50:17 -0400	[thread overview]
Message-ID: <m1ll75ff1c.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87vf6afy1r.fsf@wigwam.deepwood.net> (Daniel Brockman's message of "Mon, 25 Apr 2005 21:37:04 +0200")

>> My locally hacked Emacs has changed it to *always* mark the window
>> as dedicated.

> Does this mean that if you type C-h f cd RET M-x man RET chdir RET,
> you end up with three windows (assuming you started with just one)?

Can't remember what behavior I implemented (I use
special-display-buffer-names for those buffers anyway, so I get 3 frames
even with a vanilla Emacs), but the intention is for this not to be the case
in order to preserve the current behavior (i.e. the M-x man simply uses one
of the two existing windows, setting its dedicated flag to nil as
a side-effect).

>> It works great in my environment, don't know about others's.
> It sounds just about perfect.  Where can I get the patch? :-)

It's lost in the middle of many other changes.
See my monnier@iro.umontreal.ca--first/emacs--monnier--0 branch
in my Arch archive at http://www.iro.umontreal.ca/~monnier/archives/first.
Note that it's a branch I use only to sync my local version between
diferent machines.  It's not signed and can be broken and include temporary
hacks/debugging things, some of them left around way past their due date.

Probably a `tla changes --diffs miles@gnu.org--gnu-2005/emacs--trunk--0'
followed by a good grep for `dedicated' will give you a good idea of what's
been changed for this specific "feature".


        Stefan

  reply	other threads:[~2005-04-26 20:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24  5:45 Should killing a help or compile buffer also delete the window? Daniel Brockman
2005-04-24 11:02 ` Robert J. Chassell
2005-04-24 13:35   ` Alan Mackenzie
2005-04-25 10:32     ` Robert J. Chassell
2005-04-24 21:22 ` Richard Stallman
2005-04-24 22:50   ` Daniel Brockman
2005-04-26 10:04     ` Richard Stallman
2005-04-25 17:20 ` Drew Adams
2005-04-25 21:38   ` Daniel Brockman
2005-04-25 17:22 ` Kevin Rodgers
2005-04-25 19:04 ` Stefan Monnier
2005-04-25 19:37   ` Daniel Brockman
2005-04-26 20:50     ` Stefan Monnier [this message]
2005-04-26 14:32   ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25 13:41 David Reitter
2005-04-25 14:11 ` Daniel Brockman

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=m1ll75ff1c.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).