From: James Powell <powellj@pdx.edu>
To: emacs-orgmode@gnu.org
Subject: fuzzy link can't be exported when \begin{foo} is there
Date: Fri, 26 Mar 2021 16:55:17 -0700 [thread overview]
Message-ID: <738aa0ec-2e65-1e3c-3c46-f7f6686b05e4@pdx.edu> (raw)
First time poster, long time user. Glad to be here.
This seems to a bug.
- Org mode version 9.4.4
- GNU Emacs 25.3.1
If I write in a little table like this:
: In Table [[tableOne]] I show that this site has AADT 143925, by
TVT_Detailed_2019.xlsx.
:
: #+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 |
It should be org-lint clean and export as a link when I export to
latex. And it is and it does.
So far so good. 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".
If you wish, you may paste the text from <<start>> to <<end>>
noninclusive above in this email to reproduce. The manual says that it
should work: "The following snippets will be identified as LaTeX source
code [...] Environments of any kind" ( *info* (org) LaTeX fragments). I
searched the mailing list for help, I see lots of comments about
org-lint but not so much on this. I scanned the open bugs at
https://updates.orgmode.org/#bugs and nothing seemed relevant.
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.
Many thanks.
- JP
--
James E. Powell, MS
Pronouns: he/him/his
Applied Physics PhD Candidate
Department of Physics
Portland State University
Home page: http://web.pdx.edu/~powellj
Office: SRTC 409B Phone: +1-503-725-8515
next reply other threads:[~2021-03-28 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 23:55 James Powell [this message]
2021-03-30 4:45 ` Kyle Meyer
2021-03-31 19:56 ` James Powell
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=738aa0ec-2e65-1e3c-3c46-f7f6686b05e4@pdx.edu \
--to=powellj@pdx.edu \
--cc=emacs-orgmode@gnu.org \
--subject='Re: fuzzy link can'\''t be exported when \begin{foo} is there' \
/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
Code repositories for project(s) associated with this 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).