emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: links to filename containing word "loops" fail to export
Date: Sun, 16 Aug 2020 12:04:14 +0200	[thread overview]
Message-ID: <87d03qq541.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874kp4m18t.fsf@iki.fi> (Jarmo Hurri's message of "Sat, 15 Aug 2020 17:29:06 +0300")

Hello,

Jarmo Hurri <jarmo.hurri@iki.fi> writes:

> * Links to files containing the word ~loops~ are not exported
> ** What is the problem?
>    It seems that if a link to a file contains the word ~loops~,
>    it is not exported at all.
> ** How to replicate
>    1. Save this org into file =org-loops-in-link.org=
>    2. Save the following elisp into =minimal-org.el=, replacing the
>      location of org mode with your path:
>
>      #+begin_src elisp
>        (add-to-list 'load-path (expand-file-name "~/src/org-mode/lisp"))
>        (add-to-list 'load-path (expand-file-name "~/src/org-mode/contrib/lisp" t))
>      #+end_src
>
>    3. Open this file with
>
>       #+begin_src sh
>         emacs -Q -l minimal-org.el org-loops-in-link.org
>       #+end_src
>
>    4. Export to latex as a PDF file and open (C-c C-e l o), observing
>       missing items when the list below is exported:
>       - [[file:loopy.org]]
>       - [[file:loops.org]]
>       - [[file:loopz.org]]
>       - [[file:some-loops.org]]
>       - [[file:some-loopz.org]]

Fun bug. This should be fixed (make sure to start from the new value for
org-latex-inline-image-rules if you customized it).

Thank you.

Regards,
-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2020-08-16 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-15 14:29 Bug: links to filename containing word "loops" fail to export Jarmo Hurri
2020-08-16 10:04 ` Nicolas Goaziou [this message]
2020-08-16 10:30   ` Jarmo Hurri

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=87d03qq541.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarmo.hurri@iki.fi \
    /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 public 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).