emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
To: 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, 3 Apr 2021 20:10:49 +0530	[thread overview]
Message-ID: <TY2PR0101MB3693241F18BBA72361376852DA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <87v993pvlw.fsf@nicolasgoaziou.fr>



On 03/04/21 2:56 pm, Nicolas Goaziou wrote:
> Hello,
> 
> Ramesh Nedunchezian <rameshnedunchezian@outlook.com> 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)
  (let* ((file (buffer-file-name))
	 (file (file-relative-name (buffer-file-name) default-directory))
	 (lint-alist (org-lint))
	 (inhibit-read-only t)
	 ;; Choose a format that matches any of error regexps in
	 ;; `compilation-error-regexp-alist-alist'
	 (msg-fmt "%f: line %l: %m"))
    (with-current-buffer
	(or
	 (get-buffer-create "*My Org Lint*"))
      (pop-to-buffer
       (current-buffer))
      (erase-buffer)
      (let ((filename (buffer-file-name)))
	(save-excursion
	  (insert
	   (mapconcat #'identity
		      (cl-loop for (_ inf) in lint-alist collect
			       (pcase-let ((`[,line ,trust ,msg ,rest] inf))
				 (format-spec msg-fmt
					      (list
					       (cons ?f file)
					       (cons ?l line)
					       (cons ?t trust)
					       (cons ?m msg)))))
		      "\n"))))
      (compilation-mode 1))))

Let myfile.org be a file with following content

    * Getting the source

    - Start with source that is cloned directly from Savannah[fn:1].
      Using a clone of a clone does not work.

      If you are a member of Emacs Project use,  

      #+begin_src
	git clone <membername>@git.savannah.gnu.org:/srv/git/emacs/elpa.git
      #+end_src

      If you are not a member use,

      #+begin_src shell
	git clone https://git.savannah.gnu.org/git/emacs/elpa.git
      #+end_src


    - You must then do some setup:

      #+begin_src
	 make setup
      #+end_src

      That leaves the =packages= directory empty; you must check out the
      ones you want.

then

1. C-x C-f myfile.org  
2. M-x my-org-lint

3. M-g M-n to move between the errors.  M-g M-n would work both in
   linter output buffer and the org source buffer

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





  parent reply	other threads:[~2021-04-03 14:41 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 [this message]
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=TY2PR0101MB3693241F18BBA72361376852DA799@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com \
    --to=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/)]' \
    /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).