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 by 'suspicious-language-in-src-block [9.7.2 (release_N/A-N/A-88dd2c @ /home/user/.emacs.d/elpa/org-9.7.2/)]
Date: Wed, 05 Jun 2024 13:07:39 +0000	[thread overview]
Message-ID: <87cyov7d2c.fsf@localhost> (raw)
In-Reply-To: <87mso035kq.fsf@gmail.com>

"Suhail Singh" <suhailsingh247@gmail.com> writes:

> Any code block in a language that isn't intended to be executed results in a
> warning from 'suspicious-language-in-src-block checker.  For instance:
>
> #+begin_src conf
>   [Unit]
>   Description=Blah
> #+end_src
>
> In the above example, conf-mode exists and is used by Org to provide
> syntax highlighting and yet, org-lint reports a warning.

Org mode has no idea which languages are intended to be executed, but
happen to not have their ob-lang.el backend loaded; and
which languages do not need execution. So, Org mode warns just in case.

You can always ignore this warning.

Not a bug.
Canceled.

(If you have better ideas about how to approach the problem of
misspelled language names, feel free to share them)

-- 
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-05 13:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 18:50 [BUG] org-lint: Spurious warning by 'suspicious-language-in-src-block [9.7.2 (release_N/A-N/A-88dd2c @ /home/user/.emacs.d/elpa/org-9.7.2/)] Suhail Singh
2024-06-05 13:07 ` Ihor Radchenko [this message]
2024-06-05 13:37   ` Suhail Singh
2024-06-05 15:12     ` Ihor Radchenko
2024-06-05 16:04       ` Suhail Singh
2024-06-05 18:59         ` Ihor Radchenko
2024-06-05 19:38           ` Suhail Singh
2024-06-05 20:25             ` Ihor Radchenko
2024-06-05 23:49               ` Suhail Singh
2024-06-06 15:36                 ` 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=87cyov7d2c.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).