emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-lint: Spurious warning from 'misplaced-heading lint-checker [9.7.2 (release_N/A-N/A-88dd2c @ /home/user/.emacs.d/elpa/org-9.7.2/)]
Date: Sat, 08 Jun 2024 15:32:30 +0000	[thread overview]
Message-ID: <87wmmzwiup.fsf@localhost> (raw)
In-Reply-To: <87ed977azf.fsf@gmail.com>

Suhail Singh <suhailsingh247@gmail.com> writes:

> On a related note, what specific situation(s) was this checker intended
> to help the user in?  I.e., what are the situations that could result in
> misplaced headings?

For example,

* Heading 1
* Heading 2* Heading 3
* Heading 4

or

* Heading

Some text inside.
Accidentally deleted newline here* Heading 2

More text

* Heading 3

> While the checker seems to be similar to the 'misplaced-planning-info
> checker in spirit, the difference (in reality) is that the regular
> expression to detect possibly misplaced headings is much easier to get
> false positives for.

Sure. It is difficult to find the right balance between being useful and
generating too many false positives.

-- 
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>


  reply	other threads:[~2024-06-08 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 18:42 [BUG] org-lint: Spurious warning from 'misplaced-heading lint-checker [9.7.2 (release_N/A-N/A-88dd2c @ /home/user/.emacs.d/elpa/org-9.7.2/)] Suhail Singh
2024-06-05 13:14 ` Ihor Radchenko
2024-06-07  0:01   ` Suhail Singh
2024-06-07 14:54     ` Ihor Radchenko
2024-06-07 16:03       ` Suhail Singh
2024-06-08 14:41         ` Suhail Singh
2024-06-08 15:32           ` Ihor Radchenko [this message]
2024-06-08 15:51             ` Suhail Singh
2024-06-08 19:09               ` 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=87wmmzwiup.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=suhailsingh247@gmail.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).