From: Ramesh Nedunchezian <email@example.com> To: 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/)] Date: Sat, 3 Apr 2021 10:14:13 +0530 [thread overview] Message-ID: <TY2PR0101MB369310BAD21001F11A4C2F2ADA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw) In-Reply-To: <email@example.com> On 02/04/21 8:29 pm, Nicolas Goaziou wrote: > Ramesh Nedunchezian <firstname.lastname@example.org> writes: > >> 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. > > I don't know what convention you're talking about and I don't understand > why that would be unfortunate. I think RET will take you to the relevant > source lines whereas TAB and C-j will display them. See manual, or minor > mode docstring, for details. I was expecting that the linter report will be in `compilation-minor-mode`. (info "(emacs) Compilation Mode") If the linter buffer were in compilation mode, I can do M-g M-n, M-g to move to next or previous errors. And these key-presses will work when I am in _either_ of the source org buffer or linter report. 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?
next prev parent reply other threads:[~2021-04-03 5:00 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 [this message] 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=TY2PR0101MB369310BAD21001F11A4C2F2ADA799@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).