On 03/16/2015 02:54 PM, Eduardo A. Bustamante López wrote:
> Also, I'd like to start using github issues to track bug reports, again, as a
> mirror, so that we can provide people with an always up to date reference of
> the status of the bugs they reported, and in what specific point of bash's
> h
On Mon, Mar 16, 2015 at 3:54 PM, Eduardo A. Bustamante López
wrote:
> I know that some people are interested in a more detailed commit history in
> bash's git repository. After all, it's easier for all of us to just learn to
> use a tool, and use that for everything.
How are you planning on creat
I know that some people are interested in a more detailed commit history in
bash's git repository. After all, it's easier for all of us to just learn to
use a tool, and use that for everything.
The changelog files distributed with bash are useful, *but*, I claim that it'd
be more useful to use the
> Here's the other side: allowing `set -$-' to succeed keeps a Posix-mode
> shell running a script from throwing a fatal error. Allowing it also
> keeps the bug reports down. The same rationale can be used to add -c and
> -s to the no-op flags, since those are command-line options that end up
> i
On 3/13/15 8:47 PM, Eduardo A. Bustamante López wrote:
>> You can avoid these surprises by making -i just as other options, i.e.,
>> working within the shell not just when a shell is started. [..]
> I don't think it's good to have set +/-i available after initialization. It's
> more complex to hand
