Re: system-config-users 1.2.39 broken?

From: Les Mikesell (lesmikesell_at_gmail.com)
Date: 10/05/05

  • Next message: Terry Polzin: "FC4 cciss driver" 
    To: For users of Fedora Core releases <fedora-list@redhat.com>
Date: Wed, 05 Oct 2005 14:16:54 -0500

    On Wed, 2005-10-05 at 12:35, Tim wrote:

    > > In my experience the GUI is a major headache for many tasks. It is
    > > slow and cumbersome. Many times in a week I have to change file names
    > > or organize data files. I can do this in CLI in seconds. In the GUI
    > > it take hours. Moving 200 grouped, non-sorted files from one
    > > directory to another is a simple command in the CLI. In the GUI it
    > > takes a bunch of pointing and clicking.
    >
    > In the CLI it takes a lot of typing, changing paths, typing in new
    > names, working out the syntax for your wildcarding/renaming rules.

    But, when doing it interactively, you have path completion and wildcards
    available. When doing it repeatedly, you just save the command
    regardless of the complexity.

    > With a GUI there are wildcarding/batch selection tools, tools which take
    > much of the headache out of remembering the syntax.

    Sometimes, in some GUI's. And if they use a different syntax that makes
    it harder, not easier to remember.

    > A little bit of
    > pointing and clicking makes it easy to shift 200 JPEGs from one place to
    > another and rename them according to a pattern, for instance.

    Or, with a mouse-wiggle you can accidentally duplicate your whole
    directory tree... At least with the CLI you can pause before you
    hit enter to make sure the command is correct.

    > > Changing directories is also a pain in most GUI's that I have used.
    > > Especially when there are deep tree's. Also editing files is much
    > > quicker from a CLI than a GUI. In a term window type in ghex2
    > > {path}/{filename} and it opens. In the GUI, open application, click
    > > through all the various folders to get to the correct file and open.
    >
    > Again, in the CLI you've got to type out the new filepaths.

    Or use file/path completion. Or history recall if you have done
    it recently.

    > It's just
    > as hard to navigate into deeply nested trees,

    But you often don't _have_ to navigate there to access something.

    > and even harder to keep on
    > changing between different directories.

    What?? Pushd/popd; cd -; And, you don't have to "be" there to
    access or move files.

    > And when it comes to editing
    > files, I find a windowed editor much easier to quickly scroll through,
    > scanning the content with my eyes, and adjusting what I want where I
    > want, rather than paging through in a TUI.

    In a text-mode text editor, you normally use commands to navigate, like
    /text<enter> instead of visually scanning. It's obviously faster in
    a large document, but once you are used to it, it is also faster than
    moving your hand to the mouse even to move a few lines or words over.

    > The common argument that CLI is superior to *the* GUI seems to hinge on
    > arguing that the CLI is superior to some *particular* crap GUIs that the
    > person has to put up with. When it comes to file management, I'm yet to
    > find anything that makes things easier than using Directory Opus
    > (whether that be the Amiga or PC version, and I don't mean the
    > two-window pane thing it was at version 4).

    It's partly a matter of scale. There's a point where GUI operations
    just take to long to build their iconic representations and the result
    is not particularly useful because of the visual clutter. Suppose you
    want to copy some arbitrary file to some arbitrary location in a tree
    of many thousands of files and directories, and you already know their
    names (which is likely if some GUI mechanism hasn't been hiding them
    from you). How is scanning though the thousands of things you don't
    want to see going to help access the one you already know you want?

    On the other hand, if you are not doing anything new and the GUI
    designer has built a simple interface for everything you will ever
    attempt with your combination of programs I can see that you might
    prefer it. It just hasn't happened that way for me yet. 

    -- 
  Les Mikesell
    lesmikesell@gmail.com
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Terry Polzin: "FC4 cciss driver"

    Relevant Pages

    • Re: GUI vs: CLI (was: Shell command in VB6)
      ... >>or using the GUI. ... Unless the command you used for that CLI makes its way ... contains all the options #commented out, you use your text editor to ...
      (comp.programming)
    • Re: [OT] Debian mailinglists [was: RE: Debian or Ubuntu?]
      ... also technically be utilizing a GUI to assist in the administration :-) ... something can't be done with the CLI, I'm just saying that there are ... tasks that I find simpler in the GUI. ... from the command line I find more difficult than using a graphical tool. ...
      (Ubuntu)
    • Re: [opensuse] Beginner: How do I mount a floppy disk? Summary
      ... GUI having been tried at all. ... Sorta sounds like he was using a GUI to me...or is there a command line ... CLI command....thought it brought up a GUI disk manager? ... the modern state of linux - reflected as well in the rant sent later by ...
      (SuSE)
    • Re: GUI vs: CLI
      ... > If you're going to the trouble of a second interface for the command line, ... > program and then write a GUI wrapper around it? ... that hard to build a GUI which is also a CLI. ...
      (comp.programming)
    • Re: Should the Command Line Be Deep-Sixed?
      ... CLI in particular, as about the usefulness of CLIs in general ... I find the GUI for GIMP (and back when I last saw Photoshop, ... a programmer for her familiarity with a particular language; ... to learning any of the shells installed on his Ubuntu netbook. ...
      (rec.arts.sf.fandom)