From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Alain.Cochard@unistra.fr, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-cycle-max-level is broken, especially when using org-element-cache (was: Problem in org-inlinetask-min-level's docstring?)
Date: Tue, 13 Dec 2022 09:37:33 +0100 [thread overview]
Message-ID: <25496.14797.512207.593382@gargle.gargle.HOWL> (raw)
In-Reply-To: <871qp3g3gq.fsf@localhost>
Ihor Radchenko writes on Tue 13 Dec 2022 07:36:
> Alain.Cochard@unistra.fr writes:
>
> > NB: While experimenting, I noticed that, if I customize
> > org-cycle-max-level to 0, then a <TAB> on a headline generates the
> > cryptic "org-match-line: Invalid regexp: "Invalid content of
> > \\{\\}"".
>
> Well. It does not really make much sense to set this variable to 0
> or negative values. I guess we can add a guard against such
> scenarios.
Indeed, it does not make sense, but I realized it only when I fully
understood the behavior.
If one experiments, customizing several variables in row, it will take
time to identify the origin of the message. Specifying in the
documentation of the Customize buffer (=customize docstring?) that the
value of this variables has to be greater than or equal to 1 will
certainly help; also having as the error message, instead of the
current one, would be even better (perhaps that is what you call a
"guard").
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
prev parent reply other threads:[~2022-12-13 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 10:07 Problem in org-inlinetask-min-level's docstring? Alain.Cochard
2022-11-25 10:33 ` Ihor Radchenko
2022-12-12 12:33 ` Alain.Cochard
2022-12-13 7:33 ` Ihor Radchenko
2022-12-13 7:36 ` [BUG] org-cycle-max-level is broken, especially when using org-element-cache (was: Problem in org-inlinetask-min-level's docstring?) Ihor Radchenko
2022-12-13 8:37 ` 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=25496.14797.512207.593382@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).