Re: Scrolling instead of wrapping?

On Mon, Nov 23, 2015 at 5:13 AM, Greg Wooledge wrote: > On Fri, Nov 20, 2015 at 02:37:29PM -0800, Dan Stromberg wrote: > > I'm finding that when I have a long one-liner, bash 4.4 will scroll > > horizontally instead of wrapping to the next line. Some people may > prefer &

Scrolling instead of wrapping?

I've been using the bash 4.4 beta lately. I'm finding that when I have a long one-liner, bash 4.4 will scroll horizontally instead of wrapping to the next line. Some people may prefer this behavior, but I don't. I tried fiddling with horizontal-scroll-mode, but that didn't appear to help. I don

Re: $PS0 patch

On Thu, Oct 29, 2015 at 4:35 PM, Chet Ramey wrote: > On 10/24/15 10:00 PM, Dan Stromberg wrote: > > > > I've created a small diff against tonight's bash master branch for > > displaying a (single!) prompt after reading a command but before > executing > >

Re: $PS0 patch

I'd like to be able to log my commands' start and stop times (for good post mortem analysis), without overwhelming a disk or increasing my cut-and-paste spruce-up time. Thanks. On Sat, Oct 24, 2015 at 9:34 PM, Dan Stromberg wrote: > > I just noticed there's an fprintf b

Re: $PS0 patch

I just noticed there's an fprintf buglet in there. I've put a fixed version of at http://stromberg.dnsalias.org/~strombrg/diffs/ps0-diffs - rather than inflict another shar on the list :) Thanks again.

Re: $PS0 patch

On Sat, Oct 24, 2015 at 7:00 PM, Dan Stromberg wrote: > > > dstromberg@server:~/src/bash/src$ export PS0='fred> > > ' > I have no idea where that second > came from; please ignore it.

$PS0 patch

I've created a small diff against tonight's bash master branch for displaying a (single!) prompt after reading a command but before executing said command. It's kind of like trapping debug, but it doesn't output the prompt once for each subcommand in a pipeline - it's just once for the thing you t

trap DEBUG and $_

Is there a way of outputting a datestamp to shell stderr at the _beginning_ of the execution of a command, that won't wipe out $_? I use $_ quite a bit for the last argument to the previous command, interactively. And I'd like to datestamp all my commands. Datestamping after with $PS1 is easy, bu

Exit status of "if" statement?

What should be the behavior of the following? if cmd1 then cmd2 fi && if cmd3 then cmd4 fi I've not joined two if's with a short-circuit boolean before, but I'm suddenly working on a script where someone else has. Playing around, it appears that cmd1 and cmd3 have no direct impact on the

Differentiating false from fatal

Say you have a shell script, and you need it to be bulletproof. As you write it, you throw in error checking all over the place. But say you have a function that needs to return a boolean result in some way - call the function "bool_foo" for the sake of discussion. Further assume that bool_fo

Variable scoping

Having a shell function's variable changes reflected in its caller really kinda makes me shudder - in fact, it reminds me of gosub. It seems like a bug waiting to happen; I'm amazed I haven't been bitten by it yet. It occurred to me that this might help - but of course it's probably quite a b

Static analysis for POSIX shell or bash?

Is there such a thing as a free-and-legal static analysis tool for POSIX shell or bash? I found abash, but all I saw was a scholarly paper - not source code. I didn't read the entire paper though - not even close. I'm thinking of something along the lines of PyChecker for Python. I know abou

Re: capturing sub-expressions?

On Tue, 29 Jan 2008 18:27:05 -0800, Linda Walsh wrote: > Paul Jarc wrote: >> Linda Walsh <[EMAIL PROTECTED]> wrote: >>> p="-e -p 60 -x" >>> --- >>> That's why I wanted the capture -- to pick out the 60 -- where 60 >>> represents a positive integer. The space between the -p and the >>> number is o

set -o pipefail inherited?

Is there a way of getting "set -o pipefail" to be inherited from a shell to its subshell? Or does each subshell have to set it again?

Re: Any plans to integrate an XML parser

On Tue, 02 Oct 2007 16:31:21 -0400, Nicholas Sushkin wrote: > Hi Chet, others, > > In our bash scripts, we often access XML files. Are there any plans to > integrate an XML parser in bash? For example, merge into the main tree the > following bash patch? > > http://home.eol.ca/~parkw/index.html#

Re: bash 3.0 on AIX 5.1 compiled 64 bit segfaults

On Mon, 2005-02-28 at 09:20 -0500, Chet Ramey wrote: > > I compiled bash 3.0 with gcc -maix64, and it would segfault when setting > > the TERM variable sometimes. > > > > I recompiled it without -maix64, and it ran fine. > > A stack traceback would be helpful. I don't have any AIX machines. > >

bash 3.0 on AIX 5.1 compiled 64 bit segfaults

I compiled bash 3.0 with gcc -maix64, and it would segfault when setting the TERM variable sometimes. I recompiled it without -maix64, and it ran fine. Thanks! ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bas