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: Sat, 3 Apr 2021 20:20:02 +0530 [thread overview] Message-ID: <TY2PR0101MB369346CB29F1E48431175B0DDA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw) In-Reply-To: <TY2PR0101MB3693241F18BBA72361376852DA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> On 03/04/21 8:10 pm, Ramesh Nedunchezian wrote: > > > On 03/04/21 2:56 pm, Nicolas Goaziou wrote: >> Hello, >> >> Ramesh Nedunchezian <firstname.lastname@example.org> writes: >> >>> I was expecting that the linter report will be in >>> `compilation-minor-mode`. >> >> Well, it isn't, obviously. >> >>> With things as it is now, is there a way I can quickly move between >>> next or previous errors, when I am in _either_ of the source buffer or >>> the linter report? >> >> You move back to the linter report and proceed from there. I cannot >> think of any other way. > > Here is an attempt. > (defun my-org-lint () > (interactive) When I am re-using "*My Org Lint*" for some other file, I may have to change the `default-directory' as well. As a proof-of-concept the code I shared should hold good.
next prev parent reply other threads:[~2021-04-03 14:50 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 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 [this message] 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=TY2PR0101MB369346CB29F1E48431175B0DDA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com \ --email@example.com \ --firstname.lastname@example.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/)]' \ /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).