Terminal’s idea of the Default Working Listing is the customers dwelling listing ($HOME) as setup in Settings | Customers and Teams (defaulted to /Customers/USER). This data comes from the assistance display screen for that Terminal settings dialog within the query (press ?).
Now, often when customers are setup or modified $HOME isn’t seen to be modified. However there’s an ‘Superior’ choice to edit the consumer profile; UID, group, shell, $HOME. That is accessed by Management-Clicking the consumer in Customers and Teams.
See https://assist.apple.com/en-us/102547 for some background, although that is principally to rename an account. In that state of affairs you would be renaming the $HOME (eg. sudo mv /Customers/fred /Customers/bob), then altering the renamed consumer profile to level on the renamed $HOME. I’d think about that altering the house listing as has been achieved in your machine can be classed as ‘unsupported’.
I’d counsel that your $HOME has been modified prior to now to /Customers/USER/Paperwork/subfolder
I’ve setup a take a look at consumer on my machine and set $HOME to /Customers/USER/Paperwork, logged on as that consumer, opened Terminal, and verified that /Customers/USER/Paperwork is the house listing.
As an administrator it ought to be enough to vary it again to /Customers/USER, and logoff / logon. If the affected account is already an admin, it will likely be safer to create one other admin account to do the change with. Altering the affected account with the affected account could trigger additional issues!
Nevertheless, as soon as modified, there could also be another folders which would require shifting from Paperwork to make sure correct operation of different apps. My take a look at wasn’t complete sufficient past checking the house listing. However the change has certainly created new sub-folders for Desktop, Library, Downloads, Paperwork, .Trash; and the varied .zsh* configs. Unpicking this can be tough for you.
In fact, a dependable backup beforehand is important.
Replace:
Information from the OP (which I might missed within the query tbf..) exhibits that $HOME is ready accurately, but the issue persists. This invalidates my reply considerably, but continues to be a method of attaining the issue.