When starting tilda with a custom command:
tmux new-session -A -s main
No command prompt is displayed, just blank screen. If I run a second instance (by starting tilda from Terminal) then it loads a bash prompt with a new tilda config.
This is displayed in terminal for the original tilda instance:
(tilda:7060): VTE-CRITICAL **: 09:57:10.171: void vte_pty_spawn_with_fds_async(VtePty*, const char*, const char* const*, const char* const*, const int*, int, const int*, int, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, int, GCancellable*, GAsyncReadyCallback, gpointer): assertion 'envv == nullptr || _vte_pty_check_envv(envv)' failed
alanmcg
commented
3 years ago
When starting tilda with a custom command:
tmux new-session -A -s mainNo command prompt is displayed, just blank screen. If I run a second instance (by starting tilda from Terminal) then it loads a bash prompt with a new tilda config.
This is displayed in terminal for the original tilda instance:
(tilda:7060): VTE-CRITICAL **: 09:57:10.171: void vte_pty_spawn_with_fds_async(VtePty*, const char*, const char* const*, const char* const*, const int*, int, const int*, int, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, int, GCancellable*, GAsyncReadyCallback, gpointer): assertion 'envv == nullptr || _vte_pty_check_envv(envv)' failed