Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Description:
http://pastebin.com/f476b80da
configured via: http://pastebin.com/m62b92718
Adding --enable-minimal doesn't fix the issue which means these versions
b
Yeah honestly splitting most of the `configure` checks into multiple
threads is definitely possible.
Caching between projects is even a straightforward extension with systems
like `Nix`.
The "gotcha" here in both cases is that existing scripts that are living in
source tarballs are not feasible t
You can try to use the `requires` toposort routine to identify "Strongly
Connected Sub-Components", which is where I imagine you'll get the
best results. What you'll need to watch out for is undeclared ordering
requirements that parallelism would break.
The `m4sh` and `m4sugar` source code is docu
I've been telling folks about the config site file every time this thread
comes up. Good on you for actually trying it haha.
It can make a huge difference. You can short circuit a lot of checks this
way.
Now, the disclaimer: you still shouldn't share a cache file between
projects, and if you use
he first time I used it instead of $#, I wasn't sure if it would
work.
I think $# wins for me.
Thanks!
Alex
The man and info pages have retained the rather terse descriptions of
those oldest expansions, and they are buried in the sheer volume of the
current documentation.
On
ting are not performed.
The result is supplied as a single string,
with a newline appended,
to the command on its
--
Alex.
Chet Ramey writes:
> On 3/11/23 3:39 AM, Alex Bochannek wrote:
>> Bash Version: 5.2
>> Patch Level: 15
>> Release Status: release
>> Description:
>> The documentation for here strings says:
>> "The WORD undergoes tilde expansion, parameter and va
e as the shell does.
>> This performs alias and history expansion as well as all of the shell
>> word expansions (*note Shell Expansions::)." Maybe that can be tightened
>> up a bit as well to clarify what it does not do?
>
> Sure, it can list the word expansions it performs.
That would be helpful. The shell-expand-line command is really useful
and I don't think a lot of users understand what its limitations are.
Thank you!
--
Alex.
f
only one human is using the same account), but as the
history file grows very large this can cause a visible lag.
Alternately I could write a special-purpose command
which jumps directly to the end of the file, but it would
be really nice if bash just did this for you.
Thanks,
--
Alex
On Sun, Dec 18, 2011 at 3:26 AM, Chet Ramey wrote:
> On 12/11/11 1:13 AM, Alex Shinn wrote:
>
>> I had initially been confused by the HISTTIMEFORMAT
>> variable thinking it could be used to change what was
>> written to the history file, rather than the output o
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-redhat-linux-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR
Should the globstar (**) syntax allow for partial parameter matching
(i.e. **.c to find all *.c files in the current directory and its sub-
directories)?
Currently this can be implemented like this:
for i in **; do if [[ ${i} =~ \.c$ ]]; then ; fi; done
It would be pleasantly convenient if this w
Thanks Chet, and everyone who has contributed.
On that
I get failure to link.
If I figure out what's wrong in that specific case I'll let you know
=) For now it builds just fine on F10 (32-bit and 64-bit) as well as
Gentoo Linux (32-bit and 64-bit) which is sufficient.
Cheers for the response. Much appreciated.
Alex
Can someone please explain how 'mapfile' should be used? I am trying:
cat file.txt | mapfile
for i in ${MAPFILE};do echo $i; done
and I see no output. I've tried adding the -t option to strip
trailing newlines. If I use the following command:
mapfile -u file.txt
I get the error:
bash: mapfi
On Feb 4, 2:59 pm, Stephane CHAZELAS
wrote:
> 2009-02-4, 10:50(-08), Alex Reed:
>
> > Can someone please explain how 'mapfile' should be used? I am trying:
>
> > cat file.txt | mapfile
> > for i in ${MAPFILE};do echo $i; done
>
> > and I see no
file parse.y
Hunk #1 succeeded at 2932 with fuzz 2.
Hunk #2 succeeded at 3276 with fuzz 1.
Hunk #5 FAILED at 3442.
1 out of 4 hunks FAILED -- saving rejects to file parse.y.rej
patching file patchlevel.h
...
...
...
At least one "hunk" fails on every patch file. What am I doing wrong?
Thanks,
-Alex
On Jul 22, 4:09 pm, Bob Proulx wrote:
> Alex Reed wrote:
> > At least one "hunk" fails on every patch file. What am I doing wrong?
>
> Hmm... Works for me. Here is a trace of the important bits.
>
> $ wgetftp://ftp.gnu.org/pub/gnu/bash/bash-4.0.tar.gz
> $
behaviour, i.e. wait
until all children of current bash process will exit?
P.S. I've not seen this information in 'help wait' or 'man bash' - is this
current 'correct' behaviour is documented?
--
WBR, Alex.
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -I. -I
I couldn't get bashbug to send this, so I manually am emailing it.
"/usr/bin/bashbug: rmail: not found"
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux
script.
I will be adhering to the ICS-CERT Vulnerability Disclosure Policy and look
forward to further discussing and resolving this bug
Regards,
Alex
oting that the Kali example should have been able to have
allocated more than enough memory to hold the 2GB file since it was able to
allocate up to 4296613888 bytes of heap memory when it crashed.
On Tue, Nov 7, 2017 at 2:21 PM, Eduardo Bustamante
wrote:
> On Tue, Nov 7, 2017 at 5:58 AM, Alex
.53(1)-release : pass
4.3.0(1)-release : pass
4.3.30(1)-release : pass
4.3.48(1)-release : pass
4.4.0(1)-release : fail
4.4.12(1)-release : fail
4.4.18(1)-release : fail
5.0.0(1)-release : fail
5.0.9(1)-release : fail
- Alex Kerzner
Repeat-By:
~~~
# Long way, but potentially easier to implem
I hope this is the right place to fix it. Thanks for bash. :)
Cheers
Alex
>From 1ff12f30e83762bea2ca0c1b09c240ab2d1086ca Mon Sep 17 00:00:00 2001
From: Alex Schroeder
Date: Fri, 24 Apr 2020 19:51:25 +0200
Subject: [PATCH] Bash-5.0 patch 18: fix typo in the man page
---
doc/bash.1 | 2 +-
On Thursday, September 4, 2014 5:22:58 AM UTC-6, Dylan Cali wrote:
> Hi Chet,
>
> Just curious if it will be possible to merge this enhancement?
>
> Thanks,
> Dylan
This is what it looks like right now. It's still really helpful as is, but it
doesn't really fit in with the theme I was going for
On Thursday, September 4, 2014 7:00:16 AM UTC-6, Chet Ramey wrote:
> On 9/4/14, 7:22 AM, Dylan Cali wrote:
> > Hi Chet,
> >
> > Just curious if it will be possible to merge this enhancement?
>
> I haven't looked at it yet.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>
thanks && cc list
On Mon, Feb 15, 2021, 15:04 Chet Ramey wrote:
> On 2/15/21 8:57 AM, Alex fxmbsw7 Ratchev wrote:
> > i had yet a couple of trace msges, this one s new
> > any big meaning ?
>
> Nope, it's informational for me. You see it because you're ru
what, sorry, mailing stuff isnt much clear to me, ... its not possible to
have a var=\'\] ; assoc[$var] ?
On Mon, Feb 22, 2021 at 5:48 PM Chet Ramey wrote:
> On 2/15/21 1:28 PM, Daniel Gröber wrote:
>
> > On Mon, Feb 15, 2021 at 09:11:48AM -0500, Chet Ramey wrote:
> >> `test' is always going to
yeah i thought so.. thanks
On Tue, Feb 23, 2021 at 12:52 PM Léa Gris wrote:
> Le 23/02/2021 à 12:17, Alex fxmbsw7 Ratchev écrivait :
> > what, sorry, mailing stuff isnt much clear to me, ... its not possible to
> > have a var=\'\] ; assoc[$var] ?
>
> You can if assoc
i cannot exclude it'd be my bug ( again ) but i dunno i have no choise than
trying to present the hanger to you folks to fix it
if you'd unpack ogt1.tgz ull find ogt1/ and some dirs and scripts, the code
from the other paste didnt change, i just try to explain it so you dont
have a that hard time t
..based on it, c pros, you can prolly see clearly whats wrong
it like mmaps more and more memory beeing slower every run
) = 3
write(2, "++ [[ -v addkw[++addkw_i] ]]\n", 29++ [[ -v addkw[++addkw_i] ]]
) = 29
write(2, "++ dat[$nspace${SUBSEP}kw$SUBSEP"..., 53++
dat[$nspace${SUB
sorry for changing topics, i try .. its still the same topic code
the code (error, bug) is included in 'kws' which is supposed to eval set
keywords
i do
kws=( something ) kws
it hangs
i do
kws=( something ) ; kws
it hangs
i do only kws ( when the var is set already from last time ) it processes
n
so i fixed the code to have a newline before using the kws alias
it, to my half surprise, works perfectly, it displays the metest keyword
right, but on the second [[ -v arr[elem] ]] check it hangs, probably brk
ing few then mmaping and unmapping much, == bug ? :)
bash-5.1# bash ogt_demo
+ bash
by second [[ -v arr[elem] ]] n after hangs i mean i have two parts in this
one is the kws index array with keywords to parse, the other is kws the
alias that parses the ${kws[@]} arr
so for the first element there in the last mail it worked
and displayed the content of the alias, as the code
but on
the last analyzement of the weirdness is
arr=( .. )
_alias_
then it at least runs thru one arr[0], which is set, and evals the code
right and working, however on the next [[ -v arr[1] ]] ( empty ) check it
hangs
if i dont write the newline after arr=( .. ) for like usual, i get hung on
already a
but they get unset right, just doesnt display em
i have stuff with $'\34' separator and in set -x output the text is just
flat for the unset
+ unset 'dat[kwmetest]' 'dat[1kw1]' 'dat[1take]' 'dat[1code]'
code includes
minuskws_p1=$nspace$SUBSEP$minuskws_id$SUBSEP \
minuskws_p2=$nspace${SUBSEP}kw
say i have assoc[ ] i want to ${!assoc[begin*]}
i still dont understand, ( you speak more special english than code ), why
unset wont display the special chars, but then i suppose its not much of a
bug .. ?
On Mon, Mar 1, 2021 at 1:19 AM Chet Ramey wrote:
> On 2/28/21 6:19 PM, k...@plushkava.net wrote:
>
> >> The check for shell special chara
it just displays the wrong data completly, the special chars cutted off, ..
..
On Mon, Mar 1, 2021 at 10:28 AM Alex fxmbsw7 Ratchev
wrote:
> i still dont understand, ( you speak more special english than code ), why
> unset wont display the special chars, but then i suppose its not muc
oh i see, thank you big time for pointing it out so good
:))
On Mon, Mar 1, 2021 at 11:22 AM felix wrote:
> On Sun, Feb 28, 2021 at 10:32:13PM +, k...@plushkava.net wrote:
> > Why not indeed. However, I think that I'm able to decipher this.
> >
> > $ declare -A map; key=$'foo\34bar'; map[$ke
as a side info, only interpretation of vars in builtins may be affected, eg
solution as written : single quote the '$ley', on the other side
${var[$faulty_key]} doesnt eval it, only args usage as for declare unset
and [[ -v
.. maybe ..
On Mon, Mar 1, 2021 at 3:40 PM Greg Wooledge wrote:
> felix
i usually interate thru indexed arrays as, i=-1, while [[ -v arr[++i] ]],
but it suddenly stopped
maybe cause i switched to in-functions than aliases use
bash-5.1# cat int.fail
int() {
declare -a int
declare i=-1 now
while [[ -v int[++i] ]] && now=${int[i]} ; do
printf %s\\n "$now"
done
}
this is what i tried to achieve, but right it still fails:
# foo=( 0 1 2 ) i=-1 ; while [[ -v foo[++i] ]] ; do : ; done ; printf
$i
ogt: 3
just in functions not .. .. ?
i thought i tested, to 'shadow' the array to local to make it expandable in
the function
but it seems its empty
so declare -a arr=( "${arr[@]}" )
as is otherwise empty
any better idea ?
and as last note to end this thread:
var=foo func
leaves 'declare var ;' inside func be still 'foo'
while
var=foo ; func
does make it empty
peace, thanks, swfun
yea well i posted in a later post, locally declared vars are empty excepts
they are given on the function calling line, just like local vars, hm
the different names is not so a good idea but ill think
thank you much anyway :))
On Mon, Mar 8, 2021 at 2:25 AM Greg Wooledge wrote:
> Alex fxmb
oh i see, a bit of my fault, me noob with web mail and mailing lists
im sorry
i hope for better up soon
On Mon, Mar 8, 2021 at 2:33 AM Eli Schwartz wrote:
> On 3/7/21 8:24 PM, Alex fxmbsw7 Ratchev wrote:
> > and as last note to end this thread:
> There is no thread.
>
> There
[msg(shbot)] # foo() { declare -a foo=( "$@" ) ; declare i=-1 ; declare -p
foo ; declare -n next=foo[++i]
now=foo[i] ; while [[ -v next ]] ; do : $now ; done ; printf -- $i ; } ;
foo '' 1 2 3
[shbot(~shbot@37.139.2.101)] declare -a foo=([0]="" [1]="1" [2]="2" [3]="3")
[shbot(~shbot@37.139.2.101)] -
e ..
i hope you didnt loose me too much yet
'how would i declare -n right the 3 (or 4) right ?'
On Mon, Mar 8, 2021 at 4:30 PM Chet Ramey wrote:
> On 3/7/21 9:36 PM, Alex fxmbsw7 Ratchev wrote:
> > [msg(shbot)] # foo() { declare -a foo=( "$@" ) ; declare i=-
ckdraw, to always recheck the
#arr[@]
also if faulty code adds a non idx++ key that fails, of course thats not my
case but it comes to mind
on my todo list: more help-bash and benchmarks
thank you
On Tue, Mar 9, 2021 at 6:13 PM Chet Ramey wrote:
> On 3/8/21 11:19 AM, Alex fxmbsw7 Ratchev wrote:
maybe implent a shopt -s no_expand_subshells
On Thu, Mar 11, 2021 at 9:20 PM Chet Ramey wrote:
> On 3/11/21 10:06 AM, Jason A. Donenfeld wrote:
> > This behavior is quite surprising:
>
> The idea is that array subscripts undergo a uniform set of expansions when
> they're used, no matter the cont
i have no example to write here as this was past long
the story was, i was coding a file server daemon, with socat, and i figured
to use exec why not more exact more efficient
but using it resulted sometimes output of code of the script in the output
of the files
removing exec made it work normal
thank you sir
theres a misunderstanding tho
with exec i meant i exec socat instead of without exec
i may be able to reproduce it soon as i need to extend my softwares
peace
On Sun, Mar 14, 2021 at 3:37 PM Dale R. Worley wrote:
> > 2021年3月13日(土) 8:06 Alex fxmbsw7 Ratchev :
> >&g
normally, otherwise code appeared
..
dont mind as i cant recall or retry [new script somewhen soon]
On Mon, Mar 15, 2021 at 10:51 AM felix wrote:
> On Sat, Mar 13, 2021 at 01:05:32AM +0100, Alex fxmbsw7 Ratchev wrote:
> > i have no example to write here as this was past long
> Without sampl
hello, excuse my bad english
your sample code that you write what it should produce you propose for the
future so ?
it doesnt make me much sense that unset -v assoc[$key] gives syntax error
or so..
also about the assoc_expand_once i dont understand
cant it be as written, expand_once ( maybe _at_b
.. ?
# root ~/ogt2/confs ( 0 @ 2 ) boost ( 42098 @ 1615890149.004363 ==
2021-03-16+11:22:2920 ) #
PWD=/bla
# root /bla ( 0 @ 2 ) boost ( 42148 @ 1615890199.128728 ==
2021-03-16+11:23:1920 ) #
no idea about your internal rules of keyword and builtin but clearly its
gotta parse it at most 1. level otherwise its big security fault isnt it
its a shell fuctionality keyword, unset, so ..
On Tue, Mar 16, 2021 at 1:21 PM Greg Wooledge wrote:
> On Tue, Mar 16, 2021 at 09:24:01AM +0100, A
but is it a bug
its a bug to use heavy subshells for such
i understand the addment of this case tho
On Tue, Mar 16, 2021 at 1:23 PM Chris Elvidge wrote:
> On 16/03/2021 10:23 am, Alex fxmbsw7 Ratchev wrote:
> > .. ?
> >
> > # root ~/ogt2/confs ( 0 @ 2 ) boost ( 4209
i guess shell-keyword all then :))
On Tue, Mar 16, 2021 at 1:37 PM Greg Wooledge wrote:
> On Tue, Mar 16, 2021 at 01:26:30PM +0100, Alex fxmbsw7 Ratchev wrote:
> > no idea about your internal rules of keyword and builtin
>
> unicorn:~$ type [
> [ is a shell builtin
> unico
16, 2021 at 1:39 PM Alex fxmbsw7 Ratchev
wrote:
> i guess shell-keyword all then :))
>
> On Tue, Mar 16, 2021 at 1:37 PM Greg Wooledge wrote:
>
>> On Tue, Mar 16, 2021 at 01:26:30PM +0100, Alex fxmbsw7 Ratchev wrote:
>> > no idea about your internal rules of keywor
okay, cool, thank you for valuable infos =))
On Tue, Mar 16, 2021 at 2:31 PM Chet Ramey wrote:
> On 3/16/21 6:23 AM, Alex fxmbsw7 Ratchev wrote:
> > .. ?
> >
> > # root ~/ogt2/confs ( 0 @ 2 ) boost ( 42098 @ 1615890149.004363 ==
> > 2021-03-16+11:22:2920 ) #
> >
, Mar 17, 2021 at 4:46 AM Robert Elz wrote:
> Date:Tue, 16 Mar 2021 13:26:30 +0100
> From:Alex fxmbsw7 Ratchev
> Message-ID: p09ca...@mail.gmail.com>
>
> | no idea about your internal rules of keyword and builtin but clearly
> its
> | gotta par
i code on a bash feature linker 'ogt2' that binds functions, aliases, etc,
by filenames and their content ( and location ( prepath \\ subpath ) )
now i have /root/ogt2/traps/ and being in /root/ogt2
i type traps i expected traps/ it autocompleted none more it shows
'traps' as only option to complet
it makes the output no more possible if interpreted by tty
the \e's get processed by terminal and no more .. just an example where it
is so:
var=$'1\e[G\e[K2' ; declare -p var
if G was H for other line then it completly messes the terminal up
isnt it better to escape by \e ? ..
and what about the traps to not-with-slash one ?
bash: type: traps: not found
On Wed, Mar 17, 2021 at 4:39 PM Chet Ramey wrote:
> On 3/17/21 6:43 AM, Alex fxmbsw7 Ratchev wrote:
> > i code on a bash feature linker 'ogt2' that binds functions, aliases,
> etc,
> > by
when it works for you its no bug
for me, ill try later that completition removation stuff
but as upstream works it works, .. :)
On Wed, Mar 17, 2021 at 7:06 PM Chet Ramey wrote:
> On 3/17/21 12:45 PM, Alex fxmbsw7 Ratchev wrote:
> > and what about the traps to not-with-slash one ?
hm at least now we know array declare -p formatting would work in
workarounds, good to .. :)
On Wed, Mar 17, 2021 at 9:05 PM Greg Wooledge wrote:
> On Wed, Mar 17, 2021 at 09:58:24PM +0200, Ilkka Virta wrote:
> > On Wed, Mar 17, 2021 at 8:26 PM Greg Wooledge wrote:
> >
> > > I thought, for a mo
there is way to crop data to wanted, by cropping the exclulsions away
but what about a way to extract data, eg @( .. ) match
not about using [[ =~ but only var internal stuff
.. or do i miss there something
as i got suggested here for help-bash for new ..
there is ways to crop data to wanted by cropping the excludes out
but where is the simple way of keeping matching
i'd say implent backtrack references for @( .. ) etc groups
pseudo exmaple
declare -A big=( mess of data )
var=$( declare -p big )
t;]="" [$'\' [1]=\034']="" ["];eval echo shitt"]=""
[$'foo\034 [2]="blah" ']="" [abc]="" ["abc [22]=\"bar\""]="" [blah]="" )
peace
On Thu, Mar 18, 2021 at 2:33 PM G
wheres the sense of not having same var format rules as.. normal, but not
for unset ?
i can do arr[$key]= without problems, cool, why bug around big in unset
( aka choose keywords instead of lower for, ... important functionality )
On Wed, Mar 17, 2021 at 5:05 PM Jesse Hathaway
wrote:
> I wou
n Thu, Mar 18, 2021 at 3:39 PM Greg Wooledge wrote:
> On Thu, Mar 18, 2021 at 02:44:06PM +0100, Alex fxmbsw7 Ratchev wrote:
> > isnt it obvious ..
>
> No.
>
> > ${var//@(abc|cde)@(bla|blubb)/\2\1} # just like sed
> > and an extension for regex there
>
> That's
as for goal, and no believance, it is handling quoting, string issues,
nothing else
you may know if you think about it im a freelance code there is nothing now
but major functionality issues
..
On Thu, Mar 18, 2021 at 3:57 PM Alex fxmbsw7 Ratchev
wrote:
> what, dude, of course you can re
PM Alex fxmbsw7 Ratchev
wrote:
> as for goal, and no believance, it is handling quoting, string issues,
> nothing else
> you may know if you think about it im a freelance code there is nothing
> now but major functionality issues
> ..
>
> On Thu, Mar 18, 2021 at 3:57 PM
v cont[++i] ]] && src=${cont[i]} ; do
declare -n _src=$src
for key in "${!)src[@]}" ; do
res+=\ ${key@Q}
done
done
declare -ga "${dest:-arr}=\($res\)"
On Thu, Mar 18, 2021 at 4:03 PM Alex fxmbsw7 Ratchev
wrote:
> i also wanna say
> no extraction method is no g
well i have nothing against, excepts my .c is weak
ill get the k&r book then we can talk about it
On Thu, Mar 18, 2021 at 4:27 PM Chet Ramey wrote:
> On 3/18/21 11:03 AM, Alex fxmbsw7 Ratchev wrote:
> > i also wanna say
> > no extraction method is no good for a coding langu
i just report, sorry for overheat
its a fresh system i probably dont have readline-dev or such maybe its
cause that
g the -dev installed
how can i help fixing or analyzing this ?
On Thu, Mar 18, 2021 at 8:24 PM Chet Ramey wrote:
> On 3/18/21 12:08 PM, Alex fxmbsw7 Ratchev wrote:
> > i just report, sorry for overheat
>
> I can't reproduce this.
>
> --
> ``The lyf so short,
do you error out on configure for this case or not
cause mine was running fine
On Thu, Mar 18, 2021 at 8:25 PM Chet Ramey wrote:
> On 3/18/21 12:10 PM, Alex fxmbsw7 Ratchev wrote:
> > its a fresh system i probably dont have readline-dev or such maybe its
> > cause that
>
&
it may also be config path error cause i didnt PREFIX or so cause i dont
want to but cp'd to /bin , but then still it installed and found paths
i dunno, but i wish to analyze the problem, just help me on it, .. show me
some cmds or what i should try, ..
On Thu, Mar 18, 2021 at 8:29 PM
yea well it does wonders, however was looking for a way without spawning
externals like gawk.. maybe in future there will be =)
On Fri, Mar 19, 2021 at 2:02 AM Dale R. Worley wrote:
> Alex fxmbsw7 Ratchev writes:
> > there is way to crop data to wanted, by cropping the exclulsions awa
eval $'alias n=bla\nn() { type $FUNCNAME ; }\nn'
bla is a function
bla ()
{
type $FUNCNAME
}
it was supposed to be n() ..
ehe :))
you tell me rather a good pike beginnings resource
On Fri, Mar 19, 2021 at 9:42 AM Andreas Schwab
wrote:
> On Mär 19 2021, Alex fxmbsw7 Ratchev wrote:
>
> > yea well it does wonders, however was looking for a way without spawning
> > externals like gawk.. maybe in fu
oh i know, it works as expected by alias definition, there is no space
between alias defined and op, so it gets expanded correspondingly
thank you
On Fri, Mar 19, 2021, 10:14 Mike Jonkmans wrote:
> On Fri, Mar 19, 2021 at 09:12:34AM +0100, Alex fxmbsw7 Ratchev wrote:
> > eval $'
yes, thank you
On Fri, Mar 19, 2021, 14:11 Chet Ramey wrote:
> On 3/19/21 4:12 AM, Alex fxmbsw7 Ratchev wrote:
> > eval $'alias n=bla\nn() { type $FUNCNAME ; }\nn'
> > bla is a function
> > bla ()
> > {
> > type $FUNCNAME
> > }
> >
>
try with dev bash version, aliases work there, also include an ending space
in your aliases to make the next get expanded instead of passed as arg
On Fri, Mar 19, 2021, 15:59 Oğuz wrote:
> On Fri, Mar 19, 2021 at 4:11 PM Chet Ramey wrote:
>
>> On 3/19/21 4:12 AM, Alex fxmbsw7 R
thank you
i dunno about gdb but adding ncurses et la fixed it
thanks
On Fri, Mar 19, 2021 at 2:18 PM Chet Ramey wrote:
>
> On 3/18/21 3:28 PM, Alex fxmbsw7 Ratchev wrote:
> > hm how can i help
> > its a fresh deb all-tree's system, i had bash 5.1.4-maint from a month or
&
i have my codes much ready, but now on a clean reboot i noticed it
doesnt do few stuffs anymore
i call a per code that does eval, which i seem to call twice or trice
inside stacked
the content of args=( ) or files=( ) doesnt seem anymore active after some run
could that be ?
i guess the solution is
i realize its somewhat of a big limitation, to have only global and
one level further ( local ) args, no per function
however about my code, i fixed it with a growing mapfile reader
'mapfile -t -d "" -O ${#big[@]} big <"$_hd"/init/"$per"' \
or at least partly fixed, yet stuff worked
and eval t
im sorry to not be able to reply to all your stuffs
you didnt make it easy
im happy it works for me now
On Mon, Mar 22, 2021 at 3:43 AM Greg Wooledge wrote:
>
> On Mon, Mar 22, 2021 at 03:12:25AM +0100, Alex fxmbsw7 Ratchev wrote:
> > i realize its somewhat of a big limitation,
case statements are imho string comparision, nothing to do with aliases
On Mon, Mar 29, 2021, 17:23 Chet Ramey wrote:
> On 3/19/21 10:59 AM, Oğuz wrote:
>
> > Not much related, but isn't this supposed to work?
> >
> > $ cat foo.sh
> > alias c='case ' w='foo ' i='in ' p=') ' e='esac' u='uname ' s
i still vote for same syntax to unset as setting it, makes only sense
On Wed, Mar 31, 2021, 01:05 konsolebox wrote:
> On Tue, Mar 16, 2021 at 8:12 AM Chet Ramey wrote:
> > This means that, given the following script,
> >
> > declare -A a
> > key='$(echo foo)'
> > a[$key]=1
> > a['$key']=2
> > a
arr=( ) implies no [0]=
On Mon, Apr 5, 2021, 22:46 konsolebox wrote:
> set -u
> array=()
> __ref=array[@]
> : "${array[@]}" # Reports nothing
> : "${!__ref}" # Unbound variable
>
> Using bash version 5.1.4. I know this can be avoided by using namerefs
> instead but indirection is more portable w
what i meant was there is not one element defined so .. any reference to
anything in it will be not set.. makes sense @ is not defined
i remember !var worked with it, or at least other defined sub elements
On Tue, Apr 6, 2021, 16:26 konsolebox wrote:
> On Tue, Apr 6, 2021 at 9:57 PM A
im sorry i dont support set -u cant discuss it
On Tue, Apr 6, 2021, 16:40 konsolebox wrote:
> On Tue, Apr 6, 2021 at 10:38 PM Alex fxmbsw7 Ratchev
> wrote:
> >
> > what i meant was there is not one element defined so .. any reference to
> anything in it will be not set..
set sets args, and exits null
no bug there
On Wed, Apr 7, 2021, 16:40 konsolebox wrote:
> On Wed, Apr 7, 2021 at 9:25 PM Chet Ramey wrote:
> >
> > On 4/5/21 4:45 PM, konsolebox wrote:
> > > set -u
> > > array=()
> > > __ref=array[@]
> > > : "${array[@]}" # Reports nothing
> >
> > This is a spec
you wrong set
set -e
shopt -s extglob
da=( ?(a)match )
declare -p da
i recomment u dont set -e
On Fri, Apr 23, 2021, 16:43 john wrote:
> From: john
> To: bug-bash@gnu.org
> Subject: ls dumps bash
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: l
mkdir ttt ; cd ttt
printf 'printf success' >some\'thing
chmod +x *
./tabtab == nothing
found by samus aran on freenode irc
1 - 100 of 612 matches
Mail list logo
