On Sat, 25 Mar 2017 15:16:31 -0400, Chet Ramey wrote:
>
> On 3/24/17 11:57 PM, Torka Noda wrote:
> > From what I understand, \[ and \] characters are only
> > useful for the prompts, right?
>
> Yes, but one of the primary motivations for including the @P
> modifier was requests to be able to use
On Sat, 25 Mar 2017 15:33:47 -0400
Chet Ramey wrote:
> >
> > Is it normal for Bash positional parameters not to be
> > available from ~/.bashrc during initialization?
>
> Yes. Bash has always worked like this. The startup files are
> read before the positional parameters are assigned.
>
Fo
Hi,
I'd like to ask if there is crucial reason, beside the correct foreground
process group, not to allow the lastpipe shell option for an interactive
bash? Maybe something like in the attachment could be an option?
Werner
--
"Having a smoking section in a restaurant is like having
On Mon, Mar 27, 2017 at 8:32 AM, Torka Noda wrote:
> For any particular reason?
>
> Why are they not all made available anyway? with an alternative
> array for the arguments sent to the commands fed to Bash stdin
> with "-s", so we don't have to handle all possible arguments if
> we just want the
When the command to be fixed-up has a process substitution, `fc' prints
out not only the fixed-up command (as expected) but also any commands that
are part of a process substitution in the command:
$ FCEDIT=':' # doesn't really matter
$ : <(: A)
$ fc
: <(: A) # expected
: A
