self, other software that uses bash). Is there a
"better" branch that I could use for this purpose?
Best regards and "see you next year",
George...
On Wednesday, December 27, 2023 at 10:10:56 AM PST, Chet Ramey
wrote:
On 12/26/23 1:06 PM, George R Goffe wrote
pends] Error 127
I do have a full log if you need/want it. I don't see mkdep anywhere in the
build tree. Is this a "bug" or a mistake on my part?
Best regards and happy hollidays.
George...
On Wed, 2022-08-31 at 11:11 -0400, Chet Ramey wrote:
> On 8/29/22 2:03 PM, tetsu...@scope-eye.net wrote:
>
> > It would also help
> > greatly if the shell could internally handle hierarchical data in
> > variables.
>
> That's a fundamental change. There would have to be a better reason
> to make
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin20.5.0
Compiler: gcc
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Darwin Georges-Mac-Pro.local 20.5.0 Darwin Kernel Version
20.5.0: Sat May 8 05:10:33 PDT 2021; root:xnu-
ave a full build log available if needed.
Regards and THANKS for your help,
George...
gcc -DHAVE_CONFIG_H -DSHELL -I. -I.. -I.. -I../include -I../lib -I. -g
-O2 -Wno-parentheses -Wno-format-security -rdynamic -g -O2 -Wno-parentheses
-Wno-format-security -rdynamic -g -O2 -Wno-parentheses
make (or try) the failure
appear. Your thoughts?
Regards,
George...
George...
On Wednesday, August 19, 2020, 5:58:03 AM PDT, Chet Ramey
wrote:
On 8/19/20 12:02 AM, George R Goffe wrote:
> Chet,
>
> I've been thinking about what you've said below... that
is fix?
I don't see a way to work around it myself, other than not using debug
traps which isn't an option as far as I can tell. I'll help in any way I
can.
Thanks,
George
have negative impact (huge buffer preallocation) on the existing
?30 years? of users/scripts.
Some docs on how the SIZE is used (hint for preallocation of hash table
size, not hard limit on number of entries) probably also in order.
Thanks,
---george jones
On Mon, Apr 20, 2020, 4:23 PM Chet Ramey
better on, e.g. Spark if that were and option in the environment).
Even the old behavior was probably good enough for most people. It's only
when you start abusing bash to to "big data" that the problem shows up.
Thanks again, and impressive quick work !
---george jones
On Mo
LINES 290 ELAPSED 58
lines_per_sec 5.00 LINES 300 ELAPSED 60
lines_per_sec 5.00 LINES 310 ELAPSED 62
---George Jones
On Sun, Apr 19, 2020 at 3:52 PM Koichi Murase
wrote:
> 2020-04-19 23:54 George Jones :
> > It looks like hash_search just does a linear walk if arra
here https://eludom.github.io/blog/20200418/
Thanks,
---george jones
On Sun, 2020-03-29 at 01:55 -0700, John W wrote:
> On 3/26/20, George <
> tetsu...@scope-eye.net
> > wrote:
> > On Thu, 2020-03-26 at 19:05 +0200, Vaidas BoQsc wrote:
> > I think shells would really benefit from things like
> > more powerful data structures, bett
On Thu, 2020-03-26 at 19:05 +0200, Vaidas BoQsc wrote:
> I keep on wondering why these shells can't come up with something better
> than improving previous shell syntax by little by only providing poor
> better alternatives.
> I somehow think there is a need to rethink shells from scratch to make t
xport/home/tools/bash/bash-5.0/examples/loadables'
make: [Makefile:824: install] Error 2 (ignored)
trying without the bashrc function. Sigh...
same result. bash/examples/loadables has a mkdir! Why would make install try to
mkdir for the "current" directory?
I removed mkdir from the Makefile and named it xx... make -f xx install worked!
Any thoughts?
George...
Hi,
I've been seeing these crashes randomly for the past month. This happens when I
try to use filename completion. Is this a bash bug?
Regards,
George...
This is the bash version: bash-5.0.7-3.fc31.x86_64
xpdAssertion 'pthread_mutex_init(&b->memfd_cache_mutex, NULL) ==
Hi,
I just built the latest bash in an effort to determine if thie script shows a
bug or a ufu. Can you help me please?
I was expecting to see:
12345
Best regards AND thanks for your help,
George...
#!./bash -xv
x="1 2 3 4 5"
+ x='1 2 3 4 5'
for z in "$x"
On Sun, 2018-05-20 at 04:56 +0200, Garreau, Alexandre wrote:
> On 2015-11-13 at 07:17, Greg Wooledge wrote:
> Actually in the most general case, where those output streams may
> contain NUL bytes, it requires two temp files, because you can't store
> arbitrary data streams in bash variables at all.
On Sun, 2017-06-25 at 12:23 -0400, Chet Ramey wrote:
> On 6/24/17 1:41 PM, Eduardo A. Bustamante López wrote:
>
> >
> > dualbus@debian:~$ LANG=zh_CN.GBK printf '\u4e57' | od -tx1 -An
> > 81 5c
> >
> > It looks like it doesn't detect that \x81\x5c is a single character, and
> > instead treat
On Sat, 2017-06-24 at 12:41 -0500, Eduardo A. Bustamante López wrote:
> I was looking through this old thread:
> http://seclists.org/oss-sec/2014/q3/851
>
> It looks like the issue reported in there is still there:
>
> dualbus@debian:~$ LANG=zh_CN.GBK printf 'echo \u4e57\n' |LANG=zh_CN.GBK bash
On Tue, 2017-06-20 at 23:47 -0500, Eduardo A. Bustamante López wrote:
> On Tue, Jun 20, 2017 at 11:49:56AM -0400, tetsu...@scope-eye.net wrote:
> [...]
> >
> > So implementing Unix Domain Sockets in the shell would give you the
> > ability to connect to existing services on the machine that use na
On Sat, 2017-06-17 at 20:23 -0400, Chet Ramey wrote:
> On 6/14/17 12:04 PM, tetsu...@scope-eye.net wrote:
> >
> >
> > This is relevant to my interests!
> >
> > So first off, the circular reference problem with "declare -n"
> > apparently doesn't exist in Korn Shell: If you "typeset -n x=$1", and
On Tue, 2017-06-13 at 20:14 -0400, Chet Ramey wrote:
> On 6/13/17 5:19 PM, tetsu...@scope-eye.net wrote:
> >
> >
> > In that case, the answer is simple:
> >
> > The shell swiftly rejects the script, and provides a clear reason why
> > it cannot be run. ("bash: Script requires the en_US.utf8 loca
On Sat, 2017-06-10 at 19:33 +0300, Pierre Gaston wrote:
>
>
> > >
> > One option that might make a feature like this integrate into the shell
> > better would be to store a captured byte stream as an integer array rather
> > than as an atomic variable. The back-end implementation in this case c
On Sat, 2017-06-10 at 11:20 -0500, Eduardo Bustamante wrote:
> On Sat, Jun 10, 2017 at 04:56:35PM +0200, Paul Peet wrote:
> >
> > I would like to report a bug with bash (readline?). This bug can be
> > reproduced by opening gnome-terminal with bash running. By quickly
> > horizontally resizing the
On Fri, 2017-06-09 at 20:58 +0300, Pierre Gaston wrote:
> On Fri, Jun 9, 2017 at 8:40 PM, Peter & Kelly Passchier <
> peterke...@passchier.net> wrote:
>
> >
> > On 09/06/2560 23:38, L A Walsh wrote:
> > >
> > > Chet Ramey wrote:
> > > >
> > > >
> > > > Should mapfile silently drop the NULs?
>
On Tue, 2017-06-06 at 10:20 -0400, Greg Wooledge wrote:
> (OK, in reality, I am not taking any of this seriously. This entire
> proposal and discussion are like some bizarre fantasy land to me. Bash
> is a SHELL, for god's sake. Not a serious programming language. Even
> serious programming lan
On Mon, 2017-06-05 at 16:16 -0700, L A Walsh wrote:
> George wrote:
> >
> > On Mon, 2017-06-05 at 15:59 +0700, Peter & Kelly Passchier wrote:
> >
> > >
> > > On 05/06/2560 15:52, George wrote:
> > >
> > > >
> > >
On Mon, 2017-06-05 at 15:59 +0700, Peter & Kelly Passchier wrote:
> On 05/06/2560 15:52, George wrote:
> >
> > there's not a reliable mechanism in place to run a script in a locale
> > whose character encoding doesn't match that of the script
> From my
On Sun, 2017-06-04 at 11:47 -0700, L A Walsh wrote:
> dualbus wrote:
> >
> > I hadn't realized that bash already supports Unicode in function names!
> > FWIW:
> >
> > bash-4.4$
> > Lēv=?
> > Φ=0.618033988749894848
> >
> >
> > With this terrible patch:
> >
> > dualbus@debian:~/src/gnu/
On Sat, 2017-06-03 at 01:20 -0700, L A Walsh wrote:
> Some conventions regarding character set usage have already been "solved"
> and encoded in binary properties of the characters. For example, the
> start and continue "ID" properties are best associated with names used
> for variables.
Referrin
On Mon, 2017-05-29 at 11:37 -0500, dualbus wrote:
> On Mon, May 29, 2017 at 12:29:16AM -0400, George Caswell wrote:
> [...]
> >
> > Bash's builtin function "read" has one simple job: read data, return
> > it to the caller. There shouldn't be an
On Mon, 2017-05-29 at 15:36 -0400, Chet Ramey wrote:
>
> >
> > > Well, that's disappointing. So there is no technical reason for
> > this behavior
> > > other than copying the behavior of ksh. BTW zsh does the right
> > thing and in the
> > > following scenario:
> > >
> > > ls -lh /proc/
>On 5/8/17 1:31 PM, Eduardo Bustamante wrote:
>> I think `edit-and-execute-command' shouldn't be allowed under `read -e'.
>
>There's no compelling reason to disallow it. If a system administrator
>wants to unbind certain readline commands (and unset INPUTRC!) to protect
>against a specific use cas
On Sun, 2017-05-21 at 10:47 -0500, Eduardo Bustamante wrote:
> FWIW, this seems to "fix" the issue.
...
Great! Any chance we could get this fix into the next release? :)
On Fri, 2017-05-19 at 21:37 -0500, Eduardo Bustamante wrote:
> On Fri, May 19, 2017 at 12:08 PM, wrote:
> [...]
> >
> > Anyway, I thought I'd float the idea and see if it might be a
> > possibility.
> Feel free to send patches.
>
> Could you provide examples on how you expect this to be used? I
On Fri, 2017-05-19 at 21:38 -0500, Eduardo Bustamante wrote:
> On Fri, May 19, 2017 at 3:32 PM, wrote:
> [...]
> >
> > I'd really like to see Bash get on the right side of this issue - and
> > the sooner the better.
> There is no right side. Only two opposing viewpoints. I don't think
> it's eno
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-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
> On 4/13/16 1:54 AM, George Caswell wrote:
> > Personally, I don't think it makes sense for a redirection on a command to
> > persist beyond the scope of that command. A redirection with a
> > dynamically-assigned fd is basically equivalent to a redirection to a
>
> On 1/27/16 1:18 PM, Mathieu Patenaude wrote:
> >
> > When using "named" file descriptors inside a function, the file descriptors
> > are not automatically un-linked when the function returns, but when using
> > regular "numbered" file descriptors they are automatically "destroyed".
>
> Yes. Th
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.
Never mind. Further investigation shows it's working as designed, and the
(ir)rationale behind it.
Sigh. Just when I thought EBCDIC was nothing but a distant, painful memory,
it gets institutionalized.
gwb
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2 -
L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -
DCONF_OSTYPE='linux-gnu' -D
ly implies that, because
newline is a control operator, newline is also a metacharacter.
A proper fix could be to change the definition of operator to be "a control
operator or a redirection operator. [...] Operators contain at least one
unquoted metacharacter or an unquoted newline character."
Thanks for your time,
George Gallo
el is
misbehaving in this case.
On Tue, Apr 10, 2012 at 9:20 AM, Chet Ramey wrote:
> On 6/13/11 1:45 AM, George wrote:
> > I'm the maintainer of a terminal emulator on Mac OS and a user
> > reported that if he pastes a large string of the form:
> >
> > cat << EOF >
TUVWXYZABCDEFGHIJKLMNOPQRSTUVW
etc.
On Linux, you get the occasional short line. On Mac OS, you get only a
few lines and they're very long.
I can reproduce this on Mac OS with the latest bash source build with
default settings.
Thanks for your help,
George
Chet,
I'll do that right now.
Thanks for the QUICK response.
George...
On Tue, Mar 29, 2011 at 11:19 AM, Chet Ramey wrote:
> On 3/29/11 2:09 PM, George Goffe wrote:
> > Howdy,
> >
> > I am experiencing a problem with sourcing a file. It's really my bash
almost 3000 lines of code...
mostly little functions that I would otherwise write separate scripts for.
Regards,
George...
end of the second log that
shows the error. If you need both logs I can send them, no problem. It's like
make distclean or make clean removes too many files, without either, the build
succeeds both times. I'm enclosing the script so you'll see my options.
Regards,
George...
o
Howdy,
I have noticed that some commands appear in history and some do not. I have
isolated that to commands that have blanks before their name. I sometimes see
this with pasted commands but this may be the same problem.
Am I doing something wrong by any chance?
Regards,
George...
"
warning: process substitution mechanism fail, please do not consider
warning: this a test failure"
Thanks for the help :-))
Bill T.
-Original Message-
From: Chet Ramey [mailto:chet.ra...@case.edu]
Sent: Thursday, September 03, 2009 7:44 AM
To: Tovrea, George W (US SSA)
Cc: bug-
ginal Message-
From: Chet Ramey [mailto:c...@caleb.ins.cwru.edu] On Behalf Of Chet Ramey
Sent: Tuesday, September 01, 2009 2:52 PM
To: Tovrea, George W (US SSA)
Cc: bug-bash@gnu.org; c...@po.cwru.edu
Subject: Re: Who handles "fails to build" problems for bash?
> Could not find any
Could not find any groups other than this for bash problems. My build is
failing with
make[1]: Leaving directory `/home/users/tovrea/BASH/build_sgi_bash/lib/tilde'
rm -f bash
/home/users/tovrea/local/sgi6/bin/gcc -L./builtins -L./lib/readline
-L./lib/readline -L./lib/glob -L./lib/tilde -L./lib
Chet,
No appreciable change in behavior... I added my script that I use to
build all the free software I build to the beginning of the log.
Regards,
George...
Chet Ramey wrote:
George R. Goffe wrote:
Howdy,
I'm trying to build this bash version (4.0 rc1) and am having problems.
ny success. Here's the latest build
log file.
Regards,
George...
bld.log3.gz
Description: application/gzip
- The version number of Bash.
[12:[EMAIL PROTECTED]:/tmp]$ bash --version
GNU bash, version 2.05b.0(1)-release (powerpc-apple-darwin8.0)
Copyright (C) 2002 Free Software Foundation, Inc.
- The hardware and operating system.
On a Macbook Pro running OSX 10.4:
[12:[EMAIL PROTECTED]:/tmp]$ uname -a
D
Howdy,
This result (see below) seems to be redily re-creatable. Could you
take a peek at this and tell me if it is a bug or if I'm doing
something wrong please?
Regards and thanks for your time,
George...
rm -f bash
gcc -L./builtins -L./lib/readline -L./lib/readline -L./lib/glob
-L./lib/
d in bash 3.0 and there wasn't anything in the changes that is
related to basic parsing like this.
Repeat-By:
Use typical let statement such as let a=(5+3).
George Sherwood
signature.asc
Description: This is a digitally signed message part
___
57 matches
Mail list logo
