all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: too many buffers
Date: Mon, 18 Jan 2010 08:25:49 +1100	[thread overview]
Message-ID: <87my0cbezm.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.1572.1263737418.18930.help-gnu-emacs@gnu.org

andrea <andrea.crotti.0@gmail.com> writes:

> When I use emacs for long times I end up having a lot of buffers.
> It's not a big problem but it can be annoying, and there are some
> buffers that should just not stay there:
> - magit buffers
> - dired buffers (I didn't find a variable useful to limit the opening of
>   new buffers)
> - completions/help/annotate.
>
> I normally use those things once and if I need them again I'll execute
> again the function.
>
> Can I limit the creation of new buffers or maybe I should write some
> functions that cleans the situation automatically (using ibuffer maybe)?
>
> And also with org-mode when I use the agenda it visits ALL the buffers
> without closing them after, is that normal?
>
> I have more than 50 files in the agenda only...
> Thanks
>

Its quite normal for emacs to have lots of open buffers. I think the
trick is to use some of the facilities and other packages out there to
reduce the apparent clutter presented to the user when using things like
list-buffers or switch to buffer etc. 

Have a look on the emacs wiki at a few of the buffer related packages.
There are actually quite a few options out there. Your bound to find
something that will suit your preferences and requirements - in fact,
the issue will probably be identifying which one is best. Often, trial
and error is the best approach. 

Personally, I'm currently using ido mode and while I have lots of
buffers open, I tend to not notice them. I've also found ibuffer and
friends useful at times. 

Note that Org often keeps a lot of buffers open so that when you do
things like agenda views etc, it doesn't have the lead time of opening
them all again to determine what items may have been added/changed etc.
Of course, the number depends on the how many org files you have and
which ones are automatically included in your agenda views. 
Tim
-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2010-01-17 21:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1572.1263737418.18930.help-gnu-emacs@gnu.org>
2010-01-17 15:45 ` too many buffers Galen Boyer
2010-01-17 16:15 ` Florian Diesch
2010-01-17 21:25 ` Tim X [this message]
2010-01-17 14:09 andrea
2010-01-17 15:37 ` Peter Dyballa
2010-01-17 17:58 ` Sean Sieger
2010-01-18  5:07 ` Thien-Thi Nguyen
2010-01-20 19:06 ` Sam Steingold
2010-01-20 21:03   ` Thierry Volpiatto
2010-01-20 22:17     ` Suvayu Ali
2010-01-20 22:34       ` Thierry Volpiatto
2010-01-21 16:25         ` andrea
2010-01-21 16:43           ` Suvayu Ali
2010-01-21 19:22             ` Drew Adams

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=87my0cbezm.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --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.
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.