emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Closing org buffers after agenda
Date: Wed, 18 Jul 2012 14:43:24 -0500	[thread overview]
Message-ID: <CA+M2ft86NeepEKzuVjyJQNjask_G2QCTVsxN6rU2zBC3p0+bEQ@mail.gmail.com> (raw)
In-Reply-To: <6286.1342640463@alphaville>

On Wed, Jul 18, 2012 at 2:41 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> John Hendy <jw.hendy@gmail.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.

Doh! Thanks :)

> 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.

As in, if you're editing files linked in the agenda, you'd rather
leave them open and navigate to them from agenda? If so, that makes
sense. I keep nearly everything in one projects.org file but search
other files for reference material (I have an education.org for
classes I've taken at work, devel.org for goal tracking/evaluation
stuff, contacts.org, etc.). I use those other files quite rarely, so I
really only need projects.org open for the most part.


> Nick

      reply	other threads:[~2012-07-18 19:43 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
2012-07-18 19:43   ` John Hendy [this message]

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:

  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=CA+M2ft86NeepEKzuVjyJQNjask_G2QCTVsxN6rU2zBC3p0+bEQ@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \


* 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).