-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support: zsh exiting after failed commands #269
Comments
I'm back from travelling and will be back to coding this week. I'll get the square brackets PR merged then will solve whatever is happening here. The PR should fix many oddities. Will aim to get the PR merged and whatever the fix for this done by end of this week. |
Can you grab a time on https://cal.com/balupton/meet |
1 similar comment
Can you grab a time on https://cal.com/balupton/meet |
Sweet thanks! I just changed shells from Zsh to Bash and then did the install a second time. Uhm, in truth, actually a third time, because the second time I chose to customise 'localhost' when prompted. As my device is unrooted, it ended in tears. Third time lucky, the install went down without a hitch. Well there was no adverse console output nor shell warning and I was prompted to answer a lot of install questions, which all seemed to go well. But, then to check the install after restarting my shell and environment, I entered the following as advised to ensure everything was kosher: (base) localhost :: ~ % dorothy theme
zsh: command not found: dorothy
7:57:12 root@localhost ~ su hummingbird108 Of couse, as the Cheers |
i get the same err fyi |
Whoops, maybe it's https://cal.com/balupton/call |
For why Dorothy may not be loading, see https://github.com/bevry/dorothy/blob/master/docs/dorothy/dorothy-not-loading.md |
@b9Joker108 can you grab a time on https://cal.com/balupton/call I'm keen to solve this for you |
@b9Joker108 in the zsh shell that is crashing, can you run:
and let me the output and if it crashes |
(base) localhost:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
(base) localhost:~ $ uname -a
Linux localhost 6.2.1-PRoot-Distro #1 SMP PREEMPT Mon Oct 14 00:51:42 UTC 2024 aarch64 GNU/Linux |
(base) localhost:~ $ printf '%s\n' $-
569JNRXZeghikms
(base) localhost:~ $ test 1 -eq 2
root@localhost [1] # The first one-liner outlined an alphanumeric string. The second one-liner results in the shell dropping to root: (base) [hummingbird108@localhost ~ ]$ printf '%s\n' $?
0 |
Yeah, so the issue is that We need to find out when/where that flag is getting set. Maybe your |
(base) localhost:~ $ printf '%s\n' $-
569JNRXZeghikms
(base) localhost:~ $ test 1 -eq 2
root@localhost [1] # The second one-liner results in the shell dropping to root: I really appreciate you learning me about the shell debugging one-liner! I have never encountered that before and I am doing a write up on it now in my ObsidianMD vault and adding it to my toolkit. I may have set the console silence flag in my OMZ config. I know I definitely did it in the OMZ config of the Zsh shell of my Termux host environment, but I don't have a memory of doing it in my Debian proot chroot, but that doesn't mean I didn't. |
I am closing this issue. Please let me know what you think about this in regards to our conversation when you have time: https://youtu.be/DYvXb_ukIzg?si=T6Cnr0ACNWhNoJbX |
@b9Joker108 cool, will take a look when I have time. For future reference, this issue was due to errexit being set in either the user configuration or the zsh configuration, applied from something unrelated to Dorothy. |
Hi
I finally installed Dorothy in one of my environments. I contacted you quite some time ago about progressing a Dorothy install in my Termux host environment and integrating it with a number of other third-party dotfiles management projects that I have progressively implemented and adapted locally, making somewhat of a super-hybrid or motly-chimera. Due to a complex of factors, I have not yet implemented Dorothy in that environment, as I still intend to do, as integrating the other projects has taken quite some time and I kind of stalled with it, instead progressong and attending to other things.
Today, on whim, somewhat as a personal virtual Christmas present, I resolved to install Dorothy in one of my many proot chroots instead, so I may start to familiarise myself with a local implementation of the project. I installed Dorothy in the aarch64 Debian 12 'Bookworm' proot chroot that houses most of my coding and development environments and projects. Unfortunately, the install did not go without a hitch:
I don't know why, but recently the Zsh shell of the standard user of this user account in my Debian proot chroot, has become unstable and temperamental. Recently, approaching pretty much always, if the shell console has an output, requesting input, or I enter a spelling error of any command in the console, for example, the shell automatically drops from my standard user, to the standard user's root account and environment and changes directory which is curious and really quite annoying, as well as counterproductive. So, that's the long-winded bloody context.
Anyway, that said and contextualised, I feel that the following line extracted from the above shell console output from the Dorothy install, demonstrates just such a console output, requesting input and subsequently triggering a drop from the shell and environment of my standard user, to the root user and their shell and environment. Which, as a consequence, terminated the install from that point onwards:
I am hoping that you may be able to identify what needs to be done to finesse and finalise the install and repair the installation glitch.
Just respond when convenient amd timely. I appreciate things are probably hectic for you, given that it is currently right smack-bang in the middle of the Silly Season. I wish you and yours a joyous and merry Christmas.
I await your advice in due course.
Thanking you in anticipation
Beauford
The text was updated successfully, but these errors were encountered: