(Appologies if this doesn't get associated with the right thread, since it's not a "reply". I just wanted to add 2 cents..)
I also wanted to say I agree with David's view... it's annoying having to quote globbing rules in scp etc. There was a time when I didn't really value this.. but recently I've been been bumping into this a lot more often with things like: scp server:path/file* find . -name somefile*.ext At which point -- I'm sure you get the idea. So, the options I see: 1. keep as is 2. configuration option -- but as Michael points out: "Configurability is the root of all evil" (well... not ideal at least) 3. 'noglob' command... not a lot better 4. Only expand globbing patterns when valid (as in bash) Does anyone have anything to say against option 4? Sure, error messages from commands like 'ls file*' are going to change from: fish: Warning: No match for wildcard “file*”. The command will not be executed. ls file* ^ to: ls: cannot access file*: No such file or directory but I don't see why this should be a big deal. Or are there some important cases I've missed, where this is a bigger deal? Diggory ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
