[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fuzzy link can't be exported when \begin{foo} is there
From: |
Kyle Meyer |
Subject: |
Re: fuzzy link can't be exported when \begin{foo} is there |
Date: |
Tue, 30 Mar 2021 00:45:57 -0400 |
James Powell writes:
> First time poster, long time user. Glad to be here.
Welcome.
> This seems to a bug.
[...]
> When I add some latex in the middle:
> <<start>>
> In Table [[tableOne]] I show that this site has AADT 143925, by
> TVT_Detailed_2019.xlsx.
>
> \begin{landscape}
> #+NAME: tableOne
> #+CAPTION: Site 26016 has AADT 143925.
> | SITE_ID | LRM | BEGMP | ENDMP | CLASS_01 | [...] | AADT |
> K_FACTOR | D_FACTOR | Ton_Factor |
> | 26016 | 00100I00 | 297.31 | 298.93 | 0.11 | [...] | 143925
> | 7.5 | 52 | 4 |
> \end{landscape}
> <<end>>
> I expect it to keep on working. But instead, now I get
>
> : 1 high Unknown fuzzy location "tableOne"
> in org-lint. Latex export reports "BROKEN LINK".
I believe the above text is sent as is (i.e. that won't be processed as
an Org table). Calling org-element-at-point on it reports that it's a
latex-environment.
Perhaps you want
--8<---------------cut here---------------start------------->8---
#+LATEX: \begin{landscape}
#+NAME: tableOne
#+CAPTION: Site 26016 has AADT 143925.
| SITE_ID | LRM | BEGMP | ENDMP | CLASS_01 | [...] | AADT | K_FACTOR |
D_FACTOR | Ton_Factor |
| 26016 | 00100I00 | 297.31 | 298.93 | 0.11 | [...] | 143925 | 7.5 |
52 | 4 |
#+LATEX: \end{landscape}
--8<---------------cut here---------------end--------------->8---
> Incidentally I started this bug report with org-mode 9.3.6. Back in
> 9.3.6, it was worse: not only would org-lint report 'unknown fuzzy'
> and latex export say "BROKEN LINK" but also C-c C-o
> (org-open-at-point) would fail to find the target and make the jump.
The type error was guarded against with 3bb073b63 (ol: Fix type error in
org-link-search corner case, 2020-11-30). There's no name here, so it
then falls back to fuzzy search.
Compare
(org-element-property :name (org-element-at-point))
in with point on the table in your original snippet and the suggested
one above.