emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Suhail Singh <suhailsingh247@gmail.com>,  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: Thu, 06 Jun 2024 20:01:28 -0400	[thread overview]
Message-ID: <877cf1boyv.fsf@gmail.com> (raw)
In-Reply-To: <87a5jz7cqv.fsf@localhost> (Ihor Radchenko's message of "Wed, 05 Jun 2024 13:14:32 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> "Suhail Singh" <suhailsingh247@gmail.com> writes:
>
>> When there is, say, an "example" result block that is indented (i.e.,
>> the entire block including the delimiters is indented) and it contains
>> some asterisks in the middle, org-lint considers it to be a possible
>> case of misplaced-heading.  Case in point:
>>
>> #+begin_src org
>>   - Some words
>>     ,#+begin_example
>>       this is a line with asterisks** in the middle
>>     ,#+end_example
>> #+end_src
>>
>> The lint check should guard against occurrences that happen within code
>> blocks.
>
> Makes sense.
> Fixed, on bugfix.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=b8497aa7f

This doesn't seem fixed as of 9.7.3 (the MRE above still shows spurious
warning).  It seems that org-at-block-p returns nil when point is within
the block.

-- 
Suhail


  reply	other threads:[~2024-06-07  0:02 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 [this message]
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
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=877cf1boyv.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --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).