From: "merv" <merv@spidernet.com.cy>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] initscripts in python
Date: Fri, 18 Apr 2003 02:32:23 +0300 [thread overview]
Message-ID: <3E9F63B7.29004.103CC5DA@localhost> (raw)
In-Reply-To: <1050618384.29994.5.camel@chinstrap.penguins.homeunix.net>
thanks for the link and the encouragement
i have been in this discussion now for a couple of days (since the first
post entitled "initscripts in python") and am preparing to sit down and
plan this "extensible shell plugin" somewhat more deliberately and
carefully.
several people have posted links to previous attempts/projects at this
kind of things and all of them seem to have fizzled out over time. of
course this is part of the nature of community development but
perhaps it is also an indication of the size of this task.
I am a C programmer by profession so I guess that's where I'll start but
I want to build in Python/C APIs as early as possible since Python has
been the topic of the discussion and seems a particularly good place to
start in view of its syntactical/semantic "cleanness", besides being
Gentoo fodder. I intend very much that an extensible shell with Python
plugin should be a testing bed and that others will follow, including
Perl, Ruby etc etc ... whatever there is a demand/need/curiosity for.
And the implementation will need breaking down into build-
time/emerge packaging, initscripts/boot-time related code, extensible
(dynamically loadable) shell environment code, script-
loading/reading/interpreting code, etc etc etc
watch this space...patiently (I have four babies and seven kittens
besides a full time job :) )
"IDEAS MAKE SOFTWARE BEAUTIFUL" - so keep 'em comin' !
On 17 Apr 2003 at 18:26, Caleb Shay wrote:
> On Thu, 2003-04-17 at 16:56, merv wrote:
> <snip>
>
> >
> > >From my own point of view, the underlying theme of the idea is the
> > concept of a more "extensible" shell.
>
> <snip>
>
> I saw this line and thought "A plugin extensible shell, how cool would
> that be? You want perl regexps? Load the preg extension. Don't use
> tab-completion? Don't load the tab-completion extension and save some
> ram. A quick google turns up:
>
> http://sourceforge.net/projects/dxsh/
>
> Doesn't look like it's seen much activity lately, but what a great idea!
>
> Caleb
>
>
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
--
Merv Hammer
mailto: merv@spidernet.com.cy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-17 23:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 1:29 [gentoo-dev] initscripts in python Justin Whitney
2003-04-16 4:09 ` Daniel Armyr
2003-04-16 5:38 ` merv
2003-04-16 7:25 ` Jeff Rose
2003-04-16 8:49 ` merv
2003-04-16 8:19 ` Paul de Vrieze
2003-04-16 8:52 ` Sven Vermeulen
2003-04-16 20:54 ` Justin Whitney
2003-04-17 20:05 ` merv
2003-04-17 5:49 ` Joseph Carter
2003-04-17 6:27 ` George Shapovalov
2003-04-17 18:25 ` merv
2003-04-17 7:42 ` Paul de Vrieze
2003-04-16 22:44 ` Abhishek Amit
2003-04-17 6:45 ` Sven Vermeulen
2003-04-17 20:56 ` merv
2003-04-17 22:26 ` Caleb Shay
2003-04-17 23:32 ` merv [this message]
2003-04-17 18:18 ` merv
2003-04-16 21:08 ` Brad Laue
2003-04-17 6:47 ` Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 11:13 merv
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=3E9F63B7.29004.103CC5DA@localhost \
--to=merv@spidernet.com.cy \
--cc=gentoo-dev@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