From: torys.anderson@gmail.com (Tory S. Anderson)
To: Kyle Meyer <kyle@kyleam.com>
Cc: orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Org Agenda Mode Line
Date: Fri, 30 Jan 2015 12:55:30 -0500 [thread overview]
Message-ID: <871tmcqhkd.fsf@gmail.com> (raw)
In-Reply-To: <87vbjocgxd.fsf@kyleam.com> (Kyle Meyer's message of "Fri, 30 Jan 2015 12:33:02 -0500")
Hey, thanks for telling me about org-agenda-sticky. I'm going to use that in the future! Having tested, I seem to have gotten rid of the 2015-01-24 line; I notice, though, that it seems to include those messages of one sort or another in every case now. By default it now shows *Org Agenda(a)* and using some other agenda function will show something else. Is this behavior from a recent patch? I don't remember it previously.
Kyle Meyer <kyle@kyleam.com> writes:
> torys.anderson@gmail.com (Tory S. Anderson) wrote:
>> Suddenly I see my org agenda mode line has, as the buffer name,
>> *Org Agenda(a:2015-01-24)
>>
>> I've tried closing and restarting agenda but it persists. What does
>> this mean?
>
> That looks like a buffer name generated when org-agenda-sticky is
> non-nil. The text in parentheses tells you how the command was invoked.
> For example, "*Org Agenda(s:term)*" means that after calling org-agenda,
> you pressed 's' and searched for 'term'. In your case, you used the 'a'
> key, but I'm uncertain of how the '2015-01-24' was generated.
>
> How are you trying to close the buffer? With a sticky agenda, 'q' will
> just bury the buffer. You need to press 'Q' or call kill-buffer
> directly to actually kill it.
prev parent reply other threads:[~2015-01-30 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 13:00 Org Agenda Mode Line Tory S. Anderson
2015-01-30 17:33 ` Kyle Meyer
2015-01-30 17:55 ` Tory S. Anderson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tmcqhkd.fsf@gmail.com \
--to=torys.anderson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.