Re: Interested in contributing to Bash

2017-05-23 Thread Chet Ramey 
On 5/23/17 2:55 PM, John McKown wrote:
> 
> 
> On Tue, May 23, 2017 at 1:39 PM, Chet Ramey  > wrote:
> 
> 
> The best thing to read to learn about how the shell is structured -- other
> than the code itself -- is the unedited version of the chapter I wrote for
> AOSA (The Architecture of Open Source Applications).  It's in the bash-4.4
> distribution in doc/aosa-bash-full.pdf.
> 
> 
> Typos in PDF? I see "Postx" instead of "Posix". Just looks wrong to me. But
> I'm not an expert.

It's quite possible there are typos. I tried to get as many as I could, and
we went back and forth a couple of times, but this was before we really
started editing to cut the length.  It's maybe twice as long as the final
version.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Re: Interested in contributing to Bash

2017-05-23 Thread John McKown 
On Tue, May 23, 2017 at 1:55 PM, John McKown 
wrote:

>
>
> On Tue, May 23, 2017 at 1:39 PM, Chet Ramey  wrote:
>
>>
>> The best thing to read to learn about how the shell is structured -- other
>> than the code itself -- is the unedited version of the chapter I wrote for
>> AOSA (The Architecture of Open Source Applications).  It's in the bash-4.4
>> distribution in doc/aosa-bash-full.pdf.
>>
>
> Typos in PDF? I see "Postx" instead of "Posix". Just looks wrong to me.
> But I'm not an expert.
>

​Never mind. The font on my PC was messed up. It is "Posix" but Adobe
Reader decided to render the work tightly kerned and "smushed together".
There are reasons that I like Helvetica and Times Roman over most others.
Old eyes.​



>
>
>
>>
>> Chet
>> --
>> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>>  ``Ars longa, vita brevis'' - Hippocrates
>> Chet Ramey, UTech, CWRUc...@case.edu
>> http://cnswww.cns.cwru.edu/~chet/
>>
>>
> --
Windows. A funny name for a operating system that doesn't let you see
anything.

Maranatha! <><
John McKown

Re: Interested in contributing to Bash

2017-05-23 Thread John McKown 
On Tue, May 23, 2017 at 1:39 PM, Chet Ramey  wrote:

>
> The best thing to read to learn about how the shell is structured -- other
> than the code itself -- is the unedited version of the chapter I wrote for
> AOSA (The Architecture of Open Source Applications).  It's in the bash-4.4
> distribution in doc/aosa-bash-full.pdf.
>

Typos in PDF? I see "Postx" instead of "Posix". Just looks wrong to me. But
I'm not an expert.



>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~
> chet/
>
>


-- 
Windows. A funny name for a operating system that doesn't let you see
anything.

Maranatha! <><
John McKown

Re: Interested in contributing to Bash

2017-05-23 Thread Chet Ramey 
On 5/23/17 2:49 PM, Pranav Deshpande wrote:
> Thank you!
> I will be reading it now. What do you think of the 'bugs' Eduardo mentioned?

I'll weigh in later. I'm still catching up from traveling.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Re: Interested in contributing to Bash

2017-05-23 Thread Pranav Deshpande 
Thank you!
I will be reading it now. What do you think of the 'bugs' Eduardo mentioned?

Regards,
Pranav.

On Wed, May 24, 2017 at 12:09 AM, Chet Ramey  wrote:

> On 5/21/17 11:53 AM, Eduardo Bustamante wrote:
> > On Sun, May 21, 2017 at 5:44 AM, Pranav Deshpande
> >  wrote:
> > [...]
> >> Any guidance on so as how to get started? Are there any tasks that I can
> >> take up so that I get introduced to the code base.
> >
> > My recommendations would be:
> >
> > - Clone the git repository (https://savannah.gnu.org/git/?group=bash)
> > - Subscribe both bug-bash@gnu.org and help-b...@gnu.org. Try to
> > reproduce bug reports and report back the results.
> > - Read the mailing list archives
> > (https://lists.gnu.org/archive/html/bug-bash/ and
> > https://lists.gnu.org/archive/html/help-bash/), and take note of any
> > reported bugs that are not answered or fixed yet in the latest `devel'
> > branch of the git repository.
> > - Some people place bug reports in the Savannah issue tracker
> > (https://savannah.gnu.org/support/?group=bash). You might also want to
> > check there and see if any of the issues reported there are still not
> > fixed in the latest `devel' branch.
>
> The best thing to read to learn about how the shell is structured -- other
> than the code itself -- is the unedited version of the chapter I wrote for
> AOSA (The Architecture of Open Source Applications).  It's in the bash-4.4
> distribution in doc/aosa-bash-full.pdf.
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~
> chet/
>

Re: Interested in contributing to Bash

2017-05-23 Thread Chet Ramey 
On 5/21/17 11:53 AM, Eduardo Bustamante wrote:
> On Sun, May 21, 2017 at 5:44 AM, Pranav Deshpande
>  wrote:
> [...]
>> Any guidance on so as how to get started? Are there any tasks that I can
>> take up so that I get introduced to the code base.
> 
> My recommendations would be:
> 
> - Clone the git repository (https://savannah.gnu.org/git/?group=bash)
> - Subscribe both bug-bash@gnu.org and help-b...@gnu.org. Try to
> reproduce bug reports and report back the results.
> - Read the mailing list archives
> (https://lists.gnu.org/archive/html/bug-bash/ and
> https://lists.gnu.org/archive/html/help-bash/), and take note of any
> reported bugs that are not answered or fixed yet in the latest `devel'
> branch of the git repository.
> - Some people place bug reports in the Savannah issue tracker
> (https://savannah.gnu.org/support/?group=bash). You might also want to
> check there and see if any of the issues reported there are still not
> fixed in the latest `devel' branch.

The best thing to read to learn about how the shell is structured -- other
than the code itself -- is the unedited version of the chapter I wrote for
AOSA (The Architecture of Open Source Applications).  It's in the bash-4.4
distribution in doc/aosa-bash-full.pdf.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Re: Interested in contributing to Bash

2017-05-21 Thread Eduardo Bustamante 
On Sun, May 21, 2017 at 5:44 AM, Pranav Deshpande
 wrote:
[...]
> Any guidance on so as how to get started? Are there any tasks that I can
> take up so that I get introduced to the code base.

My recommendations would be:

- Clone the git repository (https://savannah.gnu.org/git/?group=bash)
- Subscribe both bug-bash@gnu.org and help-b...@gnu.org. Try to
reproduce bug reports and report back the results.
- Read the mailing list archives
(https://lists.gnu.org/archive/html/bug-bash/ and
https://lists.gnu.org/archive/html/help-bash/), and take note of any
reported bugs that are not answered or fixed yet in the latest `devel'
branch of the git repository.
- Some people place bug reports in the Savannah issue tracker
(https://savannah.gnu.org/support/?group=bash). You might also want to
check there and see if any of the issues reported there are still not
fixed in the latest `devel' branch.

Interested in contributing to Bash

2017-05-21 Thread Pranav Deshpande 
Hello everyone,
I am a beginner when it comes to open source and am interested in
contributing to GNU Bash.

Any guidance on so as how to get started? Are there any tasks that I can
take up so that I get introduced to the code base.

Regards,
Pranav.