Fish looks interesting - I might give it a whirl. But I wasn't thinking of
something as extravigantly coded as that. And the trouble with fish is that it
isn't bash - which is the default Linux shell.
My idea is more aimed at people wanting to first learn how to use the bash
shell - like students and new Linux users. Currently, when you first learn the
shell you have to go elsewhere to find info when you get stuck - like a book,
or the Internet, or a computer class. And you often get stuck because you don't
know any commands yet. So my idea is to put all the basic info you need in a
window that pops up alongside the shell when it is launched. The window has a
directory-like list of commands (organised alphabetically, functionally, and in
groups), and basic admin info (runlevels, permissions, etc.), VI and Emacs key
shortcuts, etc. This way you can easily find a command or admin info you need
without having to go elsewhere for it. It would be like having a nicely
organised set of cheat sheets right next to the shell. I believe that this
would cut down the time it takes to learn Linux by maybe half, and possibly
entice more people to try Linux.
RR
Conrad Parker <[EMAIL PROTECTED]> wrote:
On 07/01/2008, R R wrote:
> Thanks,
>
> I might learn some coding and try to make this project for my own use at
> first. I've done some research into similar projects and for some reason
> shells with ease-of-use enhancements have never caught on.
I've heard and read good things about the shell called "fish". It
gives lots of nice hints about what commands to use, and displays help
info in your browser window. Perhaps that could be a good starting
point for you.
cheers,
Conrad.
>
> RR
>
>
> Erik de Castro Lopo wrote:
>
> R R wrote:
>
> > I'm not a coder myself but I have been working on the command
> > lists and admin functions. If there are any coder/s who might
> > be interested in working on this project, please let me know.
>
> I don't want to rain on your parade or anything, but I suspect
> that your chances of finding anyone is vanishingly small.
>
> The reasons for this are as follows:
>
> - Most people who know how to code have enough projects of their
> own that they don't have time for. For me, I have a list in
> a text file of stuff I'd like to do if I could find the time.
> If someone was willing to pay me my current salary, it would
> take me about 10 years to complete my current list. After the
> first year, i suspect that list would grow to 20 years work.
>
> - It sounds like this project of yours would have two participants,
> you in a management role and someone else in a coder role.
> Unfortunately, I think you will find that most coders will have
> had numerous bad experiences with bad management and would be
> unlikely to find an un-paid volunteer project that had a non-
> coding manager all that attractive.
>
> Honestly, coding is not that hard and can be extremely rewarding
> (both personally and professionally) if you take the time to start
> learning. Be aware however, that learning how to program can take
> some time to really master:
>
> http://norvig.com/21-days.html
>
> Erik
> --
> -----------------------------------------------------------------
> Erik de Castro Lopo
> -----------------------------------------------------------------
> "We reject kings, presidents, and voting. We believe in rough
> consensus and running code." -- Dave Clark (IETF 1992)
> _______________________________________________
> coders mailing list
> coders@slug.org.au
> http://lists.slug.org.au/listinfo/coders
>
>
>
> ________________________________
> Make the switch to the world's best email. Get the new Yahoo!7 Mail now.
>
>
> _______________________________________________
> coders mailing list
> coders@slug.org.au
> http://lists.slug.org.au/listinfo/coders
>
>
---------------------------------
Make the switch to the world's best email. Get the new Yahoo!7 Mail now._______________________________________________
coders mailing list
coders@slug.org.au
http://lists.slug.org.au/listinfo/coders
