find command cannot find my files which do exist












4















One weird situation occurs to me that find command cannot find some files but can find another, and they all exist in the local path.



The original code as a screenshot:



screen.



The files are there:



$ ls -lh ~/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


But they cannot be found:



$ find ~/.config -name z.lua
$ find ~/.config -name prompt_pwd.fish


The upper directory and files in it:



$ ls -ld ~/.config/fish/
drwx------ 2 echecod echecod 4096 Feb 20 13:35 /home/echecod/.config/fish/

$ ls -lh ~/.config/fish/
total 24K
lrwxrwxrwx 1 echecod echecod 46 Dec 20 16:45 config.fish -> ../../Dotfiles.d/fish/.config/fish/config.fish*
-rw-r--r-- 1 echecod echecod 1.3K Dec 7 11:00 fishd.DUA-001
-rw-r--r-- 1 echecod echecod 14K Feb 19 18:21 fishd.DUA-BuildServer000
-rw-r--r-- 1 echecod echecod 2.7K Feb 19 10:47 fish_variables
lrwxrwxrwx 1 echecod echecod 44 Dec 20 16:45 functions -> ../../Dotfiles.d/fish/.config/fish/functions/


These can be found:



$ find ~/.config -name config.fish
/home/echecod/.config/fish/config.fish
$ find ~/.config -name fish_variables
/home/echecod/.config/fish/fish_variables
$ find ~/.config -name functions
/home/echecod/.config/fish/functions


And just in case (because of functions -> ../../Dotfiles.d/fish/.config/fish/functions/):



$ ls -lh ~/Dotfiles.d/fish/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


What is wrong with my find?



FYI:




  • Ubuntu 16.04.3 LTS amd64

  • find (GNU findutils) 4.7.0-git, /usr/bin/find










share|improve this question

























  • @John1024 Sorry about that, but it contains a lot of text, I've show a lot details in the image, and it's hard to copy all of them and keep its structures at the same time, and it is easy spot the point from the image for those experts.

    – CodyChan
    1 hour ago






  • 1





    @John1024 I've formatted it to text, and the problem is solved. Thanks.

    – CodyChan
    47 mins ago











  • Very good. Also, glad the problem was solved.

    – John1024
    44 mins ago
















4















One weird situation occurs to me that find command cannot find some files but can find another, and they all exist in the local path.



The original code as a screenshot:



screen.



The files are there:



$ ls -lh ~/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


But they cannot be found:



$ find ~/.config -name z.lua
$ find ~/.config -name prompt_pwd.fish


The upper directory and files in it:



$ ls -ld ~/.config/fish/
drwx------ 2 echecod echecod 4096 Feb 20 13:35 /home/echecod/.config/fish/

$ ls -lh ~/.config/fish/
total 24K
lrwxrwxrwx 1 echecod echecod 46 Dec 20 16:45 config.fish -> ../../Dotfiles.d/fish/.config/fish/config.fish*
-rw-r--r-- 1 echecod echecod 1.3K Dec 7 11:00 fishd.DUA-001
-rw-r--r-- 1 echecod echecod 14K Feb 19 18:21 fishd.DUA-BuildServer000
-rw-r--r-- 1 echecod echecod 2.7K Feb 19 10:47 fish_variables
lrwxrwxrwx 1 echecod echecod 44 Dec 20 16:45 functions -> ../../Dotfiles.d/fish/.config/fish/functions/


These can be found:



$ find ~/.config -name config.fish
/home/echecod/.config/fish/config.fish
$ find ~/.config -name fish_variables
/home/echecod/.config/fish/fish_variables
$ find ~/.config -name functions
/home/echecod/.config/fish/functions


And just in case (because of functions -> ../../Dotfiles.d/fish/.config/fish/functions/):



$ ls -lh ~/Dotfiles.d/fish/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


What is wrong with my find?



FYI:




  • Ubuntu 16.04.3 LTS amd64

  • find (GNU findutils) 4.7.0-git, /usr/bin/find










share|improve this question

























  • @John1024 Sorry about that, but it contains a lot of text, I've show a lot details in the image, and it's hard to copy all of them and keep its structures at the same time, and it is easy spot the point from the image for those experts.

    – CodyChan
    1 hour ago






  • 1





    @John1024 I've formatted it to text, and the problem is solved. Thanks.

    – CodyChan
    47 mins ago











  • Very good. Also, glad the problem was solved.

    – John1024
    44 mins ago














4












4








4








One weird situation occurs to me that find command cannot find some files but can find another, and they all exist in the local path.



The original code as a screenshot:



screen.



The files are there:



$ ls -lh ~/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


But they cannot be found:



$ find ~/.config -name z.lua
$ find ~/.config -name prompt_pwd.fish


The upper directory and files in it:



$ ls -ld ~/.config/fish/
drwx------ 2 echecod echecod 4096 Feb 20 13:35 /home/echecod/.config/fish/

$ ls -lh ~/.config/fish/
total 24K
lrwxrwxrwx 1 echecod echecod 46 Dec 20 16:45 config.fish -> ../../Dotfiles.d/fish/.config/fish/config.fish*
-rw-r--r-- 1 echecod echecod 1.3K Dec 7 11:00 fishd.DUA-001
-rw-r--r-- 1 echecod echecod 14K Feb 19 18:21 fishd.DUA-BuildServer000
-rw-r--r-- 1 echecod echecod 2.7K Feb 19 10:47 fish_variables
lrwxrwxrwx 1 echecod echecod 44 Dec 20 16:45 functions -> ../../Dotfiles.d/fish/.config/fish/functions/


These can be found:



$ find ~/.config -name config.fish
/home/echecod/.config/fish/config.fish
$ find ~/.config -name fish_variables
/home/echecod/.config/fish/fish_variables
$ find ~/.config -name functions
/home/echecod/.config/fish/functions


And just in case (because of functions -> ../../Dotfiles.d/fish/.config/fish/functions/):



$ ls -lh ~/Dotfiles.d/fish/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


What is wrong with my find?



FYI:




  • Ubuntu 16.04.3 LTS amd64

  • find (GNU findutils) 4.7.0-git, /usr/bin/find










share|improve this question
















One weird situation occurs to me that find command cannot find some files but can find another, and they all exist in the local path.



The original code as a screenshot:



screen.



The files are there:



$ ls -lh ~/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


But they cannot be found:



$ find ~/.config -name z.lua
$ find ~/.config -name prompt_pwd.fish


The upper directory and files in it:



$ ls -ld ~/.config/fish/
drwx------ 2 echecod echecod 4096 Feb 20 13:35 /home/echecod/.config/fish/

$ ls -lh ~/.config/fish/
total 24K
lrwxrwxrwx 1 echecod echecod 46 Dec 20 16:45 config.fish -> ../../Dotfiles.d/fish/.config/fish/config.fish*
-rw-r--r-- 1 echecod echecod 1.3K Dec 7 11:00 fishd.DUA-001
-rw-r--r-- 1 echecod echecod 14K Feb 19 18:21 fishd.DUA-BuildServer000
-rw-r--r-- 1 echecod echecod 2.7K Feb 19 10:47 fish_variables
lrwxrwxrwx 1 echecod echecod 44 Dec 20 16:45 functions -> ../../Dotfiles.d/fish/.config/fish/functions/


These can be found:



$ find ~/.config -name config.fish
/home/echecod/.config/fish/config.fish
$ find ~/.config -name fish_variables
/home/echecod/.config/fish/fish_variables
$ find ~/.config -name functions
/home/echecod/.config/fish/functions


And just in case (because of functions -> ../../Dotfiles.d/fish/.config/fish/functions/):



$ ls -lh ~/Dotfiles.d/fish/.config/fish/functions/
total 92K
-rw-rw-r-- 1 echecod echecod 4.2K Dec 20 16:42 __async_prompt.fish
-rw-rw-r-- 1 echecod echecod 3.0K Dec 20 16:42 done.fish
-rw-rw-r-- 1 echecod echecod 597 Dec 20 16:42 humanize_duration.fish
-rwxrwxr-x 1 echecod echecod 5.2K Dec 20 16:42 __informative_git_prompt.fish*
-rwxrwxr-x 1 echecod echecod 1.4K Dec 20 16:42 prompt_pwd.fish*
-rw-rw-r-- 1 echecod echecod 61K Feb 20 11:38 z.lua


What is wrong with my find?



FYI:




  • Ubuntu 16.04.3 LTS amd64

  • find (GNU findutils) 4.7.0-git, /usr/bin/find







linux command-line find






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 43 mins ago









Kamil Maciorowski

27.4k155982




27.4k155982










asked 2 hours ago









CodyChanCodyChan

274311




274311













  • @John1024 Sorry about that, but it contains a lot of text, I've show a lot details in the image, and it's hard to copy all of them and keep its structures at the same time, and it is easy spot the point from the image for those experts.

    – CodyChan
    1 hour ago






  • 1





    @John1024 I've formatted it to text, and the problem is solved. Thanks.

    – CodyChan
    47 mins ago











  • Very good. Also, glad the problem was solved.

    – John1024
    44 mins ago



















  • @John1024 Sorry about that, but it contains a lot of text, I've show a lot details in the image, and it's hard to copy all of them and keep its structures at the same time, and it is easy spot the point from the image for those experts.

    – CodyChan
    1 hour ago






  • 1





    @John1024 I've formatted it to text, and the problem is solved. Thanks.

    – CodyChan
    47 mins ago











  • Very good. Also, glad the problem was solved.

    – John1024
    44 mins ago

















@John1024 Sorry about that, but it contains a lot of text, I've show a lot details in the image, and it's hard to copy all of them and keep its structures at the same time, and it is easy spot the point from the image for those experts.

– CodyChan
1 hour ago





@John1024 Sorry about that, but it contains a lot of text, I've show a lot details in the image, and it's hard to copy all of them and keep its structures at the same time, and it is easy spot the point from the image for those experts.

– CodyChan
1 hour ago




1




1





@John1024 I've formatted it to text, and the problem is solved. Thanks.

– CodyChan
47 mins ago





@John1024 I've formatted it to text, and the problem is solved. Thanks.

– CodyChan
47 mins ago













Very good. Also, glad the problem was solved.

– John1024
44 mins ago





Very good. Also, glad the problem was solved.

– John1024
44 mins ago










1 Answer
1






active

oldest

votes


















5














~/.config/fish/functions is a symlink. Therefore it's about [emphasis mine]:




-P
Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.



-L

Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the properties of the file to which the link points, not from the link itself [...]. If -L is in effect and find discovers a symbolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched.




(source)



Use find -L. This is an option, not operand; it should appear before path(s).






share|improve this answer


























  • I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

    – CodyChan
    1 hour ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1407705%2ffind-command-cannot-find-my-files-which-do-exist%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









5














~/.config/fish/functions is a symlink. Therefore it's about [emphasis mine]:




-P
Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.



-L

Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the properties of the file to which the link points, not from the link itself [...]. If -L is in effect and find discovers a symbolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched.




(source)



Use find -L. This is an option, not operand; it should appear before path(s).






share|improve this answer


























  • I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

    – CodyChan
    1 hour ago


















5














~/.config/fish/functions is a symlink. Therefore it's about [emphasis mine]:




-P
Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.



-L

Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the properties of the file to which the link points, not from the link itself [...]. If -L is in effect and find discovers a symbolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched.




(source)



Use find -L. This is an option, not operand; it should appear before path(s).






share|improve this answer


























  • I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

    – CodyChan
    1 hour ago
















5












5








5







~/.config/fish/functions is a symlink. Therefore it's about [emphasis mine]:




-P
Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.



-L

Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the properties of the file to which the link points, not from the link itself [...]. If -L is in effect and find discovers a symbolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched.




(source)



Use find -L. This is an option, not operand; it should appear before path(s).






share|improve this answer















~/.config/fish/functions is a symlink. Therefore it's about [emphasis mine]:




-P
Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.



-L

Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the properties of the file to which the link points, not from the link itself [...]. If -L is in effect and find discovers a symbolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched.




(source)



Use find -L. This is an option, not operand; it should appear before path(s).







share|improve this answer














share|improve this answer



share|improve this answer








edited 32 mins ago

























answered 1 hour ago









Kamil MaciorowskiKamil Maciorowski

27.4k155982




27.4k155982













  • I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

    – CodyChan
    1 hour ago





















  • I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

    – CodyChan
    1 hour ago



















I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

– CodyChan
1 hour ago







I've added updates. And after adding -L options, it works. Sorry about my mistake, I though fish was a symlink and never pay attention to symlink issue before this post.

– CodyChan
1 hour ago




















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1407705%2ffind-command-cannot-find-my-files-which-do-exist%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)