cmd completion.. normal that it doesnt complete dirs when cmds are available ?

2021-11-12 Thread Alex fxmbsw7 Ratchev
i have a dir with some xbl*/ dirs and few xbl* commands ( via $PATH ) i tried there xbl,tabtab but it only completed cmds is this desired ? snip 2021-11-12 , Fri Nov , 18:17:56.530771 == 1636741076.530771 # root:0:0 # @ /dev/pts/1 ( 0 ) localhost -> /root/e xblsslfile/ xblfiletransfer/

Re: bash conditional expressions

2021-11-12 Thread Andreas Schwab
FILE1 -nt FILE2 True if file1 is newer than file2 (according to modification date). Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: bash conditional expressions

2021-11-12 Thread Greg Wooledge
On Fri, Nov 12, 2021 at 02:21:15PM +0100, Mischa Baars wrote: > It is how my makefiles work :) Then they aren't Makefiles. They're BaarsBuilder files or something. > Do you realize how much time it takes to load the stat executable on all > source files [...] What the hell. You're writing

Re: bash conditional expressions

2021-11-12 Thread Michael J. Baars
Yeeh, that's funny indeed :) Now this: time ( test2Y=$(stat -c %Y test2); for (( i=0; i<1024; i++ )); do if (( $(stat -c %Y test1) < ${test2Y} )); then echo >> /dev/null; else echo >> /dev/null; fi; done; ); real0m4.503s user0m1.048s sys 0m3.240s time ( for (( i=0; i<1024; i++

Re: bash conditional expressions

2021-11-12 Thread Lawrence Velázquez
On Fri, Nov 12, 2021, at 4:36 AM, Mischa Baars wrote: > Using Fedora 32 (bash 5.0.17) this returns a true, while on Fedora 35 (bash > 5.1.8) this returns a false: > touch test; if [[ -N test ]]; then echo true; else echo false; fi; > > [...] > > As I understand it, -N stands for NEW and therefore

Re: coproc does not work with a lower case variable name

2021-11-12 Thread Chet Ramey
On 11/11/21 11:09 PM, g...@as.lan wrote: Bash Version: 5.1 Patch Level: 8 Release Status: release Description: coproc gives a syntax error if I try to use it with a lower case variable name and a compound command: bash: syntax error near unexpected token `}' bash:

Re: coproc does not work with a lower case variable name

2021-11-12 Thread Alex fxmbsw7 Ratchev
never seen, and i never coproc uppercase i suspect your bc is a half complex alias On Fri, Nov 12, 2021, 15:29 wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -O2 -Wall -D_FORTIFY_SOURCE=2

coproc does not work with a lower case variable name

2021-11-12 Thread gd
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g

coproc does not work with a lower case variable name

2021-11-12 Thread Grósz Dániel
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong - funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection - Werror=return-type -flto=auto -g

Re: bash conditional expressions

2021-11-12 Thread Ilkka Virta
On Fri, Nov 12, 2021 at 3:22 PM Mischa Baars wrote: > It is how my makefiles work :) > Sounds to me you're not using Make, but some self-made tool, so the files you have would be more properly called build scripts or whatever, and not makefiles.

Re: bash conditional expressions

2021-11-12 Thread Alex fxmbsw7 Ratchev
i suggest a bash only makefile script then that spawns few instances of whatever only, i do such whatever overall systems a find printf to comparement is fairly fast, to estimate new files then a good gcc in one cmd done On Fri, Nov 12, 2021, 14:22 Mischa Baars wrote: > Hi Greg, > > It is how

Re: bash conditional expressions

2021-11-12 Thread Mischa Baars
Hi Greg, It is how my makefiles work :) Do you realize how much time it takes to load the stat executable on all source files and object files? Conditional expressions are already in memory. I prefer using the mtime field, the atime field and conditional expressions. Mischa. On Fri, Nov 12,

Re: bash conditional expressions

2021-11-12 Thread Greg Wooledge
On Fri, Nov 12, 2021 at 10:36:01AM +0100, Mischa Baars wrote: > All of my makefiles only compile source files and link object files that > are NEW, as in the modification timestamp is newer than OR EQUAL TO the > access timestamp, That's not how Makefiles work. Makefiles compare the mtimes of

Re: bash conditional expressions

2021-11-12 Thread Oğuz
> I agree that the `mtime >= atime' behavior should be restored; ``file > is newly created or was accessed since last modified'' is not a useful > information, nor is the opposite. Or, -N can be split into -A (atime > mtime) and -M (mtime > atime), and everyone would be happy :D

Re: bash conditional expressions

2021-11-12 Thread Oğuz
On Fri, Nov 12, 2021 at 12:44 PM Mischa Baars wrote: > Using Fedora 32 (bash 5.0.17) this returns a true, while on Fedora 35 (bash > 5.1.8) this returns a false: > touch test; if [[ -N test ]]; then echo true; else echo false; fi; This seems to have changed as a result of this bug report:

Re: bash conditional expressions

2021-11-12 Thread Andreas Schwab
On Nov 12 2021, Mischa Baars wrote: > Using Fedora 32 (bash 5.0.17) this returns a true, while on Fedora 35 (bash > 5.1.8) this returns a false: > touch test; if [[ -N test ]]; then echo true; else echo false; fi; What does `stat test' print respectively? Andreas. -- Andreas Schwab,

bash conditional expressions

2021-11-12 Thread Mischa Baars
Hi All, All of my makefiles only compile source files and link object files that are NEW, as in the modification timestamp is newer than OR EQUAL TO the access timestamp, such that when I include a new source file into a project or produce a new object file during compilation of the project, it