emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
Cc: emacs-orgmode@gnu.org
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: Sat, 03 Apr 2021 21:50:17 +0200	[thread overview]
Message-ID: <87r1jrp2py.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <TY2PR0101MB3693241F18BBA72361376852DA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (Ramesh Nedunchezian's message of "Sat, 3 Apr 2021 20:10:49 +0530")

Ramesh Nedunchezian <rameshnedunchezian@outlook.com> writes:

> The advantage is you move to an error, fix it, then M-g M-n, fix it
> and so on and so forth.

But all reports are not errors. You may not want to fix them all either.
OTOH, you lose the ability to hide or ignore unwanted reports, or sort
them by trust level. 

I don't think this is a net win. Maybe other users of Org Lint may want
to chime in.

Regards,


  parent reply	other threads:[~2021-04-03 19:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  8:17 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/)] 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
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 [this message]
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=87r1jrp2py.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rameshnedunchezian@outlook.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).