From: Ihor Radchenko <yantar92@posteo.net>
To: Jason May <jmay@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode version 9.7-pre (9.7-pre-n/a-g093879
Date: Thu, 08 Feb 2024 15:31:47 +0000 [thread overview]
Message-ID: <87sf23ynto.fsf@localhost> (raw)
In-Reply-To: <27899b3fba30cc984e2d8fa4701d26066471f8b9@hey.com>
Jason May <jmay@pobox.com> writes:
> This request was prompted by an issue encounted in org-journal, and it
> probably exists in org-roam and other similar packages.
>
> Ignoring blank lines sounds like a reasonable approach.
It is reasonable, but I am not convinced that it is important enough to
make changes to Org mode syntax.
Allowing blank lines may help with certain types of accidental edits - a
small fraction of possible accidental edits. The benefit is very small.
Too small, IMHO.
> For more significant syntax violations such as your example, perhaps
> org-entry-get and other functions should raise errors instead of
> silently returning nil?
That would require org-entry-get to try searching things that /look
like/ malformed property drawer. This will be (1) slower; (2) defeat the
purpose of changes introduced in Org 8.3
https://orgmode.org/worg/org-release-notes.html#orgaf78411
I am not in favor of such change.
> I'm going to investigate how it might be possible to initiate an org-
> lint if an exception situation was to arise in org-journal.
Org syntax is not restrictive. We deliberately allow people to write
arbitrary text that do not follow strict rules and Org still recognizes
such text as generic text with no special meaning. So, Org mode syntax
has no notion of exceptions.
There are of course common mistakes when writing Org markup. That's why
we have org-lint. However, org-lint is always suggestive - it is an
equivalent of compiler warnings.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-02-08 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 1:42 Org mode version 9.7-pre (9.7-pre-n/a-g093879 Jason May
2024-02-07 17:09 ` Ihor Radchenko
2024-02-08 4:00 ` Jason May
2024-02-08 15:31 ` Ihor Radchenko [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=87sf23ynto.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jmay@pobox.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).