zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>,
	Zsh-Users List <zsh-users@zsh.org>
Subject: Re: Finding out where features come from (Was: disown -a)
Date: Wed, 3 Mar 2021 15:45:57 +0100	[thread overview]
Message-ID: <CAP+y1xBOq1QrJEPvtfbGC8beFOQe-3k+PmdU8SicAKje1mzWmA@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xCzmBZ-PibdXaKQRU_pbQmSv6kXw7WUXNnWCwTnVqj3bg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]

oh I see now that you already changed the topic

Pier Paolo Grassi


Il giorno mer 3 mar 2021 alle ore 15:00 Pier Paolo Grassi <
pierpaolog@gmail.com> ha scritto:

> that's quite interesting, for me at least. If you have any good link to
> articles or books about the history of shell programs and the motivations
> behind various choices and want to share I would really appreciate it
> idk if this is interesting to the list also or I should message privately
> about topics not directly related to zsh, or if I should start a new
> thread, I would appreciate some direction on this
>
> Pier Paolo Grassi
>
>
> Il giorno mer 3 mar 2021 alle ore 11:23 Stephane Chazelas <
> stephane@chazelas.org> ha scritto:
>
>> 2021-03-03 08:57:15 +0100, Pier Paolo Grassi:
>> > out of curiosity, how have you assembled this informations? from memory
>> or
>> > digging in the source trees?
>> [...]
>>
>> I do collect a number of old archives of various shell source
>> codes downloaded from here and there and look in there for this
>> kind of information. I enjoy this kind of archeological digging.
>>
>> For recent versions, you can generally look in cvs/svn/git logs,
>> or use git blame/svn ann or git log --grep...
>>
>> For older versions, most shells keep changelogs. zsh has some
>> Etc/ChangeLog*, bash has a NEWS and CWRU/changelog. zsh links
>> its changelog to the mailing list. So not only you can find the
>> change, but also the reasoning and discussions behind it. That's
>> quite unique and invaluable.
>>
>> It's hard to obtain old ksh versions. All I have is ksh86 (from
>> some bsd source tree), svr4.2 ksh88d from archive.org, the
>> leaked solaris11's ksh88i, ksh93d from dtksh, ksh85's man page
>> and some of ksh93's since it's been made opensource. There's a
>> RELEASE file in there (and more for the libraries) but it's a
>> bit patchy.
>>
>> BSD shells (based on ash originally published on usenet in 1989,
>> so easy to find, except for OpenBSD which switched to pdksh) are
>> easy as the sccs history is publicly available.
>>
>> For tcsh, someone compiled all versions back to 6.06.1 in the
>> git repo. Some older versions can be found on usenet.
>>
>> I started using zsh around the time bash 2.0 came out. But that
>> was 25 years ago. I can't say I remember much from then. Back
>> then, bash was already quite limited compared to zsh. It didn't
>> even have arrays.
>>
>> --
>> Stephane
>>
>

[-- Attachment #2: Type: text/html, Size: 3543 bytes --]

  reply	other threads:[~2021-03-03 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 11:34 quonting and globbing Pier Paolo Grassi
2021-03-02 11:58 ` Mikael Magnusson
2021-03-02 12:24   ` Pier Paolo Grassi
2021-03-02 23:31 ` disown -a zzapper
2021-03-03  0:05   ` Daniel Shahaf
2021-03-03  7:15     ` Stephane Chazelas
2021-03-03  7:57       ` Pier Paolo Grassi
2021-03-03 10:23         ` Finding out where features come from (Was: disown -a) Stephane Chazelas
2021-03-03 14:00           ` Pier Paolo Grassi
2021-03-03 14:45             ` Pier Paolo Grassi [this message]
2021-03-03  9:36       ` disown -a zzapper
2021-03-03  9:40         ` Peter Stephenson
2021-03-03 20:12         ` Daniel Shahaf
2021-03-03  0:12   ` Daniel Shahaf
2021-03-03 10:17     ` zsh

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=CAP+y1xBOq1QrJEPvtfbGC8beFOQe-3k+PmdU8SicAKje1mzWmA@mail.gmail.com \
    --to=pierpaolog@gmail.com \
    --cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).