Re: interactive shell detection in shrc

2024-09-26 Thread Robert Elz
Date:Fri, 27 Sep 2024 01:48:13 +0200 From:Steffen Nurpmeso Message-ID: <20240926234813.hgDdmZkJ@steffen%sdaoden.eu> | I changed it to (but tab indent; private credits to you..) | | if [ -z "$___SHRC" ]; then | if [ "$-" != "${-%i*}" ] || [ "$-" != "${-%m

Re: interactive shell detection in shrc

2024-09-26 Thread Steffen Nurpmeso
Steffen Nurpmeso wrote in <20240926233234.MwKivWJi@steffen%sdaoden.eu>: |Greg A. Woods wrote in | : ||At Tue, 24 Sep 2024 00:56:40 +0200, Steffen Nurpmeso \ ... ||To work around this I do the following: || || _interactive=false || case "$-" in || *i*) || _interactive=true || ;; || e

Re: interactive shell detection in shrc

2024-09-26 Thread Steffen Nurpmeso
Hello. Greg A. Woods wrote in : |At Tue, 24 Sep 2024 00:56:40 +0200, Steffen Nurpmeso \ |wrote: |Subject: Re: interactive shell detection in shrc |> |> case ${-} in |> *i*|*m*) # {{{ |> ... |> esac | |I'm very curious: why did you include "m" in that te

Re: interactive shell detection in shrc

2024-09-26 Thread Robert Elz
Date:Fri, 27 Sep 2024 01:32:34 +0200 From:Steffen Nurpmeso Message-ID: <20240926233234.MwKivWJi@steffen%sdaoden.eu> | Yes i am afraid of shell field splitting and expansion, and i do | not understand why eg | | a() { | echo $#,1="$1"/$1,2="$2"/$

Re: interactive shell detection in shrc

2024-09-26 Thread RVP
On Fri, 27 Sep 2024, Steffen Nurpmeso wrote: Yes i am afraid of shell field splitting and expansion, and i do not understand why eg a() { echo $#,1="$1"/$1,2="$2"/$2,3="$3"/$3,4="$4"/$4,5="$5"/$5,6="$6"/$6,'*'="$*"/$*,'@'="$@",$@ echo $#,1= "$1" , $1 , 2= "$2" , $2 , 3= "$3"

Re: interactive shell detection in shrc

2024-09-26 Thread Robert Elz
Date:Thu, 26 Sep 2024 15:16:39 -0700 From:"Greg A. Woods" Message-ID: | I'm very curious: why did you include "m" in that test? I wondered about that as well. But I suspect you have supplied the answer. | I do note the following from the bosh(1) manual: |

Re: sh(1) read: add LINE_MAX safeguard and "-n" option

2024-09-26 Thread Robert Elz
Date:Tue, 24 Sep 2024 17:30:42 +0200 From:tlaro...@kergis.com Message-ID: | Furthermore the continuation test on: | | if (c != '\n') /* \ \n is always just removed */ | goto wdch; | | seems wrong. Shouldn't it be?: | |

Re: interactive shell detection in shrc

2024-09-26 Thread Greg A. Woods
At Tue, 24 Sep 2024 00:56:40 +0200, Steffen Nurpmeso wrote: Subject: Re: interactive shell detection in shrc > > case ${-} in > *i*|*m*) # {{{ > ... > esac I'm very curious: why did you include "m" in that test? I do note the following from the bosh(1) manual:

postinstall vs. obsolete libs

2024-09-26 Thread Valery Ushakov
Martin's bin/58697 made me look at postinstall again, which reminded me that _obsolete_libs has an awk script that is unnecessarily opaque (with variable names like "res", "result", "line", a function "digit" that actually returns a number, not necessarily single-digit, etc). Since I had to dig int

Re: Symbols from new jemalloc not found

2024-09-26 Thread Christos Zoulas
On 2024-09-26 3:19 am, Rin Okuyama wrote: Hi, It seems due to our local change: https://mail-index.netbsd.org/source-changes/2019/03/12/msg104255.html http://cvsweb.netbsd.org/bsdweb.cgi/src/external/bsd/jemalloc/include/jemalloc/jemalloc.h.diff?r1=1.5&r2=1.6&f=h lost during merge for 5.3.

Re: Symbols from new jemalloc not found

2024-09-26 Thread Ryo ONODERA
Hi, Taylor R Campbell writes: >> Date: Thu, 26 Sep 2024 12:48:12 +0900 >> From: Ryo ONODERA >> >> On NetBSD/amd64-current of today with new jemalloc, >> linking to jemalloc always returns undefined references. >> This problem causes build failures of pkgsrc/www/firefox >> and misc/libreoffice

Re: Symbols from new jemalloc not found

2024-09-26 Thread Taylor R Campbell
> Date: Thu, 26 Sep 2024 12:48:12 +0900 > From: Ryo ONODERA > > On NetBSD/amd64-current of today with new jemalloc, > linking to jemalloc always returns undefined references. > This problem causes build failures of pkgsrc/www/firefox > and misc/libreoffice at least. > [...] > $ gcc test.c -ljemal

Re: Symbols from new jemalloc not found

2024-09-26 Thread Ryo ONODERA
Hi, Rin Okuyama writes: > Hi, > > It seems due to our local change: > > https://mail-index.netbsd.org/source-changes/2019/03/12/msg104255.html > > http://cvsweb.netbsd.org/bsdweb.cgi/src/external/bsd/jemalloc/include/jemalloc/jemalloc.h.diff?r1=1.5&r2=1.6&f=h > > lost during merge for 5.3. I ha

PATH_OPT: allowing to search for qualified utilities

2024-09-26 Thread tlaronde
[was also: sh(1): POSIX "Command Search and Execution"] Please note that this is not an "official" proposal. It just a modification that I implement and could be picked up by others. In a nutshell, I want to add the possibility to "qualify" an utility name, with a name composed with components se

Re: Symbols from new jemalloc not found

2024-09-26 Thread Rin Okuyama
Hi, It seems due to our local change: https://mail-index.netbsd.org/source-changes/2019/03/12/msg104255.html http://cvsweb.netbsd.org/bsdweb.cgi/src/external/bsd/jemalloc/include/jemalloc/jemalloc.h.diff?r1=1.5&r2=1.6&f=h lost during merge for 5.3. Thanks, rin P.S. Good news is that fallout