emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: Global agenda views creates lots of buffers.
Date: Fri, 15 Jan 2010 06:50:04 +0100	[thread overview]
Message-ID: <BFC21192-47DC-4D6A-8F5B-A95F5CFBF9EA@gmail.com> (raw)
In-Reply-To: <87iqb43eco.fsf@telefonica.net>


On Jan 14, 2010, at 4:17 PM, Óscar Fuentes wrote:

> I have quite a few org files in org-agenda-files. When a global agenda
> view is displayed (the Global TODO, for instance) org-mode visits all
> the files and keeps the buffer for each of them. I'll prefer this
> behavior:
>
> for each file in org-agenda-files
>    have we a buffer containing it?
>      no -> create a buffer and visit it
>    do our stuff (gather TODO items, etc)
>    if we were not visiting the file
>      kill the buffer that contains it.
>
> Is there a reason for keeping all those buffers around?

The reason is that org makes links from the agenda to the files
using markers, and markers die when the buffer is closed.

What could be possible is throwing away all buffers that
have not produced an entry.  However, I have worked with the
assumption that once you start the agenda you might run more
agenda commands, so keeping the buffers removes the overhead
of reopening many files again and again.

As Darlan has said, you can exit the agenda with "x" to get
rid of all buffers that where created to make the agenda
and have not been modified since making them.

HTH

- Carsten

  parent reply	other threads:[~2010-01-15  5:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 15:17 Global agenda views creates lots of buffers Óscar Fuentes
2010-01-15  3:57 ` Darlan Cavalcante Moreira
2010-01-15  5:50 ` Carsten Dominik [this message]
2010-01-15 10:14   ` Óscar Fuentes

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BFC21192-47DC-4D6A-8F5B-A95F5CFBF9EA@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ofv@wanadoo.es \
    /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/org-mode.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).