I am not sure if the following is of any help at all but here goes:
I have several independent projects in different directories, and the
Geany workspace is also a separate directory. So we have:
~/home/Projects
projectA
projectB
...
workspace
My system opens Geany with the command /usr/bin/geany
Geany then starts up with the last active project, but you can easily
switch from one to another. If projectA is active, I can easily view and
process files in projectB without having to actually switch to projectB.
Files can be added to a project by any method you choose, whether or not
Geany is active - you do not have to use the Geany GUI for this.
So it might be that you do not need a new-instance for your 'book'
project. If you use the geany search command, you can find files in any
project you like.
It might help more expert people if you could outline what you are
trying to do in your 'normal' or 'book' projects. I would suggest you
produce a simple diagram of the structure for each of your projects
along with perhaps a Knuth style presentation of actions. At the moment
it is unclear what the 'book' projects does.
Geoff
On 22/09/2025 15: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?
I'm truly unable to put this any clearer than I already did in my question. I'm simply trying to open new
files into a specific Geany "project"/instance (from a script/terminal), but it seems to me as if
this is just not possible. Geany seems to only support manually "adding" new files into a
"project" via its own GUI menus. I never thought that *this* of all things would be an issue...
I'm still somewhat convinced that it must be possible, because it seems like something that would naturally "come up"
at some early point when developing a program like this. It would be a complete mess to have all files in one single
"project"/instance, even if they belong to different "projects". But those "configs" again seem
completely separate from the list of files and other stuff associated with a "project".
Why isn't there simply a `--project="blabla"` flag I can use so it knows which
Geany I want to open a file in?
_______________________________________________
Users mailing list -- users@lists.geany.org
To unsubscribe send an email to users-le...@lists.geany.org
_______________________________________________
Users mailing list -- users@lists.geany.org
To unsubscribe send an email to users-le...@lists.geany.org
