On Fri, Jun 1, 2018 at 6:18 PM, Chet Ramey wrote:
> The general rule is simple: bash reads input a line at a time, feeding
> each line to the parser, until it has enough input for a complete
> command. If it doesn't have enough to complete a command, it will read
> additional lines. If a newline w
On Sat, Jun 02, 2018 at 09:18:14PM -0700, Thomas Fischer wrote:
> Repeat-By:
> echo {a..z}{a..z}{a..z}{a..z}{a..z}{a..z}
26^6 = 308915776 words of 6 bytes each, plus however much overhead is
involved in constructing a list of 308915776 strings.
You've probably gone well over 2 GB of virtual memor
On Sun, Jun 03, 2018 at 02:32:03PM -0400, Chet Ramey wrote:
> On 6/2/18 10:08 PM, Jungsub Shin wrote:
> > # mount -o remount,append=~/test_aufs/ro1=ro+wh ~/test_aufs/mount
> >
> > mount failed with ~/test_aufs/ro1 path isn't exist message.
> > So i try to debug with strace and i find out bash don'
On 4.6. 06:48, Edward Huff wrote:
That is unexpected.
bash --version
GNU bash, version 4.4.19(1)-release (x86_64-redhat-linux-gnu)
I assume you'd like Bash to behave like ksh here, and to expand the
process expansion filename as a distinct word instead of concatenating
it with the surroundin
On Mon, Jun 4, 2018 at 11:48 AM, Edward Huff wrote:
> That is unexpected.
>
I agree it may look "unexpected" because "cat
That is unexpected.
bash --version
GNU bash, version 4.4.19(1)-release (x86_64-redhat-linux-gnu)
ñ
