From: Angel de Vicente <angel.vicente.garrido@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-super-agenda global list of TODO items
Date: Wed, 14 Sep 2022 10:32:41 +0100 [thread overview]
Message-ID: <875yhqgv2e.fsf@gmail.com> (raw)
In-Reply-To: 54831f8f5c4e27cdc5fdf2889faaff37@citadels.eu
Hello,
Christophe Schockaert <R3vLibre@citadels.eu> writes:
> If I am right (I am playing with the config, it’s not in my daily setup yet for
> now), I could achieve this by defining "org-agenda-custom-commands" as shown in
> the "Projects" example :
> https://github.com/alphapapa/org-super-agenda/blob/master/examples.org#projects.
>
> In that case, "org-super-agenda-groups" is defined differently according to the
> context, so the "time-grid" captures the timed entries in its scope. Then,
> "org-super-agenda-groups" applies to the TODOs in the "todo" or "alltodo"
> context (I used the latter one) where I don’t define the "time-grid"
> selection. Or, maybe I applied it to the "alltodo" only, and discarded it for
> the agenda grid to work only on the TODOs. I don’t remember exactly, however
> this might be a workaround to try that does not need an update of the code,
> especially if it is not expected to be stable and supported by the author.
great. That looks very promising, and without the need to change the
source code. I will try it later on and report back.
Cheers,
--
Ángel de Vicente
Research Software Engineer (Supercomputing and BigData)
Instituto de Astrofísica de Canarias (https://www.iac.es/en)
next prev parent reply other threads:[~2022-09-14 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 8:15 org-super-agenda global list of TODO items Angel de Vicente
2022-09-13 1:39 ` Ihor Radchenko
2022-09-13 5:41 ` Angel de Vicente
2022-09-13 14:26 ` Ihor Radchenko
2022-09-13 14:30 ` Angel de Vicente
2022-09-13 14:50 ` Ihor Radchenko
2022-09-13 18:55 ` Angel de Vicente
2022-09-13 19:55 ` Christophe Schockaert
2022-09-14 9:32 ` Angel de Vicente [this message]
2022-09-14 10:24 ` Angel de Vicente
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=875yhqgv2e.fsf@gmail.com \
--to=angel.vicente.garrido@gmail.com \
--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).