Comments on: 10-ish Unix CLI File Commands Every WordPress Developer Should Know https://wpshout.com/10-unix-cli-file-commands-every-wp-dev-should-know/ A hub for advanced WordPress users, developers & savvy business owners. Tue, 06 Jun 2017 17:14:50 +0000 hourly 1 https://wordpress.org/?v=6.4.3 By: Working With The Command Line and WP-CLI – WPShout https://wpshout.com/10-unix-cli-file-commands-every-wp-dev-should-know/#comment-20535 Tue, 06 Jun 2017 17:14:50 +0000 https://wpshout.com/?p=11557#comment-20535 […] 10-ish Unix CLI File Commands Every WordPress Developer Should Know […]

]]>
By: Anatomy of a WP-CLI Command: wp database import | WPShout https://wpshout.com/10-unix-cli-file-commands-every-wp-dev-should-know/#comment-20534 Tue, 09 May 2017 15:56:44 +0000 https://wpshout.com/?p=11557#comment-20534 […] Article: 10-ish Unix CLI File Commands Every WordPress Developer Should Know […]

]]>
By: The What, How and Why of WP-CLI: WordPress in Your Terminal | WPShout https://wpshout.com/10-unix-cli-file-commands-every-wp-dev-should-know/#comment-20533 Tue, 31 Jan 2017 16:26:32 +0000 https://wpshout.com/?p=11557#comment-20533 […] don’t think or worry about WP-CLI. (But if you’re interested, here are the basics of file and non-file Unix CLI commands.) WP-CLI isn’t essential and it’s not something you […]

]]>
By: Mastering the Unix Terminal: Working With Permissions, Networking, and Other Key Concepts | WPShout https://wpshout.com/10-unix-cli-file-commands-every-wp-dev-should-know/#comment-20532 Tue, 17 Jan 2017 17:22:28 +0000 https://wpshout.com/?p=11557#comment-20532 […] Last time we covered Unix commands, we talked about how you can move around the filesystem from the command line. These ideas are crucial; if you don’t understand the basics of navigating files and folders from the terminal, there’s not a lot you can do on the command line. If you’ve not mastered that, start with this on file-manipulation from the command line. […]

]]>
By: Gary Hall https://wpshout.com/10-unix-cli-file-commands-every-wp-dev-should-know/#comment-20531 Tue, 29 Nov 2016 20:09:52 +0000 https://wpshout.com/?p=11557#comment-20531 In filenames you can use wildcards and ‘*” is a very common one. So ls *.txt will show you all files with the extension txt. and ls twenty*.pdf will list all pdf files that start with twenty. And cp *.log ~/oldlogs will copy all files ending in .log.

Which brings up this: rm *.log will wipe out all files ending in .log in one stroke. When using wildcards with rm it is best to use rm -i, i stands for interactive and prompts you y or n to delete a file. So, if you were to type rm -i *.log then you will be prompted for each file that matches *.log. So, if one of the logs was named superimportant_DONOTDELETE.log then rm -i *.log would give you the opportunity to keep that file.

]]>