emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manish <mailtomanish.sharma@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Julian Burgos <jmburgos@uw.edu>, Bernt Hansen <bernt@norang.ca>,
	Michael Markert <markert.michael@googlemail.com>
Subject: Re: Re: agenda view opening multiple buffers
Date: Tue, 29 Mar 2011 00:00:36 +0530	[thread overview]
Message-ID: <AANLkTik3C73WsVCTFo4QKHsYGL4Mqga74zn37vGuRmZv@mail.gmail.com> (raw)
In-Reply-To: <815582FF-9288-4B52-9B5A-4D838D6A1FFD@gmail.com>

On Mon, Mar 28, 2011 at 8:48 PM, Carsten Dominik wrote:
> On 27.3.2011, at 20:55, Manish wrote:
>> 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 ()
>>              (interactive)
>>              (org-release-buffers org-agenda-new-buffers)
>>              (setq org-agenda-new-buffers nil)))
>> #+end_src
> This will make the agenda disfunctional.  Each line in the agenda contains a pointer to the entry the line was derived from, so remote editing etc will stop working.
> Exiting with "x" is the much better solution.

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?


  reply	other threads:[~2011-03-28 18:31 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 [this message]
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=AANLkTik3C73WsVCTFo4QKHsYGL4Mqga74zn37vGuRmZv@mail.gmail.com \
    --to=mailtomanish.sharma@gmail.com \
    --cc=bernt@norang.ca \
    --cc=carsten.dominik@gmail.com \
    --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).