From: Ignacio Casso <firstname.lastname@example.org> To: email@example.com Subject: [BUG] (org-agenda-files) after restrict agenda to a file [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)] Date: Wed, 20 Apr 2022 09:33:21 +0200 [thread overview] Message-ID: <PAXPR06MB7760F3A02D140E7DE2BAAEC6C6F59@PAXPR06MB7760.eurprd06.prod.outlook.com> (raw) Hello, After restricting the agenda to a file for a single agenda command, with 'C-c a < a', and exiting the agenda with 'x', (org-agenda-files) still returns that file instead of the original list of agenda files. This can be easily solved using the UNRESTRICTED optional argument in `org-agenda-files', but I wonder if this behavior is correct. The docstring of `org-agenda-files' says "Optional UNRESTRICTED means return the full list even if a restriction is currently in place." But as I understand it, the restriction is no longer in place, since it was only for the duration of the agenda command, as the Org Mode Manual says: "If you would like to focus the agenda temporarily on a file not in this list, or on just one file in the list, or even on only a subtree in a file, then this can be done in different ways. For a single agenda command, you may press ‘<’ once or several times in the dispatcher. To restrict the agenda scope for an extended period ..." *note This is probably a minor issue, but since it was the cause of a bug in my config that took me a while to debug, I'm reporting it in case you think that something should be done about it. In case you are curious about my use case, I was just doing something like (eval-after-load 'a-package '(setq org-agenda-files (append (org-agenda-files) (...))) Regards, Ignacio Emacs : GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.20) of 2022-01-16 Package: Org mode version 9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)
next reply other threads:[~2022-04-20 8:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-20 7:33 Ignacio Casso [this message] 2022-04-20 10:04 ` Ihor Radchenko
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=PAXPR06MB7760F3A02D140E7DE2BAAEC6C6F59@PAXPR06MB7760.eurprd06.prod.outlook.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [BUG] (org-agenda-files) after restrict agenda to a file [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)]' \ /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
Code repositories for project(s) associated with this 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).