Rainer M Krug writes:
> something along the line of "Link to non-existent local file "..." in
> the description part" would make clear that it is ion the description of
> a link.
Done. Thanks.
Regards,
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> OK - now I get it. The syntax implies that I want to display the image
>> located there as the descriptor.
>
> Correct.
>
>> Would it be possible for org-lint to give a more direct warning that this
>> link is in the description and not the li
Rainer M Krug writes:
> OK - now I get it. The syntax implies that I want to display the image
> located there as the descriptor.
Correct.
> Would it be possible for org-lint to give a more direct warning that this
> link is in the description and not the link itself?
Could you suggest an appr
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>>> Here, Org Lint is correct. Link's description is really a link to
>>> a file, "./__BOX__/Aerodynamic", followed by a space, and
>>> "resistances.docx" text.
>>
>> But it is in the description part - shouldn't this be considered "normal
>> tex
Rainer M Krug writes:
>> Here, Org Lint is correct. Link's description is really a link to
>> a file, "./__BOX__/Aerodynamic", followed by a space, and
>> "resistances.docx" text.
>
> But it is in the description part - shouldn't this be considered "normal
> text" whatever it is?
I wish it would
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> The link
>>
>> ,
>> | [[file:__BOX__/Aerodynamic%20resistances.docx][file:./__BOX__/Aerodynamic
>> resistances.docx]]
>> `
>>
>> causes the following warnings:
>>
>> ,
>> | 9094 low Link to non-existent local file
>> "__BOX__
Rainer M Krug writes:
> The link
>
> ,
> | [[file:__BOX__/Aerodynamic%20resistances.docx][file:./__BOX__/Aerodynamic
> resistances.docx]]
> `
>
> causes the following warnings:
>
> ,
> | 9094 low Link to non-existent local file
> "__BOX__/Aerodynamic%20resistances.docx"
Fixed.
One more observation:
The link
,
| [[file:__BOX__/Aerodynamic%20resistances.docx][file:./__BOX__/Aerodynamic
resistances.docx]]
`
causes the following warnings:
,
| 9094 low Link to non-existent local file
"__BOX__/Aerodynamic%20resistances.docx"
| 9094 low Link to non-exi
Hello,
Andreas Leha writes:
> some more spurious warnings I get:
>
>
> 1. Captions with short version:
>
> ,
> | 1105 low Possible missing colon in keyword "#+caption[Data"
> `
>
> 2. header arguments from ob-latex:
>
> ,
> |451 high Unknown header argument "packages"
> |4
Hi Nicolas,
some more spurious warnings I get:
1. Captions with short version:
,
| 1105 low Possible missing colon in keyword "#+caption[Data"
`
2. header arguments from ob-latex:
,
|451 high Unknown header argument "packages"
|451 high Unknown header argument "imoutop
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> Concerning ignoring: it would be nice to dynamically exclude certain
>> types of messages - i.e. hiding them from the results of the
>> linting. I don't think this is possible at
>> the moment?
>>
>> I have literally about 100 names with a col
Rainer M Krug writes:
> Concerning ignoring: it would be nice to dynamically exclude certain
> types of messages - i.e. hiding them from the results of the
> linting. I don't think this is possible at
> the moment?
>
> I have literally about 100 names with a colon - so these messages are
> oversh
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> 1) not identifying header argument with +
>> ,
>> | #+PROPERTY: header-args+ :tangle no
>> `
>>
>> results in
>>
>> ,
>> | 87 high Unknown header argument ""
>> `
>
> This should be fixed.
Thanks.
>
>> 2) not knowing header
Rainer M Krug writes:
> 1) not identifying header argument with +
> ,
> | #+PROPERTY: header-args+ :tangle no
> `
>
> results in
>
> ,
> | 87 high Unknown header argument ""
> `
This should be fixed.
> 2) not knowing header argument "file-ext" from R
> ,
> | #+begin_src R
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> Well - now it does. The following produces the error:
>>
>> #+PROPERTY: header-args :tangle-mode (identity #o444)
>>
>> * Some code
>>
>> #+begin_src R :results nons
>>
>> #+end_src
>>
>> The problem is the (identity #o444) which is causing t
Rainer M Krug writes:
> Well - now it does. The following produces the error:
>
> #+PROPERTY: header-args :tangle-mode (identity #o444)
>
> * Some code
>
> #+begin_src R :results nons
>
> #+end_src
>
> The problem is the (identity #o444) which is causing the problem.
Fixed. Thank you.
Regards,
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> Two more questions:
>>
>> I get the following warnings:
>>
>> ,
>> | 10 low Unknown OPTIONS item "@"
>> | 11 low Unknown OPTIONS item "skip"
>> | 11 low Unknown OPTIONS item "LaTeX"
>> | 11 low Unknown OPTIONS item
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> Two more questions:
>>
>> I get the following warnings:
>>
>> ,
>> | 10 low Unknown OPTIONS item "@"
>> | 11 low Unknown OPTIONS item "skip"
>> | 11 low Unknown OPTIONS item "LaTeX"
>> | 11 low Unknown OPTIONS item
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> Two more questions:
>>
>> I get the following warnings:
>>
>> ,
>> | 10 low Unknown OPTIONS item "@"
>> | 11 low Unknown OPTIONS item "skip"
>> | 11 low Unknown OPTIONS item "LaTeX"
>> | 11 low Unknown OPTIONS item
Rainer M Krug writes:
> Two more questions:
>
> I get the following warnings:
>
> ,
> | 10 low Unknown OPTIONS item "@"
> | 11 low Unknown OPTIONS item "skip"
> | 11 low Unknown OPTIONS item "LaTeX"
> | 11 low Unknown OPTIONS item "TeX"
> `
>
> based on the followi
Nicolas Goaziou writes:
> Rainer M Krug writes:
>
>> There is an example where I get the error:
>>
>> * Fitting the kernel to the data
>> The parameter which will be fitted can be found in Table [[tab:fitInitial]]
>>
>> #+CAPTION: Variables used for the initial fit of the wind profile using the
Rainer M Krug writes:
> There is an example where I get the error:
>
> * Fitting the kernel to the data
> The parameter which will be fitted can be found in Table [[tab:fitInitial]]
>
> #+CAPTION: Variables used for the initial fit of the wind profile using the
> function and the initial values.
Envoyé de mon iPhone
> Le 20 mai 2015 à 22:42, Andreas Leha a
> écrit :
>
> Hi Rainer,
>
> Rainer M Krug writes:
>> Rainer M Krug writes:
>>
>>> Rainer M Krug writes:
>>>
Andreas Leha writes:
> Hi Rainer,
>
> Rainer M Krug writes:
>> Nicolas Goaziou writes
Hi Rainer,
Rainer M Krug writes:
> Rainer M Krug writes:
>
>> Rainer M Krug writes:
>>
>>> Andreas Leha writes:
>>>
Hi Rainer,
Rainer M Krug writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> The following library implements linting for Org syntax. The sol
Rainer M Krug writes:
> Rainer M Krug writes:
>
>> Andreas Leha writes:
>>
>>> Hi Rainer,
>>>
>>> Rainer M Krug writes:
Nicolas Goaziou writes:
> Hello,
>
> The following library implements linting for Org syntax. The sole public
> function is `org-lint', which see.
Rainer M Krug writes:
> Andreas Leha writes:
>
>> Hi Rainer,
>>
>> Rainer M Krug writes:
>>> Nicolas Goaziou writes:
>>>
Hello,
The following library implements linting for Org syntax. The sole public
function is `org-lint', which see.
Internally, the library defi
Andreas Leha writes:
> Hi Rainer,
>
> Rainer M Krug writes:
>> Nicolas Goaziou writes:
>>
>>> Hello,
>>>
>>> The following library implements linting for Org syntax. The sole public
>>> function is `org-lint', which see.
>>>
>>> Internally, the library defines a new structure: `org-lint-checker
Hi Nicolas,
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> * Test code block names
>>
>> #+name: test
>> #+begin_src R :results none
>> 1:10
>> #+end_src
>
> OK. It was a R-specific bug. It should now be fixed.
>
Thank you! Fix confirmed. The last warning is gone.
Thanks,
Andreas
Andreas Leha writes:
> * Test code block names
>
> #+name: test
> #+begin_src R :results none
> 1:10
> #+end_src
OK. It was a R-specific bug. It should now be fixed.
Thank you.
Regards,
Hi Nicolas,
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> But I still get
>>
>> 191 low Unknown value "none" for header ":results"
>
> Could you show an ECM? I cannot reproduce it.
>
Sure:
--8<---cut here---start->8---
* Test code block names
#+name:
Andreas Leha writes:
> But I still get
>
> 191 low Unknown value "none" for header ":results"
Could you show an ECM? I cannot reproduce it.
Regards,
Hi Nicolas,
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> I just pulled and rebased again. The "never-export" issue is
>> gone, indeed. The others are still there. What am I missing
>> here?
>
> Nothing. I overlooked a typo. It should be fixed in wip-lint.
Thanks. Now the :tangle heade
Andreas Leha writes:
> I just pulled and rebased again. The "never-export" issue is
> gone, indeed. The others are still there. What am I missing
> here?
Nothing. I overlooked a typo. It should be fixed in wip-lint.
Thank you.
Regards,
Hi Nicolas,
Nicolas Goaziou writes:
>> I have finally made some time to test this. I get some
>> unexpected warnings:
>>
>>79 low Unknown value "myfile.R" for header ":tangle"
>> 192 low Unknown value "none" for header ":results"
>
> Make sure you rebased the wip-lint branch on top of m
Rainer M Krug writes:
> This sounds very interesting and I would like to try it out. I
> understand that it can't be put into master, but could it be put into a
> branch?
It already lives in "wip-lint" branch.
Regards,
Hi Rainer,
Rainer M Krug writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> The following library implements linting for Org syntax. The sole public
>> function is `org-lint', which see.
>>
>> Internally, the library defines a new structure: `org-lint-checker',
>> with the following slots:
>>
>
Hello,
Andreas Leha writes:
> I have finally made some time to test this. I get some
> unexpected warnings:
>
>79 low Unknown value "myfile.R" for header ":tangle"
> 192 low Unknown value "none" for header ":results"
Make sure you rebased the wip-lint branch on top of master.
> 22985
Nicolas Goaziou writes:
> Hello,
>
> The following library implements linting for Org syntax. The sole public
> function is `org-lint', which see.
>
> Internally, the library defines a new structure: `org-lint-checker',
> with the following slots:
>
> - NAME: Unique check identifier, as a symbo
Nicolas Goaziou writes:
> Hello,
>
> The following library implements linting for Org syntax. The sole public
> function is `org-lint', which see.
>
> Internally, the library defines a new structure: `org-lint-checker',
> with the following slots:
>
> - NAME: Unique check identifier, as a symbol
> -Original Message-
> On
> Behalf Of Nicolas Goaziou
> Sent: Sunday, 2015 April 19 09:32
> To: Org Mode List
> Subject: [O] [RFC] Org linting library
>
> Hello,
>
> The following library implements linting for Org syntax. The sole
> public
> function is `org-lint', which see.
> Nicolas
Sebastien Vauban
writes:
> Could `org-lint' return a success/fail indication, so that we could
> write something along in an export hook:
>
> (if (org-lint)
> ... continue with export ...
> ... stop with message or display the lint buffer ...)
>
> As well, could the buffer be hidden (or k
Nicolas Goaziou wrote:
> Here's another update. I added a few more tests.
>
> If there's no more bug report or feedback, I'll simply put it in
> a "wip-lint" branch until Org 8.4 starts its development cycle.
Could `org-lint' return a success/fail indication, so that we could
write something along
Nicolas Goaziou writes:
> Here's another update. I added a few more tests.
>
> If there's no more bug report or feedback, I'll simply put it in
> a "wip-lint" branch until Org 8.4 starts its development cycle.
This is handy! No bugs to report.
Sebastien Vauban
writes:
> I'd like to enforce org-lint on all my Org docs, either in a find-file
> hook or before export, for example.
>
> Can't you put it in master as well?
No, I can't.
As explained in the original post, "org-lint.el" requires at least Emacs
24.3 (lexical binding, pcase,
Here's another update. I added a few more tests.
If there's no more bug report or feedback, I'll simply put it in
a "wip-lint" branch until Org 8.4 starts its development cycle.
Regards,
org-lint.el
Description: application/emacs-lisp
Hello Nicolas,
Nicolas Goaziou wrote:
> Here's another update. I added a few more tests.
>
> If there's no more bug report or feedback, I'll simply put it in
> a "wip-lint" branch until Org 8.4 starts its development cycle.
I'd like to enforce org-lint on all my Org docs, either in a find-file
ho
Marco Wahl writes:
> I think it's too much that org-lint tries to follow ssh links.
It doesn't follow remote paths.
> 2278 low Link to non-existent local file
> "///ssh:root@127.0.0.1#:/etc/httpd/conf/httpd.conf"
^ ^^^
There's a bug in the par
"Charles C. Berry" writes:
>> - orphaned affiliated keywords
>
> This generates an orphaned keyword warning, but seems innocuous and is
> what babel renders.
>
> #+NAME: abc
> #+BEGIN_SRC emacs-lisp
> nil #+END_SRC
>
> #+RESULTS: abc
Indeed, it is innocuous. It is meant to catch, e.g.,
#+CA
On Sun, 19 Apr 2015, Nicolas Goaziou wrote:
Hello,
The following library implements linting for Org syntax. The sole public
function is `org-lint', which see.
Nice!
Comments below.
Internally, the library defines a new structure: `org-lint-checker',
with the following slots:
[snip]
Hi!
Nicolas Goaziou writes:
> The following library implements linting for Org syntax. The sole public
> function is `org-lint', which see.
Great, thanks a lot. Already found some issues with some org-files.
> Results are displayed in a special "*Org Lint*" buffer with a dedicated
> major mod
Rasmus writes:
> It looks like a great tool. Especially given the fact that the org format
> still seems to be developing.
Indeed. We can use it as another channel for syntax deprecation.
> Anyway, some very premature notes:
>
> One venue that may worth pursuing is better error messages during
Hi,
Nicolas Goaziou writes:
> Since it relies on lexical binding, `pcase' and `string-prefix-p', it
> cannot be added to Org 8.3, but can make it into Org 8.4, if deemed
> useful enough.
It looks like a great tool. Especially given the fact that the org format
still seems to be developing.
An
52 matches
Mail list logo
