Sorry for the false alarm.
Best,
--
Jason Franklin
confirm this?
Best,
--
Jason Franklin
On Wed, Apr 27, 2022, 20:30 Chet Ramey wrote:
> On 4/27/22 2:01 PM, Jason A. Donenfeld wrote:
> > ---
> > lib/glob/glob.c | 2 +-
> > locale.c| 10 +-
> > 2 files changed, 6 insertions(+), 6 deletions(-)
>
> Thanks for the patch.
>
> &
---
lib/glob/glob.c | 2 +-
locale.c| 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/lib/glob/glob.c b/lib/glob/glob.c
index eb6277f0..cadabba9 100644
--- a/lib/glob/glob.c
+++ b/lib/glob/glob.c
@@ -120,7 +120,7 @@ void udequote_pathname PARAMS((char *));
v
ook like this now...
#! /bin/sh
unset FOO
FOO=x /usr/bin/other_program
Of course, this still may fail if the shell that actually runs this
script happens to make FOO readonly in its current or future version.
I think this topic has been exhausted. I don't have much else to say
here. I am aware of the behavior now, so I can't run into this myself.
However, the choice to keep this behavior seems like an odd one.
--
Jason
On Wed, 2021-08-11 at 20:36 -0400, Greg Wooledge wrote:
> On Wed, Aug 11, 2021 at 08:00:12PM -0400, Franklin, Jason wrote:
> > This doesn't work unless it was recently fixed. A variation does...
> >
> > bash-5.0$ echo $BASH_VERSION
> > 5.0.17(1)-release
> &
d have, but I'm not seeing a good enough reason to change it
> 25-30 years in.
I think the result is that this report will surface at regular intervals
for decades to come.
--
Jason Franklin
Thanks to all of you for taking time to think about my question!
--
Jason Franklin
Hey, Greg!
I presume that you are the Wooledge who hosts the BashFAQ.
If so, thanks for hosting that. It's a huge help. :)
On Mon, 2021-08-09 at 20:36 -0400, Greg Wooledge wrote:
> On Mon, Aug 09, 2021 at 05:35:56PM -0400, Franklin, Jason wrote:
> > Should bash, invoked with &
uot;sh", omit the special
treatment of variables such as GROUPS?
--
Jason Franklin
Single quotes with the nested double quote? That's nuts. But okay. I
guess there really is some double expansion eval-like logic happening
with the unset operator.
This behavior is quite surprising:
$ declare -A blah
$ blah['$(DOESNOTEXIST)']=broken
$ for i in "${!blah[@]}"; do echo "$i"; done
$(DOESNOTEXIST)
$ for i in "${!blah[@]}"; do unset blah["$i"]; done
bash: DOESNOTEXIST: command not found
bash: unset: [$(DOESNOTEXIST)]: bad array subscript
I wouldn
On Wed, 30 Sep 2020 09:19:34 -0400 Chet Ramey wrote:
...
> I explained the reasoning in
>
> https://lists.gnu.org/archive/html/bug-bash/2016-11/msg00165.html
...
The reasoning is 100% sound, but would it make sense to add the old behavior to
a compat option? I'm not at all familiar with the dec
unset foo
echo ${!foo} bar
"shopt -s compat44" does not seem to make a difference
-Jason
On Thu, Aug 6, 2020 at 4:49 PM Chet Ramey wrote:
>
> On 8/6/20 10:36 AM, Jason A. Donenfeld wrote:
> > Hi Chet,
> >
> > On Thu, Aug 6, 2020 at 4:30 PM Chet Ramey wrote:
> >>
> >> On 8/6/20 6:05 AM, Jason A. Donenfeld wrote:
> >>> Hi,
> &
Hi Chet,
On Thu, Aug 6, 2020 at 4:30 PM Chet Ramey wrote:
>
> On 8/6/20 6:05 AM, Jason A. Donenfeld wrote:
> > Hi,
> >
> > It may be a surprise to some that this code here winds up printing
> > "done", always:
> >
> > $ cat a.bash
> > set
On Thu, Aug 6, 2020 at 2:14 PM Jason A. Donenfeld wrote:
>
> On Thu, Aug 6, 2020 at 1:15 PM Oğuz wrote:
> >
> >
> >
> > 6 Ağustos 2020 Perşembe tarihinde Jason A. Donenfeld
> > yazdı:
> >>
> >> Hi,
> >>
> >> It may be a su
On Thu, Aug 6, 2020 at 1:15 PM Oğuz wrote:
>
>
>
> 6 Ağustos 2020 Perşembe tarihinde Jason A. Donenfeld yazdı:
>>
>> Hi,
>>
>> It may be a surprise to some that this code here winds up printing
>> "done", always:
>>
>> $ cat a.bas
ion for the upcoming bash
5.1, which would cause process substitution to propagate its errors
upwards, even if done asynchronously.
Chet - thoughts?
It'd certainly make a lot of my scripts more reliable.
Jason
On Mon, Jun 22, 2020 at 2:16 PM Ilkka Virta wrote:
>
> On 22.6. 19.35, Chet Ramey wrote:
> > On 6/22/20 1:53 AM, Jason A. Donenfeld wrote:
> >> Currently a static sized buffer is used for reading files. At the moment
> >> it is extremely small, making parsing
way.
Jason
.
Signed-off-by: Jason A. Donenfeld
---
lib/sh/zread.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/sh/zread.c b/lib/sh/zread.c
index 8dd78102..f1389887 100644
--- a/lib/sh/zread.c
+++ b/lib/sh/zread.c
@@ -117,7 +117,7 @@ zreadintr (fd, buf, len)
in read(2). This does
# example command
bash-5.0$
Thus, the argument in question is specifically "-0" proper. This, to
me, means "the fc command itself" that did this work.
Would a good solution be to have "0" function as-is, but have "-0" only
be valid in the listing case? This would avoid the problem above.
Of course, documenting the intent of the feature would be key to making
the change a successful one!
Thanks, Chet!
--
Jason Franklin
eversal of histbeg and histend to before
when histend is checked. This handles the other case when a segfault
could occur (where histbeg is real_last).
Thanks again for reviewing!
--
Jason Franklin
diff --git a/builtins/fc.def b/builtins/fc.def
index 6951a687..04361b92 100644
--- a/builtins/fc
mains fixed
into the future.
I worked in tandem with my colleague, Brandon Pfeifer, to track down and
fix this issue. He deserves equal credit. If you decide to include the
patch, please credit us in your changelog as report and patch by Jason
Franklin and Brandon Pfeifer
.
Thanks in advanc
Were you planning on committing this to Savannah?
On Mon, Apr 20, 2020 at 3:58 PM Chet Ramey wrote:
> OK, good. It was either that or closing the fd after reaping the child
> process -- I couldn't tell 100% from the system call trace.
The latter is an interesting possibility. I assume SIGCHLD comes in
through a signal handler, so it's asynchrono
On Mon, Apr 20, 2020 at 3:49 PM Chet Ramey wrote:
>
> On 4/20/20 5:01 PM, Jason A. Donenfeld wrote:
> > On 4/20/20, Chet Ramey wrote:
> >> On 4/20/20 1:15 AM, Jason A. Donenfeld wrote:
> >>> Hi,
> >>>
> >>> I've uncovered a very un
This one will reproduce immediately:
#!/bin/bash
set -e
a="my name is a"
b="my name is b"
sleep() { read -t "$1" -N 1 || true; }
doit() { sleep 0.1; "$@"; }
while true; do
doit cat <(echo "$a") <(echo "$b")
done
Here's a simpler reproducer:
set -e
a="my name is a"
b="my name is b"
pretty() { echo -e "\x1b[0m"; }
doit() { pretty; "$@"; }
while true; do
doit cat <(echo "$a") <(echo "$b")
done
On 4/20/20, Chet Ramey wrote:
> On 4/20/20 1:15 AM, Jason A. Donenfeld wrote:
>> Hi,
>>
>> I've uncovered a very unusual race condition when using process
>> substitution and developed as minimal a reproducer as I could create:
>
> What version of bash are you using?
>
5.0.016
e attention to the line marked as "WHY IS BASH DOING THIS".
Indeed, why is bash doing that? Is there some weird process substitution
lifetime bug, in which returning from a function nested at depth 2
(pretty) causes the process substitution parameter to be returned,
instead of doing that from the function nested at depth 1? But in that
case, why only one and not both? Or is something else happening here?
Thanks,
Jason
On 4/16/20 10:11 AM, Chet Ramey wrote:
> On 4/16/20 9:21 AM, Franklin, Jason wrote:
>> On 4/15/20 5:35 PM, Chet Ramey wrote:
>>> These all pretty much all fall into the category of the editor reprinting
>>> the prompt before it returns.
>>
>> Hmmm...
>&g
allow PROMPT_COMMAND to function as expected. It is
surprising to see status indicators in my prompt NOT be updated when
using .
I thought that this would be easy. Is it really not possible to fix?
--
Jason Franklin
simple as that, but I
guess not!
In any case, I hope this helps improve Bash. Thanks a ton!
--
Jason Franklin
On 4/15/20 2:44 PM, Chet Ramey wrote:
> On 4/15/20 11:45 AM, Franklin, Jason wrote:
>> Greetings:
>>
>> I realized that I didn't include my email when I used bashbug to report
>> my issue, so I'm sending a follow-up email so that the maintainers can
>> be
ecute PROMPT_COMMAND directly. This
didn't work, and I'm still not sure why.
Maybe the Chet, et al., can make sense of this. Thanks so much for your
help and for maintaining my favorite shell!
--
Jason Franklin
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/bash-LQgi2O/bash-5.0=.
-fstack-protector-strong -Wform$
uname output: Linux jpt 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21
UT
So just FYI.
But we could also avoid this entire tempfile creation discussion by
getting rid of the need for those functions in the first place. :)
Jason
On Thu, Apr 11, 2019 at 6:02 AM Jason A. Donenfeld wrote:
> curious about is - what about internally treating "x <
Hi Chet,
On Wed, Apr 10, 2019 at 3:07 PM Chet Ramey wrote:
> This is unnecessary hyperbole. The existing file-based mechanism works
> just fine. We're talking about what's essentially an optimization.
> [...]
> This doesn't make any sense.
> [...]
> There isn't an "insecure path."
I'm a bit late
A fancy way would be to set NONBLOCK mode, see if it
returns EAGAIN, and only fork() if the write would block. Either way seem
basically fine, with the critical part being that the temporary file is
totally gone from the equation.
Thoughts on this?
Thanks,
Jason
(because
they don't clear the variables after execution) by typing in echo
$PASSWORD_VARIABLE.
The point is, their is a legitimate use for sourcing Binary Shell
Scripts and BASH as is, won't let you do this. Maybe not allow it by
default but have a parameter to ignore the file check to see if it is
binary.
Jason Hall
t readline, which could be something to do
with it.
Thanks & Best Regards,
Jason
On 04/02/2019, Chet Ramey wrote:
> On 2/4/19 3:22 AM, Jason Vas Dias wrote:
>> Good day -
>>
>> Under bash 4.4.23, with emacs history editing enabled, I can do:
>>$ echo &#x
ically without user initiation of command editing.
Can either of these new behaviors be disabled in bash 5.0.2 ?
Thanks & Best Regards,
Jason Vas Dias
The first line of builtins/mkbuiltins.c gives the comment:
/* mkbuiltins.c - Create builtins.c, builtext.h, and builtdoc.c from
a single source file called builtins.def. */
Where is builtins.def?
Thanks!
JHM
7;]([\\\'\'']+)[\\\'\''][^\\\'\'']*$ ]]; then echo
${BASH_REMATCH[1]}; fi;'
++ [[ "" =~ ^[^\']*[\']([\']+)[\'][^\']*$ ]]
+ set +x
+
I think bash needs some kind of "q/.../'" and 'qq/../' syntax / built-ins, or
whatever syntax its author likes, like PERL has, whereby the single quote
("'") or double quote ('"') respectively are totally ignored within
'/.../' parameter
strings, which should use a different quoting character than '"' or
"'" to delineate
them.
If the author won't develop these, I will & will send a patch.
Regards,
Jason
patch
file or in the forthcoming bash-4.4 release ?
I think it should, as it is rather unfair of bash to make its
internal bookkeeping errors appear as if they could be
user programming errors.
Regards,
Jason
On 05/06/2016, Jason Vas Dias wrote:
> The strace log shows that process 8277 is th
emits the
message:
"xxx.sh: line 46: No record of process 8278" .
Line 46 in my script consist of
function f()
.
This seems buggy to me - I'll try developing a
patch to fix it and will post back here.
Regards, Jason
On 05/06/2016, Jason Vas Dias wrote:
> With a build of bash 4.
sed in the subshell
running the f output parsing loop.
All this seems to work OK, but why the warning
message about "no record of process X"?
Or is this message indicating something has
gone seriously wrong ?
Thanks in advance for any replies,
Regards,
Jason
`$tab]+([0-9.]+)'
Do you agree ?
If not, what sort of regexp should I use to match ':[]+[0-9]+' ?
The problem happens regardless of whether I use the $tab variable or
a literal '\'$'\011' sequence (sorry, I can't type in this mailer).
Thanks in advance for any replies,
Regards,
Jason
nvoker.sh
then it is really hard to kill the resulting nterm.sh process -
one has to use kill -9 $nterm_pid .
So, please give scripts some means of saying
"if I am killed, kill my current simple command",
even in interactive mode, with some new shopt option,
or provide something like the killpg / setpgid built-ins attached.
Thanks & Regards,
Jason
nterm_demo.tar
Description: Unix tar archive
ember '0' is set or not.
To get this currently, we'd have to test if the variable is an
array, if it is an associative or normal array, and have different
methods for each case . [ ${#v[@] -gt 0 ] does not work
if $v is a normal variable.
It would be nice if -v could mean 'ha
assigned a value).
or is this a bug with -v ?
I'm using bash-4.3.30(1) , but it appears also to be an issue with
bash-4.3.11(1) .
Regards,
Jason
27;, so was trying to stty on stdin, which was the list file.
Sorry, my mistake - a nasty coincindence that it was the first
thing I tried with the new bash version.
Regards,
Jason
On 9/25/14, Jason Vas Dias wrote:
> Good day Chet, bash-list -
>
> I just checked out the latest git hea
/bin/bash /tmp/tsh
/dev/pts/6
lrwx-- 1 jvasdias jvd 64 Sep 25 14:47 /dev/fd/1 -> /dev/pts/6
not a tty
lrwx-- 1 jvasdias jvd 64 Sep 25 14:47 /dev/fd/1 -> /dev/pts/6
not a tty
lrwx-- 1 jvasdias jvd 64 Sep 25 14:47 /dev/fd/1 -> /dev/pts/6
This is rather confusing !
Any ideas what may th
tion f() { local an_array=$1; local value='1.0';
local ev='['"'"'value'"'"']='"'""$value""'"; eval
${an_array}='('"$ev"')'; }; declare -A my_array;
-x; f my_array )
+ f my_array
+ local an_array=my_array
+ local value=1.0
+ local v=1.0
+ local 'ev=['\''value'\'']='\''1.0'\'''
+ eval 'my_array=(['\''value'\'']='\''1.0'\
ciative array, as
declare -F does for functions ?
Or is there some way to test if a variable is an associative array or not?
Thanks & Regards,
Jason
On 8/29/14, Jason Vas Dias wrote:
> Good day list -
>
> There seems to be no way of testing if an array variable is associative or
>
Good day list -
There seems to be no way of testing if an array variable is associative or not ,
yet attempting to make associative assigments to a normal array results in a
syntax error .
I have something like:
declare -xr TYPE_ARRAY=0 TYPE_ASSOC=1
function f()
{ declare -n an_arra
7;d appreciate an explanation as to why this behavior is not a bug .
Thanks & Regards,
Jason
test_-e.sh
Description: Bourne shell script
standards ?
Is there some other variable I could test to retrieve $? if it has
been mangled by a '!'
in the conditional ?
Is there any other conclusion than : "if you want to access the return
status of a
function in an if clause , don't use '!' in the conditional" ?
Any responses / suggestions gratefully received.
Thanks & Regards,
Jason
and end up fighting, leading to undefined behavior.
There's a saying about assumptions that probably applies here...
On Fri, Jul 12, 2013 at 3:30 AM, Andreas Schwab wrote:
> Jason Sipula writes:
>
> > This fixed bash. So it does appear MySQL is disabling echo.Strange that
>
mysqldump -u someuser -p somedb | mysql -u someuser -p -D someotherdb
>
> so you are saying the password to someuser is somedb and not giving a
> database.
> in the second case you are saying that the password to someuser is -D
>
>
>
> *Gesendet:* Donnerstag, 11. Juli 2013 um
took the time to explain this to me
instead of just blowing me off. Thank you very much.
-Jason
On Thu, Jul 11, 2013 at 11:04 AM, Greg Wooledge wrote:
> On Thu, Jul 11, 2013 at 10:47:12AM -0700, Jason Sipula wrote:
> > I still think this is a bash issue. After the command terminat
like echo is turned off
> try typing
> stty +echo
> when you you say you don't see any output.
> And if its turned off it was probably turned off my mysql.
> *Gesendet:* Donnerstag, 11. Juli 2013 um 19:53 Uhr
> *Von:* "Jason Sipula"
> *An:* Kein Empfänger
> *Cc
something like
> read -sp "Password:" Password
> mysqldump -u someuser --password ${Password} -p somedb | mysql -u someuser
> --password ${Password} -p -D someotherdb
>
> *Gesendet:* Mittwoch, 10. Juli 2013 um 23:54 Uhr
> *Von:* "Jason Sipula"
>
ting the shell prompt on the same line.
Repeat-By:
At the shell, issue the command:
~]# mysqldump -u someuser -p somedb | mysql -u someuser -p -D someotherdb
Shouldn't need to run that command as root, but the mysql user must be
privileged enough to work with the two databases. To simplify things you
can replace "someuser" with root.
Thank you,
Jason Sipula
alup...@gmail.com
point .
Does anyone know if there is a way to disable this ?
Thanks in advance for any response -
Best Regards,
Jason Vas Dias
of escaping not being enabled during word-splitting
not documented anywhere ?
Thanks & Regards,
Jason
On Sun, Jul 29, 2012 at 9:05 PM, Andreas Schwab wrote:
> Jason Vas Dias writes:
>
>> Thanks Dan -
>> The plot thickens - Yes, you're right, I had $IFS mistakenly se
uldn't it
be doing so?
Escaping works in filenames, so why not in word-splitting ?
Thanks & Regards,
Jason
On Sun, Jul 29, 2012 at 4:19 PM, Dan Douglas wrote:
> On Sunday, July 29, 2012 03:23:29 PM Jason Vas Dias wrote:
>> echo $(count_args 1 2 3\ 4)
>
> I should als
imiter (' ', '') . Quoting doesn't seem to help either:
$ echo $(count_args 1 2 3\ 4) $(count_colons 1:2:3':4')
3 4
To me, this appears to be a bug.
But I bet you're going to tell me it is a feature ?
Please explain.
Thanks & Regards,
Jason
BTW, docum
On Sun, Jul 8, 2012 at 5:50 PM, Chet Ramey wrote:
> On 7/7/12 11:39 AM, Jason Vas Dias wrote:
>
>> Next Question :
>> - any plans to allow us to export array or associative store
>> variables ? ie. represent them in *environ passed to programs
>> with an i
tive store
variables ? ie. represent them in *environ passed to programs
with an integration with glibc "getenv()" to support this ?
Thanks & Regards,
Jason
On Thu, Jul 5, 2012 at 12:59 PM, Jason Vas Dias
wrote:
> hi Eric - thanks for your response, but bash-4.2.29(2), just built
ed to give to enable it? Thanks!
On 5 Jul 2012 13:24, "Eric Blake" wrote:
> On 07/05/2012 04:58 AM, Jason Vas Dias wrote:
>
> > Now it changes the input string into
> > 'less \$SRC/' and prevents tab expansion
> > as would be done without use of any
edir .
Now it changes the input string into
'less \$SRC/' and prevents tab expansion
as would be done without use of any variables.
Would anyone know how to restore the old behavior
with bash 4.2.2 + readline 6.2 (linux ubuntu 12.04) ?
Thanks & Regards, Jason
ame of the new working directory is
written to the standard output. An argument
of - is otherwise equivalent to $OLDPWD.
Jason
most of the above is made up of some of your
thoughts, your text, and of your code that you told to me. Only the
idea to ship them as bindings with Bash is mine.
--
Jason Spiro: software/web developer, packager, trainer, IT consultant.
I support Linux, UNIX, Windows, and more. Contact me to discuss your needs.
+1 (416) 992-3445 / www.jspiro.com
if you knew this or not, but at
least on my linux boxen you can use '# sysctl kernel.core_pattern' to
see where core files will be created and their name. I guess it's
typically kernel.core_pattern = core, but sometimes you'll fi
dumped)
% ls -l core
-rw--- 1 jacr swdvt 2265088 2006-10-19 14:24 core
Jason,
This clearly is not a bash bug as your own program shows that getrlimit
reports the correct setting of 512K for RLIMIT_CORE.
This is a kernel surprise. The RLIMIT_CORE setting does not actually
limit
the size
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu'
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../
Hi,
I'm trying to limit the size of coredumps using 'ulimit -c'. Can
someone please explain why a core file gets generated from the coretest
program (source is below)?
Thanks for any help or suggestions.
Shell interaction
% ulimit -H -c
unlimited
% ulimit -S -c
0
% bash --version
GNU bash, v
Thanks! Sorry to waste your time with something which was in the man
page afterall. This is exactly what I was looking for.
-jason pepas
On Thu, Aug 25, 2005 at 02:02:40AM -0400, Chris F.A. Johnson wrote:
> On Wed, 24 Aug 2005 [EMAIL PROTECTED] wrote:
> >
> >Configurat
Norman Virus Control a supprimé le message original qui contenait le virus
[EMAIL PROTECTED]
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
84 matches
Mail list logo
