9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: giacomo@tesio.it (Giacomo Tesio)
Subject: [9fans] Why Plan 9 uses $ifs instead of $IFS?
Date: Tue, 17 Oct 2017 18:22:50 +0200	[thread overview]
Message-ID: <CAHL7psHTBvGq5=j4b+MFZQbBTTRkP8ptaQmyf5hW3t7Rjq6k7w@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmLKHSzypKz-zvU1zOEHuirsAHsKiGq9C3skV+NzZ2JO+w@mail.gmail.com>

2017-10-17 18:00 GMT+02:00 Skip Tavakkolian <skip.tavakkolian at gmail.com>:

> On Tue, Oct 17, 2017, 8:05 AM Giacomo Tesio <giacomo at tesio.it> wrote:
>
>> Really? Just aesthetics? :-o
>>
>
>
>> This would flips the question a bit: I wonder why the same designers
>> chose uppercase variable names while designing Unix... :-)
>>
>
> Programs can evolve, why not names? There was no expectation that sh
> scripts would work in rc.
>


They can! For sure! But usually they evolve towards a goal... and I'm a
curious person.. :-)

Also this is not about sh scripts run by rc, but sh script run by an sh
shell started by rc.
Or, rc scripts run by an rc shell invoked by an sh.

Just to explain, for example, you could have an sh script that changes
$USER and then invoke psu that would keep using the previous $user.


Giacomo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.9fans.net/private/9fans/attachments/20171017/900fd815/attachment-0001.html>


  reply	other threads:[~2017-10-17 16:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 14:38 Giacomo Tesio
2017-10-17 14:39 ` Dan Cross
2017-10-17 15:05   ` Giacomo Tesio
2017-10-17 15:18     ` Charles Forsyth
2017-10-17 15:45       ` Giacomo Tesio
2017-10-17 16:04         ` Giacomo Tesio
2017-10-17 17:35           ` Dan Cross
2017-10-17 22:32           ` Tiago Natel
2017-10-17 16:00     ` Skip Tavakkolian
2017-10-17 16:22       ` Giacomo Tesio [this message]
2017-10-17 15:46 ` Teodoro Santoni
2017-10-17 18:28 ` Anthony Martin
2017-10-17 21:12   ` Jules Merit
2017-10-17 21:45     ` Jules Merit
2017-10-17 21:49       ` Jules Merit
2017-10-17 22:18         ` Charles Forsyth

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='CAHL7psHTBvGq5=j4b+MFZQbBTTRkP8ptaQmyf5hW3t7Rjq6k7w@mail.gmail.com' \
    --to=giacomo@tesio.it \
    /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).