Malcolm Purvis writes:
>
>> There is another problem though. Consider: 1. M-x org-lint
>> 2. Switch back to the original .org buffer 3. M-g M-n 4. Observe
>> link report and .org window swapped and point moving back
>>to the lint report. It is not what usually happens with error
>>
There is another problem though. Consider: 1. M-x org-lint
2. Switch back to the original .org buffer 3. M-g M-n 4. Observe
link report and .org window swapped and point moving back
to the lint report. It is not what usually happens with error
navigation (e.g. during compile or grep na
Malcolm Purvis writes:
> Thanks for the review and happy new year..
>
>>> -| {{{kbd(S)}}} | Sort reports by the column at point |
>> Looks like you deleted this line by accident.
>
> I've restored this in the patch below.
I think you can simply squash the fix with the original patch.
>> I
Thanks for the review and happy new year..
-| {{{kbd(S)}}} | Sort reports by the column at point |
Looks like you deleted this line by accident.
I've restored this in the patch below.
I just tried your patch on an Org file with 2 warnings and tried
to press C-x ` repeatedly. Upon moving to
Malcolm Purvis 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 comma
Thanks for the patch! Unfortunately, the patch seems to be
malformed (something inserted line breaks in inappropriate
places). May you please re-send the patch as an attachment, to
make sure that your MUA does not break things?
Apologies for the malformed patch. Here it is as an attachme
Malcolm Purvis writes:
> Years of muscle memory have made me expect that the output of
> linter tools can be processed with `next-error' (C-x `). This
> isn't the case with org-lint. This patch hooks the org linter
> report into the next-error infrastructure.
Thanks for the patch!
Unfortuna
