From: Alain.Cochard@unistra.fr
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Alain.Cochard@unistra.fr
Subject: Re: multiple agenda views -- sticky agendas?, buffer renaming?
Date: Tue, 22 Aug 2017 15:25:52 +0200 [thread overview]
Message-ID: <22940.12512.487200.396236@frac.u-strasbg.fr> (raw)
In-Reply-To: <87a84m0ypt.fsf@bzg.fr>
Bastien writes on Mon 3 Jul 2017 07:09:
> Alain.Cochard@unistra.fr writes:
>
> > I want my *Org Agenda* buffer to be open at all times, but I still
> > want to be able to (say) match as many different tags as desired.
> >
> > Googling and searching the archives suggested 2 possible ways: (1)
> > use of sticky agenda views and (2) use 'M-x rename-uniquely'.
> "Sticky" agenda buffers means that agenda buffers won't be recreated
> each time you call M-x org-agenda. I'm not sure this is exactly what
> you mean by "my *Org Agenda* buffer to be open at all times", is it?
>
> Also I'm not sure what is the exact error you are pointing to: can
> you restate it by saying what you expected from what action, and what
> you got instead?
Hi Bastien, and thank you very much for the feedback. I am sorry for
the delay in replying.
I now try to explain myself more clearly.
Say I have emacs open, with a single frame. If I do
M-x org-agenda a
I see what I call my "agenda" (not sure this is the proper
terminology), in what I assumed was called an "*Org Agenda* buffer" --
I realize now how confusing this could have been, because it seems
that all buffers obtained from some 'M-x org-agenda' command are named
"Org-agenda."
If I now do
M-x make-frame
I get a 2nd frame. I would like to be able to work with that 2nd
frame without modifying the content of the 1st frame. This is what I
meant by "my *Org Agenda* buffer to be open at all times" (in the 1st
frame in this example).
But if, in the 2nd frame, I do
M-x org-agenda m tag1
the contents of *both* the 1st and 2nd frames are modified
accordingly. I understand this to be normal, but this is not what I
want, because my agenda is no longer showing in the 1st frame.
I was assuming sticky agendas would produce the behavior I wish, so
(starting fresh), I try
M-x org-agenda * a
then
M-x make-frame
and, in the 2nd, newly created, frame:
M-x org-agenda m tag1
So far, the behavior is as I expect: my agenda is still in the 1st
frame while, in the 2nd one, I have the *Org Agenda(m)* buffer, which
I can use as expected (typically, put the cursor on some line, press
<TAB>, etc.). It is from this point that it appears to me to go
wrong; specifically, if I try to do, still in the 2nd frame:
M-x org-agenda m tag2
then, as soon as the 'm' is typed, the following message appears in
the minibuffer: "Sticky Agenda buffer, use `r' to refresh". But
typing 'r' does not do any good.
The behavior that I expect is (1) to not see the above mentioned
message in the minibuffer, (2) to be able to finish typing 'M-x
org-agenda m tag2', (3) have the *Org Agenda(m)* buffer relevant to
tag2.
In fact, I made progress since my initial email: I had never paid
attention to the following message, which appear after the first tag
search:
Press `C-u r' to search again with new search string
I had ignored it because for me it is more convenient to always use
the same key combination for a given operation (in this case 'C-c a m'
for a tag search).
If I do use 'C-u r', then I can indeed perform another tag search (and
others afterward), and I can say that the use of a sticky agenda does
solve my initial problem!
The somehow funny thing is that after this 'C-u r', I can again use
'M-x org-agenda m some_tag'. In fact I cannot use 'M-x org-agenda m
some_tag' twice in a row: I have to intermingle it with at least one
instance of 'C-u r some_tag'.
So I could reformulate my initial email by saying that tag search does
not behave the same way whether the agenda is sticky or not: with a
non sticky agenda, one may always use 'M-x org-agenda m some_tag' for
a tag search whereas this is not possible with a sticky agenda.
I hope I could make myself clear this time.
Regards,
alain
--
EOST (École et Observatoire des Sciences de la Terre)
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | Fax: +33 (0)3 68 85 01 25
prev parent reply other threads:[~2017-08-22 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:31 "COMMENT" keyword not properly documented in the manual Alain.Cochard
2017-01-08 23:51 ` Nicolas Goaziou
2017-01-10 7:36 ` Alain.Cochard
2017-01-10 18:05 ` Samuel Wales
2017-01-13 23:28 ` Nicolas Goaziou
2017-01-10 20:10 ` Matt Price
2017-06-06 15:19 ` multiple agenda views -- sticky agendas?, buffer renaming? Alain.Cochard
2017-07-03 5:09 ` Bastien
2017-08-22 13:25 ` Alain.Cochard [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
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=22940.12512.487200.396236@frac.u-strasbg.fr \
--to=alain.cochard@unistra.fr \
--cc=bzg@gnu.org \
--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).