On 8/26/24 16:29, Chet Ramey wrote:
On 8/24/24 11:53 PM, Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
This seemed to happen over and over and only during "make install".
There are a number of loadable builtins that require arrays and don't build
with
On 8/26/24 16:29, Chet Ramey wrote:
On 8/24/24 11:53 PM, Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
This seemed to happen over and over and only during "make install".
There are a number of loadable builtins that require arrays and don't build
with
'/opt/bw/build/bash-5.2.32_rhel9_amd64.001/examples/loadables'
make: [Makefile:846: install] Error 2 (ignored)
Not very helpful.
This is off the shelf bone stock RHEL9 with the default compiler and
linker and nothing remotely interesting.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
On Sun, Mar 24, 2024 at 4:04 PM Greg Wooledge wrote:
> The @K (capital) transformation gives you quoted strings which need to
> be eval'ed. Very Bourne-shell-ish.
>
> The @k (lowercase) transformation gives you a list of alternating raw
> key/value strings, like what you'd expect from a Tcl comm
On Sun, Mar 24, 2024 at 1:56 PM Greg Wooledge wrote:
> It would be pretty reasonable to have a builtin that could take an array
> name plus any number of additional argument pairs, and load those pairs
> as keys/values into said array. Then you could do something like this:
>
> declare -A ha
was happening over and over with different builds. Only on
that oddball hardware of course.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
On 3/4/24 12:05, Chet Ramey wrote:
On 2/29/24 12:11 PM, Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
Well this has me a bit baffled.
I downloaded the bash source tarball for 5.2.21 and then applied the
few patches to get me to :
io$
io$ which bash
/opt/bw/bin/bash
io
MAILPATH CDPATH
+ eval test '${CDPATH+y}'
++ test
+ :
+ :
+ :
+ exec
+ :
+ :
+ PATH_SEPARATOR=:
+ as_myself=
+ case $0 in
+ as_myself=./configure
+ test x./configure = x
+ test '!' -f ./configure
malloc: ../bash-5.2.21/dispose_cmd.c:249: assertion botched
free: called with alrea
On Mon, Dec 11, 2023 at 1:09 AM Dan Jacobson wrote:
> Type ^R and some string,
> At the point while we are typing that the search fails, all that
> happens is the word "failed" gets added at front,
>
> (reverse-i-search)`nni': set
> jida^Ci.org/geo/house_numbering/grids/us/il/lake/lake_county/
>
-- Forwarded message -
From: Dennis Williamson
Date: Thu, Oct 26, 2023 at 12:09 PM
Subject: Re: Strange results
To: Victor Pasko
echo "echo11 ${ASCII_SET:-10:1}"echo "echo11 ${ASCII_SET:-10:1}"
On Thu, Oct 26, 2023 at 9:54 AM Victor Pasko wrote:
> Hi,
On Tue, Aug 15, 2023 at 8:57 PM Wiley Young wrote:
> So this behavior of `bash`s seems like a bug to me. I stumbled across it by
> accident.
>
> From within a stack of x3 functions called from a case within a for loop,
> when trying to assign a value to a read-only variable, `printf` and `read`
>
On Wed, Jul 26, 2023, 3:40 PM wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -Wall
> uname output: Linux fnord42 6.1.25-1rodete1
On Fri, Jul 14, 2023, 3:44 AM Grisha Levit wrote:
> On Fri, Jul 14, 2023 at 3:44 AM Martin D Kealey
> wrote:
> >
> > On the whole I think this is great, and thankyou for working up the
> patch, but I would like to offer some comments and suggestions:
>
> Thanks for looking at it, feedback very m
On Mon, Jul 3, 2023 at 11:11 AM alex xmb ratchev wrote:
>
>
>
> thats a like 30% or smth
> enuff for me
> i d be the fool typing nonsensly ; s
>
Do what you like, but percentages don't mean anything unless you're running
a lot of assignments in a loop like the artificial conditions in the test I
On Mon, Jul 3, 2023 at 10:32 AM alex xmb ratchev wrote:
>
> i chain assignments , have impression its faster
>
> kre
> >
> >
> >
>
Tests are better than impressions. Sometimes they match though.
$ time for ((i = 0; i <= 100; i++)); do j=$i; k=$j; m=10;
n=foobarbazqux; p=100; q=$n; r=$k;
On Tue, Jun 27, 2023 at 12:29 AM n952162 wrote:
> Is this correct?
>
> declare -A l1
>
> l1=([a]=b [c]=d)
> echo ${!l1[@]}
>
> l1=($(echo [a]=b [c]=d))
> echo ${!l1[@]}
>
> $ bash t4
> c a
> [a]=b [c]=d
>
> If so, why? And how can I assign a list of members to an associative
On Mon, Jun 26, 2023, 2:47 PM Hugo Napoli wrote:
> Dear Dennis and Martin, thank you very much for the quick response.
>
> From now on, I'll use *exec bash "$0" *instead of *bash "$0"*.
> What I'm wondering is (now that I understand why this happened)
On Mon, Jun 26, 2023, 11:07 AM Hugo Napoli wrote:
> Good day.
>
> Something strange is happening to me with this script that I have designed
> moments ago.
> I am a Computer Science professor, and among the subjects I teach, there is
> one that has to do with BASH programming.
> I make my own mat
On Tue, Jun 20, 2023 at 10:55 PM LitHack wrote:
> Sorry instead of alias we have to use the function.
>
> Corrected command: mkdir dir;cd dir;<>file;file()bash;*
>
> Thanks and regards.
>
You don't need the function either.
mkdir dir; cd dir; touch bash; *
--
Visit serverfault.com to get yo
On Sat, Jun 17, 2023, 6:59 AM alex xmb ratchev wrote:
> On Thu, Jun 15, 2023, 20:40 alex xmb ratchev wrote:
>
> >
> >
> > On Thu, Jun 15, 2023, 15:06 Chet Ramey wrote:
> >
> >> On 6/14/23 5:18 PM, alex xmb ratchev wrote:
> >>
> >> > [[ -v a["$subscript"] ]]
> >>
> >
> a small question about
On Wed, May 24, 2023, 5:21 PM William via Bug reports for the GNU Bourne
Again SHell wrote:
> Hi. It's the first time I send a message about a bug using bashbug. I
> don't known if the message was sent properly. So, I repeat it that way.
>
>
> Machine: i686
>
> OS: linux-gnu
> Compiler: gcc
> Com
On Fri, Mar 31, 2023, 3:02 PM Martin Schulte
wrote:
> Hi Dennis,
>
> thanks for your answer!
>
> > This isn't regex.
>
> Sure!
>
> > It's a command synopsis using a long standing notation
> > style. You can see it set out in POSIX in
>
On Fri, Mar 31, 2023, 2:47 PM Martin Schulte
wrote:
> Hi Chet!
>
> > >> Thanks for the report. The synopsis should read
> > >>
> > >> cd [-L|[-P [-e]]] [-@] [dir]
> > > ^ ^
> > > But aren't these two brackets just superfluous?
> >
> > -L and -P are mutually exclusive, and -e is va
On Sun, Oct 30, 2022 at 4:41 PM Alex fxmbsw7 Ratchev
wrote:
>
>
> i coded a files tree to bash code via gawk reading and printing bash code
> i did noeol no newline at end
> logically , cause , who wants var='from file\n'
>
> >
>
Because command substitution strips trailing newlines?
$ echo -e
On Tue, Oct 11, 2022, 3:12 PM Greg Wooledge wrote:
> On Tue, Oct 11, 2022 at 12:38:44PM -0700, Koichi Murase wrote:
> > As far as I know, glob/extglob
> > does not have constructs that cannot be represented by formal regular
> > languages so should always be able to be represented by NFAs and thu
On Sat, Sep 24, 2022 at 11:02 AM kurt wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto
> -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=f
On Sun, Aug 28, 2022 at 7:47 PM Dale R. Worley wrote:
> The "obvious" way to support Json in Bash would be a utility that parses
> Json and produces e.g. a Bash associative array, and conversely a
> utility that reads a Bash associative array and produces Json. The real
> limitation is that it's
On Wed, Aug 24, 2022, 9:07 AM Alex fxmbsw7 Ratchev
wrote:
> debian 5.2.0(1)-beta bash
>
> i did code lightly in interactive
> then i did
>
> set -- 1 2 3
> echo ${!#}
>
> then arrow up
> .. both cmds were skipped , and on the term was rather the old code , which
> i previously wrote
>
> then i di
On Fri, Aug 12, 2022 at 6:51 PM Budi wrote:
> It doesn't work means no use on set -x, no value is shown
>
> On 8/13/22, Dennis Williamson wrote:
> > On Fri, Aug 12, 2022, 6:28 PM Budi wrote:
> >
> >> How come math/arithmetic ((i=k+l)) cannot make use of set
On Fri, Aug 12, 2022, 6:28 PM Budi wrote:
> How come math/arithmetic ((i=k+l)) cannot make use of set -x
>
> Please help..
> (so annoying).
>
It works for me. What are you expecting?
It would help if you show what you're doing, the result you're getting and
what you expect instead.
"It doesn'
On Mon, Jul 11, 2022 at 8:22 AM Chet Ramey wrote:
> The normal rules of precedence apply, and the conditional expression on the
> rhs of the `:' can't contain an assignment, since the assignment operator
> has higher precedence.
>
>
This excerpt from the Bash man page ARITHMETIC EVALUATION sectio
In help declare it says:
Using `+' instead of `-' turns off the given attribute.
In the Bash man page it says:
Using `+' instead of `-' turns off the attribute instead, with the
exceptions that +a and +A may not be used to destroy array variables and
+r will not remove the readonly at
On Tue, Apr 12, 2022, 3:18 PM Sergio Fuentes <
fuentes.sergio.nov2...@gmail.com> wrote:
> Hello,
>
> Please, run the following 3 commands to reproduce the bug:
>
> echo '. ./poc.sh' > poc.sh
> chmod +x poc.sh
> bash -c './poc.sh'
>
> The backtrace from gdb:
> gdb /bin/bash core
> ...
> Program ter
On Mon, Mar 21, 2022 at 4:01 AM Michaelll Lee wrote:
> . . .
> While using non-printing characters without "\[...\]" proves to be fine in
> versions prior to 5.x.x (e.g., many suggestions from some online forums
> have suggested "PS1=\e[0m" for using ANSI escape code in the prompt), the
> same co
On Sun, Feb 13, 2022, 9:48 PM Robert Elz wrote:
> Date:Sun, 13 Feb 2022 21:38:19 -0500
> From:"Dale R. Worley"
> Message-ID: <87o83a895w@hobgoblin.ariadne.com>
>
> | The two a-priori plausable behaviors are for the backslash to be taken
> | literally (which i
On Thu, Feb 3, 2022, 11:14 AM Alex fxmbsw7 Ratchev
wrote:
> aliases are the way not to write duplicate code
>
>
No, functions are.
>
On Mon, Nov 1, 2021, 3:46 PM Greg Wooledge wrote:
> On Tue, Nov 02, 2021 at 03:23:15AM +0700, Robert Elz wrote:
> > Date:Mon, 1 Nov 2021 12:03:48 -0400
> > From:Greg Wooledge
> > Message-ID:
> >
> > | > bash: : command not found
> > | > bash: : command not found
On Fri, Oct 22, 2021, 8:53 PM Alex fxmbsw7 Ratchev
wrote:
> could someone share some git wisdom
> in preciese few and similiar commands
>
> show version ( of .git url )
> show available versions
> git update tree [ to specific release / version, or newest ]
>
I'm sure there are lists that provid
On Mon, Oct 4, 2021, 9:09 AM Ilkka Virta wrote:
> On Mon, Oct 4, 2021 at 4:46 PM Chet Ramey wrote:
>
> > Bash reports the error it gets back from execve. In this case, it's
> > probably that the loader specified for the executable isn't present on
> your
> > system.
> >
>
> OTOH, for a script, B
On Sun, Sep 19, 2021, 4:07 PM Lawrence Velázquez wrote:
> On Sun, Sep 19, 2021, at 3:25 PM, 積丹尼 Dan Jacobson wrote:
> > $ help for
> > only mentions
> >for name [ [ in [ word ... ] ] ; ] do list ; done
> > and needs to be updated to mention
> >for (( expr1 ; expr2 ; expr3 )) ; do
On Wed, Sep 1, 2021, 8:42 PM Greg Wooledge wrote:
> On Wed, Sep 01, 2021 at 09:37:02PM -0400, Dale R. Worley wrote:
> > "C. Yang" writes:
> > > emacs test.txt &
> > >
> > > fg
> >
> > > bash: fg: no job control
>
> > It sounds like Bash doesn't activate the job-control features until
> > .bashrc
On Wed, Jul 7, 2021, 7:55 PM wrote:
>
>
> Things are clearer now.
>
>
>
> > Seriously, just replace the :- expansion with := and go on with your
> code.
> > It's the least intrusive change, and won't disturb your logic.
>
>
>
> I executed
>
>
>
> echo "${parameter:-word}"; echo "${parameter}"
>
On Wed, Jul 7, 2021, 4:50 PM wrote:
>
> Have noticed that parameter expansion with `:` does not work
>
>
>
> : ${fltype:-"texi,org"} # alternative to `fltype=`
>
>
$ unset foo
$ : ${foo:-bar}
$ echo "$foo"
$ : ${foo:=bar}
$ echo "$foo"
bar
The first form is a substitution and the second form
On Tue, Apr 6, 2021, 3:09 PM Greg Wooledge wrote:
> On Wed, Apr 07, 2021 at 03:53:43AM +0800, konsolebox wrote:
> > Also if Bash could just store associative array
> > values as a list to preserve store order and stop expanding
> > "${array[@]}" based on the sorted order of the keys, then the sli
.
On Tue, Mar 16, 2021, 10:22 PM Lawrence Velázquez wrote:
> > On Mar 16, 2021, at 11:08 PM, Dennis Williamson <
> dennistwilliam...@gmail.com> wrote:
> >
> > I've been playing with your optimized code changing the read to grab data
> > in chunks like
On Tue, Mar 16, 2021, 6:19 PM Lawrence Velázquez wrote:
> > On Mar 16, 2021, at 6:01 PM, Jay via Bug reports for the GNU Bourne
> Again SHell wrote:
> >
> > Hello,
> >
> > I have been using/exploring Linux for ~ 2yrs; have corrupted a couple
> > systems more than once either through their
uot; will result in the segfault.
Also, Chet has no access to the real hardware and thus looking at this
on x86 is like looking at the problem with a Raspberry Pi. Not the same
at all. Perhaps a nightly buildbot would help here? It certainly is a
trivial matter to setup a small zone on an Oracle box here and then let
it run.
Dennis
On 12/31/20 12:31 AM, Chet Ramey wrote:
> On 12/29/20 7:28 PM, Dennis Clarke wrote:
>>
>> Firstly as a minor nit that seems to re-appear yearly there are still
>> source files in the release tarballs that are not readable to a normal
>> user :
>>
>> #
>
= (char *)NULL;
_rl_term_kh = _rl_term_kH = _rl_term_at7 = _rl_term_kI = (char *)NULL;
_rl_term_so = _rl_term_se = (char *)NULL;
#if defined(HACK_TERMCAP_MOTION)
_rl_term_forward_char = (char *)NULL;
#endif
For reasons that I can not yet figure out sh_get_env_value ("TER
On Sun, Jun 28, 2020, 8:50 AM felix wrote:
>
>_out=$(date -d "$_string" +%s)
> many time in same script, I run something like:
>
> _fifo=$(mktemp -u /tmp/fifo-)
> mkfifo $_fifo
> exec 9> >(exec stdbuf -o0 date -f - +%s >$_fifo 2>&1)
> exec 8<$_fifo
> rm $_fifo
>
>
On Thu, Jun 18, 2020, 6:03 PM Bryan Henderson
wrote:
> ...
Any ideas on how I could see
> the raw character stream sent to a terminal?
>
>
Try the xev program. It will show X events and may reveal the keypresses
you're interested in.
>
On Wed, Jun 17, 2020, 5:07 PM wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
> -fdebug-prefix-map=/build/bash-2bxm7h/bash-5.0=. -fstack-protector-strong
> -Wformat -Werror=format-security
On Sat, Nov 30, 2019, 11:24 AM Chet Ramey wrote:
>
Readline binds the terminal special characters if the variable
> `bind-tty-special-chars' is set, and it's set by default.
>
Wow, that's been in Bash a long time and I never noticed it! Thanks!
>
On Fri, Nov 29, 2019, 10:40 AM Nikolaos Kakouros wrote:
> Using bash version:
>
> GNU bash, version 5.0.11(1)-release (x86_64-pc-linux-gnu)
>
>
> Trying to map Backspace to execute a function, I try to do:
>
> bind -x '"Rubout": my_func'
>
> This, as expected, binds the string 'Rubout' to the fun
On Tue, Nov 26, 2019, 9:50 AM Алексей Шилин wrote:
> В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет:
> > You have printable characters enclosed. For example, \u. _Each_
> > sequence of unprintable characters needs to be separately enclosed
> > _without_ enclosi
On Tue, Nov 26, 2019, 5:46 AM Алексей Шилин wrote:
> В Пн, 25/11/2019 в 18:29 -0800, L A Walsh пишет:
> > Multi-byte or not, invisible characters need to be enclosed
> > as documented under 'PROMPTING':
> >
> > \[ begin a sequence of non-printing characters, which could
> >
name on it there Chet.
Anyways ... just wanted to utter a reminder that the tarball has some
restricted ./lib/glob/smatch.c in there as well as other ... stuff.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
Forwarded Message --
On Tue, Oct 22, 2019, 8:10 AM younes berramdane
wrote:
> Hello,
> I have found a seg in the history of bash while I was doing a project for
> my school,
> (Put fc -s at the last command of the history file [~/.sh_history] for
> bash posix or [~/.bash_history] for bash then launch bash and execute
On 8/29/19 2:22 PM, Chet Ramey wrote:
BASH PATCH REPORT
=
Small problem when building bash-5.0-011 out of tree is that the
file lib/glob/smatch.c is set chmod 600 and thus not readable by
the build user.
--
Dennis
XLY_CORRECT then the shell can make coffee for you. Personally I am
of the opinion that a tool in the Linux/UNIX world should do one thing
well and then stop. Otherwise we may as well just make Windows 12.
Dennis
On 7/12/19 4:45 PM, Chet Ramey wrote:
On 7/12/19 4:26 PM, Martijn Dekker wrote:
Op 12-07-19 om 21:46 schreef Dennis Clarke:
Well the man page for XPG6 bc in Solaris 10 claims :
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that
On 7/12/19 4:45 PM, Chet Ramey wrote:
On 7/12/19 4:26 PM, Martijn Dekker wrote:
Op 12-07-19 om 21:46 schreef Dennis Clarke:
Well the man page for XPG6 bc in Solaris 10 claims :
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that
On Fri, Jul 12, 2019, 3:46 PM L A Walsh wrote:
> On 2019/07/12 11:51, Eli Schwartz wrote:
>
>
> find_cmds() {
> for c in "$@"; do
> type -P $c >&/dev/null || {
> Pe "$0#$LINENO: Cannot find %s", "$c"
> exit 1; }
> alias $c=$(type -P $c);
> done
> }
>
>
>
This is a perfect
On 7/12/19 4:26 PM, Martijn Dekker wrote:
Op 12-07-19 om 21:46 schreef Dennis Clarke:
Well the man page for XPG6 bc in Solaris 10 claims :
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that affect the execution of bc: LANG, LC_ALL
On 7/12/19 3:50 PM, Chet Ramey wrote:
On 7/12/19 3:46 PM, Dennis Clarke wrote:
uh huh ...
LC_NUMERIC
This category specifies the decimal and thousands
delimiters. The information corresponding to this
category is stored in a database
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html#tag_20_09_16
"The bc utility always uses the ( '.' ) character to represent
a radix point, regardless of any decimal-point character specified as
part of the current locale.
Good catch. I went by the bc man page t
n/bc -l
a = 0,1
syntax error on line 1, teletype
a = 0.1
b = 0.01
c = a + b
c
.11
c(c)
.99395609795669685035
corv $
Well now. That is XPG6 compliant bc on Solaris 10 sparc.
It could care less about locale it seems. Nifty.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
>From the bc man page on Ubuntu:
This version of bc was implemented from the POSIX P1003.2/D11 draft and
contains several differences and extensions rela‐
tive to the draft and traditional implementations.
and
LANG environment
This version does not conform to the POSIX
On Sun, Jun 23, 2019, 7:18 AM bitfreak25 wrote:
> On Sun, 23 Jun 2019 06:04:29 -0500
> Dennis Williamson wrote:
>
> > On Sun, Jun 23, 2019, 5:31 AM bitfreak25 wrote:
> >
> > > OS: Arch Linux 5.1.12-arch1-1-ARCH (tty1)
> > > Bash-Version: 5.0.7(1)-releas
On Sun, Jun 23, 2019, 5:31 AM bitfreak25 wrote:
> OS: Arch Linux 5.1.12-arch1-1-ARCH (tty1)
> Bash-Version: 5.0.7(1)-release
> localization: de_DE.UTF-8 UTF-8
> keymap: de-latin1-nodeadkeys
>
> Description:
> The command "cat /etc/localtime" was called in a tty-terminal. After that
> some charact
On 5/25/19 5:55 PM, Chet Ramey wrote:
On 5/25/19 2:06 PM, Dennis Clarke wrote:
On any Solaris boxen there really isn't O_CLOEXEC so even after a neat
compile and test the install will blow up.
http://lists.gnu.org/archive/html/bug-bash/2019-02/msg00167.html
You can use the patch there
0-007_SunOS5.10_sparc64vii+.002/examples/loadables'
gmake: [Makefile:824: install] Error 2 (ignored)
beta #
Yeah well. Okay.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On Tue, May 21, 2019 at 3:04 AM Henning wrote:
> On 20/05/2019 15:38, Chet Ramey wrote:
> > On 5/19/19 10:43 AM, Henning wrote:
> >> I don't like to have dozens of key bindings I never use. Currently I
> >> am issuing lots of lots of bind -r/-u commands to get rid of the
> >> default bindings. Th
On Sat, May 4, 2019, 3:39 PM wrote:
> 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_V
has left the building and all the great Solaris guys were
taken to the chemical shed and shot. Oracle Solaris is a dead product.
Good luck getting the userbase back. Oracle did *everything* to kill it.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On 4/22/19 1:26 PM, Greg Wooledge wrote:
On Mon, Apr 22, 2019 at 01:21:38PM -0400, Dennis Clarke wrote:
I don't think bash 5 has hit Debian sid yet.
It's not only in sid; it's also in buster.
Here's the relevant excerpt from the changelog:
bash (5.0-1) unstable; urgency=
On 4/22/19 1:01 PM, Greg Wooledge wrote:
On Mon, Apr 22, 2019 at 12:54:28PM -0400, Dennis Clarke wrote:
I see these are all published in the gnu ftp server :
https://ftp.gnu.org/pub/gnu/bash/bash-5.0-patches/
So I will try again from the sources but am curious if there is a definitive
I will try again from the sources but am curious if there is a
definitive list of dependencies that bash 5.0.7 will need/want ?
Dennis
On Sun, Feb 17, 2019, 6:01 PM L A Walsh
>
> On 2/17/2019 2:19 PM, Dennis Williamson wrote:
> >
> > So it really is a bug of some sort, not that I use BASH ALIASES
> > for anything. Was going to, but ... and you're right, lots of
> &
On Sun, Feb 17, 2019, 3:10 PM L A Walsh
>
> On 2/16/2019 4:57 AM, Robert Elz wrote:
> > Date:Fri, 15 Feb 2019 22:21:25 -0800
> > From:L A Walsh
> > Message-ID: <5c67abe5.1030...@tlinx.org>
> >
> > | Thought about thatrestarted a fresh shell. Same same.
> >
On Fri, Feb 15, 2019, 10:46 PM L A Walsh
> I printed the various declares using:
>
> declare -p |& more
>
> One of the early entries is:
>
> declare -A BASH_ALIASES=()
>
> Yet if I type 'alias |& wc, I see 56 lines starting with alias.
>
> I _thought_ BASH_ALIASES was suppose to hold the aliases
>
etc
Most likely we need a check for the existence of O_CLOEXEC during the
configure stage and then adjust ./examples/loadables/Makefile.in to
remove or skip the example file.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On Fri, Jan 25, 2019, 9:51 PM Robert White On 1/22/19 10:23 PM, Chet Ramey wrote:
> > On 1/22/19 3:32 PM, Robert White wrote:
> >> Howdy,
> >>
> >> The following cannot work because, for some reason, the array subscript
> >> parser insists on doing math on array indices even when the array is
> >>
On Tue, Jan 8, 2019, 3:10 PM Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -fstack-protector -Wno-parentheses -Wno-format-security
> uname output: Linux bongo 2.6.32-042stab134.8 #1 SMP Fri Dec 7 17:16:09
>
On Sat, Jan 5, 2019, 4:05 PM Robert Hailey
> To the most excellent bash maintainers:
>
> I have found, what I consider to be a bug, in the following version of
> bash:
> * bash-4.4.23-1.fc28.x86_64
>
> It is related to this error message:
> * "return: can only `return' from a function or sourced s
On Tue, Sep 25, 2018, 7:17 PM L A Walsh wrote:
> It struck me as it might be convenient if 'shift' could take an optional
> arrayname as an argument. Would that be possible or would it cause some
> incompatibility?
>
> i.e.
>
> > set one two three four five
> > dcl -a ARGV=("$@")
> > shift AR
On Sat, Mar 24, 2018, 12:23 PM Dennis Williamson <
dennistwilliam...@gmail.com> wrote:
>
>
> On Sat, Mar 24, 2018, 11:45 AM Clark Wang wrote:
>
>> Hi Chet,
>>
>> Today I compiled bash5 (using default configuration) from the devel branch
>> (f602026a0ce
On Sat, Mar 24, 2018, 11:45 AM Clark Wang wrote:
> Hi Chet,
>
> Today I compiled bash5 (using default configuration) from the devel branch
> (f602026a0ce - commit bash-20180316 snapshot) on macOS and found it breaks
> one of my rc files. After some time of debugging I have the following
> minimal
On Nov 5, 2017 7:05 PM, "積丹尼 Dan Jacobson" wrote:
$ help shopt
shopt: shopt [-pqsu] [-o] [optname ...]
Set and unset shell options.
Change the setting of each shell option OPTNAME. Without any option
arguments, list all shell options with an indication of whether or not
each
is
subshell line.
When the variable s is set to readonly the script does not exit and echoes
"abc":
#!/bin/bash
set -e
readonly s=$(false)
echo "abc"
This behavior is unexpected. I could reproduce the bug
on ubuntu 16.04 with bash version 4.3-14ubuntu1.1
Regards,
Dennis Kuhn
s
On Dec 30, 2016 11:20 PM, "Peter & Kelly Passchier" <
peterke...@passchier.net> wrote:
Thanks Dennis and Grisha! I understand.
I had thought that every line that is piped into bash is it's own shell
alignment, but I understand it's more like sourcing, so these wo
On Tue, Dec 6, 2016 at 4:09 PM, L A Walsh wrote:
>
> Is there a way, in bash, to filter stderr and let the
> filtered result continue on stderr with the original
> stdout being output on stdout?
>
> with prog being the program to filter, and RE_filt being the
> filtering expression, conceptually,
On Sun, Nov 27, 2016 at 7:25 PM, Robert Durkacz
wrote:
> Has thought been given, over the years, to extending bash to do
> what make does, in the obvious way that I am about to describe?
>
> It would be a matter of having chosen build commands do nothing if their
> outputs are newer than their in
On Aug 13, 2016 6:36 AM, "L. A. Walsh" wrote:
>
> I was looking at how the 'ldd' command(bash script) on my system and
> came across the code usage:
>
> for file do ## about line 138 in my version
> ...
> case $file in
> */* :
> ;;
> *) file=./$file
> ;;
> esac
> ...
> done
>
On Jun 2, 2016 11:25 AM, "Charles T. Smith"
wrote:
>
> Hello,
>
> I moved from ubuntu 10.04 to 14.04 and now readline usually doesn't
refresh
> my command line when scrolling through my history - the last tokens are
often
> not shown until I move the cursor there. Is that due to a change in bash?
$ type -a ls
ls is /bin/ls
$ # ls tab completion includes ls
$ ls foo
foo
$ EXECIGNORE=/bin/ls
$ type -a ls
bash: type: ls: not found
$ # ls tab completion does not include ls
$ ls foo
foo
$ /bin/ls foo
foo
So ls is still executed despite the setting. I tried the same with
/usr/bin/find and got th
>
>
>
Either EXECIGNORE should block execution or type -a should indicate that
its argument matches a pattern in EXECIGNORE.
I vote for the latter so a user isn't surprised by execution without a
means to identify where it came from. I would also prefer another name. If
the purpose is to reduce co
On Mon, Jan 4, 2016 at 4:35 PM, Dennis Williamson <
dennistwilliam...@gmail.com> wrote:
>
>
> On Mon, Jan 4, 2016 at 4:05 PM, Dennis Williamson <
> dennistwilliam...@gmail.com> wrote:
>
>>
>>
>> On Mon, Jan 4, 2016 at 3:07 PM, Eduardo A. Bustamante Lóp
On Mon, Jan 4, 2016 at 4:05 PM, Dennis Williamson <
dennistwilliam...@gmail.com> wrote:
>
>
> On Mon, Jan 4, 2016 at 3:07 PM, Eduardo A. Bustamante López <
> dual...@gmail.com> wrote:
>
>> Take into account that many options have been provided (history -d, the
On Mon, Jan 4, 2016 at 3:07 PM, Eduardo A. Bustamante López <
dual...@gmail.com> wrote:
> Take into account that many options have been provided (history -d, the
> space
> prefix, even editing .bash_history yourself).
>
> But you request a single key stroke to do this... why?
>
> If you enter a pa
1 - 100 of 237 matches
Mail list logo
