On Sat, Apr 13, 2019 at 09:43:47AM +0200, Toralf Förster wrote:
> Except, that I used the opposite:
>
> min_days=${1:-5}
> min_hours=${2:-12}
> min_compl=${3:-3500}
> shift "$(( $# < 3 ? $# : 3 ))"
> setupargs="$@"
So... this user interface of yours. It looks someth
On Mon, Apr 15, 2019 at 08:42:53AM -0400, Greg Wooledge wrote:
> On Sat, Apr 13, 2019 at 09:43:47AM +0200, Toralf Förster wrote:
> > Except, that I used the opposite:
> >
> > min_days=${1:-5}
> > min_hours=${2:-12}
> > min_compl=${3:-3500}
> > shift "$(( $# < 3 ? $# : 3 ))"
> >
Date:Mon, 15 Apr 2019 09:19:19 -0400
From:Greg Wooledge
Message-ID: <20190415131919.gy6...@eeg.ccf.org>
| > > setupargs="$@"
| Also, you are squashing all of your filename arguments down into a
| single string variable,
This is simply an unspecified o
On Sat 2019-04-13 14:03:22 -0400, Chet Ramey wrote:
> It's an easy change. See the attachment.
Thanks! The attached patch removed a comment and changed an #if 1 to
#if 0, but i think the comment change is just a cleanup reflecting the
previous state of the codebase. Is that right?
> I agree tha
On 4/14/19 9:40 PM, Paul Wise wrote:
> On Sun, 2019-04-14 at 17:28 -0400, Chet Ramey wrote:
>
>> That's the number of positional parameters.
>
> Oops, I mean the command number variable \# that is available at PS1
> evaluation time but not when PROMPT_COMMAND is run. I was able to
> workaround th
On 4/15/19 2:40 PM, Daniel Kahn Gillmor wrote:
> On Sat 2019-04-13 14:03:22 -0400, Chet Ramey wrote:
>> It's an easy change. See the attachment.
>
> Thanks! The attached patch removed a comment and changed an #if 1 to
> #if 0, but i think the comment change is just a cleanup reflecting the
> prev
On Mon 2019-04-15 17:35:49 -0400, Chet Ramey wrote:
> I'll probably release a patch, yes. In the meantime, distributions are free
> to take the change and apply it to their versions.
Thanks for the followup! I've updated https://bugs.debian.org/920455
with the appropriate details.
--dkg
On Mon, 2019-04-15 at 17:31 -0400, Chet Ramey wrote:
> You can use $HISTCMD with a slight fix that's now in the devel branch.
That doesn't increment when you use HISTCONTROL=erasedups AFAICT but
the command number does increment. Also HISTCMD doesn't start at zero.
> The Korn shell uses values >
Date:Tue, 16 Apr 2019 10:29:36 +0800
From:Paul Wise
Message-ID: <5be7a3060ecb029ac36a4592bbee7fc071becd12.ca...@bonedaddy.net>
| I wonder if bash could set an additional variable to indicate if $? is
| from a normal exit, a signal exit, a shell keystroke etc,
Tha
On Tue, 2019-04-16 at 12:38 +0700, Robert Elz wrote:
> That's really hard to do and do correctly.
I was operating on the assumption that it could be done in the same way
that the $? and $PIPESTATUS variables are created/updated.
> There's no way to pass variables back from a subshell
I think I
10 matches
Mail list logo
