From: Kyle Meyer <kyle@kyleam.com>
To: wlharvey4@mac.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’
Date: Thu, 19 Nov 2020 23:28:26 -0500 [thread overview]
Message-ID: <8736141wk5.fsf@kyleam.com> (raw)
In-Reply-To: <63B40662-0EAB-4D02-B607-B00F02D82113@mac.com>
wlharvey4@mac.com writes:
> In Org 9.4, Manual section 11 Agenda Views, second to last paragraph,
> neither of the referenced variables appears to exist.
Hmm, what leads you to say that?
$ git describe master
release_9.4-134-g0d525cbc7
$ git grep 'org-agenda-skip-\(comment\|archived\)-trees' master
master:doc/org-manual.org: #+vindex: org-agenda-skip-archived-trees
master:doc/org-manual.org: ~org-agenda-skip-archived-trees~, in which case these trees are
master:doc/org-manual.org:#+vindex: org-agenda-skip-comment-trees
master:doc/org-manual.org:#+vindex: org-agenda-skip-archived-trees
master:doc/org-manual.org:setting ~org-agenda-skip-comment-trees~ and
master:doc/org-manual.org:~org-agenda-skip-archived-trees~ to ~nil~.
master:lisp/org-agenda.el:(defcustom org-agenda-skip-comment-trees t
master:lisp/org-agenda.el: (and org-agenda-skip-archived-trees (not org-agenda-archives-mode)
master:lisp/org-agenda.el: (and org-agenda-skip-comment-trees
master:lisp/org.el:(defcustom org-agenda-skip-archived-trees t
master:lisp/org.el:(defvar org-agenda-skip-comment-trees)
master:lisp/org.el: (org-agenda-skip-archived-trees (memq 'archive skip))
master:lisp/org.el: (org-agenda-skip-comment-trees (memq 'comment skip))
master:lisp/org.el: (when org-agenda-skip-archived-trees
next prev parent reply other threads:[~2020-11-20 4:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 0:51 Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’ wlharvey4
2020-11-20 4:28 ` Kyle Meyer [this message]
2020-11-20 6:24 ` wlharvey4
2020-11-20 7:01 ` Tim Cross
2020-11-20 6:32 ` wlharvey4
2020-11-20 7:01 ` wlharvey4
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=8736141wk5.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=wlharvey4@mac.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 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).