Hi, I often open bash files from a script to edit by either doing this:
geany "some file.sh"
or this
xdg-open "some file.sh"
Every time I do that I get a separate instance of geany with the file. Is there a way to force it to *not* do a new instance but rather open a new pane or tab or whatever its called in an existing window?
Thanks!
Opening a new tab in a running instance is the default behaviour, there is something going wrong if it doesn't work. Look in `help->debug messages` after it opens a new instance.
Otherwise need more information.
Cheers Lex
On Tue, 7 Jun 2022 at 11:22, Dave Parker cedardocster@gmail.com wrote:
Hi, I often open bash files from a script to edit by either doing this:
geany "some file.sh"or this
xdg-open "some file.sh"Every time I do that I get a separate instance of geany with the file. Is there a way to force it to *not* do a new instance but rather open a new pane or tab or whatever its called in an existing window?
Thanks! _______________________________________________ Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
Ok, thanks. Here's the errors message:
11:43:23.623807: GLib-GIO DEBUG : _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ 11:43:23.651576: Geany WARNING : Failed to bind IPC socket (/run/user/1000/geany/geany_socket.9ecfe310): 13: Permission denied 11:43:23.651593: Geany INFO : Geany 1.38, en_CA.UTF-8 11:43:23.651601: Geany INFO : GTK 3.24.33, GLib 2.72.1 11:43:23.651646: Geany INFO : OS: Ubuntu 22.04 LTS (jammy) 11:43:23.651655: Geany INFO : System data dir: /usr/share/geany 11:43:23.651665: Geany INFO : User config dir: /home/david/.config/geany 11:43:23.780411: Geany INFO : Loaded GTK+ CSS theme '/usr/share/geany/geany.css' 11:43:23.780982: Geany INFO : Loaded GTK+ CSS theme '/usr/share/geany/geany-3.20.css' 11:43:23.785913: Geany INFO : System plugin path: /usr/lib/x86_64-linux-gnu/geany 11:43:23.793917: Geany INFO : Added filetype JSON (64). 11:43:23.793929: Geany INFO : Added filetype Scala (65). 11:43:23.793936: Geany INFO : Added filetype Arduino (66). 11:43:23.793943: Geany INFO : Added filetype Graphviz (67). 11:43:23.793950: Geany INFO : Added filetype Cython (68). 11:43:23.793956: Geany INFO : Added filetype Nim (69). 11:43:23.793962: Geany INFO : Added filetype Groovy (70). 11:43:23.793969: Geany INFO : Added filetype TypeScript (71). 11:43:23.793975: Geany INFO : Added filetype Kotlin (72). 11:43:23.793981: Geany INFO : Added filetype CUDA (73). 11:43:23.793988: Geany INFO : Added filetype Genie (74). 11:43:23.793994: Geany INFO : Added filetype Meson (75). 11:43:23.794001: Geany INFO : Added filetype Clojure (76). 11:43:23.794008: Geany INFO : Added filetype Swift (77). 11:43:23.806276: Geany INFO : Loaded libvte from libvte-2.91.so.0 11:43:23.808343: Geany WARNING : IPC socket could not be created, see Help->Debug Messages for details. 11:43:23.809102: Geany INFO : Loaded: /usr/lib/x86_64-linux-gnu/geany/overview.so (Overview) 11:43:23.816614: Geany INFO : /tmp/alllists : None (UTF-8)
Looks like a permission problem. I hate fixing linux permission problems. Any suggestions (other than tacking on "sudo" in front of every single command, ha ha)? I wish there was a blanket security permission thing I could just set to "low" as I'm literally the only person using this system.
On Mon, Jun 6, 2022 at 7:31 PM Lex Trotman elextr@gmail.com wrote:
Opening a new tab in a running instance is the default behaviour, there is something going wrong if it doesn't work. Look in `help->debug messages` after it opens a new instance.
Otherwise need more information.
Cheers Lex
On Tue, 7 Jun 2022 at 11:22, Dave Parker cedardocster@gmail.com wrote:
Hi, I often open bash files from a script to edit by either doing this:
geany "some file.sh"or this
xdg-open "some file.sh"Every time I do that I get a separate instance of geany with the file.
Is there a way to force it to *not* do a new instance but rather open a new pane or tab or whatever its called in an existing window?
Thanks! _______________________________________________ Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
thanks, but that didn't fix it :'(
On Tue, Jun 7, 2022 at 12:08 PM Alain Aupeix alain.aupeix@wanadoo.fr wrote:
Le 07/06/2022 à 19:55, Dave Parker a écrit :
Ok, thanks. Here's the errors message:
11:43:23.623807: GLib-GIO DEBUG : _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ 11:43:23.651576: Geany WARNING : Failed to bind IPC socket (/run/user/1000/geany/geany_socket.9ecfe310): 13: Permission denied
Perhaps you have use geany in sudo mode.
Looks like a permission problem. I hate fixing linux permission problems. Any suggestions (other than tacking on "sudo" in front of every single command, ha ha)? I wish there was a blanket security permission thing I could just set to "low" as I'm literally the only person using this system.
Perhaps changing owner of .run/user/1000/geany
sudo chown -R $user:$user .run/user/1000/geany A+
--
*Alain Aupeix* Sites web : JujuLand http://jujuland.pagesperso-orange.fr/ | Pissobi-Lacassagne http://pissobi-lacassagne.pagesperso-orange.fr/ | Gadel https://www.gadel-environnement.org/
X.ubuntu 16.04 | H.arbour 3.2.0dev (r2021-04-28 18:02) | Hw.gui 2.23-2 (r3055) | G.ramps 5.1.2
Ok, I got it working by uninstalling and re-installing (after trying the snap package that didn't work)
thanks for the suggestions!
On Tue, Jun 7, 2022 at 12:11 PM Dave Parker cedardocster@gmail.com wrote:
thanks, but that didn't fix it :'(
On Tue, Jun 7, 2022 at 12:08 PM Alain Aupeix alain.aupeix@wanadoo.fr wrote:
Le 07/06/2022 à 19:55, Dave Parker a écrit :
Ok, thanks. Here's the errors message:
11:43:23.623807: GLib-GIO DEBUG : _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ 11:43:23.651576: Geany WARNING : Failed to bind IPC socket (/run/user/1000/geany/geany_socket.9ecfe310): 13: Permission denied
Perhaps you have use geany in sudo mode.
Looks like a permission problem. I hate fixing linux permission problems. Any suggestions (other than tacking on "sudo" in front of every single command, ha ha)? I wish there was a blanket security permission thing I could just set to "low" as I'm literally the only person using this system.
Perhaps changing owner of .run/user/1000/geany
sudo chown -R $user:$user .run/user/1000/geany A+
--
*Alain Aupeix* Sites web : JujuLand http://jujuland.pagesperso-orange.fr/ | Pissobi-Lacassagne http://pissobi-lacassagne.pagesperso-orange.fr/ | Gadel https://www.gadel-environnement.org/
X.ubuntu 16.04 | H.arbour 3.2.0dev (r2021-04-28 18:02) | Hw.gui 2.23-2 (r3055) | G.ramps 5.1.2
-- *Dr David Parker*
*ChiropracticExerciseDietAttitudeRecovery* cedar-chiropractic.c http://cedar-chiropractic.com/om http://cedar-chiropractic.com/
On Tuesday, June 07, 2022 02:11:36 PM Dave Parker wrote:
thanks, but that didn't fix it :'(
On Tue, Jun 7, 2022 at 12:08 PM Alain Aupeix alain.aupeix@wanadoo.fr
Perhaps changing owner of .run/user/1000/geany
sudo chown -R $user:$user .run/user/1000/geany
What command did you actually run, or what is the owner and group of that file now?
A number of comments, which may be rather "elementary" (or may sound condescending) depending on the level of expertise of Dave:
* on my Debian Wheezy system, it is $USER to get the username
* I understand that on newer (Debian?) systems the behavior of sudo has changed somehow, specifically with respect to what environment it uses (that of the user or that of root), you may have to do something like add a - (like "sudo -"), but I have not paid careful attention to discussions about that.
* where is file .run/user/1000/geany? I assume (I know) that it is in the user's home directory (i.e., /home/<username>/.run/user/1000/geany
I prefer to write commands like that, especially in an email to a (to me) unknown user, more like:
# chown -R <username>.<groupname> /home/<user>.run/user/1000/geany
(the pound prompt implies being run as root)
or some variation that, I hope, a user will recognize what needs to be done.
BTW, is that /home/<user>.run/user/1000/geany a file or a directory -- if a file, the -R (for recursive) is not necessary
There are possible alternates, like
$ sudo <-??> <username>.<groupname> /home/<user>.run/user/1000/geany
Note: if the - (dash) is required in the sudo command, I'm about 95% sure a separating space is required.
(the pound prompt implies being run as the user)
Running ls -al /home/<user>.run/user/1000/geany would let you know if the desired change was accomplished (if that is a directory, appending a /* would be helpful) -- you can post the results here if you have any doubts.
A note to everybody:
The error message from Geany was for a socket in /run/user etc etc NOT .run/user.
Cheers Lex
On Wed, 8 Jun 2022 at 21:06, rhkramer@gmail.com wrote:
On Tuesday, June 07, 2022 02:11:36 PM Dave Parker wrote:
thanks, but that didn't fix it :'(
On Tue, Jun 7, 2022 at 12:08 PM Alain Aupeix alain.aupeix@wanadoo.fr
Perhaps changing owner of .run/user/1000/geany
sudo chown -R $user:$user .run/user/1000/geany
What command did you actually run, or what is the owner and group of that file now?
A number of comments, which may be rather "elementary" (or may sound condescending) depending on the level of expertise of Dave:
on my Debian Wheezy system, it is $USER to get the username
I understand that on newer (Debian?) systems the behavior of sudo has
changed somehow, specifically with respect to what environment it uses (that of the user or that of root), you may have to do something like add a - (like "sudo -"), but I have not paid careful attention to discussions about that.
- where is file .run/user/1000/geany? I assume (I know) that it is in the
user's home directory (i.e., /home/<username>/.run/user/1000/geany
I prefer to write commands like that, especially in an email to a (to me) unknown user, more like:
# chown -R <username>.<groupname> /home/<user>.run/user/1000/geany
(the pound prompt implies being run as root)
or some variation that, I hope, a user will recognize what needs to be done.
BTW, is that /home/<user>.run/user/1000/geany a file or a directory -- if a file, the -R (for recursive) is not necessary
There are possible alternates, like
$ sudo <-??> <username>.<groupname> /home/<user>.run/user/1000/geany
Note: if the - (dash) is required in the sudo command, I'm about 95% sure a separating space is required.
(the pound prompt implies being run as the user)
Running ls -al /home/<user>.run/user/1000/geany would let you know if the desired change was accomplished (if that is a directory, appending a /* would be helpful) -- you can post the results here if you have any doubts. _______________________________________________ Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
Dave,
Did you check if a link exists in ~/.config/geany/geany_socket.something and delete it if it exists (Important: when _all_ Geanys are closed)?
That link points to the socket in /run/user/etc etc, so if it is deleted a new socket will be created with your user ownership.
Cheers Lex
On Wed, 8 Jun 2022 at 22:20, Lex Trotman elextr@gmail.com wrote:
A note to everybody:
The error message from Geany was for a socket in /run/user etc etc NOT .run/user.
Cheers Lex
Oops, fixing at least some of the typos -- I left out a / in a few places:
On Wednesday, June 08, 2022 07:06:08 AM rhkramer@gmail.com wrote:
# chown -R <username>.<groupname> /home/<user>.run/user/1000/geany
Should have been:
# chown -R <username>.<groupname> /home/<user>/.run/user/1000/geany
(see the added slash between <user> and .run
$ sudo <-??> <username>.<groupname> /home/<user>.run/user/1000/geany
again, should have been:
$ sudo <-??> <username>.<groupname> /home/<user>/.run/user/1000/geany
On Wed, 8 Jun 2022 at 23:12, rhkramer@gmail.com wrote:
Oops, fixing at least some of the typos -- I left out a / in a few places:
On Wednesday, June 08, 2022 07:06:08 AM rhkramer@gmail.com wrote:
# chown -R <username>.<groupname> /home/<user>.run/user/1000/geany
Should have been:
# chown -R <username>.<groupname> /home/<user>/.run/user/1000/geany
There may be a ~/.run on your system, but there is not on others, and as I pointed out the Geany error message was directly to `/run/user/1000/geany/geany_socket.xxxxxxxx`
(see the added slash between <user> and .run
$ sudo <-??> <username>.<groupname> /home/<user>.run/user/1000/geany
again, should have been:
$ sudo <-??> <username>.<groupname> /home/<user>/.run/user/1000/geany
And changing the permissions of the socket is the wrong thing to do. After the geany reading it closed no other geany will read it again, it should be deleted but even if its still there, if the link I mentioned above is deleted the next geany run will make a new socket and read from it..
Cheers Lex
Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
I saw the ".run" and just assumed it was a typo and replaced the "." with a "/"
so I did this: sudo chown -R david:david /run/user/1000/geany
but not this: sudo chown -R david:david /.run/user/1000/geany
(but I don't have a /.run folder anyway)
I'm just happy reinstalling fixed it, ha ha
- Dave
On Wed, Jun 8, 2022 at 7:25 AM Lex Trotman elextr@gmail.com wrote:
On Wed, 8 Jun 2022 at 23:12, rhkramer@gmail.com wrote:
Oops, fixing at least some of the typos -- I left out a / in a few
places:
On Wednesday, June 08, 2022 07:06:08 AM rhkramer@gmail.com wrote:
# chown -R <username>.<groupname> /home/<user>.run/user/1000/geany
Should have been:
# chown -R <username>.<groupname> /home/<user>/.run/user/1000/geany
There may be a ~/.run on your system, but there is not on others, and as I pointed out the Geany error message was directly to `/run/user/1000/geany/geany_socket.xxxxxxxx`
(see the added slash between <user> and .run
$ sudo <-??> <username>.<groupname> /home/<user>.run/user/1000/geany
again, should have been:
$ sudo <-??> <username>.<groupname> /home/<user>/.run/user/1000/geany
And changing the permissions of the socket is the wrong thing to do. After the geany reading it closed no other geany will read it again, it should be deleted but even if its still there, if the link I mentioned above is deleted the next geany run will make a new socket and read from it..
Cheers Lex
Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
On 2022-06-08 06:12, rhkramer@gmail.com wrote:
Should have been:
# chown -R <username>.<groupname> /home/<user>/.run/user/1000/geany
Another tip to avoid errors—*never* use the angle brackets for anything on the command line, unless that is exactly what you want.
Too many chances for disaster.
If you really feel like you need to mark them, use ${} or similar:
$ ls -l /home/${USER}/.run/user/1000/geany
But perhaps all caps can work too.
-Mike
As another respondent (who replied to you not the list, please don't do that) said, perhaps you used Geany as root and that left the link to the socket in your config owned by root. You should close _all_ Geanys and delete the dead link in your config (default ~/.config/geany/geany_socket.some_stuff_depending_on_your_machine) with sudo. Ubuntu is one of the brain dead sudo implementations that does not change the user when you sudo, so you leave root owned crap in the user directory that they can't get rid of.
Cheers Lex
On Wed, 8 Jun 2022 at 03:55, Dave Parker cedardocster@gmail.com wrote:
Ok, thanks. Here's the errors message:
11:43:23.623807: GLib-GIO DEBUG : _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ 11:43:23.651576: Geany WARNING : Failed to bind IPC socket (/run/user/1000/geany/geany_socket.9ecfe310): 13: Permission denied 11:43:23.651593: Geany INFO : Geany 1.38, en_CA.UTF-8 11:43:23.651601: Geany INFO : GTK 3.24.33, GLib 2.72.1 11:43:23.651646: Geany INFO : OS: Ubuntu 22.04 LTS (jammy) 11:43:23.651655: Geany INFO : System data dir: /usr/share/geany 11:43:23.651665: Geany INFO : User config dir: /home/david/.config/geany 11:43:23.780411: Geany INFO : Loaded GTK+ CSS theme '/usr/share/geany/geany.css' 11:43:23.780982: Geany INFO : Loaded GTK+ CSS theme '/usr/share/geany/geany-3.20.css' 11:43:23.785913: Geany INFO : System plugin path: /usr/lib/x86_64-linux-gnu/geany 11:43:23.793917: Geany INFO : Added filetype JSON (64). 11:43:23.793929: Geany INFO : Added filetype Scala (65). 11:43:23.793936: Geany INFO : Added filetype Arduino (66). 11:43:23.793943: Geany INFO : Added filetype Graphviz (67). 11:43:23.793950: Geany INFO : Added filetype Cython (68). 11:43:23.793956: Geany INFO : Added filetype Nim (69). 11:43:23.793962: Geany INFO : Added filetype Groovy (70). 11:43:23.793969: Geany INFO : Added filetype TypeScript (71). 11:43:23.793975: Geany INFO : Added filetype Kotlin (72). 11:43:23.793981: Geany INFO : Added filetype CUDA (73). 11:43:23.793988: Geany INFO : Added filetype Genie (74). 11:43:23.793994: Geany INFO : Added filetype Meson (75). 11:43:23.794001: Geany INFO : Added filetype Clojure (76). 11:43:23.794008: Geany INFO : Added filetype Swift (77). 11:43:23.806276: Geany INFO : Loaded libvte from libvte-2.91.so.0 11:43:23.808343: Geany WARNING : IPC socket could not be created, see Help->Debug Messages for details. 11:43:23.809102: Geany INFO : Loaded: /usr/lib/x86_64-linux-gnu/geany/overview.so (Overview) 11:43:23.816614: Geany INFO : /tmp/alllists : None (UTF-8)
Looks like a permission problem. I hate fixing linux permission problems. Any suggestions (other than tacking on "sudo" in front of every single command, ha ha)? I wish there was a blanket security permission thing I could just set to "low" as I'm literally the only person using this system.
On Mon, Jun 6, 2022 at 7:31 PM Lex Trotman elextr@gmail.com wrote:
Opening a new tab in a running instance is the default behaviour, there is something going wrong if it doesn't work. Look in `help->debug messages` after it opens a new instance.
Otherwise need more information.
Cheers Lex
On Tue, 7 Jun 2022 at 11:22, Dave Parker cedardocster@gmail.com wrote:
Hi, I often open bash files from a script to edit by either doing this:
geany "some file.sh"or this
xdg-open "some file.sh"Every time I do that I get a separate instance of geany with the file.
Is there a way to force it to *not* do a new instance but rather open a new pane or tab or whatever its called in an existing window?
Thanks! _______________________________________________ Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org
-- *Dr David Parker*
*ChiropracticExerciseDietAttitudeRecovery* cedar-chiropractic.c http://cedar-chiropractic.com/om http://cedar-chiropractic.com/ _______________________________________________ Users mailing list -- users@lists.geany.org To unsubscribe send an email to users-leave@lists.geany.org