This starts up sh, changes the directory to $HOME, and then exec's your $SHELL to replace the sh. This is absolutely not needed since it's much easier to use wsl ~, but: wsl -e sh -c 'cd $HOME exec $SHELL' Remove the "source" attribute and replace it with "commandline": "guid": "",Īlso, for the fun of it, here's an alternative (hacky) way to open WSL to ~/ $HOME (without hardcoding as with the other answers). If you are editing your settings.json directly (currently found in %userprofile%\AppData\Local\Packages\MicrosoftWindowsTerminal.\LocalState\settings.json, but this may change). Full sync support podcast client for Windows Installation Either from the official Nextcloud app store ( link to app page ) or by downloading the latest release and extracting it into your Nextcloud apps/ directory. Older Windows Terminal Releases, or if you want to edit manually Since Windows Terminal now has a GUI for Settings, you can just edit your profile to point to wsl ~ in the ->General->Command Line setting. Current and Recent Windows Terminal Releases This is an undocumented flag to wsl.exe, and it must be the first argument (e.g. If it differs for other machines, mention that too. Anything to this effect on windows ps: currently trying to do this on xp machines. in linux shell (debian based) we do a cd and it instantly takes to the current logged user's directory /home/.The easiest way to do that is simply to create or change the "commandline" property to wsl ~. Any short way to cd to the user specific directories in the command prompt. The other answers here (especially the latest one from are great for starting in an arbitrary directory, but the example in your question was to start in your home directory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |