[CLUE-Tech] A Simpler way

[ian]

For sake of argument.  I do all file moving based on the CLI.  It is the
easiest for me to remember and to get the file path I use bash file
completion.  I know that I'm getting it to the correct location because
otherwise the file completion does not turn into the path that I need.
Doing the GUI is harder for me since I have to move my hands off of the 
keyboard to click and select things.  I am also known to accidently drag
and drop files into the wrong directory.  Overwriting files is hard to do
as I have interactive default aliased for mv & rm.  

Certian tasks such as layout of a CD for burning is significantly easier
for me to visualize how the layout is going to turn out and if I'm missing
files.  

So by your definition "least mental energy, least possiblity of mistake,
with greatest reliability" is going to be different for everyone.  

ian


On Sun, Apr 15, 2001 at 12:51:01PM -1000, Cyberclops wrote:
> I should think simplest would mean using the least mental energy with
> the least possibility of making a mistake, while achieving the greatest
> reliability.  The KDE GUI method is easy except for the fact that with a
> directory with a large number of files in it, it seems to lock up.  So
> if the command line is not to hard to remember, and if it's more
> reliable, then I would say that it is the simplest.  I notice that even
> the most ardent CLI fans come up short when it comes to remembering some
> certain command to do some certain task.  On the other hand a GUI is
> there to see, and the "drag and drop" are common through out.  For
> myself, I find even with the CLI, I like to have Konqueror open so I can
> easily see the file path and file spelling (naming).
> 
> ian wrote:
> > 
> > In a highly complex system the "simplest way" can be defined as the way
> > you know how to do it.  When there is as many ways to do something as you
> > can imagine and one more, getting it done in a way you know how counts
> > pretty high in my definition.
> > 
> > It is an academic exercise to find the way that is the simplest.  What
> > criteria will it be defined to do something the simplest?  Least keystrokes?
> > Least button clicks?
> > 
> > I routinely use both the CLI & GUI to do things.  Its all a matter of what
> > I know now and what I have the time to learn.
> > 
> > ian
> > 
> > On Sun, Apr 15, 2001 at 08:49:40AM -1000, Cyberclops wrote:
> > > I think you make a very good point about doing things the simplest way.
> > > One of the problems I have is just understanding the command line
> > > syntax.  Ideally. I would like a session with computers where a simple
> > > file is created and then we learn to manipulate it with the CLI
> > > interface and a variety of ways and then explore the possibility of
> > > doing the same maneuvers with a GUI.  SOmetimes I believe the GUI is
> > > simpler for simpler things, but I believe the CLI would be better for
> > > more complex tasks.  I'm also wondering if the CLI is more error free
> > > assuming you type the correct commands ion the first place.  THe reason
> > > I say this is that I know for a fact that the KDE copy or move
> > > operations can become overwhelmed and crash out in the middle of the
> > > operation.  I doubt this happens in a CLI mode only.
> > >
> > > Kevin Cullis wrote:
> > > >
> > > > Hey all,
> > > >
> > > > I've been having a discussion with a programmer friend of mine and it's
> > > > funny how we both have different views of the same problem.  I sometimes
> > > > want to "cut and paste" data from the web browser into VIM in order to
> > > > parse the data into useable form, such as records to be inported into a
> > > > database. However, he has stated, along with other programmers I know,
> > > > that I should save the file in HTML and then parse the HTML out of the
> > > > file.  However, while both achieve the same results, my programming
> > > > friends way takes considerably more work and knowledge than my "cut and
> > > > paste" method.  In fact, all I have in my file is the data with a large
> > > > number of spaces which require ONLY one command to use in order to
> > > > remove the multiple spaces rather than his PERL or other method to
> > > > parsing HTML tags.
> > > >
> > > > Why am I mentioning this?  Because most new people to Linux can be
> > > > bombarded with more technical approaches to a problem when sometimes a
> > > > simple problem requires a simple solution.
> > > >
> > > > In VIM, I type:
> > > >
> > > > :%s/   *//g
> > > >
> > > > to remove all multiple spaces leaving only my data in fields.  However,
> > > > my friends approach can be used for more complex approaches to other
> > > > problems which I can consider in future projects.
> > > >
> > > > Just a comment.
> > > >
> > > > Kevin
> > > > _______________________________________________
> > > > CLUE-Tech mailing list
> > > > CLUE-Tech at clue.denver.co.us
> > > > http://clue.denver.co.us/mailman/listinfo/clue-tech
> > > _______________________________________________
> > > CLUE-Tech mailing list
> > > CLUE-Tech at clue.denver.co.us
> > > http://clue.denver.co.us/mailman/listinfo/clue-tech
> > _______________________________________________
> > CLUE-Tech mailing list
> > CLUE-Tech at clue.denver.co.us
> > http://clue.denver.co.us/mailman/listinfo/clue-tech
> _______________________________________________
> CLUE-Tech mailing list
> CLUE-Tech at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-tech