public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Anyone else having a problem with bash?
Date: Mon, 13 Jul 2015 16:40:12 +0200	[thread overview]
Message-ID: <55a3cdcc.p0QLXw1k9KfcLJfy%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <mo0g12$1ps$1@ger.gmane.org>

Martin Vaeth <martin@mvath.de> wrote:

> Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de> wrote:
> > Martin Vaeth <martin@mvath.de> wrote:
> >>
> >> This is not true, either: Although finally bash took some of the
> >> features of zsh (arrays, regular expression matching, etc.) there
> >> are still many features missing in bash (extended globbing, many
> >> variable and array operations etc.)
> >
> > AFAIK, this was not introduced by zsh but by ksh.
>
> Yes, you are right: To be historically correct, one should call

It migh be of interest that I recently asked David Korn whether adding a bunch 
of typical commands as builtins into the shell was introduced by ksh or by 
Bruce Perens (busybox). David answered:

	As far as I know, I added these to ksh93 before busy box existed.

To be more verbose, even loadable builtins existed in ksh in the middle between 
ksh88 and ksh93.

> many of them "ksh features". However, fact is that zsh *has* almost
> all ksh features (with mainly identical syntax) while bash still
> lacks a lot of them (and for others it has a more cumbersome
> syntax).
>
> This might change in the long run: as mentioned, bash has

It also might be of interest that we decided to standardize a new way to manage 
builtin commands in the shell and this has been derived from the method that 
was introduced for OpenSolaris when ksh93 was added to OpenSolaris in August 
2007:

	Builtins beyond the documented builtins from POSIX must be searched
	by a tagged PATH in POSIX issue 8.

Jörg

-- 
 EMail:joerg@schily.net                    (home) Jörg Schilling D-13353 Berlin
       joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'


  reply	other threads:[~2015-07-13 14:40 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 17:01 [gentoo-user] Anyone else having a problem with bash? walt
2015-07-06 17:18 ` Alexander Kapshuk
2015-07-06 19:07   ` [gentoo-user] " »Q«
2015-07-06 20:43     ` Alex Thorne
2015-07-06 14:09       ` Bill Kenworthy
2015-07-08  4:44         ` Jc García
2015-07-08  5:00           ` Anton Shumskyi
2015-07-08  7:00             ` Alan McKinnon
2015-07-08  9:06               ` Florian Gamböck
2015-07-08  9:28                 ` Stephan Müller
2015-07-08 10:08                   ` Florian Gamböck
2015-07-08 10:13                     ` Joerg Schilling
2015-07-08 10:40                       ` Florian Gamböck
2015-07-08 10:53                         ` Joerg Schilling
2015-07-08  0:48   ` walt
2015-07-08  7:15     ` Florian Gamböck
2015-07-08 13:10       ` Todd Goodman
2015-07-08 13:46         ` Florian Gamböck
2015-07-08 10:17 ` Nikos Chantziaras
2015-07-08 10:29   ` Joerg Schilling
2015-07-09 11:38 ` [gentoo-user] " Stephan Müller
2015-07-09 11:48   ` Neil Bothwick
2015-07-09 12:01     ` Gevisz
2015-07-09 12:07       ` [gentoo-user] " Nikos Chantziaras
2015-07-09 12:20         ` Gevisz
2015-07-09 16:07         ` Neil Bothwick
2015-07-09 17:45           ` Gevisz
2015-07-09 17:54             ` Neil Bothwick
2015-07-09 23:34           ` Nikos Chantziaras
2015-07-09 23:36             ` Nikos Chantziaras
2015-07-09 23:54               ` wraeth
2015-07-10  5:29               ` Franz Fellner
2015-07-10  8:16               ` Neil Bothwick
2015-07-10 15:00                 ` Gevisz
2015-07-10 17:39                   ` Nikos Chantziaras
2015-07-10 22:18                     ` Marc Joliet
2015-07-11 10:22                       ` Nikos Chantziaras
2015-07-11 10:39                         ` Marc Joliet
2015-07-11 20:56                         ` Martin Vaeth
2015-07-12 16:52                           ` Nikos Chantziaras
2015-07-12 17:01                             ` Neil Bothwick
2015-07-12 22:35                               ` Martin Vaeth
2015-07-11  5:53                     ` Martin Vaeth
2015-07-11 11:04                       ` covici
2015-07-11 20:47                         ` Martin Vaeth
2015-07-13  9:21               ` Joerg Schilling
2015-07-13  9:30                 ` Peter Humphrey
2015-07-10  6:06             ` Martin Vaeth
2015-07-10  6:18           ` Martin Vaeth
2015-07-10  8:35             ` Neil Bothwick
2015-07-10 15:31               ` Martin Vaeth
2015-07-13  9:39                 ` Joerg Schilling
2015-07-13 14:00                   ` Martin Vaeth
2015-07-13 15:03                     ` Joerg Schilling
2015-07-13  9:27             ` Joerg Schilling
2015-07-13 13:55               ` Martin Vaeth
2015-07-13 14:40                 ` Joerg Schilling [this message]
2015-07-09 12:19     ` Nikos Chantziaras
2015-07-09 12:24       ` wraeth
2015-07-09 12:37         ` Nikos Chantziaras
2015-07-09 14:46           ` wraeth
2015-07-10 11:46           ` wraeth
2015-07-11 22:21             ` walt
2015-07-09 12:41     ` walt

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=55a3cdcc.p0QLXw1k9KfcLJfy%Joerg.Schilling@fokus.fraunhofer.de \
    --to=joerg.schilling@fokus.fraunhofer.de \
    --cc=gentoo-user@lists.gentoo.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