2022年1月24日(月) 11:40 Ángel :
> Your English reads fine here :-)
Thank you! Yeah, I think it can be "fine" for the communications, but
I'm not sure if it qualifies for the explanation in the English
manual. At least, I recognize that, when it comes to explaining
complicated things, my English tends
On 2022-01-21 at 01:43 +0900, Koichi Murase wrote:
> Thank you. I'll later work on it though I actually don't have
> confidence in my English ability. Anyway, I believe other people can
> correct my broken English.
> --
> Koichi
Your English reads fine here :-)
On 1/20/22 11:43 AM, Koichi Murase wrote:
2022年1月21日(金) 1:33 Chet Ramey :
Contributions are always welcome.
Thank you. I'll later work on it though I actually don't have
confidence in my English ability. Anyway, I believe other people can
correct my broken English.
I'm a fine editor.
--
On 1/19/22 8:46 PM, Koichi Murase wrote:
Sorry, I hadn't checked the bashref.html of the devel branch. Now I
have read the description. I think this is sufficiently clear, and in
particular, these examples are very useful to understand the actual
behavior. I like it. I couldn't find similar
2022年1月21日(金) 1:33 Chet Ramey :
> Contributions are always welcome.
Thank you. I'll later work on it though I actually don't have
confidence in my English ability. Anyway, I believe other people can
correct my broken English.
--
Koichi
i still vote for back referenceable groups
yes im no .c coder wush bye idea
On Thu, Jan 20, 2022, 02:48 Koichi Murase wrote:
> 2022年1月20日(木) 9:39 Chet Ramey :
> > It will be in bash-5.2-beta.
>
> Thank you for the clarification.
>
> > There is fairly extensive documentation in the current
2022年1月20日(木) 9:39 Chet Ramey :
> It will be in bash-5.2-beta.
Thank you for the clarification.
> There is fairly extensive documentation in the current version of the
> texinfo manual. Take a look; tell me what you think.
Sorry, I hadn't checked the bashref.html of the devel branch. Now I
have
On 1/18/22 8:50 PM, Koichi Murase wrote:
Thank you for your consideration and for implementing it. I have
tried the latest devel branch and played with it. I now really like
its behavior. Thank you very much for taking it into consideration.
It's this kind of back and forth I find valuable.
Thank you for your consideration and for implementing it. I have
tried the latest devel branch and played with it. I now really like
its behavior. Thank you very much for taking it into consideration.
> I generally make new functionality that's controlled by a separate option
> off by default
> --- a/CHANGES
> +++ b/CHANGES
> @@ -1,3 +1,326 @@
> +This document details the changes between this version, bash-5.2-alpha, and
> +the previous version, bash-5.1-release.
>
> [...]
>
> +x. New shell option: patsub_replacement. When enabled, a `&' in the
> replacement
> + string of the
Thank you for the reply and sorry for my late reply. I am busy recently.
> > --
> > Suggestion / Discussion
> >
> > I suggest that '&' has the meaning of the matched part only when it is
> > not quoted in the parameter-expansion
On 10/5/21 4:41 AM, Koichi Murase wrote:
> I have questions on the new feature ${var/pat/&} in the devel branch.
>
>> commit f188aa6a013e89d421e39354086eed513652b492 (upstream/devel)
>> Author: Chet Ramey
>> Date: Mon Oct 4 15:30:21 2021 -0400
>>
>> enable support for using `&' in the
12 matches
Mail list logo
