Closed peey closed 6 years ago
If you simply start it from a crontab it can't connect to the X server. It must be started in a way that the DISPLAY-variable is set correctly, and that it has access to your X cookie. If it's running as your user, a simple "DISPLAY=:0 /path/to/script.tcl" should probably do the trick.
On Fri, Mar 2, 2018 at 1:34 PM, Peeyush Kushwaha notifications@github.com wrote:
I'm facing a weird issue. I added
@reboot /path/to/dir/containing/ghost-text-server.tcl
and I can confirm that the job is started (I tried starting it again via command line, but got the error couldn't open socket: address already in use, then I check via ps aux | grep ghost-text-server.tcl$ that indeed the script is running)
But it doesn't open up GVim. If I run it on terminal then it works fine.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/falstro/ghost-text-vim/issues/16, or mute the thread https://github.com/notifications/unsubscribe-auth/AIVQ2FFp4oJZYg3VRqj9euv_dhH3l3pqks5taTxigaJpZM4SZ1PB .
This worked, thanks!
(Appropriately enough, this was typed on Vim via GhostText, with the script started from crontab)
I'm facing a weird issue. I added
and I can confirm that the job is started (I tried starting it again via command line, but got the error
couldn't open socket: address already in use
, then I check viaps aux | grep ghost-text-server.tcl$
that indeed the script is running)But it doesn't open up GVim. If I run it on terminal then it works fine.