10/31/2023 0 Comments Fish shell default macI accidentally entered a directory path and fish changed directory. For example, find $PWD -name '*.txt' silently fails in shells that don't resolve symlinked paths. This issue can also be seen when doing IO redirection.Īnother related issue is that many programs that operate on recursive directory trees, like the find command, silently ignore symlinked directories. This issue is not possible to fix without either making every single command into a builtin, breaking Unix semantics or implementing kludges in every single command. ![]() changes the current directory to ~, and the prompt, the pwd builtin and many other directory information sources suggest that the current directory is ~/images and its parent is ~. given the above directory structure would list the contents of ~/Documents, not of ~, even though using cd. Most such issues have to do with how '.' is handled, and are varitations of the following example: But it was felt there are enough serious corner cases that this is a bad idea. ![]() It is indeed possible to do this partially, and many other shells do so. Why does cd, $PWD and and various fish commands always resolve symlinked directories to their canonical path? For example if ~/images is a symlink to ~/Documents/Images, if I write 'cd images', my prompt will say ~/D/Images, not ~/images.īecause it is impossible to consistently keep symlinked directories unresolved.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |