From: Ramesh Nedunchezian <firstname.lastname@example.org> To: email@example.com Subject: Re: Bug: Error while exporting o TexInfo. Html export works fine. [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)] Date: Fri, 2 Apr 2021 10:03:48 +0530 [thread overview] Message-ID: <TY2PR0101MB369308F8E1F04D7DC4AE570CDA7A9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw) In-Reply-To: <TY2PR0101MB3693DA652413EA6548970A5ADA7B9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> On 01/04/21 1:47 pm, Ramesh Nedunchezian wrote: > (FWIW, the above snippet is from the README file of Emacs's official ELPA repo. cf. https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/README#n80) While I was trying to convert the above `org' file to `info' I observed the following: 1. org linter report being /unlike/ compilation buffer. 2. source blocks with do /not/ specify a language failing to export. The file has two source blocks like with "empty" language. (Note that there are other src blocks in that file, which /do/ specify language as shell.) #+begin_src make packages/<pkgname> #+end_src and doing C-c C-e i o results in a failure. M-x org-lint produces the following result 44 high Missing language in source block 51 high Missing language in source block While in the lint buffer, I was expecting that M-g M-n, M-g M-p would take me to the relevant source lines. Unfortunately, this isn't the case. And the linter report is derived from `org-lint--report-mode-map' which is derived from `tabulated-list-mode'. The departure from convention surprised me. And .... the following snippet works fine i.e., The linter finds any issue with an "unknown" language but complaints if the "unknown" language happens to be empty. #+begin_src zzzzzzzzzzzzz make packages/<pkgname> #+end_src I wonder why an unknown langauge would be acceptable for export and not a "empty" language. Isn't source blocks with no language equivalent to example blocks.
next prev parent reply other threads:[~2021-04-02 4:34 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 8:17 Ramesh Nedunchezian 2021-04-01 15:16 ` Nicolas Goaziou 2021-04-02 4:09 ` Ramesh Nedunchezian 2021-04-02 14:50 ` Nicolas Goaziou 2021-04-02 4:33 ` Ramesh Nedunchezian [this message] 2021-04-02 14:59 ` Nicolas Goaziou 2021-04-03 4:44 ` Ramesh Nedunchezian 2021-04-03 9:26 ` Nicolas Goaziou 2021-04-03 11:41 ` Ramesh Nedunchezian 2021-04-03 14:40 ` Ramesh Nedunchezian 2021-04-03 14:50 ` Ramesh Nedunchezian 2021-04-03 19:50 ` Nicolas Goaziou 2021-04-04 4:26 ` Ramesh Nedunchezian 2021-04-07 17:59 ` Nicolas Goaziou 2021-04-08 14:00 ` Ramesh Nedunchezian 2021-04-19 9:30 ` Nicolas Goaziou
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=TY2PR0101MB369308F8E1F04D7DC4AE570CDA7A9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Bug: Error while exporting o TexInfo. Html export works fine. [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]' \ /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
Code repositories for project(s) associated with this 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).