From: jpl.jpl at gmail.com (John P. Linderman)
Subject: [COFF] 21st Century Equivalent to 'learn'?
Date: Thu, 5 Mar 2020 07:43:59 -0500 [thread overview]
Message-ID: <CAC0cEp9XeonwiWPa38ooWEkxXPB=Jq7FPvx40x3xPZNDbo1z6w@mail.gmail.com> (raw)
In-Reply-To: <20200305010021.GA23129@minnie.tuhs.org>
Marc Rochkind used to recommend reading the entire UNIX manual each year.
That was good advice in the late 70's, but it would be hopelessly
impractical now, quite beyond the lack of a manual to read. There are just
too many commands and libraries. A valuable service would be to identify
the most useful tools. Those in the old manuals would be an interesting
starting point, but I can't remember when I last used "ar" command, which I
mostly used to pack multiple files into a single one to save inodes and
wasted file system space, neither of which matter any more. If there were a
corpus of contemporary shell scripts, identifying the most used commands
could be interesting. Perl's CPAN (comprehensive perl archive network)
could be a corpus of scripts from which the most commonly used system calls
could be extracted.
On Wed, Mar 4, 2020 at 8:00 PM Warren Toomey <wkt at tuhs.org> wrote:
> On Wed, Mar 04, 2020 at 01:49:25PM +1000, Warren Toomey wrote:
> > Hi all, I'm looking for an interactive tool to help students learn the
> > Unix/Linux command line. I still remember the "learn" tool. Is there an
> > equivalent for current systems?
> > Thanks in advance for any tips/pointers.
>
> I've made a start with a new version of a "learn"ing tool. It uses tmux
> to have a pane of instructions and a pane where the user enters commands.
> Link to the repo is:
> https://github.com/DoctorWkt/tlearn/blob/master/tlearn
>
> This is all protoyping at present. I'd love any ideas & suggestions.
>
> Cheers, Warren
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200305/41c2c99c/attachment.html>
next prev parent reply other threads:[~2020-03-05 12:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 3:49 wkt
2020-03-04 6:23 ` spedraja
2020-03-04 6:55 ` thomas.paulsen
2020-03-04 9:53 ` wkt
2020-03-04 19:31 ` dave
2020-03-05 1:00 ` wkt
2020-03-05 12:43 ` jpl.jpl [this message]
2020-03-05 21:23 ` arrigo
2020-03-06 3:14 ` grog
2020-03-06 9:10 ` akosela
2020-03-07 21:50 ` dave
2020-03-07 22:05 ` clemc
2020-03-07 23:02 ` dfawcus+lists-coff
2020-03-08 0:02 ` clemc
2020-03-06 3:39 ` bakul
2020-03-12 20:53 ` rtomek
2020-03-08 3:39 rudi.j.blom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC0cEp9XeonwiWPa38ooWEkxXPB=Jq7FPvx40x3xPZNDbo1z6w@mail.gmail.com' \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).