emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Tilde not expanded during latex export
Date: Fri, 6 Jan 2023 23:46:38 +0100	[thread overview]
Message-ID: <25528.42190.53674.62381@gargle.gargle.HOWL> (raw)


release_9.6-193-g30314c 

I have file '~/Org/test.org', which contains

   #+begin_src org
     * foo
     bar
   #+end_src

I do 'C-c '' from within the src block, then 'C-c C-e l o' from the
*Org Src test.org[ org ]* buffer.

The minibuffer asks for an output file:
 
   Output file: ~/Org/

I add 'foobar.tex' then <RET> and get:

   Wrote /home/cochard/Org/foobar.tex
   Processing LaTeX file ~/Org/foobar.tex...
   Latexmk: Filename '~/Org/foobar.tex' contains character not allowed
   for TeX file.
   Latexmk: Stopping because of bad filename(s).
   Rc files read:
     /etc/latexmkrc
   Latexmk: This is Latexmk, John Collins, 17 Mar. 2022. Version 4.77,
   version: 4.77.
   if: File "/home/cochard/Org/foobar.pdf" wasn’t produced.  See "*Org
   PDF LaTeX Output*" for details

(that Output buffer just repeats the same info)

Now, if instead I write the '~' explicitly, as

   Output file: /home/cochard/Org/foobar.tex<RET>

then everything goes smoothly and the expected pdf is generated.

Is there a way to circumvent this (minor) inconvenience?

Thanks


-- 
EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 110]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France     | [ slot available for rent ]



             reply	other threads:[~2023-01-06 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 22:46 Alain.Cochard [this message]
2023-01-07 12:16 ` Tilde not expanded during latex export Ihor Radchenko

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=25528.42190.53674.62381@gargle.gargle.HOWL \
    --to=alain.cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).