From: Nick Dokos <email@example.com>
To: John Hendy <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: Closing org buffers after agenda
Date: Wed, 18 Jul 2012 15:41:03 -0400 [thread overview]
Message-ID: <6286.1342640463@alphaville> (raw)
In-Reply-To: Message from John Hendy <firstname.lastname@example.org> of "Wed, 18 Jul 2012 14:34:59 CDT." <CA+M2ft8y_242oJgyJjOuv2Coh1X_djSC=bWa2JiX8x7fe08Lqg@mail.gmail.com>
John Hendy <email@example.com> wrote:
> I don't use agenda as often as a lot of folks. When I do, I notice
> that all org files in my agenda path end up open. Sometimes this has
> caused issues as I've been working on a file and then after agenda I
> notice that there's a file.org<2> buffer. I'll go to save one and it
> will tell me it's changed on disk and I have a hard time figuring out
> which one I should keep!
> Is there a way to close the buffers opened by agenda? Does agenda
> leave them open for quicker searching for the next time? Or I wondered
> if they need to be open buffers to it to look at the contents.
'x' in the agenda (bound to org-agenda-exit) will do that.
However, I find it easier to go from the agenda to the file, rather than
navigating through the file system: C-c a a <move cursor to entry> TAB gets me
there pretty quickly.
next prev parent reply other threads:[~2012-07-18 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 19:34 Closing org buffers after agenda John Hendy
2012-07-18 19:41 ` Nick Dokos [this message]
2012-07-18 19:43 ` John Hendy
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).