On 8/26/22 9:29 PM, Kerin Millar wrote:
Hi Chet,
On Fri, 26 Aug 2022 14:28:00 -0400
Chet Ramey wrote:
1. Changes to Bash
a. Added a compatibility mode feature that causes the parser to parse command
substitutions as if extglob were enabled. If it is enabled before execution,
parse at
On 8/27/22 2:38 PM, Matteo Paolini wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Description:
I recently discovered Readline's 'yank-pop' and 'vi-yank-pop' commands.
From what I understand, 'yank-pop' is supposed to cycle through Bash's
internal kill-ring
after yanking the m
Thanks for your reply.
>
> Thanks for the report. It looks like this behavior (which happens only at
> the beginning of a line) has been around since the original code was
> contributed in 2011.
>
That's strange, for me 'vi-yank-pop' issues an error regardless of the
cursor's position on the line.
On 8/28/22 5:06 PM, Saint Michael wrote:
He has a point, though. To have some of the functionality of jq inside Bash
may be very useful.
If he can supply a patch, why not?
Because then it becomes a support and maintenance issue, and a piece of
technical debt.
A well-encapsulated loadable built
On 8/28/22 8:47 PM, Dale R. Worley wrote:
The "obvious" way to support Json in Bash would be a utility that parses
Json and produces e.g. a Bash associative array, and conversely a
utility that reads a Bash associative array and produces Json. The real
limitation is that it's difficult to have a
On 8/28/22 5:50 PM, Yair Lenga wrote:
First, thanks for taking the time to read and provide your thoughts. This
is the real value of the discussion/
Second: I'm NOT trying to argue that there isn't valid use for
combining bash/curl/jq, Nor do I suggest adding JSON as first class object
to bash (
On 8/28/22 2:11 PM, Lawrence Velázquez wrote:
On Sun, Aug 28, 2022, at 9:24 AM, Yair Lenga wrote:
Wanted to get feedback about the following "extensions" to bash that will
make it easier to work with simple JSON object. To emphasize, the goal is
NOT to "compete" with Python/Javascript (and other
On 8/28/22 10:47 AM, Yair Lenga wrote:
Hi,
I've noticed Bash code uses "old-style" C89 declarations:
* Parameters are separated from the prototype
Changing to C99-style function declarations is something that's on the list
to do.
* Variables declared only at the beginning of the function
* N
On Mon, 29 Aug 2022 09:53:39 -0400
Chet Ramey wrote:
> On 8/26/22 9:29 PM, Kerin Millar wrote:
> > Hi Chet,
> >
> > On Fri, 26 Aug 2022 14:28:00 -0400
> > Chet Ramey wrote:
> >
> >> 1. Changes to Bash
> >>
> >> a. Added a compatibility mode feature that causes the parser to parse
> >> command
On 2022-08-29 11:43, Chet Ramey wrote:
On 8/28/22 2:11 PM, Lawrence Velázquez wrote:
On Sun, Aug 28, 2022, at 9:24 AM, Yair Lenga wrote:
Wanted to get feedback about the following "extensions" to bash that
will
make it easier to work with simple JSON object. (...)
just to make it easier to bu
On 8/28/22 1:17 PM, Yair Lenga wrote:
Yes, you are correct - (most/all of) of those examples "K&R".
However, given bash's important role in modern computing - isn't it time to
take advantage of new language features ? this can make code more readable,
efficient and reliable.
There's no actual
On 8/29/22 11:20 AM, Matteo Paolini wrote:
Thanks for your reply.
Thanks for the report. It looks like this behavior (which happens only at
the beginning of a line) has been around since the original code was
contributed in 2011.
That's strange, for me 'vi-yank-pop' issues an error regardles
12 matches
Mail list logo
