unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: How can I kill these buffers automatically (Woman-log Completions)
Date: Sun, 23 Oct 2005 18:41:28 +0200	[thread overview]
Message-ID: <uu0f8gp8n.fsf@gnu.org> (raw)
In-Reply-To: <874q78cuz4.fsf@magma.ca> (message from Angelina Carlton on Sun,  23 Oct 2005 07:51:11 -0400)

> From: Angelina Carlton <brat@magma.ca>
> Date: Sun, 23 Oct 2005 07:51:11 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > That's because you set woman-show-log too late: it should be set
> > _before_ woman.elc is loaded.  Alternatively, use the Customize
> > feature to customize the value of the variable, and have Customize
> > write the correct code into your .emacs.
> >
> I tried it placing the line right at the top of my .emacs and it still
> wont do anything, also tried via the customize menus also with no effect.

Perhaps we are miscommunicating: this variable controls whether the
log buffer is _shown_, not whether it is created and filled with log
message.  If you expected that setting it to nil will prevent WoMan
from logging messages into the log buffer, you misunderstood the doc
string of woman-show-log.

> Because although I use Iswitch buffer, when I have *Compile-log*
> *Completions* and some other file I might be visiting that happens to
> begin with Comp it becomes for me at least, a little extra step to type
> out the buffer name. (or enough of the buffer name to be unique) 

You can tailor this Iswitch's behavior by customizing the variable
iswitchb-buffer-ignore.

> Maybe its because I am relatively new to emacs and this is the way it
> works, you just get used to having lots of buffers?

Yes, I think you should get used to this.  Emacs creates a lot of
buffers, so this is perfectly normal.

> > I also don't see any sense in killing the *Help* buffer, because it
> > will be reused (and recreated, if needed) by the next help command.
> > It is also handy to go to that buffer if you forgot some detail.
> 
> I dont care really if emacs has to recreate the buffer

My point was that, even if you kill *Help*, it will be created again
in a short while.  So why bother?

  parent reply	other threads:[~2005-10-23 16:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 19:23 How can I kill these buffers automatically (Woman-log Completions) Angelina Carlton
2005-10-23  7:17 ` Eli Zaretskii
2005-10-23 11:51   ` Angelina Carlton
2005-10-23 13:14     ` Lennart Borgman
2005-10-23 16:29       ` Angelina Carlton
2005-10-23 16:26     ` Drew Adams
2005-10-23 16:38     ` Henrik Enberg
2005-10-23 16:41     ` Eli Zaretskii [this message]
2005-10-23 18:01       ` Angelina Carlton
2005-10-27 22:58 ` Slawomir Nowaczyk
2005-10-28  5:48   ` William Xu
     [not found] <mailman.12253.1130009042.20277.help-gnu-emacs@gnu.org>
2005-10-24  2:40 ` Shug Boabby

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=uu0f8gp8n.fsf@gnu.org \
    --to=eliz@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.
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).