Hello,
Dominik Schrempf writes:
> I have the following in-buffer variable set:
>
> #+SETUPFILE: https://path/to/some/setupfile.setup
>
> Org lint reports
>
> 17 low Non-existent setup file "https://path/to/some/seutpfile.setup
>
> This is true, but also not very relevant.
Fixed. Thank you.
Hi,
I have the following in-buffer variable set:
#+SETUPFILE: https://path/to/some/setupfile.setup
Org lint reports
17 low Non-existent setup file "https://path/to/some/seutpfile.setup
This is true, but also not very relevant. Should we check for URLs with
org-lint?
Kind regards,
Dominik
On Friday, 25 Aug 2017 at 15:25, Nicolas Goaziou wrote:
> Hello,
>
> Eric S Fraga writes:
>
>> In tracking down another problem with the latest version of org (more to
>> follow probably), I thought using org-lint might help. With the
>> attached simple example, I get:
>>
>> 5 high Missing
Hello,
Eric S Fraga writes:
> In tracking down another problem with the latest version of org (more to
> follow probably), I thought using org-lint might help. With the
> attached simple example, I get:
>
> 5 high Missing definition for footnote [1]
>
> from org-lint.
>
> The footnote def
In tracking down another problem with the latest version of org (more to
follow probably), I thought using org-lint might help. With the
attached simple example, I get:
5 high Missing definition for footnote [1]
from org-lint.
The footnote definition is there as it's inline...
--
: Eric
Hi, again,
On 11/22/2016 12:25 PM, Nicolas Goaziou wrote:
Hello,
Charles Millar writes:
The following is not a critical issue.
I use ob-rec to generate tables from my recfiles.
org-lint issues a warning for ob-recs parameters, such as data, type,
fields, sort, etc.
Is there some code tha
Hello,
Charles Millar writes:
> The following is not a critical issue.
>
> I use ob-rec to generate tables from my recfiles.
>
> org-lint issues a warning for ob-recs parameters, such as data, type,
> fields, sort, etc.
>
> Is there some code that I could include in my .emacs to avoid the
> warn
Hi,
The following is not a critical issue.
I use ob-rec to generate tables from my recfiles.
org-lint issues a warning for ob-recs parameters, such as data, type,
fields, sort, etc.
Is there some code that I could include in my .emacs to avoid the
warnings? For that matter is this an issue
Karl Voit writes:
> I've done org-lint on [1] which was finished quite fast - so it's not
> an issue with my huge files only: I had to kill -9 Emacs to quit.
You can select individual checkers or categories for org-lint (see
docstring). It may be interesting to find which checker it faulty.
I gu
* Nicolas Goaziou wrote:
> Hello,
Hi Nicolas!
> Karl Voit writes:
>
> It is. C-g with `toggle-debug-on-quit' would be interesting. Also, you
> could bisect your document to check if is really coming from its sheer
> size or from particular structure in it.
I have several Org-mode related issue
Hello,
Karl Voit writes:
> Independent to your resolved issue: on my Org-mode files with 30,000
> to 40,000 lines of Org-mode my computer took up to 12 hours to
> finish org-lint.
>
> Interesting fact: after finishing and saving the results, GNU/Emacs
> runs into an endless-loop when I try to ex
* Gregor Zattler wrote:
>
> I run org-lint on one of my org-mode buffers -- 13015 lines with
> ~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.
Independent to your resolved issue: on my Org-mode files with 30,000
to 40,000 lines of Org-mode my computer took up to 12 hours to
finish
Hello,
Gregor Zattler writes:
> I fixed another org-mode file and there is another strange
> behaviour of org-lint:
>
> org-lint complains:
> 9846 high Incorrect contents for PROPERTIES drawer
>
> because of this:
>
> * watermelon watermelon watermelon
> :PRO
Hello,
Gregor Zattler writes:
> org-lint cpmlains:
> 10702 low Misplaced planning info line
>
> because of this:
>
> * DONE xxx X x X
> DEADLINE: <2011-11-25 Fr> CLOSED: [2011-12-17 Sa 21:42]
> <2011-11-22 Di>
> :LOGBOOK:
> - State
Hi Nicolas, org-mode developers,
I fixed another org-mode file and there is another strange
behaviour of org-lint:
org-lint complains:
9846 high Incorrect contents for PROPERTIES drawer
because of this:
* watermelon watermelon watermelon
:PROPERTIES:
:
Hi Nicolas, org-mode developers,
org-lint cpmlains:
10702 low Misplaced planning info line
because of this:
* DONE xxx X x X
DEADLINE: <2011-11-25 Fr> CLOSED: [2011-12-17 Sa 21:42]
<2011-11-22 Di>
:LOGBOOK:
- State "DONE" from
Nicolas Goaziou writes:
> Hello,
>
> Thomas S. Dye writes:
>
>>> In the process of tracking down misbehavior during export, I ran
>>> org-lint, which failed with this error:
>>>
>>> Debugger entered--Lisp error: (wrong-number-of-arguments max 0)
>>> max()
>>> apply(max nil)
>>>
>>> I suspec
Hello,
Thomas S. Dye writes:
>> In the process of tracking down misbehavior during export, I ran
>> org-lint, which failed with this error:
>>
>> Debugger entered--Lisp error: (wrong-number-of-arguments max 0)
>> max()
>> apply(max nil)
>>
>> I suspect I have some error in my Org mode file t
Aloha all,
Answering myself here.
Thomas S. Dye writes:
> Aloha all,
>
> In the process of tracking down misbehavior during export, I ran
> org-lint, which failed with this error:
>
> Debugger entered--Lisp error: (wrong-number-of-arguments max 0)
> max()
> apply(max nil)
>
> I suspect I ha
Aloha all,
In the process of tracking down misbehavior during export, I ran
org-lint, which failed with this error:
Debugger entered--Lisp error: (wrong-number-of-arguments max 0)
max()
apply(max nil)
The backtrace appears to include my entire Org mode file, so I won't
attach it. However, h
Gregor Zattler writes:
> You are right. I bisected the file. There is a ’>’ missing. At
> least with my configuration the attached file ’bad.org’ freezes
> Emacs with latest org-mode (but it is in most cases possible to
> do a C-G):
>
> emacs-snapshot -Q -L ~/src/org-mode/lisp/ -nw bad.org
>
Hi Nicolas,
* Nicolas Goaziou [10. Aug. 2015]:
> Gregor Zattler writes:
>> I run org-lint on one of my org-mode buffers -- 13015 lines with
>> ~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.
>>
>> Is this a bug? I did another run for a few minutes and profiled
>> this on. Profil
Hello,
Gregor Zattler writes:
> I run org-lint on one of my org-mode buffers -- 13015 lines with
> ~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.
>
> Is this a bug? I did another run for a few minutes and profiled
> this on. Profiler reports are attached.
It looks like an inf
Dear org-mode developers,
I run org-lint on one of my org-mode buffers -- 13015 lines with
~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.
Is this a bug? I did another run for a few minutes and profiled
this on. Profiler reports are attached.
This is on
GNU Emacs 25.0.50.7 (i6
Nicolas Goaziou writes:
> Fabrice Niessen writes:
>
>> Though, there is one error with which I don't agree:
>>
>>367 high Missing colon in header argument ")"
>>
>> where line 367 is indicated by "<<<":
>
> Are you sure you are using the latest wip-lint? It should be fixed
> already (commit 4
Fabrice Niessen
writes:
> Though, there is one error with which I don't agree:
>
>367 high Missing colon in header argument ")"
>
> where line 367 is indicated by "<<<":
Are you sure you are using the latest wip-lint? It should be fixed
already (commit 406cfbf2a148c4ea98278603ed5b096bbcdd5
Nicolas Goaziou writes:
> Fabrice Niessen writes:
>
>> Same error with file
>> https://github.com/fniessen/refcard-org-babel/blob/master/docs/eval.org.
>
> I cannot reproduce it.
>
> Could you pull again wip-lint and try one more time? Thank you.
It works, indeed. Sorry.
Though, there is one er
Fabrice Niessen
writes:
> Same error with file
> https://github.com/fniessen/refcard-org-babel/blob/master/docs/eval.org.
I cannot reproduce it.
Could you pull again wip-lint and try one more time? Thank you.
Regards,
Hello,
Nicolas Goaziou writes:
> Fabrice Niessen writes:
>
>> When trying to lint my "Org mode refcard" [1], I get this error:
>>
>> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>
> Fixed. Thank you.
Same error with file
https://github.com/fniessen/refcard-org-babel/blob/master/
Hello,
>> A suggestion here: could Org-lint tell the user to replace such
>> a block:
>>
>> #+PROPERTY: eval never
>> #+PROPERTY: padline yes
>> #+PROPERTY: tangle yes
>>
>> by its newer syntax:
>>
>> #+PROPERTY: header-args :eval never :padline yes :tangle yes
>>
>> ?
>
> Done. Thank you.
Did
Hello,
Sebastien Vauban
writes:
> A suggestion here: could Org-lint tell the user to replace such
> a block:
>
> #+PROPERTY: eval never
> #+PROPERTY: padline yes
> #+PROPERTY: tangle yes
>
> by its newer syntax:
>
> #+PROPERTY: header-args :eval never :padline yes :tangle yes
>
> ?
Done. T
Hello,
Fabrice Niessen
writes:
> When trying to lint my "Org mode refcard" [1], I get this error:
>
> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Rainer M Krug writes:
> Sebastien Vauban writes:
>> A suggestion here: could Org-lint tell the user to replace such
>> a block:
>>
>> #+PROPERTY: eval never
>> #+PROPERTY: padline yes
>> #+PROPERTY: tangle yes
>>
>> by its newer syntax:
>>
>> #+PROPERTY: header-args :eval never :padline yes :
Sebastien Vauban writes:
> Hello,
>
> A suggestion here: could Org-lint tell the user to replace such
> a block:
>
> #+PROPERTY: eval never
> #+PROPERTY: padline yes
> #+PROPERTY: tangle yes
>
> by its newer syntax:
>
> #+PROPERTY: header-args :eval never :padline yes :tangle yes
I agree - t
Hello Nicolas,
When trying to lint my "Org mode refcard" [1], I get this error:
--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
replace-regexp-in-string("[ \n]+\\'" "" nil)
(replace-regexp-in-string "\\`[
Hello,
A suggestion here: could Org-lint tell the user to replace such
a block:
--8<---cut here---start->8---
#+PROPERTY: eval never
#+PROPERTY: padline yes
#+PROPERTY: tangle yes
--8<---cut here---end--->8---
by its newe
Hello,
Karl Voit writes:
> Who do I have to contact, when I've got ideas of checks that
> corrupted my Org-mode files?
You can implement checks and send them to the ML. You can also suggest
them on the ML.
> For example, I have the issue that once upon a Org-mode-Git-
> checkout, the property
* Thomas S. Dye wrote:
>
> Org-lint is a big help picking up an old project. Thanks Nicolas.
Hey, I missed org-lint so far.
However, I was desperately asking for an Org-mode syntax validation
multiple times for a long time.[1]
Who do I have to contact, when I've got ideas of checks that
corrup
t...@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
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Org-lint gives this warning:
>>
>> ,--
>> | 31 low Unknown value "no-export" for header ":eval"
>> `-
t...@tsdye.com (Thomas S. Dye) writes:
> Org-lint gives this warning:
>
> ,--
> | 31 low Unknown value "no-export" for header ":eval"
> `--
>
> But, ob-core.el appears to k
Nicolas Goaziou writes:
> Nicolas Goaziou writes:
>
>>> Is org-lint supposed to catch :results output graphics?
>>
>> It catches
>>
>> :results output graphic
>>
>> Is it
>>
>> :results output graphics
>
> Nevermind.
>
> I realized allowed values and combinations are already known to Babel,
>
Nicolas Goaziou writes:
> I realized allowed values and combinations are already known to Babel,
> so I improved the checker.
Looks good. Org-lint raises many more warnings now.
Thanks,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Nicolas Goaziou writes:
>> Is org-lint supposed to catch :results output graphics?
>
> It catches
>
> :results output graphic
>
> Is it
>
> :results output graphics
Nevermind.
I realized allowed values and combinations are already known to Babel,
so I improved the checker.
> Is org-lint supposed to catch :results output graphics?
It catches
:results output graphic
Is it
:results output graphics
Regards,
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> So, I decided to track wip-lint. Now, the linting stops with this
>> error:
>>
>> ,
>> | Org linting process starting...
>> | let: Wron
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> So, I decided to track wip-lint. Now, the linting stops with this
> error:
>
> ,
> | Org linting process starting...
> | let: Wrong type argument: listp, ":results repl
Aloha all,
Org-lint is a big help picking up an old project. Thanks Nicolas.
The original patch sent to the ML ran through my old org mode file and
found lots of potential problems.
So, I decided to track wip-lint. Now, the linting stops with this
error:
,-
48 matches
Mail list logo
