emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: emacs-orgmode@gnu.org
Cc: alain.cochard@unistra.fr
Subject: multiple agenda views -- sticky agendas?, buffer renaming?
Date: Tue, 6 Jun 2017 17:19:39 +0200	[thread overview]
Message-ID: <22838.51211.771733.11287@frac.u-strasbg.fr> (raw)
In-Reply-To: <22638.29899.634767.904773@frac.u-strasbg.fr>


Hello.

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'.  

Use of sticky agendas does not seem to be suited for my need (but
maybe I am missing something), while renaming the buffer seems more
promising except that it partly fails -- again, maybe I am missing
something or there is a bug.

(1) Trying with sticky agendas, I do:

M-x org-agenda * a

M-x make-frame

In the newly created frame: M-x org-agenda m some_tag

so far, so good.

But If, in that same newly created frame, I want to search for another
tag, as soon as I do 'M-x org-agenda m', I get the message "Sticky
Agenda buffer, use `r' to refresh".

Sure, I can refresh, bug cannot search for another tag.

Am I doing something wrong?

(2) Trying renaming the buffer, I do:

M-x org-agenda a

M-x rename-uniquely

M-x make-frame

In the newly created frame: M-x org-agenda m some_tag

At this point, the behavior is as I expect in the newly created agenda
view: pressing <TAB> on a given line of the agenda view puts the point
at the proper place of the proper buffer in the other window.

But it does not work that way in the initial agenda view: pressing
<TAB> generates the message "Wrong type argument: integer-or-marker-p,
nil". 

Again, am I doing something wrong?

Are there other ways of doing what I want?

NB: I have used an extremely minimal setup, both with Org version
8.2.10, which is the default for my GNU Emacs 24.5.1 installation, and
with Org version 9.0.8-elpa.

I have tried with M-x rename-buffer instead of M-x rename-uniquely,
but the result is the same.


Thank you for any help.

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     

  parent reply	other threads:[~2017-06-06 15:19 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 ` Alain.Cochard [this message]
2017-07-03  5:09   ` multiple agenda views -- sticky agendas?, buffer renaming? Bastien
2017-08-22 13:25     ` Alain.Cochard

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=22838.51211.771733.11287@frac.u-strasbg.fr \
    --to=alain.cochard@unistra.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).