On 8/4/2019 22:53, Robert Elz wrote:
> [Aside: when the destination is a builtin, another strategy is to
> simply write the here doc into mem, and have the builtin read directly
> from the mem buffer - no actual I/O of any kind involved at all.]
When in the past I proposed this syntax: cmd >>>va
Date:Mon, 8 Apr 2019 22:03:25 -0700
From:pepa65
Message-ID:
| What is nice about here docs/strings is that there are no subshells
| involved.
When they use files, that's correct, but when a pipe is used, unless
the data size is both known in advance, and limited
On 8/4/2019 21:19, Robert Elz wrote:
> In general here docs (and here strings) are overused - it is always
> possible to simply write a pipe instead
What is nice about here docs/strings is that there are no subshells
involved.
I think Linda's main drive is to seek improvement in how bash works. N
Date:Mon, 08 Apr 2019 17:04:41 -0700
From:L A Walsh
Message-ID: <5cabe199.9030...@tlinx.org>
| On 4/8/2019 7:10 AM, Chet Ramey wrote:
| > Pipes are objectively not the same as files. They
| >
| > 1. Do not have file semantics. For instance, they are not seeka
On 4/8/2019 7:10 AM, Chet Ramey wrote:
> On 4/7/19 4:21 PM, L A Walsh wrote:
>
>> On 3/22/2019 6:49 AM, Chet Ramey wrote:
>>
>>> Yes, that's how bash chooses to implement it. There are a few portable
>>> ways
>>> to turn a string into a file descriptor, and a temp file is one of them (a
On 4/8/19 12:57 PM, Eli Schwartz wrote:
> . The `globstar' code now skips over symbolic links to directories,
> preventing them from being scanned twice.
>
> What is the purpose of this change? In bash 4.4, if I wanted to print
> all the entries in a directory tree, whether it is a file,
On Mon, Apr 08, 2019 at 12:57:52PM -0400, Eli Schwartz wrote:
> #bash pointed out to me that **/* will do what I want on both bash 4 and
> bash 5, but I'm afraid I totally don't understand what the rules of
> globstar are supposed to be, or whether changes to the output are
> intended. The behavior
. The `globstar' code now skips over symbolic links to directories,
preventing them from being scanned twice.
What is the purpose of this change? In bash 4.4, if I wanted to print
all the entries in a directory tree, whether it is a file, directory, or
symbolic link, I could use shopt -s
On Mon, Apr 08, 2019 at 10:53:46AM -0400, Chet Ramey wrote:
> On 4/8/19 10:36 AM, Greg Wooledge wrote:
>
> > That's incorrect in this context. We're talking about boot scripts here,
> > not interactive user shells. In boot scripts, on every operating system
> > I've ever used, the shell being us
On 4/8/19 10:36 AM, Greg Wooledge wrote:
> That's incorrect in this context. We're talking about boot scripts here,
> not interactive user shells. In boot scripts, on every operating system
> I've ever used, the shell being used is either POSIX sh or Bourne sh.
This is clearly wrong in general,
On Sun, Apr 07, 2019 at 01:06:21PM -0700, L A Walsh wrote:
> On 3/20/2019 5:19 AM, Greg Wooledge wrote:
> > Just like that one time L. Walsh tried to write a bash boot script that
> > used <() to populate an array, and it failed because she was running
> > it too early in the boot sequence, and /de
On 4/7/19 4:21 PM, L A Walsh wrote:
> On 3/22/2019 6:49 AM, Chet Ramey wrote:
>> Yes, that's how bash chooses to implement it. There are a few portable
>> ways
>> to turn a string into a file descriptor, and a temp file is one of them (a
>> child process using a pipe is another, but pipes have othe
On 4/7/19 4:06 PM, L A Walsh wrote:
>> Just like that one time L. Walsh tried to write a bash boot script that
>> used <() to populate an array, and it failed because she was running
>> it too early in the boot sequence, and /dev/fd/ wasn't available yet
>>
>
> ---
> /dev/fd was available,
On Fri, Apr 05, 2019 at 03:57:16PM -0700, L A Walsh wrote:
> What would be wrong with doing something like:
>
> readarray -t last10< <(COMMAND |tail -10)
>
> That will put the last 10 lines of COMMAND_OUTPUT into
> the array 'last10'. Now you can launch another command
> to process that last
14 matches
Mail list logo
