From: Matt Lundin <firstname.lastname@example.org>
To: Carsten Dominik <email@example.com>
Cc: Julian Burgos <firstname.lastname@example.org>, Bernt Hansen <email@example.com>,
Michael Markert <firstname.lastname@example.org>
Subject: Re: agenda view opening multiple buffers
Date: Wed, 30 Mar 2011 14:59:24 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <73568D24-AB5A-433F-B28A-DDDCF3071F2E@gmail.com> (Carsten Dominik's message of "Mon, 28 Mar 2011 20:47:34 +0200")
Carsten Dominik <firstname.lastname@example.org> writes:
>> Thanks for pointing that out. Wouldn't "x" that close the agenda as
>> well along with the buffers?
>> OP said: " It would be good to have the
>> agenda open in a buffer without having all the agenda files opened
>> too." May be a special custom agenda command that calls the above
>> lambda function at the end would work better by limiting the damaged
>> behaviour to just one command?
> No. The agenda buffer needs the source buffers alive to function.
In addition, closing agenda buffers with "x" means that the next time
ones call the agenda, Emacs has to load and parse all those files again,
which takes much longer than simply rescanning buffers in memory.
In other words, the expense of keeping the buffers open (a relatively
small amount of RAM) is much less than the expense (disk IO, processing,
time) of reloading the files each time one calls the agenda. In
addition, pressing "x" will interrupt clocking.
If the problem is difficulty scanning through and navigating to buffers
in the Buffer List, ido offers a nice way to switch buffers quickly.
In my experience, Emacs is better savored as a sumptuous feast than as a
spartan repast. The more dishes there are on the table, the merrier
everyone is. :)
(length (buffer-list)) => 178
And I haven't started ERC yet. ;)
prev parent reply other threads:[~2011-03-30 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 13:03 agenda view opening multiple buffers Julian Burgos
2011-03-27 13:58 ` Bernt Hansen
2011-03-27 14:21 ` Michael Markert
2011-03-27 14:51 ` Julian Burgos
2011-03-27 18:55 ` Manish
2011-03-28 15:18 ` Carsten Dominik
2011-03-28 18:30 ` Manish
2011-03-28 18:47 ` Carsten Dominik
2011-03-30 18:59 ` Matt Lundin [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).