(Getting to send this message sure was a major struggle...) I'm trying to switch from Kate to Geany on Linux (Debian 13). I've long searched for an alternative to Kate and Geany is the only thing that comes close to being a contestant, but it all seems to fall apart with this stupid, basic detail...
On Kate, I do this on boot: kate -s normal -new kate -s book -new That opens two Kate separate instances/windows: * One with my "normal" profile, used for all coding, general notes and to open any text file temporarily. (It's the default 'profile'.) * One with my "book" profile, which is dedicated solely for my current book project. It has completely different files and settings such as where to search for files. I've now spent many hours trying to replicate this basic setup in Geany, reading and re-reading its manual and experimenting a lot, without success. It seems as if Geany instead of Kate's "sessions" (which I always found poorly worded since they are really "profiles") has something it calls "projects". So I first set up two "project" files for Geany: normal.geany and book.geany. I then load Geany up like this: geany <path_to_standard.geany> geany <path_to_book.geany> It does open them as separate instances: so far, so good. But then I'm stuck, because as the manual cryptically states: "Projects can also be opened but a project file (*.geany) must be the first non-option argument. All additionally given files are ignored." If I interpret this very confusing message correctly, it's saying that you cannot specify a Geany "project" while also opening a given file? So I cannot tell my environment from the terminal (or, in practice, from scripts) to open file X into a specific Geany project/window/instance? No matter what I do, whether I use the `-i` flag or not, it just opens another Geany instance or otherwise behaves in an unexpected and unwanted manner. I just cannot get it to work as one would expect. And the `--config` option doesn't seem relevant to this, although it does confuse me since the project files seem to contain "configuration"... My question is thus: Is there really no way to tell Geany to open a given file *using a specific 'project'"? I'm not talking about manually dragging and dropping files into the window, or using the GUI menus from within the program, but doing it on the terminal/from a script. Something like: geany --project=<path_to_a_geany_project_file> <path_to_actual_file_to_open> Please tell me I've just missed some detail, because if this is impossible, I can't use Geany even though it seems better and saner than Kate in most ways by default. It seems unlikely that something so "basic" (in my opinion) would be missing from what seems like such a mature and (mostly) thought-through software project. It was installed via `apt` and it's called: "geany/stable,now 2.0-2 amd64". _______________________________________________ Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-le...@lists.geany.org
