From: Ihor Radchenko <yantar92@posteo.net>
To: Malcolm Purvis <malcolm@purvis.id.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Add next-error support to org-lint report buffer
Date: Sat, 28 Dec 2024 15:12:01 +0000 [thread overview]
Message-ID: <87cyhb970e.fsf@localhost> (raw)
In-Reply-To: <m2wmfk1ynb.fsf@purvis.id.au>
Malcolm Purvis <malcolm@purvis.id.au> writes:
> Apologies for the malformed patch. Here it is as an attachment.
Thanks!
> -| {{{kbd(S)}}} | Sort reports by the column at point |
Looks like you deleted this line by accident.
> +*** next-error supports =org-lint= reports
> +
> +The command =next-error= can now be used to jump to the next
> +=org-lint= error.
I just tried your patch on an Org file with 2 warnings and tried to
press C-x ` repeatedly. Upon moving to the last line in *Org lint*
buffer, I got
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
aref(nil 0)
(get-text-property 0 'org-lint-marker (aref (tabulated-list-get-entry) 0))
org-lint--current-marker()
(let ((mk (org-lint--current-marker))) (switch-to-buffer-other-window org-lint--source-buffer) (if (<= (point-min) mk (point-max)) nil (widen)) (goto-char mk) (org-fold-show-set-visibility 'local) (recenter))
org-lint--jump-to-source()
(let ((buffer (current-buffer))) (org-lint--jump-to-source) (switch-to-buffer-other-window buffer))
org-lint--show-source()
org-lint--next-error-function(1 nil)
next-error(nil)
funcall-interactively(next-error nil)
command-execute(next-error)
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-12-28 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 7:25 [PATCH] Add next-error support to org-lint report buffer Malcolm Purvis
2024-12-24 11:02 ` Ihor Radchenko
2024-12-27 23:42 ` Malcolm Purvis
2024-12-28 15:12 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyhb970e.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=malcolm@purvis.id.au \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.