emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Markert <markert.michael@googlemail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Julian Burgos <jmburgos@uw.edu>, emacs-orgmode@gnu.org
Subject: Re: Re: agenda view opening multiple buffers
Date: Sun, 27 Mar 2011 16:21:00 +0200	[thread overview]
Message-ID: <878vw0y78z.wl%markert.michael@googlemail.com> (raw)
In-Reply-To: <87ei5sr7gj.fsf@norang.ca>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On 27 Mar 2011, Bernt Hansen wrote:
> Julian Burgos <jmburgos@uw.edu> writes:
>> Dear list,
>> When asking for an agenda view (C-c a), org mode opens all files in
>> the agenda list in individual buffers.  I keep lots of files in my
>> list (one per project), so having all those buffers open each time I
>> visit my agenda is pretty annoying.  Is there a way to make org mode
>> not open each file in a buffer (or close the buffers after reading the
>> file) when asking for an agenda view?
>> Thanks,
>> Julian
> Hi Julian,
> I think 'e' in the agenda is supposed to exit the agenda and close
> automatically opened agenda files.

It's `x'. But I think Julian meant that the buffers should be closed
automatically and not open at least as long as the agenda is shown.

For the original issue I think the following would help:
#+begin_src emacs-lisp
(defun project-agenda (&optional args keys restriction)
  (let ((org-agenda-files '("~/project-file1"
    (org-agenda args keys restriction)))

Or pressing `<' in the prompt buffer, for more see (describe-function


[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-03-27 14:21 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 [this message]
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

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=878vw0y78z.wl%markert.michael@googlemail.com \
    --to=markert.michael@googlemail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=jmburgos@uw.edu \


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