Comments on: Why bash/*nix rules http://blogs.gnome.org/johncarr/2007/02/26/why-bashnix-rules/ Making your brain invert and fall out of your ear since 2007 Tue, 11 Aug 2009 14:52:44 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Evan http://blogs.gnome.org/johncarr/2007/02/26/why-bashnix-rules/comment-page-1/#comment-1 Evan Thu, 29 Mar 2007 13:37:07 +0000 http://blogs.gnome.org/johncarr/?p=16#comment-1 WRT to opening multiple files . . . just use gvim instead of gedit! Ok, editor wars aside, I would use: locate mv-simple | xargs -n1 gedit The -n1 argument to xargs means that xargs should only pass 1 argument at a time to gedit -- in other words it will open gedit once per file that locate returns. WRT to opening multiple files . . . just use gvim instead of gedit!

Ok, editor wars aside, I would use: locate mv-simple | xargs -n1 gedit

The -n1 argument to xargs means that xargs should only pass 1 argument at a time to gedit — in other words it will open gedit once per file that locate returns.

]]> By: jonnylamb http://blogs.gnome.org/johncarr/2007/02/26/why-bashnix-rules/comment-page-1/#comment-2 jonnylamb Tue, 06 Mar 2007 12:07:10 +0000 http://blogs.gnome.org/johncarr/?p=16#comment-2 echo `locate mv-simple` | xargs -i cp {} ~/Desktop Using the -i argument on xargs means it'll replace {} with the arg (filename in this, and most, example), instead of just plonking it at the end. echo `locate mv-simple` | xargs -i cp {} ~/Desktop

Using the -i argument on xargs means it’ll replace {} with the arg (filename in this, and most, example), instead of just plonking it at the end.

]]>