On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote:
WTF - there is a reason the "-f" flag exists - RTFM
I don't know what manual you're reading. But -f has a specific function and *this* *isn't* *it*.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/02/2014 05:59 PM, benfell@parts-unknown.org wrote:
On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote:
WTF - there is a reason the "-f" flag exists - RTFM
I don't know what manual you're reading. But -f has a specific function and *this* *isn't* *it*.
Don't feed the trolls, and be careful of the CC. He's not on the mailing list proper for a reason.
- -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77
On Wed, Apr 02, 2014 at 06:04:00PM -0500, Jim Perrin wrote:
Don't feed the trolls, and be careful of the CC. He's not on the mailing list proper for a reason.
My apologies. I did not realize. But of course you're right.
This issue is all about shell interpretation--before the command string even gets to the command.
Should I always strip the cc when posting to this list?
On Wed, Apr 02, 2014 at 04:46:51PM -0700, benfell@parts-unknown.org wrote:
This issue is all about shell interpretation--before the command string even gets to the command.
Actually, yes and no. Some commands, notably those using the GNU getopt() family, understand the concept of "--" ending _all_ argument parsing and anything after being a parameter and not a command argument.
Apparently zsh handles this differently from what was stated here earlier. If this is indeed the case this is arguably a zsh bug.
Should I always strip the cc when posting to this list?
Nah, just lease Reindl off :)
John
On Wed, Apr 02, 2014 at 07:59:28PM -0500, John R. Dennison wrote:
On Wed, Apr 02, 2014 at 04:46:51PM -0700, benfell@parts-unknown.org wrote:
This issue is all about shell interpretation--before the command string even gets to the command.
Apparently zsh handles this differently from what was stated here earlier. If this is indeed the case this is arguably a zsh bug.
I don't know. I couldn't reproduce the behavior today:
[benfell@munich]~% print $SHELL /bin/zsh [benfell@munich]~% touch -- --DoingMyselfIn [benfell@munich]~% ls -al -- --DoingMyselfIn -rw-rw-r-- 1 benfell benfell 0 Apr 2 18:10 --DoingMyselfIn [benfell@munich]~% rm -- --DoingMyselfIn [benfell@munich]~% ls -al -- --DoingMyselfIn ls: cannot access --DoingMyselfIn: No such file or directory [benfell@munich]~%
On Wed, Apr 02, 2014 at 06:13:05PM -0700, benfell@parts-unknown.org wrote:
I don't know. I couldn't reproduce the behavior today:
If you are able to duplicate the original behavior please let us, or at least me, know. I am curious as to what may have transpired that caused the initial problem.
John
On Wed, Apr 02, 2014 at 03:59:26PM -0700, benfell@parts-unknown.org wrote:
On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote:
WTF - there is a reason the "-f" flag exists - RTFM
I don't know what manual you're reading. But -f has a specific function and *this* *isn't* *it*.
Please ignore and do not respond to this person; he's not a member of the list and is using nefarious methods to post to it.
John
-
benfell＠parts-unknown.org -
Jim Perrin -
John R. Dennison