emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: James Powell <powellj@pdx.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: fuzzy link can't be exported when \begin{foo} is there
Date: Tue, 30 Mar 2021 00:45:57 -0400	[thread overview]
Message-ID: <87r1jx2qre.fsf@kyleam.com> (raw)
In-Reply-To: <738aa0ec-2e65-1e3c-3c46-f7f6686b05e4@pdx.edu>

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.


  reply	other threads:[~2021-03-30  4:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 23:55 James Powell
2021-03-30  4:45 ` Kyle Meyer [this message]
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=87r1jx2qre.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=powellj@pdx.edu \
    --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).