On 28/01/2021 03.29, Léa Gris wrote:
> Now if you want to preserve all the newlines you can use an ASCII EOF
> character (formerly Ctrl + Z) that is unlikely to be part of a legit
> string:
>
> a=$(printf $'hello\n\n\n\32'); a=${a%$'\32'}; declare -p a
When doing this there is no subshell involve
On 1/27/21 4:07 PM, Alex fxmbsw7 Ratchev wrote:
thank you big time sir
can you handle me the git cmd to get the sources with the fixes ? :))
Just fetch the devel branch.
git clone --branch devel git://git.savannah.gnu.org/bash.git
will probably work.
You have to uncomment the fix. Search for
thank you big time sir
can you handle me the git cmd to get the sources with the fixes ? :))
/good night and thank you big time for your kind friendlyness
On Wed, Jan 27, 2021, 22:01 Chet Ramey wrote:
> On 1/27/21 3:37 PM, Alex fxmbsw7 Ratchev wrote:
> > hm had it wrong memorized, maybe i was w
On 1/27/21 3:37 PM, Alex fxmbsw7 Ratchev wrote:
hm had it wrong memorized, maybe i was working with a space instead of x there
i sadly left all computer stuff since you didnt fix the three four major
bugs i posted, since those stopped my coding wantings to 100% :(
however i have a repost of em
hm had it wrong memorized, maybe i was working with a space instead of x
there
i sadly left all computer stuff since you didnt fix the three four major
bugs i posted, since those stopped my coding wantings to 100% :(
however i have a repost of em ( no code isolationed cases since i only know
the b
On 1/27/21 3:29 PM, Léa Gris wrote:
Now if you want to preserve all the newlines you can use an ASCII EOF
character (formerly Ctrl + Z) that is unlikely to be part of a legit string:
a=$(printf $'hello\n\n\n\32'); a=${a%$'\32'}; declare -p a
It doesn't matter what you use (besides a newline,
Le 27/01/2021 à 21:21, Alex fxmbsw7 Ratchev écrivait :
as well as one newline instead of x, it cuts afik _one_ ending nrwline, not
all
It removes every trailing newline
a=$(printf $'hello\n\n\n'); declare -p a
Now if you want to preserve all the newlines you can use an ASCII EOF
character (f
On 1/27/21 3:21 PM, Alex fxmbsw7 Ratchev wrote:
as well as one newline instead of x, it cuts afik _one_ ending nrwline, not all
No, command substitution removes all trailing newlines.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - H
On Wed, Jan 27, 2021 at 09:21:09PM +0100, Alex fxmbsw7 Ratchev wrote:
> as well as one newline instead of x, it cuts afik _one_ ending nrwline, not
> all
If you mean command substitution, this is incorrect. Command substitution
removes all trailing newlines.
as well as one newline instead of x, it cuts afik _one_ ending nrwline, not
all
On Wed, Jan 27, 2021, 21:01 Chet Ramey wrote:
> On 1/27/21 12:08 AM, Oğuz wrote:
> > What's wrong with printing an `x' at the end and removing it later?
>
> Nothing.
>
> --
> ``The lyf so short, the craft so long to
On 1/27/21 12:08 AM, Oğuz wrote:
What's wrong with printing an `x' at the end and removing it later?
Nothing.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.
On 1/27/21 4:07 AM, pepa65 wrote:
On 27/01/2021 14.49, k...@plushkava.net wrote:
That's why your .? glob doesn't match the .. pathname. Normally,
GLOBIGNORE isn't set.
After unsetting GLOBIGNORE:
That doesn't unset GLOBIGNORE.
$ declare -p GLOBIGNORE
declare -x GLOBIGNORE=""
Depending o
On 27/01/2021 16.07, Clark Wang wrote:
> $(|cmd ...) makes more sense for me. '|' is a pipe which means passthrough.
>
> For future extensions, use
>
> $(&flag1[=value1]&flag2[=value2] cmd ...)
>
> For example,
>
> $(&keep_trailing_newlines cmd ...) is just the same as $(|cmd ...).
> $(&n
On 27/01/2021 14.49, k...@plushkava.net wrote:
> That's why your .? glob doesn't match the .. pathname. Normally,
> GLOBIGNORE isn't set.
After unsetting GLOBIGNORE:
$ declare -p GLOBIGNORE
declare -x GLOBIGNORE=""
$ shopt -u extglob
$ echo @(?|.?)
-bash: syntax error near unexpected token `('
$
On Wed, Jan 27, 2021 at 4:40 PM Clark Wang wrote:
> On Wed, Jan 27, 2021 at 12:14 PM Clark Wang wrote:
>
>> For example, we can use ${( ... )} which is now wrong syntax.
>>
>> $ v=${( command ... )}
>> bash: ${( command ... )}: bad substitution
>>
>
> Or keep it similar to $(cmd), like:
>
> $(
On Wed, Jan 27, 2021 at 12:14 PM Clark Wang wrote:
> For example, we can use ${( ... )} which is now wrong syntax.
>
> $ v=${( command ... )}
> bash: ${( command ... )}: bad substitution
>
Or keep it similar to $(cmd), like:
$(& cmd ...)
$(; cmd ...)
$(| cmd ...)
16 matches
Mail list logo
