command line vs gui
in [General Linux]
|
Prev: micro solution backpack cd-writer hell
Next: "...error while loading shared libraries: libg2c.so.0"
From: Tobias Brox on 30 Nov 2005 07:30 [Chris Barts] > You can pipe anything in a Unix shell: I commonly convert image files from > one format to another using command-line programs, for example, something > that is an exercise in pure binary I/O. No use to do piping for that anymore; http://www.imagemagick.org/script/convert.php -- This signature has been virus scanned, and is probably safe to read Tobias Brox, 69?42'N, 18?57'E
From: Tobias Brox on 30 Nov 2005 08:06 [Lee Sau Dan] > Peter> Because it's NOT infinite. Boolean forms have a "normal > Peter> form" to which all may be reduced: the conjunction of > Peter> disjuncts of atomic propositions and their negations. > It's infinite because the grammar is recursive. A rational number can also be written recursively, still any rational number can be expressed in a normalized form, using only two integers. Similarly, any recursive boolean expression, no matter how deep it is, can be expressed non-recursively. Further on, it is possible to cover the very most of the common use cases with a simple user interface. I'm quite sure that it should be trivial to make a GUI to find, and using such an interface will be easier than to read the find manual. However, quite often find is used as part of a script, and the possibility to combine different commands into a script is something that cannot easily be done in a GUI. -- This signature has been virus scanned, and is probably safe to read Tobias Brox, 69?42'N, 18?57'E
From: Jacob Sparre Andersen on 30 Nov 2005 08:06 Reinder Verlinde wrote: > Jacob Sparre Andersen <sparre(a)nbi.dk> wrote: > Thanks for that pointer. Zsh indeed seems to offer better completion > than other shells I know of. However, on my system (Mac OS X without > any effort from my side to configure Zsh), I would not say that it > 'generally' gives me a list of available commands/options/files. For > example, the first tool I tried is rmdir. Zsh did not inform me > about its '-p' option, and erroneously listed all files in my home > directory as arguments. It definitely sounds like Mac OS X comes with a lousy Zsh installation. There's no zshcompsys(1) manual? The first one or two screen-fulls of that manual should be enough to get you started, if the operating system doesn't activate command completion in Zsh for you. - But this still depends on having a reasonable collection of command completion configuration files (in Debian these come as a part of the "zsh" package). >> That's a nice idea. Another nice idea (I can't remember _where_ I >> saw it) is to let a GUI generate commands in the shell. That >> allows the user to take the generated commands and generalize them >> as needed. > > commando did that, too. (aslo, it got all information it needed from > the executable file itself. That decreased the risk of getting a > mismatch between what a command accepted and what commando thought > it accepted. If that idea had caught on, zsh could auto-configure > itself) That sounds cool, but it sounds like something that requires quite a lot from the implementation of the commands to be completed. It's probably less complex than writing a separate command completion configuration file, but in a slightly anarchistic world like ours, I think it is more realistic to try to get the command completion configuration files written. > The preferred I/O format in the new Windows shell seems to be a sort > of SQL table. The shell auto-converts these to text when showing > them to the user. That doesn't sound completely stupid. - Actually it is probably as good a choice as text. > msh> get-childitem | sort-object extension | select extension > | where { $_.extension.length -eq 4 } > > > to list all four-character file extensions in the current directory > in alphabetical order > > The text/Unix 'equivalents' for these commands would be: > get-childitem ~= ls > sort-object ~= sort > select ~= cut > where ~= grep > > but there is no way I can see to extract those file extensions from > ls. That's logical, since the concept of a "file extension" doesn't exist in Unix. If you want to emulate `select extension`, with: egrep '[.]' | perl -lpe 's/^.+[.]([^.]+)$/$1/' Thus making the command: ls | egrep '[.]' | perl -lpe 's/^.+[.]([^.]+)$/$1/' | sort \ | grep '^....$' Which I would simplify to: ls | egrep '[.]....$' | perl -lpe 's/^.+[.]([^.]+)$/$1/' | sort > Also, I think the windows shell is more readable and more maintainable. I agree that `select extension` is easier to read than `egrep '[.]' | perl -lpe 's/^.+[.]([^.]+)$/$1/'`, but since this concept is Microsoft specific, I consider that comparison slightly unfair. The Msh way of picking out elements with a specific length is definitly more readable than the Unix way. I think Msh seems more readable, but I think the flexibility and standardised syntax I get from Zsh outweighs that benefit. A properly thought-through open shell standard using some of the ideas used in Msh would probably win over Zsh. Jacob -- Photo of the day: http://billeder.jacob-sparre.dk/dagens/2005-11-25
From: stan on 30 Nov 2005 10:27 Chris Barts <puonegf+hfrarg(a)tznvy.pbz> wrote: :> :> I do not understand your remark. Can you elaborate on it? :> : You can pipe anything in a Unix shell: I commonly convert image files from Well, just to be more precise--- you can pipe what you want- but ONLY if the apps on both ends of the pipe can read/write to stdio. Same statement applies to Windows and lots of other OS's. Stan -- Stan Bischof ("stan" at the below domain) www.worldbadminton.com
From: Shmuel (Seymour J.) Metz on 30 Nov 2005 14:48
In <fM-dnSPYOuEvoBDeRVn-iw(a)is.co.za>, on 11/29/2005 at 11:50 PM, news(a)absamail.co.za said: >My bare-bones newsreader just dumps the 'envelope' & contents to a >text-frame. You're confusing envelope with header. >the author sequence is inside the context. "author sequence"? "context"? Do you mean that the attribution line is within the body? >What do YOU need the References field for ? I need it in order to be able to construct a correct followup. Others need it because they use threaded news readers. >BTW these days the 'envelope' is getting massively absurd, You're confusing envelope with header. >also with emails. Four short lines[1], unless you're using ESMTP extensions. It's the header that is getting bloated, along with those insane disclosure getting tacked on to the body. [1] HELO/EHLO, MAIL FROM, RCPT TO, DATA. -- Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel> Unsolicited bulk E-mail subject to legal action. I reserve the right to publicly post or ridicule any abusive E-mail. Reply to domain Patriot dot net user shmuel+news to contact me. Do not reply to spamtrap(a)library.lspace.org |