Re: LilyPond 2.23.6 *-tmp-* files

[Simon Bailey]

For what it’s worth, this happened to me recently using frescobaldi on windows 
while having one of the resulting PDFs open in Adobe Acrobat. This may be 
something similar – most PDF readers lock the files, so lilypond can’t write to 
the PDF and then also won’t delete the intermediate files. probably a different 
scenario to the OP’s though. 

regards,
sb

Sent from my iPhone

> On 1 Jun 2022, at 05:03, Andrew Bernard <andrew.bernard@mailbox.org> wrote:
> 
> The @ just means the file has extended attributes which can be seen with 
> xattr.
> 
> MacOS is just UNIX underneath, so I don't see why /tmp should not operate 
> normally. Is  there any chance the OP has TMPDIR set to '.'?
> 
> Here's a post on /tmp in MacOS that may be illuminating.
> 
> https://osxdaily.com/2018/08/17/where-temp-folder-mac-access/
> 
> Unlike plain Linux systems Apple seems to want to hide its tmp directories 
> from ordinary users.
> 
> Andrew
> 
> 
> 
> David Wright wrote on 1/06/2022 1:38 PM:
>> As for the latter, I don't think I can be of any help. My own
>> experience is that these files, whether being preserved or not,
>> are placed/left in the temporary files directory (/tmp, TMPDIR etc),
>> which is not expected to be at ~/musicformats-git-dev/files/musicxmlfiles.
>> 
>> And now, looking at the idiosyncratic file listing (I didn't spot the
>> hyperlink in the text version of the OP, or understand the @ sign),
>> and a quick Order→From in my MUA, I see that the OP's platform is
>> likely a Mac Mini M1, whatever that is, so I'll bow out.
>> 
> 
>