emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Dominik Schrempf <dominik.schrempf@gmail.com>
Cc: Emacs Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Org lint and named source blocks
Date: Tue, 21 Sep 2021 21:18:55 +0800	[thread overview]
Message-ID: <87o88mqd6o.fsf@localhost> (raw)
In-Reply-To: <87h7ee5q8u.fsf@gmail.com>

Dominik Schrempf <dominik.schrempf@gmail.com> writes:

> Running =org-lint= on an Org file containing
> #+NAME:Hello
> #+BEGIN_SRC emacs-lisp :exports code
> I get the following error:
> #+begin_quote
> Debugger entered--Lisp error: (search-failed "^[ \11]*#\\+[A-Za-z]+: +Hello *$")
> #+end_quote


This one is tricky. The linter (org-lint-duplicate-name) expects that
NAME keyword must have space before value. However, the actual Org
parser (org-element--collect-affiliated-keywords) does not care about
space. My intuition says that the parser behaviour is
unintentional. However, not requiring a whitespace may also be a valid

Dear Orgers,

Should we allow syntax like #+KEYWORD:value to be correct or do we
require a whitespace/space after colon all the time?


  reply	other threads:[~2021-09-21 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  7:39 Org lint and named source blocks Dominik Schrempf
2021-09-21 13:18 ` Ihor Radchenko [this message]
2021-09-21 20:32   ` Tom Gillespie
2021-10-04  6:19     ` Ihor Radchenko
2021-10-04  8:02       ` Tom Gillespie
2021-10-04  8:21         ` Timothy
2021-10-04  9:14           ` Tom Gillespie
2021-10-04  6:16   ` 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:

  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=87o88mqd6o.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=dominik.schrempf@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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