When Astronaut is started with no configuration file present, it has
no keybinds, and thus starts and runs normally but ignores all
keystrokes. Thus there's no way to use the program or to quit it (and
you need to kill it from outside).
Either defaulting to an internal usable config, or exiting with an
error in this case, would be more reasonable behavior.
I am using git commit ced9e028957df80c90dc35042f9a23a75e2f424a (master
at time of writing).
--
Tom Hunt
On Sat Sep 18, 2021 at 4:42 PM EDT, Tom Hunt wrote:
> When Astronaut is started with no configuration file present, it has> no keybinds, and thus starts and runs normally but ignores all> keystrokes. Thus there's no way to use the program or to quit it (and> you need to kill it from outside).>> Either defaulting to an internal usable config, or exiting with an> error in this case, would be more reasonable behavior.>> I am using git commit ced9e028957df80c90dc35042f9a23a75e2f424a (master> at time of writing).
That is strange. Did you compile astronaut with make or with go build?
If no configuration is present, astronaut should attempt to install the
default configuration from the share directory.
I'll investigate this further.
> That is strange. Did you compile astronaut with make or with go build?> If no configuration is present, astronaut should attempt to install the> default configuration from the share directory.
I used make, but not make install. Thus I think there's no config in the share
directory. (My general practice is to not install third-party software outside
/home unless it's really necessary.)
astronaut works just fine when run from ~/bin and the default configuration
installed manually.
--
Tom Hunt
On Sat Sep 18, 2021 at 5:19 PM EDT, Tom Hunt wrote:
> > That is strange. Did you compile astronaut with make or with go build?> > If no configuration is present, astronaut should attempt to install the> > default configuration from the share directory.>> I used make, but not make install. Thus I think there's no config in the share> directory. (My general practice is to not install third-party software outside> /home unless it's really necessary.)>> astronaut works just fine when run from ~/bin and the default configuration> installed manually.
I see. I think an error message in this case is probably the best
solution.