Skip to main content
14 events
when toggle format what by license comment
Jun 15, 2020 at 8:04 history edited CommunityBot
Commonmark migration
Jan 13, 2016 at 23:56 vote accept user3321819
Jan 13, 2016 at 18:16 answer added nohillside timeline score: 2
Jan 12, 2016 at 18:27 comment added nohillside Did you try it?
Jan 12, 2016 at 17:26 answer added user3321819 timeline score: -1
Jan 12, 2016 at 17:13 comment added user3321819 There's some weird auto quoting going on when the command is called that screws it up. Since echoing the command actually displays the correct command, I can just pipe it to bash, and it works fine lol....
Jan 12, 2016 at 17:05 comment added user3321819 Passing "$@" would pass all the file paths as 1 long string. Each file path argument needs to be encased in quotes
Jan 12, 2016 at 17:03 history edited user3321819 CC BY-SA 3.0
deleted 4 characters in body
Jan 12, 2016 at 17:00 comment added nohillside Why do you preprocess $@ into $F, can't you pass "$@" to rar directly?
Jan 12, 2016 at 15:07 comment added user3321819 Oops, yeah I didn't mean to have quotes around the ~/archive.rar. and actually, yeah it also does not work in terminal, the error says it still can't open the file(s) in the arguments
Jan 12, 2016 at 15:05 history edited user3321819 CC BY-SA 3.0
removed quotes from archive in script
Jan 12, 2016 at 7:04 comment added nohillside ~ doesn't get expanded inside quotes, so you need at least ~/"archive.rar" there. And I would suspect some issues with handling spaces and quoting also for $F. Does it work if you run it directly in Terminal?
Jan 12, 2016 at 4:36 review First posts
Jan 12, 2016 at 5:57
Jan 12, 2016 at 4:35 history asked user3321819 CC BY-SA 3.0