Hello Till, On Wed, Aug 15, 2018 at 12:55:03PM +0200, Till Smejkal wrote: > I guess the difference and hence the problem is, that if firefox is already > running, > the firefox process started via mailcap will actually not do anything except > signaling the main process to open the file. However, if firefox is not yet > running, > the firefox process started via mailcap will become the main firefox process > and > hence stay for some time. The problem is now, that mutt deletes the file ones > the > started process exits. So there is a race condition now (firefox process > signaling to > main ff-process which in turn opens the file vs. mutt deleting the file). You > can > change your mailcap maybe so that it creates a copy of the file to show before > calling firefox.
It does help indeed! Not sure if mailcap handles copy+open, I'll check now -F
