On Sun, Sep 28, 2025 at 06:00:18PM +0200, Eberhard W Lisse wrote:
Hi,
LyX 2.4.4 on Tahoe started and stopped again, repeatedly. So I ran it
with debug and it said something like "Another instance running" or
similar.
Turns our that there was a .lyxpipe.in dangling and once I removed it it
started easily.
Is it possible to perhaps make this error message a little bit less
misleading by way of perhaps adding something like "~/.lyx/.lyxpipe.in
found" or similar?
LyX should already recognize whether a pipe is dangling or not. If
another instance is using the pipe, the code simply tells the running
instance to load the files. If the pipe is actually dangling, LyX tries
to remove it and tries again.
So, something seems to go wrong in detecting a dangling instance,
because you shouldn't need to manually remove it.
If you are able to compile a simple C program I can send you a test
source that would help identifying whether the error code returned for a
dangling pipe is the one LyX expects.
On Linux, OpenBSD, Solaris, Cygwin, and many others, the error code is
ENXIO (https://man7.org/linux/man-pages/man7/fifo.7.html):
A process can open a FIFO in nonblocking mode. In this case,
opening for read-only succeeds even if no one has opened on the
write side yet and opening for write-only fails with ENXIO (no
such device or address) unless the other end has already been
opened.
I don't know if it can be different on MacOS.
--
Enrico
--
lyx-devel mailing list
[email protected]
https://lists.lyx.org/mailman/listinfo/lyx-devel
