On 7/13/19 5:55 AM, Mike Jonkmans wrote:
> This runs for two seconds:
> bash --norc --noprofile -ic "trap 'tput hs' DEBUG; sleep 2 & :|:|:"
>
> While this immediately finishes:
> bash --norc --noprofile -ic "trap ':' DEBUG; sleep 2 & :|:|:"
I believe this has to do with running a pro
On 7/12/19 3:06 PM, Luca Landi wrote:
> Bash Version: 5.0
> Patch Level: 7
> Release Status: release
>
> Description:
>
> It appears that, since ca. v4.4, job-control from within an interactive
> subshell
> is still allowed but does not work fully because the shell won't hand over
> foreground-
On 7/12/19 4:40 PM, Tianon Gravi wrote:
> What I've found is that if PS1 contains '\n' and the last line gets
> long enough for the cursor to be on the next line (for example, if \w
> gets too long), then typing will result in a single character being
> printed in the correct place followed by the
On 7/13/19 1:31 PM, Travis Everett wrote:
> Bash Version: 5.0
> Patch Level: 7
> Release Status: release
>
> *Description:*
> I've noticed that a timezone explicitly set in the TZ environment variable
> can get cached (if any date-using command/builtin is run) and then show up
> (at least) in dat
On 7/12/19 5:19 PM, Andreas Schwab wrote:
> On Jul 12 2019, Chet Ramey wrote:
>
>> I assume this means that bc doesn't use strtod.
>
> Of course not, strtod doesn't parse arbitrary precision numbers.
Yes, exactly.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
