From: Bastien <bzg@gnu.org>
To: "Robert P. Goldman" <rpgoldman@sift.info>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Multiple agenda buffers
Date: Wed, 16 Apr 2014 16:45:56 +0200 [thread overview]
Message-ID: <877g6pz0br.fsf@bzg.ath.cx> (raw)
In-Reply-To: <5332EE27.3030501@sift.info> (Robert P. Goldman's message of "Wed, 26 Mar 2014 10:11:35 -0500")
Hi Robert,
"Robert P. Goldman" <rpgoldman@sift.info> writes:
> I find if I accidentally return over an item's date, I get a second
> agenda buffer for that date.
>
> That seems fine, but what I don't like is that from now on, any org
> agenda commands go to THAT buffer, rather than going into the old agenda
> buffer, which I keep around all the time.
>
> So I have, for example *Org Agenda* and *Org Agenda(a:2014-03-25)
>
> Is there some way to kill the latter so that it does not come back?
>
> I did ^X-k in that buffer, and it disappeared, but my next org agenda
> command went into a buffer like that, instead of going into the original
> *Org Agenda* (and its frame).
You can *exit* the agenda view with `x' and quit it with `q'.
In your case, I think you want to use `x'.
With a sticky agenda, `q' only buries the agenda, it does not delete
the agenda buffer.
> Is this related to org-agenda-this-buffer-is-sticky? I don't really
> understand the description of stickiness in org-agenda.el and it's not
> referenced in the index of the manual.
I slightly rewrote the description of sticky agendas in the manual and
added an index entry.
Thanks,
--
Bastien
next prev parent reply other threads:[~2014-04-16 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 15:11 Multiple agenda buffers Robert P. Goldman
2014-04-16 14:45 ` Bastien [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 18:55 multiple " 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
2011-03-02 20:08 ` Matt Lundin
2009-12-04 14:31 Multiple " 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=877g6pz0br.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=rpgoldman@sift.info \
/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).