emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manish <mailtomanish.sharma@gmail.com>
To: Julian Burgos <jmburgos@uw.edu>
Cc: Bernt Hansen <bernt@norang.ca>,
	Michael Markert <markert.michael@googlemail.com>
Subject: Re: Re: agenda view opening multiple buffers
Date: Mon, 28 Mar 2011 00:25:49 +0530	[thread overview]
Message-ID: <AANLkTin_Mo6ht0p=qDPkmj95YsVO-+Yri-75UppSPzVo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=N-fXLAE=4ti3A7wmnVrFbBDbRpv9_1E96_XVi@mail.gmail.com>

On Sun, Mar 27, 2011 at 8:21 PM, Julian Burgos wrote:
> Thanks.  Using x is good enough for now.  I´ll explore also Michael´s
> suggestions.  It would be good to have the agenda open in a buffer
> without having all the agenda files opened too.

Following code should do what you want (I think).

#+begin_src emacs-lisp
;; function code copied from definition of org-agenda-exit
  (add-hook 'org-finalize-agenda-hook
            (lambda ()
              (org-release-buffers org-agenda-new-buffers)
              (setq org-agenda-new-buffers nil)))


> On Sun, Mar 27, 2011 at 2:21 PM, Michael Markert
> <markert.michael@googlemail.com> wrote:
>> 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)
>>  (interactive)
>>  (let ((org-agenda-files '("~/project-file1"
>>                            "~/project-file2")))
>>    (org-agenda args keys restriction)))
>> #+end_src
>> Or pressing `<' in the prompt buffer, for more see (describe-function
>> 'org-agenda)
>> Michael
> --
> Julian Mariano Burgos
> Hafrannsóknastofnunin/Marine Research Institute
> Skúlagata 4, 121 Reykjavík, Iceland
> Sími/Telephone : +354-5752037
> Bréfsími/Telefax:  +354-5752001
> Netfang/Email: julian@hafro.is, jmburgos@uw.edu

  reply	other threads:[~2011-03-27 18:56 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 [this message]
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='AANLkTin_Mo6ht0p=qDPkmj95YsVO-+Yri-75UppSPzVo@mail.gmail.com' \
    --to=mailtomanish.sharma@gmail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=jmburgos@uw.edu \
    --cc=markert.michael@googlemail.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).