Steven J Long <sl...@rathaus.eclipse.co.uk> posted 2115173.05gpc6t...@news.friendly-coders.info, excerpted below, on Tue, 02 Jun 2009 09:18:54 +0100:
> Surely it would be best simply to ask end-users which of a few variants > they'd find easiest to work with? Or indeed for their suggestions; after > all, they spend a lot more time engaging with the cli/config files than > we do. For this end-user, @ means set. Using it at a location other than the beginning for something else is possible and I'd adapt, but it /is/ confusing. :: lacks that confusion. It does have the additional complication of needing quoted or escaped in the shell, but users are supposed to do a --pretend anyway, and after it doesn't output what's expected, a user of any shell experience at all should conclude with little delay that it /could/ be the escaping even if they aren't sure, and a quick suitably escaped trial will confirm it. So either proposed solution has its caveat that users will ultimately need to learn to deal with, but I still prefer the unambiguity of ::. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
