On 2025-09-22 07:47, mullvadisen via Users wrote:
Geany does support opening a file with different instances and different
basic configurations. Please check --socket-file=FILE and --config=DIR
I already mentioned "--config" and how it seems to be something different from the
"project" with its list of opened/associated files, etc.
"--socket-file" just says "Use this socket filename for communication with a running Geany
instance", which doesn't help much. What kind of communication is that? Does it have some sort of
"API" that I need to use or what? Why over-complicate something so simple/basic?
The socket is how the command-line tells a running instance to open a file.
This is a somewhat common pattern with such tools.
You don't need to manually communicate with the socket, just pass a filename as
the socket corresponding to an instance, it will be created if needed. Think of
it as a pipe or channel between the CLI and the GUI, both must use the same one
to talk. --config would also allow you have different configuration if needed,
though the session file might still be an issue.
You could probably alias or script this.
Geany's session/project support has always been simplistic. It only moved
session info into its own .conf file a couple of years ago. That made my
dotfiles repo a lot happier. Global color schemes were sorted only a few years
before that. I'm still not happy with how the filedefs files are named backwards.
Anyway, progress is being made. If you drop the entitled attitude a simpler
(for the user) solution might make it in at some point. Until then I just open
one project at a time, with an occasional stray file here and there, and use
micro for sysad-type tasks.
-M
_______________________________________________
Users mailing list -- users@lists.geany.org
To unsubscribe send an email to users-le...@lists.geany.org
