Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was wondering what the best way to format a search would be through the console. I'm using cygwin because we use MS XP, and I would like to get a comprehensive list of certain files (*.xml) in two seperate dirs.
So far I have this:
find ./ -name *.xml | sort > xmls.txt
But there are a couple things wrong with the format. One is that they include the filepath when I only want the filename. The other is, for some reason that makes no sense to me, it does not put newlines after every file.
I figure there is probably some way to do this using grep, but I must confess I don't know much about that at all.
Awesome, that was exactly what I wanted. And the -print worked perfectly. Just to clarify, does the -exec basename {} extract the filename from the path? That's what I'm inferring from the argument and the result.
Awesome, that was exactly what I wanted. And the -print worked perfectly. Just to clarify, does the -exec basename {} extract the filename from the path? That's what I'm inferring from the argument and the result.
basename (and its opposite dirname) are normal linux/unix commands.
The -exec <command> {} \; structure is part of find. You can substitute <command> with just about any command, the {} part is where find inserts what it has found so the command can do its thing with it.
Thanks guys, you helped a lot. I'll take a look at that. Just curious, but would it be possible to use, instead of printf > filename, fprintf(filename,'%f\n') or something of the like? Perhaps not as efficient but I'm just curious if terminal supports fprintf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.