Orphaning Eshell

Orphaning Eshell

[Aidan Gauland]

I regret to announce that Eshell will no longer have a maintainer. As I
no longer use it myself, I am rather ill-suited to maintaining it. You
may recall that in February 2013, John Wiegley officially handed Eshell
over to me in light of my contributions and enthusiasm. Since then,
however, I have found myself using Eshell less and less, and I have
hardly touched it in months. I still think it is a useful piece of
software, but it fills a very small niche that I no longer operate in.

Regards,
Aidan Gauland

Re: Orphaning Eshell

[Geoffrey Teale]

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

I use eshell every day.  I'd be sad to see it go unmaintained.   As yet I
don't think I've ever had to look at the code, so I've no idea what the
maintenance task would be like.  Is it a lot of work?

-- 
Geoff Teale


On 4 April 2014 09:52, Aidan Gauland <aidalgol@amuri.net> wrote:

> I regret to announce that Eshell will no longer have a maintainer. As I
> no longer use it myself, I am rather ill-suited to maintaining it. You
> may recall that in February 2013, John Wiegley officially handed Eshell
> over to me in light of my contributions and enthusiasm. Since then,
> however, I have found myself using Eshell less and less, and I have
> hardly touched it in months. I still think it is a useful piece of
> software, but it fills a very small niche that I no longer operate in.
>
> Regards,
> Aidan Gauland
>
>

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

Re: Orphaning Eshell

[Nic Ferrier]

I would maintain eshell.

Sorry to see you go Aidan.


tealeg@member.fsf.org writes:

> I use eshell every day.  I'd be sad to see it go unmaintained.   As yet I
> don't think I've ever had to look at the code, so I've no idea what the
> maintenance task would be like.  Is it a lot of work?

Re: Orphaning Eshell

[Aidan Gauland]

On 05/04/14 03:59, Geoffrey Teale wrote:
> I use eshell every day.  I'd be sad to see it go unmaintained.   As yet
> I don't think I've ever had to look at the code, so I've no idea what
> the maintenance task would be like.  Is it a lot of work?

The only hairy bits for me were completion, control structures (loops
and if-then-else), and built-in variables.  Eshell uses pcomplete for
completion, which I would still like to puzzle out and document some
day, and is a bit cryptic.  Only for is documented, but Eshell appears
to implement while and if.  As for built-in variables, their
implementation wasn't obvious, and I never got far with tracking them down.

Regards,
Aidan Gauland