On 2026-10-22 13:18, c186282 wrote:
On 10/22/26 06:35, Carlos E.R. wrote:
On 2026-10-21 11:09, The Natural Philosopher wrote:
On 20/10/2026 19:15, rbowman wrote:
In high school the 'college entrance' kids took 2 years of LatinHonestly cant say. I did Latin and French. I liked Latin but it was
followed
by 2 years of French or German. The business and shop kids took
Spanish.
Which would have been more useful in my later life?
fairly useless. I can just about make myself understood in French
Spanish was not considered important here in Europe.
That's not surprising. Spain was isolationist for centuries. This was
started a reversion by the II R which was killed by the Francoist,
which again were isolationist.
It was the democratic regime of 1976 which opened up "finally".
˙˙ Umm ... you're forgetting south and central America - mass
˙˙ quantities of Spanish speakers (except Brazil). In the USA
˙˙ if you want a 2nd language you learn Spanish.
No, I'm not forgetting, I'm simply talking about the claim that in
Europe Spanish was not considered important, some decades ago.
On 10/22/26 07:48, Carlos E.R. wrote:
On 2026-10-22 13:18, c186282 wrote:
On 10/22/26 06:35, Carlos E.R. wrote:
On 2026-10-21 11:09, The Natural Philosopher wrote:
On 20/10/2026 19:15, rbowman wrote:
In high school the 'college entrance' kids took 2 years of LatinHonestly cant say. I did Latin and French. I liked Latin but it was >>>>> fairly useless. I can just about make myself understood in French
followed
by 2 years of French or German. The business and shop kids took
Spanish.
Which would have been more useful in my later life?
Spanish was not considered important here in Europe.
That's not surprising. Spain was isolationist for centuries. This
was started a reversion by the II R which was killed by the
Francoist, which again were isolationist.
It was the democratic regime of 1976 which opened up "finally".
˙˙ Umm ... you're forgetting south and central America - mass
˙˙ quantities of Spanish speakers (except Brazil). In the USA
˙˙ if you want a 2nd language you learn Spanish.
No, I'm not forgetting, I'm simply talking about the claim that in
Europe Spanish was not considered important, some decades ago.
˙ Since its empire went to hell Spain really hasn't
˙ been an 'important player' in Europe or elsewhere.
˙ Franco got some attention, but not much.
˙ There's *something* about Spanish economics - and
˙ seems true in S.America as well - that prevents
˙ 'general success'. The old patron/peon system and
˙ the thinking it creates may be an important factor.
On 2026-10-23 13:08, c186282 wrote:
On 10/22/26 07:48, Carlos E.R. wrote:
On 2026-10-22 13:18, c186282 wrote:
On 10/22/26 06:35, Carlos E.R. wrote:
On 2026-10-21 11:09, The Natural Philosopher wrote:
On 20/10/2026 19:15, rbowman wrote:
In high school the 'college entrance' kids took 2 years of Latin >>>>>>> followedHonestly cant say. I did Latin and French. I liked Latin but it
by 2 years of French or German. The business and shop kids took >>>>>>> Spanish.
Which would have been more useful in my later life?
was fairly useless. I can just about make myself understood in French >>>>>>
Spanish was not considered important here in Europe.
That's not surprising. Spain was isolationist for centuries. This
was started a reversion by the II R which was killed by the
Francoist, which again were isolationist.
It was the democratic regime of 1976 which opened up "finally".
˙˙ Umm ... you're forgetting south and central America - mass
˙˙ quantities of Spanish speakers (except Brazil). In the USA
˙˙ if you want a 2nd language you learn Spanish.
No, I'm not forgetting, I'm simply talking about the claim that in
Europe Spanish was not considered important, some decades ago.
˙˙ Since its empire went to hell Spain really hasn't
˙˙ been an 'important player' in Europe or elsewhere.
˙˙ Franco got some attention, but not much.
˙˙ There's *something* about Spanish economics - and
˙˙ seems true in S.America as well - that prevents
˙˙ 'general success'. The old patron/peon system and
˙˙ the thinking it creates may be an important factor.
Well, currently Spanish is one of the official languages in the EU. And there is an important trading agreement between the EU and the americas, which as it has been contested I don't know if it is active now or not.
On 10/23/26 08:11, Carlos E.R. wrote:
On 2026-10-23 13:08, c186282 wrote:
On 10/22/26 07:48, Carlos E.R. wrote:
On 2026-10-22 13:18, c186282 wrote:
On 10/22/26 06:35, Carlos E.R. wrote:
On 2026-10-21 11:09, The Natural Philosopher wrote:
On 20/10/2026 19:15, rbowman wrote:
In high school the 'college entrance' kids took 2 years of Latin >>>>>>>> followedHonestly cant say. I did Latin and French. I liked Latin but it >>>>>>> was fairly useless. I can just about make myself understood in
by 2 years of French or German. The business and shop kids took >>>>>>>> Spanish.
Which would have been more useful in my later life?
French
Spanish was not considered important here in Europe.
That's not surprising. Spain was isolationist for centuries. This >>>>>> was started a reversion by the II R which was killed by the
Francoist, which again were isolationist.
It was the democratic regime of 1976 which opened up "finally".
˙˙ Umm ... you're forgetting south and central America - mass
˙˙ quantities of Spanish speakers (except Brazil). In the USA
˙˙ if you want a 2nd language you learn Spanish.
No, I'm not forgetting, I'm simply talking about the claim that in
Europe Spanish was not considered important, some decades ago.
˙˙ Since its empire went to hell Spain really hasn't
˙˙ been an 'important player' in Europe or elsewhere.
˙˙ Franco got some attention, but not much.
˙˙ There's *something* about Spanish economics - and
˙˙ seems true in S.America as well - that prevents
˙˙ 'general success'. The old patron/peon system and
˙˙ the thinking it creates may be an important factor.
Well, currently Spanish is one of the official languages in the EU.
And there is an important trading agreement between the EU and the
americas, which as it has been contested I don't know if it is active
now or not.
˙ Spain isn't *nothing* ... but it's not a France or Germany.
˙ Industry/money, it always seems behind the proverbial curve.
Janis Papanagnou <janis_papanagnou+ng@hotmail.com>:
On 2026-10-17 22:47, Lawrence D?Oliveiro wrote:
I've just done this ("a script change while it's running") [*]
[*] What I've done was to run the following script "dynchg.sh"
˙˙ while read ; do
˙˙˙˙˙˙ echo $REPLY
˙˙ done
and change it (from another terminal) while it runs by
˙˙ sed -i '2p' dynchg.sh
As the "-i" option is not defined by the POSIX standard but by GNU sed,
I assume that your example uses GNU sed.
[...]
On 17 Oct 2026 08:52:49 GMT, St‚phane CARPENTIER wrote:
If you take the Beatles, one of the biggest band known for two things:
first their songs were loved by a lot of people and second they were
unable to read a partition.
[...]
Do you think they wrote songs by trying every possible note at once and
just ended up keeeping the good ones?
On 18 Oct 2026 14:23:10 GMT, St‚phane CARPENTIER wrote:
To sing under your shower, musical theory is useless. To compose songs
meant to be first class worldwide hit, you can't avoid it.
You forgot the key detail: "to do so efficiently, economically, and predictably, even in the face of changing taste, etc".
Lots of hummers have had #1 hits.
But I feel this conversation is focusing WAY too much on pop music stars, with are probably about 1% of people who earn their living by music one
way or another, and for which the actual "music" part is 30% or less of
the job description.
I think it's good to learn other languages, even if you never get
to the point were you can carry on a conversation.
It exposes you
to different concepts, stretching your mind a little (plus you don't
have to turn the cereal box over if you happen to pick up the French
side). Words in one language don't necessarily mean exactly the same
as the nearest equivalent in another; it's sort of like the way the
inch and centimeter marks don't line up on a ruler. This means that
subtle gradations can be different from one language to another.
And then there are the adjustments an English speaker has to make
to handle the Spanish verb "gustar"... I suppose the differences
must be even grater when going to, say, Indian or oriental
languages.
On 2026-10-21 00:54, Helmut Waitzmann wrote:
Janis Papanagnou <janis_papanagnou+ng@hotmail.com>:
On 2026-10-17 22:47, Lawrence D?Oliveiro wrote:
I've just done this ("a script change while it's running") [*]
[*] What I've done was to run the following script "dynchg.sh"
˙˙ while read ; do
˙˙˙˙˙˙ echo $REPLY
˙˙ done
and change it (from another terminal) while it runs by
˙˙ sed -i '2p' dynchg.sh
As the "-i" option is not defined by the POSIX standard but by GNU
sed, I assume that your example uses GNU sed.
Yes. (I've just used '-i' for simplicity.)
A better example would have been to issue (from another shell window)
the command
˙˙ echo "echo END" >> dynchg.sh
and we then see that after terminating the above loop the "END" will
be printed.
(I'm testing with ksh but suppose that in bash it would be similar.)
Le 19-10-2026, Tapiro Ubriaco <interwebs.dude@gmail.com> a ‚crit˙:
On 17 Oct 2026 08:52:49 GMT, St‚phane CARPENTIER wrote:
If you take the Beatles, one of the biggest band known for two things:
first their songs were loved by a lot of people and second they were
unable to read a partition.
[...]
Do you think they wrote songs by trying every possible note at once and
just ended up keeeping the good ones?
You cut my message to make it say exactly the opposite of what I mean
and you dare ask me that question? What The Fuck?
Le 20-10-2026, Charlie Gibbs <cgibbs@kltpzyxm.invalid> a ‚crit˙:
I think it's good to learn other languages, even if you never get
to the point were you can carry on a conversation.
Agreed
It exposes you
to different concepts, stretching your mind a little (plus you don't
have to turn the cereal box over if you happen to pick up the French
side). Words in one language don't necessarily mean exactly the same
as the nearest equivalent in another; it's sort of like the way the
inch and centimeter marks don't line up on a ruler. This means that
subtle gradations can be different from one language to another.
And then there are the adjustments an English speaker has to make
to handle the Spanish verb "gustar"... I suppose the differences
must be even grater when going to, say, Indian or oriental
languages.
Agreed and that imply something you didn't state: when you realise some differences between your native language and other languages, you
discover things about your own language. So learning a new language is
good at the same time for all the reasons you stated but it help you
improve mastering your own language.
˙ KSH and BASH are "mostly compatible". Minor diffs but
˙ nothing hard to get around. Anything you can do in KSH
˙ can be done in BASH.
[...]
˙ If KSH works for you then stick with it.
Note however that MOST distros default to BASH now -
so if you plan
˙ to 'distribute' your work it'd be better to move your
˙ stuff over to BASH.
Most distros, users would have to
˙ intentionally install KSH and scripts would need a
˙ shebang at the top to specify which shell to use.
˙ (good practice, always add the shebang)
KSH and BASH are "mostly compatible". Minor diffs but
nothing hard to get around. Anything you can do in KSH
can be done in BASH.
On 2026-10-24 05:59, c186282 wrote:
Note however that MOST distros default to BASH now -
Yes, Linux often has Bash as its default.
Le 24-10-2026, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> a ‚crit˙:
On 2026-10-24 05:59, c186282 wrote:
Note however that MOST distros default to BASH now -
Yes, Linux often has Bash as its default.
I just keep this because I guess, if I don't consider it to be wrong
because I know what it exactly means, I believe it's often a source of confusion. Because it can mean two different things and three different things must be considered when speaking about the default shell.
Mostly, BASH is the default for the three things, one of them can be
changed effortlessly, one of them would be very difficult to change in
the long term and the last one depend on the interaction with others.
The first thing is the way by which you interact directly with your
SHELL, a kind of REPL. It's just a field in the /etc/passwd file, it's
easy to change and if you prefer any SHELL, just install it, change the
field and it rocks. It's just a matter of taste, nothing can go wrong by changing it.
The second thing is the shell used by the distro to run its script. This
one is clearly often BASH, changing it can be challenging. And things
can go wrong in a lot of ways, from the shebang poorly defined to some specificities expected by the distro. But really, I'm not sure it's a
real issue because I'm not sure there are reason to change it. The
fact that systemd doesn't need any shell script is a reason why it's nit
that important. One can want to change the default provided by the
distro, but changing the script shell provided by the distro mean each
time an update is done, the changes will be removed. And they will need special care. When there are ways to change the default without changing
the scripts provided by the distro.
The second thing is the shell used by the distro to run its script.
This one is clearly often BASH, changing it can be challenging. And
things can go wrong in a lot of ways, from the shebang poorly
defined to some specificities expected by the distro.
On 2026-10-24 05:59, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
[...]
˙˙ If KSH works for you then stick with it.
I use Ksh meanwhile for ~35 years, and since I use a lot of
Ksh features that Bash just doesn't support there's certainly
no reason to switch. (Also its speed is a criterion, BTW. And
back then there were no Bash versions on commercial Unixes;
but commercial Linuxes haven't the prevalence any more today,
and play no role now in my private systems context.)
˙˙ Note however that MOST distros default to BASH now -
Yes, Linux often has Bash as its default.
˙˙ so if you plan
˙˙ to 'distribute' your work it'd be better to move your
˙˙ stuff over to BASH.
Certainly not.
And this is short-sighted. If _portability_ is an issue you'd
better stick with the POSIX subset of both, Ksh and Bash.
(Sadly, as we observe, especially "Linux kiddies" often don't
know what that POSIX subset actually is; in their scripts they
are writing #!/bin/sh and using some bash-specific syntax not
realizing that there's a difference, and that Bash is not the
[portable] *standard*.)
˙˙ Most distros, users would have to
˙˙ intentionally install KSH and scripts would need a
˙˙ shebang at the top to specify which shell to use.
I don't recall to have ever "intentionally installed" Ksh on
Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
you could use out of the box. Later they provided also the
much better "original" [AT&T] Ksh, and meanwhile you find on
(some?) Linuxes ksh93u+m, Martijn Dekker's improved version.
Of course you can call shell scripts with the executable-flag
set and with a she-bang line on top. Personally I run most
shell scripts with the interpreter explicitly provided, as in
˙ ksh my-script flags arguments
allowing easy debugging by adding '-x' without explicit 'set'
command in the script. Only if some script gets the status of
a "standard-command" I regularly use I set the shebang. YMMV.
(So you don't "need" a shebang line, but it's useful.)
˙˙ (good practice, always add the shebang)
Yes, if you are running your scripts executable script (or if
you want to give your editor a hint for syntax highlighting,
what shell is actually used, or just for specification purpose;
but note, as said above, that we see many people have no clear
idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
differ from the standard.
On 2026-10-24, c186282 wrote:
KSH and BASH are "mostly compatible". Minor diffs but
nothing hard to get around. Anything you can do in KSH
can be done in BASH.
Now that sounds like something Greg Sullivan of Microsoft would say.
On 10/24/26 05:53, Janis Papanagnou wrote:
On 2026-10-24 05:59, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
[...]
˙˙ If KSH works for you then stick with it.
I use Ksh meanwhile for ~35 years, and since I use a lot of
Ksh features that Bash just doesn't support there's certainly
no reason to switch. (Also its speed is a criterion, BTW. And
back then there were no Bash versions on commercial Unixes;
but commercial Linuxes haven't the prevalence any more today,
and play no role now in my private systems context.)
˙˙ Note however that MOST distros default to BASH now -
Yes, Linux often has Bash as its default.
˙˙ so if you plan
˙˙ to 'distribute' your work it'd be better to move your
˙˙ stuff over to BASH.
Certainly not.
And this is short-sighted. If _portability_ is an issue you'd
better stick with the POSIX subset of both, Ksh and Bash.
(Sadly, as we observe, especially "Linux kiddies" often don't
know what that POSIX subset actually is; in their scripts they
are writing #!/bin/sh and using some bash-specific syntax not
realizing that there's a difference, and that Bash is not the
[portable] *standard*.)
˙ Delay does not necessarily equate with 'ignorance'.
˙ Different developers ... everyone had their own idea
˙ of a 'perfect shell' - but then had to adapt and adapt
˙ again as the Real Needs became more obvious. Now, most
˙ WILL do the same things - just slightly different syntax.
˙ I rather liked the 'c-shell' long back because it, well,
˙ 'looked like C'. It was one of the things that attracted
˙ me to Unix/Linux in the first place. Now I'm happy (ok,
˙ that's not really the word) with BASH. Not much it
˙ can't do ... but the fudged-fudged-fudged syntax to add
˙ features over time CAN be a pain in the ass.
˙ If I want 'scripting' now, I do it with Python. BASH
˙ or whatever, maybe it just EVOKES the Python scripts,
˙ a one or two-liner. Wrote many rather long BASH scripts
˙ in the past, and while they worked they were, well, just
˙ TOO messy/cryptic.
˙ Last big BASH script I did was for backing up a bunch
˙ of on-network drives. Mount-checking (important), calls
˙ to rsync and openSSH and ftp, local AND 'cloud', all
˙ with some confirmation checks along the way. SEMI-repeating
˙ units but each was a bit 'special'.
˙ (ALWAYS pre-encrypt before sending to 'cloud' - I do
˙ NOT trust the providers one bit. Mine had an extension
˙ that 'suggested' some kind of ZIP, just to help them
˙ waste time)
˙ RE-did it in Python. MUCH shorter and more comprehensible
˙ and a nice easy CSV config file you could tweak in a text
˙ editor or spreadsheet. Python made it all BETTER.
˙ Had a 'C' version of that backup pgm earlier. Worked
˙ fine, but there was a lot of string checking/editing
˙ involved and 'C' is CLUNKY with string shit.
Python
˙ stole the FORTRAN string-slicing stuff, good deal !
˙ Won't ever use BASH or any other 'shell script' for
˙ that kind of task again. Those might be "trad -IX"
˙ but IMHO they're just OVER. "Solutions" MOVED ON.
˙˙ Most distros, users would have to
˙˙ intentionally install KSH and scripts would need a
˙˙ shebang at the top to specify which shell to use.
I don't recall to have ever "intentionally installed" Ksh on
Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
you could use out of the box. Later they provided also the
much better "original" [AT&T] Ksh, and meanwhile you find on
(some?) Linuxes ksh93u+m, Martijn Dekker's improved version.
˙ Um ... these days, almost all distros, you do have
˙ to "intentionally install" KSH or any rivals. BASH
˙ rules by default.
Of course you can call shell scripts with the executable-flag
set and with a she-bang line on top. Personally I run most
shell scripts with the interpreter explicitly provided, as in
˙˙ ksh my-script flags arguments
allowing easy debugging by adding '-x' without explicit 'set'
command in the script. Only if some script gets the status of
a "standard-command" I regularly use I set the shebang. YMMV.
˙ Direct spec of the shell IS useful, however the
˙ 'shebang' trick works well too.
(So you don't "need" a shebang line, but it's useful.)
˙˙ (good practice, always add the shebang)
Yes, if you are running your scripts executable script (or if
you want to give your editor a hint for syntax highlighting,
what shell is actually used, or just for specification purpose;
but note, as said above, that we see many people have no clear
idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
differ from the standard.
˙ I have, I think, FOUR shells on this machine. The
˙ shebang IS required/desired.
˙ Still kinda like 'tcsh', it's there in case I get
˙ a brain-worm and wanna fool around with olde-dayz
˙ stuff. Zsh ain't so bad either.
˙ But, as said, for 'scripting' now, Python is by
˙ far my #1 choice unless the script is like a
˙ simple little ten-liner. Tend to use those on
˙ my PIs.
˙ Fooled around a bit with Lua and Ruby for scripting,
˙ but, really, Python and the MASSIVE number of libs
˙ have them beat. Python will do ANYTHING these days,
˙ just not as fast as 'C'. However CPU speed is less
˙ of a thing these days - I/O ops drag things down
˙ more than the CPU - so Python and 'C' can usually
˙ compete pretty well.
˙ There are Python compilers too. The main issue there
˙ is all the sub-sub-versions of Python, so you always
˙ have to include the entire binaries into each compilation
˙ to ensure it'll work. But then space is also a minor
˙ issue now as well unless you're doing micro-controllers.
˙ Did my share of those - DO teach you how to really SQUEEZE
˙ shit in - all computer kiddies should learn MCs first.
˙ . . .
˙ ("Harry talks in his sleep, didn't you notice ?"
˙˙˙ Slight telling delay, then Hermonie says 'No' :-)
On 10/24/26 07:06, Nuno Silva wrote:
On 2026-10-24, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
Now that sounds like something Greg Sullivan of Microsoft would say.
˙ You "can do" most anything in COBOL or FORTRAN or 'C'
˙ in ANY other lang - just as anything in one shell script
˙ you can do in any other. The issue is 'how easily' - and
˙ that depends on your particular application.
[...]
On 2026-10-26 04:49, c186282 wrote:
On 10/24/26 05:53, Janis Papanagnou wrote:
On 2026-10-24 05:59, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
[...]
˙˙ If KSH works for you then stick with it.
I use Ksh meanwhile for ~35 years, and since I use a lot of
Ksh features that Bash just doesn't support there's certainly
no reason to switch. (Also its speed is a criterion, BTW. And
back then there were no Bash versions on commercial Unixes;
but commercial Linuxes haven't the prevalence any more today,
and play no role now in my private systems context.)
˙˙ Note however that MOST distros default to BASH now -
Yes, Linux often has Bash as its default.
˙˙ so if you plan
˙˙ to 'distribute' your work it'd be better to move your
˙˙ stuff over to BASH.
Certainly not.
And this is short-sighted. If _portability_ is an issue you'd
better stick with the POSIX subset of both, Ksh and Bash.
(Sadly, as we observe, especially "Linux kiddies" often don't
know what that POSIX subset actually is; in their scripts they
are writing #!/bin/sh and using some bash-specific syntax not
realizing that there's a difference, and that Bash is not the
[portable] *standard*.)
˙˙ Delay does not necessarily equate with 'ignorance'.
Not sure why you bring up that statement; nobody said anything
like that.
My statement about the delayed adoption of Ksh features by Bash
was just pointing to the fact that Bash users had to wait before
they could use comfortable features that Ksh had already provided
for (often many) years.
(It's also a bit unfortunate that Bash implemented some features,
and some of them IMO unnecessarily, in a slightly different way,
so that you cannot easily switch between the two shells.)
˙˙ Different developers ... everyone had their own idea
˙˙ of a 'perfect shell' - but then had to adapt and adapt
˙˙ again as the Real Needs became more obvious. Now, most
˙˙ WILL do the same things - just slightly different syntax.
Where not outright wrong, this is very fuzzy. (I don't think it
makes sense to comment on that.)
˙˙ I rather liked the 'c-shell' long back because it, well,
˙˙ 'looked like C'. It was one of the things that attracted
˙˙ me to Unix/Linux in the first place. Now I'm happy (ok,
˙˙ that's not really the word) with BASH. Not much it
˙˙ can't do ... but the fudged-fudged-fudged syntax to add
˙˙ features over time CAN be a pain in the ass.
If you think it's a good idea to use C-shell for scripting, and
since for you it seems to be just a syntax-difference, well, do
what you like in your private working context.
˙˙ If I want 'scripting' now, I do it with Python. BASH
˙˙ or whatever, maybe it just EVOKES the Python scripts,
˙˙ a one or two-liner. Wrote many rather long BASH scripts
˙˙ in the past, and while they worked they were, well, just
˙˙ TOO messy/cryptic.
Yes, I share your valuation of shells being somewhat cryptic and
also "messy".
˙˙ Last big BASH script I did was for backing up a bunch
˙˙ of on-network drives. Mount-checking (important), calls
˙˙ to rsync and openSSH and ftp, local AND 'cloud', all
˙˙ with some confirmation checks along the way. SEMI-repeating
˙˙ units but each was a bit 'special'.
Well, that's what their task mostly is, to "glue" together tools,
even if that glue is quite powerful (yet still somewhat "messy").
˙˙ (ALWAYS pre-encrypt before sending to 'cloud' - I do
˙˙ NOT trust the providers one bit. Mine had an extension
˙˙ that 'suggested' some kind of ZIP, just to help them
˙˙ waste time)
I suppose you mean here that you encrypt your backups before you
store them in the cloud. That's sensible. (I don't store my files
or backups in the cloud in the first place.)
˙˙ RE-did it in Python. MUCH shorter and more comprehensible
˙˙ and a nice easy CSV config file you could tweak in a text
˙˙ editor or spreadsheet. Python made it all BETTER.
I'm not too surprised that you say that.
˙˙ Had a 'C' version of that backup pgm earlier. Worked
˙˙ fine, but there was a lot of string checking/editing
˙˙ involved and 'C' is CLUNKY with string shit.
Shell has higher abstractions compared to "C".
˙˙ Python
˙˙ stole the FORTRAN string-slicing stuff, good deal !
Not sure what you are actually referring here to. (Shell has
such things as well. Unless you mean something more fancy when
you talk about Python or FORTRAN? My memories on FORTRAN are
very faint after 40 years when I had last used it.)
˙˙ Won't ever use BASH or any other 'shell script' for
˙˙ that kind of task again. Those might be "trad -IX"
˙˙ but IMHO they're just OVER. "Solutions" MOVED ON.
With the POSIX-Shells you have at least a standard language on
Unixes.
˙˙ Most distros, users would have to
˙˙ intentionally install KSH and scripts would need a
˙˙ shebang at the top to specify which shell to use.
I don't recall to have ever "intentionally installed" Ksh on
Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
you could use out of the box. Later they provided also the
much better "original" [AT&T] Ksh, and meanwhile you find on
(some?) Linuxes ksh93u+m, Martijn Dekker's improved version.
˙˙ Um ... these days, almost all distros, you do have
˙˙ to "intentionally install" KSH or any rivals. BASH
˙˙ rules by default.
Mine has even ksh93u+m. Some years ago I've got original ksh. Yet
more years ago I've seen PD-ksh. All in the standard distribution.
As said, I've never had to "intentionally install" a Ksh.
There's one exception; back in the days when there was only PD-Ksh
provided in the distributions and that was the only existing Ksh,
but AT&T released their ksh93 for free, I got that from the AT&T
to replace the PD-thing. That *was* an intentional install. But
all those who didn't want The Original they could just use the one
that came with the distros.
Of course you can call shell scripts with the executable-flag
set and with a she-bang line on top. Personally I run most
shell scripts with the interpreter explicitly provided, as in
˙˙ ksh my-script flags arguments
allowing easy debugging by adding '-x' without explicit 'set'
command in the script. Only if some script gets the status of
a "standard-command" I regularly use I set the shebang. YMMV.
˙˙ Direct spec of the shell IS useful, however the
˙˙ 'shebang' trick works well too.
(So you don't "need" a shebang line, but it's useful.)
˙˙ (good practice, always add the shebang)
Yes, if you are running your scripts executable script (or if
you want to give your editor a hint for syntax highlighting,
what shell is actually used, or just for specification purpose;
but note, as said above, that we see many people have no clear
idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
differ from the standard.
˙˙ I have, I think, FOUR shells on this machine. The
˙˙ shebang IS required/desired.
˙˙ Still kinda like 'tcsh', it's there in case I get
˙˙ a brain-worm and wanna fool around with olde-dayz
˙˙ stuff. Zsh ain't so bad either.
I don't consider it a good idea to use 'csh' or 'tcsh' for shell *programming*. (Browse the web for the well known paper with the
thoroughly explained rationales.)
I know some folks use and prefer 'tcsh' as interactive shells.
(Although the Bash, Zsh, or Ksh, are meanwhile quite comfortable
to use also interactively.)
˙˙ But, as said, for 'scripting' now, Python is by
˙˙ far my #1 choice unless the script is like a
˙˙ simple little ten-liner. Tend to use those on
˙˙ my PIs.
˙˙ Fooled around a bit with Lua and Ruby for scripting,
˙˙ but, really, Python and the MASSIVE number of libs
˙˙ have them beat. Python will do ANYTHING these days,
˙˙ just not as fast as 'C'. However CPU speed is less
˙˙ of a thing these days - I/O ops drag things down
˙˙ more than the CPU - so Python and 'C' can usually
˙˙ compete pretty well.
˙˙ There are Python compilers too. The main issue there
˙˙ is all the sub-sub-versions of Python, so you always
˙˙ have to include the entire binaries into each compilation
˙˙ to ensure it'll work. But then space is also a minor
˙˙ issue now as well unless you're doing micro-controllers.
˙˙ Did my share of those - DO teach you how to really SQUEEZE
˙˙ shit in - all computer kiddies should learn MCs first.
(I'm not the appropriate person to discuss Python, Lua, Ruby, and
similar.)
On 2026-10-26 04:59, c186282 wrote:
On 10/24/26 07:06, Nuno Silva wrote:
On 2026-10-24, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
Now that sounds like something Greg Sullivan of Microsoft would say.
˙˙ You "can do" most anything in COBOL or FORTRAN or 'C'
˙˙ in ANY other lang - just as anything in one shell script
˙˙ you can do in any other. The issue is 'how easily' - and
˙˙ that depends on your particular application.
(Be careful; if your argument goes in the direction of "language A
is Turing-complete so you can use it simulating language B, which
makes it effectively the same", then that statement would be of no
practical value!)
I want to give you an example code from a little shell tool I wrote:
˙ function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}
(What this does is that whenever the environment variable 'LINES'
changes - e.g. if you pick your mouse and resize the X-window - then
that function gets triggered and the actions defined executed.)
I'd be interested how you'd implement or emulate that, say, in Bash.
I want to give you an example code from a little shell tool I wrote:
function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}
(What this does is that whenever the environment variable 'LINES'
changes - e.g. if you pick your mouse and resize the X-window - then
that function gets triggered and the actions defined executed.)
I'd be interested how you'd implement or emulate that, say, in Bash.
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
[...]
I want to give you an example code from a little shell tool I wrote:
function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}
(What this does is that whenever the environment variable 'LINES'
changes - e.g. if you pick your mouse and resize the X-window - then
that function gets triggered and the actions defined executed.)
I'd be interested how you'd implement or emulate that, say, in Bash.
I do something similar in bash, but using a different mechanism (so this isn't a response to your challenge).
I trap on SIGWINCH.
On 10/26/26 01:41, Janis Papanagnou wrote:
On 2026-10-26 04:59, c186282 wrote:
On 10/24/26 07:06, Nuno Silva wrote:
On 2026-10-24, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
Now that sounds like something Greg Sullivan of Microsoft would say.
˙˙ You "can do" most anything in COBOL or FORTRAN or 'C'
˙˙ in ANY other lang - just as anything in one shell script
˙˙ you can do in any other. The issue is 'how easily' - and
˙˙ that depends on your particular application.
(Be careful; if your argument goes in the direction of "language A
is Turing-complete so you can use it simulating language B, which
makes it effectively the same", then that statement would be of no
practical value!)
˙ I know I will offend The Religious.
˙ Fuck 'em.
˙ Task, BEST solution for YOU. That is The
˙ Standard so far as I'm concerned.
I want to give you an example code from a little shell tool I wrote:
˙˙ function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}
(What this does is that whenever the environment variable 'LINES'
changes - e.g. if you pick your mouse and resize the X-window - then
that function gets triggered and the actions defined executed.)
I'd be interested how you'd implement or emulate that, say, in Bash.
˙ I'd write it in PYTHON now˙ :-)
˙ Some OS.System() and maybe Subprocess calls.
˙ Leverage the existing simple/low-level utils
˙ in Linux to your advantage. Run, parse,
˙ mutate, USE.
˙ Done a lot of apps that simply grab output
˙ from those simple Linux utils - then parse
˙ and trim and mix. Why re-invent the wheel ?
˙ You CAN - but WHY ???
On 10/26/26 01:04, Janis Papanagnou wrote:[...]
On 2026-10-26 04:49, c186282 wrote:
On 10/24/26 05:53, Janis Papanagnou wrote:
On 2026-10-24 05:59, c186282 wrote:
Not sure why you bring up that statement; nobody said anything
like that.
˙ My following exposition explains why.
My statement about the delayed adoption of Ksh features by Bash
was just pointing to the fact that Bash users had to wait before
they could use comfortable features that Ksh had already provided
for (often many) years.
˙ Well, good for them.
˙ I'll stick to my philosophic "Functional Convergence"
˙ theory here. If shell X does something neat-o then it
˙ HAS to be incorporated into all others - some way, some
˙ how, neat or not.
(It's also a bit unfortunate that Bash implemented some features,
and some of them IMO unnecessarily, in a slightly different way,
so that you cannot easily switch between the two shells.)
˙˙ Different developers ... everyone had their own idea
˙˙ of a 'perfect shell' - but then had to adapt and adapt
˙˙ again as the Real Needs became more obvious. Now, most
˙˙ WILL do the same things - just slightly different syntax.
Where not outright wrong, this is very fuzzy. (I don't think it
makes sense to comment on that.)
˙ I think it makes good sense. Everybody just HAS to
˙ somehow incorporate everyone else's good ideas
˙ eventually. Otherwise --> TRASH BIN of history.
[snip Csh talk]
˙˙ If I want 'scripting' now, I do it with Python. BASH
˙˙ or whatever, maybe it just EVOKES the Python scripts,
˙˙ a one or two-liner. Wrote many rather long BASH scripts
˙˙ in the past, and while they worked they were, well, just
˙˙ TOO messy/cryptic.
Yes, I share your valuation of shells being somewhat cryptic and
also "messy".
˙ VERY messy and OFTEN 'cryptic' (unless very short).
˙ Just no NEED for such shit anymore.
˙˙ Last big BASH script I did was for backing up a bunch
˙˙ of on-network drives. Mount-checking (important), calls
˙˙ to rsync and openSSH and ftp, local AND 'cloud', all
˙˙ with some confirmation checks along the way. SEMI-repeating
˙˙ units but each was a bit 'special'.
Well, that's what their task mostly is, to "glue" together tools,
even if that glue is quite powerful (yet still somewhat "messy").
˙ But NOT 'comprehensible' a year or two LATER.
[snip Python talk]
˙˙ (ALWAYS pre-encrypt before sending to 'cloud' - I do
˙˙ NOT trust the providers one bit. Mine had an extension
˙˙ that 'suggested' some kind of ZIP, just to help them
˙˙ waste time)
I suppose you mean here that you encrypt your backups before you
store them in the cloud. That's sensible. (I don't store my files
or backups in the cloud in the first place.)
˙ I very much mean to encrypt the backups BEFORE you
˙ send them to 'cloud'.
Don't put un-encrypted shit
˙ on their sites for a millisecond. Do NOT trust them !
˙ AES-xxx is good, though sometimes used Camilla.
˙ With several langs/FTP you can put a file on 'cloud'
˙ and then set the datetime/ownership to whatever the
˙ original had. That's how I did it for a decade+ - works
˙ very well. Encrypt, upload, then tweak the specifics.
˙ Pirates get NOTHING.
˙˙ RE-did it in Python. MUCH shorter and more comprehensible
˙˙ and a nice easy CSV config file you could tweak in a text
˙˙ editor or spreadsheet. Python made it all BETTER.
I'm not too surprised that you say that.
˙ Do you disagree ???
˙˙ Had a 'C' version of that backup pgm earlier. Worked
˙˙ fine, but there was a lot of string checking/editing
˙˙ involved and 'C' is CLUNKY with string shit.
Shell has higher abstractions compared to "C".
˙ Slightly - but also CLUNKY and hard to understand
˙ a year or two later.
Doing serious string stuff in
˙ BASH and several others ... nasty !
˙ Look, if you're 20-something it MAY be possible to
˙ hold all the sense/logic of older shit in your head.
˙ Believe me - that CHANGES. Too much shit on a
˙ small drive, so to speak.
˙˙ Python
˙˙ stole the FORTRAN string-slicing stuff, good deal !
Not sure what you are actually referring here to. (Shell has
such things as well. Unless you mean something more fancy when
you talk about Python or FORTRAN? My memories on FORTRAN are
very faint after 40 years when I had last used it.)
˙ Um ... check. Almost all the Python string shit
˙ was 'borrowed' from FORTRAN. This is a GOOD thing.
˙ SO often you have to slice and dice and squish
˙ string stuff together in the real world. It'd
˙ better be EASY and OBVIOUS or you're doomed.
[snip]
˙˙ Um ... these days, almost all distros, you do have
˙˙ to "intentionally install" KSH or any rivals. BASH
˙˙ rules by default.
Mine has even ksh93u+m. Some years ago I've got original ksh. Yet
more years ago I've seen PD-ksh. All in the standard distribution.
As said, I've never had to "intentionally install" a Ksh.
˙ Umm ... what IS this 'ksh'-defaulting distro ???
[snip]
[...]
˙ Never got TOO far into ZSH ... but it DOES have a lot
˙ of potential. Don't count it out of the picture.
[big snip of digressions]Janis
On Fri, 16 Oct 2026 09:55:25 +0100, The Natural Philosopher wrote:
On 16/10/2026 07:08, Tapiro Ubriaco wrote:
I don't understand the rabid anti-intellectualism that's going aroundI am a fully qualified degree possessing engineer, in both general and
here.
electrical engineering.
Which makes you a different beast than a _scientist_, surely :-)
There is a place for theory, but its a very much smaller place than most
third rate intellectuals would have you believe
Where are these third rate intellectuals?
and reliance on theory
rather than practice and common sense is the reason why the Left makes
such a fuckup of things.
I thought we were talking about the relationship between science and >engineering, not socialism, but eh.
Sure, you don't need a mechanical engineering degree to drive your car
around (duh!), but if you were working in the field it would generally
help, and I am very, very happy that my car was designed by people with
an actual degree.
Such faith. It almost certainly was not.
In fact almost all design is done by draughtsmen
Or technicians.
I wonder what my friends with degrees in "automotive engineering" at >Stellantis are actually doing, then...
Bless!I wonder what my friends with degrees in "automotive engineering" at
Stellantis are actually doing, then...
Ah. Eh. Well. Could you tell them that software in the Citroen
Aircross C5, 2026 edition, eh, really *sucks* ...
I'm using it as an example of everything that is wrong with modern
software witing. I don't think that a degree would make much
difference, but common sense does.
And this from someone who actually likes to read books like "Object
Oriented Software Construction, 2nd Edition" :)
On Sat, 21 Nov 2026 18:17:38 -0000 (UTC), Bob wrote:
Ah. Eh. Well. Could you tell them that software in the Citroen
Aircross C5, 2026 edition, eh, really *sucks* ...
I'm using it as an example of everything that is wrong with modern
software witing. I don't think that a degree would make much
difference, but common sense does.
And this from someone who actually likes to read books like "Object
Oriented Software Construction, 2nd Edition" :)
Are you referring to safety-critical systems like engine management, transmission, cruise control, braking etc, or to something less
crucial, namely the infotainment system?
I assume there is a clear separation between the two ...
Bob wrote:
Ah. Eh. Well. Could you tell them that software in the Citroen
Aircross C5, 2026 edition, eh, really *sucks* ...
I'm using it as an example of everything that is wrong with modern
software witing. I don't think that a degree would make much
difference, but common sense does.
And this from someone who actually likes to read books like "Object
Oriented Software Construction, 2nd Edition" :)
Are you referring to safety-critical systems like engine management, transmission, cruise control, braking etc, or to something less
crucial, namely the infotainment system?
I assume there is a clear separation between the two ...
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:27:16 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |