The questioner's Another question has done the following, but it seems that all existing PATHs have been lost.
export PATH=$aw-server:/home/yusuke/.local/bin
export PATH=$aw-watcher-afk:/home/yusuke/.local/bin
export PATH=$aw-watcher-window: /home/yusuke/.local/bin
In other words, when you need to write export PATH="/path/to/new/directory:$PATH"
in the form of an existing PATH, the contents of the PATH are almost gone and you can't find any executable files.
If you have not specifically overwritten configuration files such as ~/.profile
, you should be able to restart the shell.If you have overwritten it, you can start Bash without loading the existing .profile
in /usr/bin/env-i/bin/bash --norc--noprofile
and so on to correct the configuration file.
911 When building Fast API+Uvicorn environment with PyInstaller, console=False results in an error
581 PHP ssh2_scp_send fails to send files as intended
617 Uncaught (inpromise) Error on Electron: An object could not be cloned
578 Understanding How to Configure Google API Key
574 Who developed the "avformat-59.dll" that comes with FFmpeg?
© 2024 OneMinuteCode. All rights reserved.