[prev] [thread] [next] [lurker] [Date index for 2007/01/10]
> > A more direct clue is that variable expansion is performed before the > command is executed. So $A is not X in a place located after A=X. Which may seem reasonable if you're used to it. Boy am I happy that I'm not. I couldn't even suspect that. Seriously, why is this good (as opposed to "why does it work that way")? > > Really, I didn't mean to be harsh, but you will get a lot more out of > the unix shell if you at least take 30 mins to understand the basics. > My guess is you'll get that 30 mins back quite quickly in terms of > being able to use the shell to your advantage (whatever shell you're > stuck with). > I didn't mind the "harsh" part too much, this is a list with "hate" in it's name. As to the rest: 1. I do hope you notice a contradiction between your assumption that shells are excellent when you know the basics and your assumption that tcsh is evil, because the people behind tcsh are very likely to be shell experts, so they should have seen the light instead of making a supposedly evil shell. 2. I don't need the hidden benefits of Unix shells, because I'm happy with the interactive features like command completion and I'm happy with Python as a scripting language. I don't think that the ability to change the environments of buggy program invokations is worth the damage caused to my brain by imprinting the warts of a wierd questionable-purpose programming language. 3. I wasn't even talking about shells. I wasn't complaining about the lack of an ugly workaround. What I find interesting is the pointless locking of a file. Responses like "Work around it using your shell", and "patch the source" surprise me.There's stuff above here
Generated at 00:01 on 12 Jan 2007 by mariachi 0.52