On 21/04/2022 11:42, Ondrej Pokorny via lazarus wrote:

It means that the IPC files are still blocked. Please restart your PC and write back if it didn't help.

This Lazarus part is something I am not really proud of and should be rewritten...

It's also very annoying, if you have a hanging IDE instance. It is impossible to start a 2nd instance to attach and debug.

Even if you don't wont any of it: The most "permissive" setting is "always start a new instance". And even though, this should never need to know (nor be known) if another instance is running, it initializes the IPC stuff (and hangs, if ...).

Maybe it was meant, if an instance from a diff installation (with diff config) has a setting that says to "use a running instance". But even then, it is imho incorrect, to use an instance that says, it does not want to be used. That is to me, if I have a config "always start a new instance", then that means both: - do not look for a running instance, if started with files to open:   lazarus  unitfoo.pas - do not get found/used for opening additional files, when a lazarus with different config checks for a running instance.   (because this running instance says, the files should go into a new instance. So this running instance can not be hijacked to open files)

--------------------
Anyway, in git main branch I added a new command line param. (I added it because fppkg gave me huge time outs. And also some of the other warnings, which I know I can ignore in my development folder.) The option can be added in the lazarus.cfg file. From there it will be read even if you start the IDE from a desktop shortcut.

For the unique-instance / ipc it is
   --skip-checks=SingleInstance


Other values are:
--skip-checks=LazarusDir,FpcExe,FpcSrc,Make,Debugger,Fppkg,Setup,MissingPackageFile,InstallDir,SingleInstance,MacroScript,All

*** WARNING:
*** Disabling those checks means you will not be warned about any issues.
*** Related functionality may be broken, and you are on your own to find out why...

For the initial setup dialog (those checks normally run on every start, to check if the dialog should be shown)     LazarusDir,         // Correct Lazarus-dir / CheckLazarusDirectoryQuality
    FpcExe,         // fpc.exe / CheckFPCExeQuality
    FpcSrc,         // fpc source dir / CheckFPCSrcDirQuality
    Make,           // make.exe / CheckMakeExeQuality
    Debugger,       // CheckDebuggerQuality
    Fppkg,          // CheckFppkgConfiguration
    Setup,          // **All** of the above

    MissingPackageFile, // lisPkgSysPackageFileNotFound = 'Package file not found';
    InstallDir,     // This Config was last used by this/other installation
    SingleInstance, // Other running IDE // Attempt to get lock file
    MacroScript, // Package EditorMacroScript, skip self test

    All             // **ALL**



--
_______________________________________________
lazarus mailing list
[email protected]
https://lists.lazarus-ide.org/listinfo/lazarus

Reply via email to