You must also compare with `ls foo-<tmpname>` which is really another level of complexity. Next usage is far more efficient

> ls foo.pdf*
>rm foo.pdf+TAB completion+arrow down?+enter

However, if things are correctly implemented, you’d never even need to worry about \jobname.pdf(busy) at all, should it be from the CLI or from the desktop. The only purpose of \jobname.pdf(busy) is eventually to be deciphered, and this is far easier for most people, who only know ‘_’ for math subscript (I had already tested on my students for "synctex(busy)").

Only tools that clean things up (« Remove aux files » ) could eventually manage a new file extension but that is not a requirement.


Le 4 mai 2022 à 13:08, luigi scarso <> a écrit :

On Wed, May 4, 2022 at 12:37 PM Jérôme LAURENS <> wrote:
How do you manage \jobname-<tmpname> when the process has been killed ?

Indeed, this is the problem.
In bash, quotes are already used to escape spaces in file paths such that  ‘(‘ and ‘)’ should already be escaped for free.

sure,  indeed ls 'foo.pdf(busy)' is ok while
ls foo.pdf(busy)
it is not -- a useless complication if one has to manage files at command line.
Just avoid '(' etc, e.g.  foo.pdf_busy_  is fine.