From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id YNHPNfb+qmM8ngAAbAwnHQ (envelope-from ) for ; Tue, 27 Dec 2022 15:19:35 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id sF30NPb+qmP+AgAAG6o9tA (envelope-from ) for ; Tue, 27 Dec 2022 15:19:34 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 8D2032E72C for ; Tue, 27 Dec 2022 15:19:34 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pAAnK-00027G-Qj; Tue, 27 Dec 2022 09:19:06 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAAnI-00026E-19 for emacs-orgmode@gnu.org; Tue, 27 Dec 2022 09:19:04 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAAnE-0006C6-Ii for emacs-orgmode@gnu.org; Tue, 27 Dec 2022 09:19:03 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 88D832401A6 for ; Tue, 27 Dec 2022 15:18:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1672150738; bh=YfO31jVRKlDPKWwplSE+JbE5kdGNsISgvO8G/75RlI8=; h=From:To:Cc:Subject:Date:From; b=Z2ZM/LfA3j6mHLcl6frBTL1Zl2L6pRpKap2OqDRDxj5OxsoGYjFZHc741q5t7+fAA dwkWAwtjHZKofUNLbhNy0yn+fDb4euDofDsWBZWPoRYb7WZR+7QlM7yIBGSsat4R3f c7V8LRx04f3tHOussM4gUARKtKj8Ry6FOK/hY6M8wjs4xz7X2q4gK122rwavBR1/lP Q5wYkD0lxt/KBZ06x5LnO6fn5SXybcy5RdXEaC4GbzLMqmxMN1f6PHwaX+2xI30G+i V6g9sYualGqqGufYrgD/8aTqHijHk2rOUReYiwh/nugZamsWAYTeYKKOMRpmu2Nbe1 vyM9bojVaC8Ig== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NhGww6wrdz9rxF; Tue, 27 Dec 2022 15:18:56 +0100 (CET) From: Ihor Radchenko To: Max Nikulin Cc: emacs-orgmode@gnu.org Subject: [FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?) In-Reply-To: References: <116c3126-32cc-44d0-9e95-e802161e1e84@app.fastmail.com> <87fsdhui6z.fsf@localhost> <86pmckvisp.fsf@gmail.com> <878rj8u2na.fsf@localhost> Date: Tue, 27 Dec 2022 14:18:49 +0000 Message-ID: <87wn6d0w1i.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1672150774; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=pRULgOztPTCm7eTwqAetaxCRrjpAWOxyimu4pNxnAJ0=; b=o2INbbu6pCmNwyM3H0Jy0RDZWqow5hbAC9oa2bORNXuVbdyKXtEC9Zx/xZBVhVAw7N+QUW LW+M1FHPV2xtxV0FoHLL9zZuTtylWooIQ8Fa41PVf0i2deyuaM1XoEqn3KgzwIuYJy8Dko iChgf27N31ApJ+ApwqGP4NNs5+WrBTJYxlWsqD72wUV7e7oXe1fAFg8EIcWy5UhY/Q3pmq GGWfuNIQys5jipdOUYX4N7SvRRRnfspqCwH1Y2IY98XJiM9pgzz2rn8uT70VyzEJBktl9I Jqki37Dkh2fCgrCF+7wrxaBRD3axRtKesTXndPsOJmuHHj+VKdkRhooqNqBztQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="Z2ZM/LfA"; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1672150774; a=rsa-sha256; cv=none; b=f79VVLiEb6SMl+CaLkcIrhtq4uI6WjNTktos00QpxH3SH68kL1sJM0DoY/NKbOI653hMKb +SHWjOF9ddnjV1iyk1BKTE859Avf3GCIrFmJOUmLPjM8XNjZHbsk0FH+34W+6qECAkx/eJ EJrxJ21/K11WppJzC2wGVyngw3RQk4v+4VmHr4fr4nKdwYWJoaLZkodh6aen0rax+iXQBS UgsQwS1W4OPu4sw96Rs09t3cv1cx1U11VYeHu/APgSFk9NxfSiaT6c4y/6KL59PXeXgf9d GbQ3PrZkpXcF11E3KofiygF7Q1K3XfBwY4qp5KNSvVBofS/TXpTeCWJpYJi3cg== X-Spam-Score: -4.47 X-Migadu-Queue-Id: 8D2032E72C Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="Z2ZM/LfA"; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -4.47 X-TUID: aCEnlK73Y3PO As Max proposed, it may be a good idea to extend the concept of org-lint to export. We may unify the LaTeX errors, some errors/warnings potentially signalled by export backend, and maybe some warnings from org-lint during the export process. These errors can ideally be displayed just like in org-lint, with ability to jump to the problematic LoCs in Org/intermediate file. This is a medium task and one will need to: 1. Generalize org-lint interactive interface (list of errors) to work with other code. Extract it into a separate library. 2. Accumulate export issues into a list to be displayed. For example, broken links can be displayed 3. Make functions like `org-latex-compile' accumulate LaTeX errors as well. (Optionally) associate LaTeX buffer lines with Org source. 4. Display the list of errors/warnings at the end of successful or failed export. Each step if fairly simple, except optional part in 3. Patches welcome! Max Nikulin writes: > ... Exporter may issue warnings, they are > collected and presented to user in a temporary window with buffer names > and line numbers as in compilation-minor-mode. The user may see that > something goes wrong, but if their does not switch to the warnings > window then it disappears. It would be great if exporters and lint share > code generating warnings. Another issue that mature development tools > usually allows to suppress particular warning for a specific line. It > may be a problem taking into account specific of Org syntax. > > As to `org-lint', I believe, it is hard to discover for new users and > there should be a reason to run it. It easy to forget about it even when > some problem is faced. It is mentioned in the manual, but > - https://orgmode.org/manual/Feedback.html does not request to run > org-lint before reporting a bug > - `org-submit-bug-report' neither suggest `org-lint' nor runs it as a > check. Likely it should be suppressed (with appropriate report) for > large buffers. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at