unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: closing man and help buffers
Date: Mon, 19 Aug 2013 18:11:13 +0200	[thread overview]
Message-ID: <87y57xmzj2.fsf@web.de> (raw)
In-Reply-To: CAKoxK+6xOqTS-vFndZ3cJWGn-Ri02jGat=zKEfoijyxkV+_B1Q@mail.gmail.com

Luca Ferrari <fluca1978@infinito.it> writes:

> On Mon, Aug 19, 2013 at 4:11 PM, Michael Heerdegen
> <michael_heerdegen@web.de> wrote:
>
> > Why do you think is it important to kill those buffers?
>
> It is not important, but it bother me when I switch to other buffers
> since they are in the cycle.

IMHO cleaning up buffers that way, be it automatically or manually, is
either annoying (when doing it manually) or dangerous (when doing it
automatically - buffers may be killed that you want to keep).

Instead, try to live with many buffers.  Configure Emacs so that
commands that display new buffers do it the way you want.  Configure
`display-buffer-alist'.  Use winner-mode.  Configure
`winner-boring-buffers' so that winner doesn't restore buffers you don't
want back.

Second, try to find a better way to switch buffers than relying on the
history (there are many approaches helping here: ido, elscreen, using
multiple frames, using bookmarks or save positions in registers, also
Icicles or Helm have good interfaces for buffer switching).

Michael.




  reply	other threads:[~2013-08-19 16:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19  8:53 closing man and help buffers Luca Ferrari
2013-08-19  9:08 ` Vlad Piersec
2013-08-19  9:55   ` Luca Ferrari
2013-08-19 11:42     ` Tim Visher
2013-08-19 13:42       ` Luca Ferrari
2013-08-19 14:11         ` Michael Heerdegen
2013-08-19 14:36           ` Luca Ferrari
2013-08-19 16:11             ` Michael Heerdegen [this message]
     [not found]             ` <mailman.352.1376928704.10748.help-gnu-emacs@gnu.org>
2013-08-19 16:17               ` Dan Espen
2013-08-19 18:17                 ` Óscar Fuentes
     [not found]                 ` <mailman.361.1376936252.10748.help-gnu-emacs@gnu.org>
2013-08-19 18:54                   ` Dan Espen
2013-08-19 20:11                     ` Óscar Fuentes
     [not found]                     ` <mailman.372.1376943131.10748.help-gnu-emacs@gnu.org>
2013-08-19 20:28                       ` Dan Espen
2013-08-19 22:30                         ` Óscar Fuentes
     [not found]                         ` <mailman.382.1376951626.10748.help-gnu-emacs@gnu.org>
2013-08-19 23:26                           ` Dan Espen
2013-08-19  9:47 ` Eric Abrahamsen

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=87y57xmzj2.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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).