From: Matt Lundin <mdl@imapmail.org>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: multiple agenda buffers
Date: Wed, 02 Mar 2011 15:03:43 -0500 [thread overview]
Message-ID: <87k4ghe1cw.fsf@fastmail.fm> (raw)
In-Reply-To: <87zkpsxocj.fsf@gnu.org> (Bastien's message of "Sat, 19 Feb 2011 12:20:28 +0100")
Hi Bastien,
Bastien <bastien.guerry@wikimedia.fr> writes:
> Hi all,
>
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
>> However I was wondering, block agenda commands might work at least for
>> doing multiple searches. But I don't think there is any interactive
>> interface to it.
>
> inspired by this conversation, I have add a new agenda command:
>
> M-x org-agenda-append-agenda RET
>
> It is bound to `A' in the agenda buffer and lets you append any
> agenda to the currently displayed one, thus providing some kind
> of interactive interface to build block agendas from simple ones.
>
> I think it's a neat addition -- especially useful when you want
> to compare to _small_ list of items.
>
> Let me know what you think - and thanks Suvayu for the idea!
Thanks for the new function. However, at the moment, it has destructive
effects if it is called in a buffer other than the agenda buffer, as it
appends the new agenda results to the current buffer and then makes the
buffer read-only.
Perhaps for now we could throw an error if the append function is called
from outside the agenda:
--8<---------------cut here---------------start------------->8---
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index ea822da..f2eac99 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -2266,6 +2266,8 @@ Pressing `<' twice means to restrict to the current subtree or region
This function allows interactive building of block agendas.
Agenda views are separated by `org-agenda-block-separator'."
(interactive)
+ (unless (string= (buffer-name) org-agenda-buffer-name)
+ (error "Can only append from within agenda buffer"))
(let ((org-agenda-multi t))
(org-agenda)
(widen)))
--8<---------------cut here---------------end--------------->8---
Best,
Matt
--
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-03-02 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 18:55 multiple agenda buffers suvayu ali
2011-02-11 15:20 ` Bastien
2011-02-11 17:06 ` Suvayu Ali
2011-02-19 11:20 ` Bastien
2011-02-19 23:02 ` Suvayu Ali
2011-02-22 11:17 ` Bastien
2011-03-02 20:03 ` Matt Lundin [this message]
2011-03-03 16:41 ` [Accepted] [O] " Bastien Guerry
2011-03-03 16:43 ` Bastien
2011-03-02 20:08 ` Matt Lundin
2011-03-03 8:43 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2014-03-26 15:11 Multiple " Robert P. Goldman
2014-04-16 14:45 ` Bastien
2009-12-04 14:31 Desmond Rivet
2009-12-05 14:18 ` Jan Böcker
2009-12-09 10:02 ` Carsten Dominik
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87k4ghe1cw.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).