Use long flags when scripting (2013)

Re:Use long flags when scripting (2013) by thequux on Friday September 18, 2020 @05:26PM (#24522041)

Recent (as in, within the last ~3-5 years) versions of GNU tar automatically detect the type of compression and apply the appropriate tool, so you can often get away with `tar xvf`.

[ Parent | on HN ]

Re:Use long flags when scripting (2013) by ahartmetz on Friday September 18, 2020 @07:11PM (#24522751)

Actually close to 12 years, GNU tar 1.21 https://www.gnu.org/software/tar/

Another "recent" (much more recent IIRC) change is that you don't need the dot anymore in find to search in the current directory.

[ Parent | on HN ]

Re:Use long flags when scripting (2013) by Hello71 on Friday September 18, 2020 @07:39PM (#24522941)

according to https://git.savannah.gnu.org/cgit/findutils.git/commit/find/..., this functionality has been present since findutils was moved under source control in 1996.

[ Parent | on HN ]

Re:Use long flags when scripting (2013) by jfrunyon on Tuesday September 22, 2020 @12:17AM (#24550788)

I believe that GNU find used to (in some cases?) show a warning if the directory was omitted. Could be wrong.

[ Parent | on HN ]

Re:Use long flags when scripting (2013) by mehrdadn on Friday September 18, 2020 @08:48PM (#24523635)

I think the dot actually gives you issues on Mac? Or something like that. I remember encountering issues with it.

[ Parent | on HN ]

Re:Use long flags when scripting (2013) by taejo on Saturday September 19, 2020 @04:24AM (#24526044)

You have to specify a directory for the find on Mac; it's only a GNUism to omit it.

[ Parent | on HN ]

Re:Use long flags when scripting (2013) by mehrdadn on Saturday September 19, 2020 @06:34AM (#24526455)

Oh I see, I got it backwards somehow. Thanks!

[ Parent | on HN ]