emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Org-lint and #+call lines
Date: Tue, 28 Apr 2015 22:18:20 +0200	[thread overview]
Message-ID: <87zj5sj9bn.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2a8xsm33n.fsf@tsdye.com> (Thomas S. Dye's message of "Tue, 28 Apr 2015 10:04:28 -1000")

tsd@tsdye.com (Thomas S. Dye) writes:

> Another false positive, I think:
>
>   1360 low   Unknown value "no" for header ":eval"

Fixed too, and also cherry-picked from wip-lint.

> Also, after I run org-lint I sometimes lose the cursor.  The frame
> around the *Org Lint* window flickers a bit, as if *Org Lint* is being
> refreshed over and over.

It should only refresh if you press `g' in lint buffer.

> Apologies in advance for such a vague report. I'm not sure where to
> start debugging something like this.

You can debug `org-lint--generate-reports'. It is the function
responsible for refreshing the buffer. It should only be called once
after "M-x org-lint" and every time *Org Lint* buffer is refreshed
(i.e., with `g').


Regards,

  reply	other threads:[~2015-04-28 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 23:03 Org-lint and #+call lines Thomas S. Dye
2015-04-27  6:54 ` Nicolas Goaziou
2015-04-27  7:23   ` Thomas S. Dye
2015-04-27  7:39     ` Nicolas Goaziou
2015-04-27 11:38       ` Nicolas Goaziou
2015-04-27 15:25         ` Thomas S. Dye
2015-04-28  5:44         ` Thomas S. Dye
2015-04-28  7:57           ` Nicolas Goaziou
2015-04-28 20:04             ` Thomas S. Dye
2015-04-28 20:18               ` Nicolas Goaziou [this message]
2015-05-28 12:45 ` Org-lint (was: Org-lint and #+call lines) Karl Voit
2015-05-28 17:28   ` Org-lint 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=87zj5sj9bn.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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).