>>> The major problems with backticks is that they tend to be inconspicuous >>> (and easily confused with bits of dust or fly-droppings) and are often >>> difficult to distinguish from quotes. >>> >>> Rather than write "`find port_dir` (note the backticks)", IMO, it is >>> far easier to write $(find port_dir) - which is syntactically the >>> same but visually more obvious. >> >> That's a fair point. Do you think that the text as it currently exists >> is sufficiently clear, or do you think that it still needs the >> modification you're suggesting? I'm happy to make the change (or someone >> else can if they so desire) if that's what people thing is the right way >> to go. >> >> >> Doug >> > The text as its currently exists is a long way from being clear to a > first timer. And I am talking about the new change that just went in. > > "shar `find port_dir` (note the backticks)", > > or > > "shar $(find port_dir)" > > both address the problem nicely. > > By all means go and make the correction.
I'd second making it clearer, certainly: shar `find port_dir` threw me when I first started writing ports and was looking to submit my work. I think part of the issue was just I'd never used the shell archive command before so I had no idea quite what 'shar' actually was. Perhaps adding a one liner to explain what is actually going to happen and why your doing it might be useful? Personally I think the second suggestion of "shar $(find port_dir)" is the better one, it's far less likely to get mangled by font display and I expect it's easier for people to located $() on their keyboards than ` (backtick) Regards Eric _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
