From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Hidden files from beamer export, not cleaned up by org
Date: Mon, 01 Dec 2014 10:28:34 -0500 [thread overview]
Message-ID: <87oarncrtp.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87tx1fjwbg.wl-jamshark70@qq.com
James Harkins <jamshark70@qq.com> writes:
> I've just noticed -- after exporting an org file using the beamer
> backend, two hidden files are left in the directory. They both contain
> LaTeX code, so I'm quite sure they're coming from the export.
>
> .fuse_hidden000001c000000001:
> ~~
> \relax
> \providecommand\hyper@newdestlabel[2]{}
> \providecommand\HyperFirstAtBeginDocument{\AtBeginDocument}
> \HyperFirstAtBeginDocument{\ifx\hyper@anchor\@undefined
> \global\let\oldcontentsline\contentsline
> \gdef\contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}}
> ~~ ... And so on, for 90 lines
>
> .fuse_hidden000001c100000002:
> ~~
> \BOOKMARK [2][]{Outline0.1}{``Lifted''}{}% 1
> \BOOKMARK [2][]{Outline0.2}{``Lifted''\040sounds}{}% 2
> ~~
>
> Unlike the other LaTeX temporary files, these are not cleaned up after the export.
>
> Bug?
Somewhere but probably not in org - it can't clean up what it does not
know about. What system is this? Does this have anything to do with
http://en.wikipedia.org/wiki/Filesystem_in_Userspace
perhaps?
Nick
next prev parent reply other threads:[~2014-12-01 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 14:09 Hidden files from beamer export, not cleaned up by org James Harkins
2014-12-01 15:28 ` Nick Dokos [this message]
2014-12-01 16:31 ` Nick Dokos
2014-12-03 4:17 ` James Harkins
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=87oarncrtp.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.com \
--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).