Re: alias problem -- conflict found

2019-07-09 Thread Eli Schwartz
On 7/9/19 11:24 PM, L A Walsh wrote: > On 2019/07/09 06:21, Greg Wooledge wrote: >> On Mon, Jul 08, 2019 at 03:30:47PM -0700, L A Walsh wrote: >> >>> alias my='declare ' Export='\-x ' Map='-A ' Int='-i ' >>> >> Because the dead horse is still equine-shaped, I will beat upon it some >> mo

Re: alias problem -- conflict found

2019-07-09 Thread L A Walsh
On 2019/07/09 06:21, Greg Wooledge wrote: > On Mon, Jul 08, 2019 at 03:30:47PM -0700, L A Walsh wrote: > >> alias my='declare ' Export='\-x ' Map='-A ' Int='-i ' >> > Because the dead horse is still equine-shaped, I will beat upon it some > more: this is utterly horrible coding and you s

Re: continued alias problem -- some work, some don't, why?

2019-07-09 Thread L A Walsh
On 2019/07/09 06:40, Chet Ramey wrote: > >> With these aliases: >> alias my='declare ' Export='-x ' Map='-A ' Int='-i ' >> >> my Export Map Int e=([one]=1) >> -bash: declare: `-x': not a valid identifier >> -bash: declare: `-A': not a valid identifier >> -bash: declare: `-i': not a valid ide

Re: built-in printf %f parameter format depend on LC_NUMERIC

2019-07-09 Thread Chet Ramey
On 7/9/19 3:39 PM, Léa Gris wrote: > I note that Bash's built-in printf %f or %d does not honour LC_NUMERIC > thousands_sep=" " when dealing with integers. > > $ printf '%f\n' '1 000 000' > bash: printf: 1 000 000: nombre non valable > 1,00 > > locale -ck thousands_sep > LC_NUMERIC > thousan

Re: built-in printf %f parameter format depend on LC_NUMERIC

2019-07-09 Thread Léa Gris
Le 09/07/2019 à 20:28, Chet Ramey écrivait : On 7/9/19 11:26 AM, lea.g...@noiraude.net wrote: Bash Version: 5.0 Patch Level: 3 Release Status: release Description: When formatting floating point numbers in Bash's built-in printf with %s, the argument format depends on the LC_

Re: built-in printf %f parameter format depend on LC_NUMERIC

2019-07-09 Thread Dennis Williamson
>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

Re: continued alias problem -- some work, some don't, why?

2019-07-09 Thread L A Walsh
On 2019/07/09 06:40, Chet Ramey wrote: > I can't reproduce this. > Yeah, I'm running Bash 4.4.12, and wanted to try 5.x before submitting this but have continued to hit a few snags in doing that. Sigh.

Re: built-in printf %f parameter format depend on LC_NUMERIC

2019-07-09 Thread Chet Ramey
On 7/9/19 11:26 AM, lea.g...@noiraude.net wrote: > Bash Version: 5.0 > Patch Level: 3 > Release Status: release > > Description: > When formatting floating point numbers in Bash's built-in > printf with %s, the argument format depends on the LC_NUMERIC > environment varia

Re: file access time and file modification time

2019-07-09 Thread Chet Ramey
On 7/9/19 12:12 PM, k...@plushkava.net wrote: >> The code just returns (atime <= mtime), and has since 1997. It uses the >> st_atime and st_mtime fields. I should update it to use timespecs if >> they're available, and (mtime > atime) might work closer to your >> expectations. >> >> After the call

built-in printf %f parameter format depend on LC_NUMERIC

2019-07-09 Thread lea . gris
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 -Wformat -Werror=format-security -Wall -Wno-parentheses -Wno-format-security uname o

Re: file access time and file modification time

2019-07-09 Thread
On Tue, 9 Jul 2019 10:48:32 -0400 Chet Ramey wrote: > On 7/9/19 6:16 AM, k...@plushkava.net wrote: > > >> Did you have a look at the 'conditional.sh' script too? Looks like the > >> '-N' switch compares only the integer part of the timestamp seconds. > > > > The stat structure supports timesta

Re: file access time and file modification time

2019-07-09 Thread Chet Ramey
On 7/9/19 6:16 AM, k...@plushkava.net wrote: >> Did you have a look at the 'conditional.sh' script too? Looks like the '-N' >> switch compares only the integer part of the timestamp seconds. > > The stat structure supports timestamp fields of nanosecond granularity since > POSIX.1-2008, so it s

Re: building bash 5.x problems+coredumps

2019-07-09 Thread Chet Ramey
On 7/8/19 6:43 PM, L A Walsh wrote: > This hasn't worked for me yet, that I remember. Some of itt may be in some > library I'm linking, but not sure what might be causing the problem. > > In making bash with the 7 patches, I get various warnings and a coredump: Why not build with the default bui

Re: continued alias problem -- some work, some don't, why?

2019-07-09 Thread Chet Ramey
On 7/8/19 6:30 PM, L A Walsh wrote: > That's what I am wanting, But trying various aliases, I'm not getting > consistent results: > With these aliases: > alias my='declare ' > alias Export='-x ' > alias Map='-A ' > alias Int='-i ' > > my Export Map Int e=([one]=1) > -bash: declare: `-x': not

Re: continued alias problem -- some work, some don't, why?

2019-07-09 Thread Greg Wooledge
On Mon, Jul 08, 2019 at 03:30:47PM -0700, L A Walsh wrote: > alias my='declare ' > alias Export='-x ' > alias Map='-A ' > alias Int='-i ' > > my Export Map Int e=([one]=1) > -bash: declare: `-x': not a valid identifier > -bash: declare: `-A': not a valid identifier > -bash: declare: `-i': not

Re: file access time and file modification time

2019-07-09 Thread
Hi Mischa, On Tue, 09 Jul 2019 09:05:45 +0200 Mischa Baars wrote: > Hi Kerin, > > That indeed solves the problem in 'accesstime.sh', although I would recommend > some sort of reference from the bash manpage to the mount manpage. > > Did you have a look at the 'conditional.sh' script too? Look

Re: building bash 5.x problems+coredumps

2019-07-09 Thread L A Walsh
On 2019/07/08 18:55, Eduardo Bustamante wrote: > On Mon, Jul 8, 2019 at 3:44 PM L A Walsh wrote: > >> This hasn't worked for me yet, that I remember. Some of itt may be in some >> library I'm linking, but not sure what might be causing the problem. >> > > Can you provide more informati