unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: ng0 <ng0@libertad.pw>
Cc: guile-user@gnu.org
Subject: Re: How to pass something on to xargs rm?
Date: Tue, 27 Dec 2016 13:07:50 +0100	[thread overview]
Message-ID: <20161227120750.GA16030@jocasta.intra> (raw)
In-Reply-To: <87d1gd7gji.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Tue, Dec 27, 2016 at 11:33:21AM +0000, ng0 wrote:
     Hi,
     
     I have some scripts and small applications I'm slowly moving over
     to guile.
     One of them features this[0] line at the end which passes results on
     to xargs rm. I picked a start with just (system*) everything I
     had before to learn about the behavior and outcome, and improve
     from this point.
     I know that "|" will not work, so what else could possibly work
     (for starters, in the long run I'll generalize and extend what I
     currently have) to execute this command which deletes every file
     listed in the previous search?
     
     [0]: notmuch search --output=files tag:deleted | xargs -L 1 rm
     

I think you want something like:   .... | xargs -I {} rm {}


J'

-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-12-27 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 11:33 How to pass something on to xargs rm? ng0
2016-12-27 12:07 ` John Darrington [this message]
2016-12-27 12:42   ` ng0
2016-12-27 13:04     ` Eli Zaretskii
2017-05-29  9:36     ` Thien-Thi Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161227120750.GA16030@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=guile-user@gnu.org \
    --cc=ng0@libertad.pw \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).