![]() I think you and the people that don’t understand a thing about shells (all those that modded you up basically) should STFU and go right away learn to use a shell, and stop pretending you do.īecause your stupid rant about “rm -i’ alias that can have impact on a script is just plain BS.Īn alias on “rm -i” will just not impact any of your scripts, unless you explicitely make them login scripts, which is plain stupid if it’s not your session script. If I want to do more complex things that I can’t do easily in bash I’ll launch Perl. People talk about PowerShell being a “shell” but it looks more like a scripting language to me. NET objects and what not, but frankly it doesn’t seem very usable as an *interactive user program*. People are all talking about how awesome PowerShell is because it uses. Furthermore, most X window managers can snap a window to the edge of another window or the edge of the screen, making it extremely easy to organize your terminal windows. I can easily navigate between the terminals with Ctrl-PageUp/PageDown, and they don’t clutter the task bar. In a proper Unix terminal emulator, I can have multiple terminals in one window, seperated by tabs. I have to press Tab several times to get the filename I want. In DOS, it completes to the first match and doesn’t show you all possible matches, which is stupid. I hit tab and it completes the filename, or completes it as much as possible and presents you with possible choices. ![]() I just can’t figure out how command history in DOS works, nor do I care about how it actually works – it doesn’t work well and that’s all that matters. Can’t do that in DOS – 4 out of 5 times it gives you the wrong command. To execute the previous command I just hit ‘up’ and ‘enter’. I read a few guides on unix shell programming an within a day or two I was able to write useful shell scripts with the “no sense” sed/awk/xargs/… tools.īash, combined with a good terminal emulator, is a joy to use. “can you really say any of this makes sense in any language known to man?”Īnd you think your grandmother can make sense of a line that looks like “get-childitem | measure-object -property length -sum”? Face it: to the average user, it doesn’t matter what language you use, they’re all just magical gibberish. bash is the best interactive command line tool that exists today for shell work, period. Some people will tell you that bash is bloated, and I often will write a shell script so it does not NEED bash and can run on something leaner like ash or dash, but for an interactive shell bash cannot be beat. I like the extensions that GNU added to bash over plain old sh, and when I’m working in ksh on an AIX system, I miss all the power of gnu readline and bash’s special variables and keybindings like $! or !cmd:p, etc. I routinely pipe text through sed, awk, cut, tac… I construct lists of files with find, iterate over them in bash for loops or with xargs. Once you learn how to pipe together commands and the unix shell way of thinking, I think working in bash is very intuitive. Likewise, if you grew up using VBScript, bash is not intuitive (but the inverse is also very true). However, if you’ve never used a shell then it is not intuitive at all. ![]() I believe that bash is very intuitive if you’re fluent in ksh, for example. Whether or not a language is intuitive is determined by the user’s familiarity with similar languages, etc. I think it doesn’t really make sense to call a language unintuitive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |