Re: i cant see whats the issue, .. ps1 + propt command + date

[Alex fxmbsw7 Ratchev]

i removed the aliases ending eol and added space ending
didnt change much
but i came to the idea due to other bugs bash -x
and i see it sets it but then its empty

++ prptnow=1632594230.535965
+++ declare -p IFS
++ __savedIFS='declare -- IFS=$'\'' \t\n'\'''
++ IFS=.
++ prptnow2='(1632594230.535965)'
++ eval 'declare -- IFS=$'\'' \t\n'\'''
+++ declare -- 'IFS=
'
+++ prptrecents
+++ prptrecents2.gawk /dev/fd/63
++++ ls --quoting-style=shell-escape -AcF --
++ dfslist='.xbl-states/ bash/ bl5/ .ssh/
.bash_history .viminfo .profile .bashrc .lesshst .vimrc bl5.tgz
desk@ '
++ printf -v prptnow3 '%(%F , %T)T'
++ prptnow3+=.
1 exit // 0 old , static

2021-09-25 , 20:23:50. == 1632594230.535965
# root:0:0 # @ /dev/pts/1 ( 0 ) -> /root

.xbl-states/ bash/ bl5/ .ssh/
.bash_history .viminfo .profile .bashrc .lesshst .vimrc bl5.tgz
desk@

On Sat, Sep 25, 2021 at 7:43 PM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com> wrote:
>
> so i havent yet removed the ending newline in the aliases, but now i
> got my laptop from repair back, updated, blabla, and tried the same
> again on the laptop not on the arm phone, ... and same error was still
> there
>
> short conclusion
> i have, $prptnow , $prptnow2 and $prptnow3
> first and third are visible, second not
> i suppose something aliases declare could be wrong here
>
> i tried, declare -p prptnow{,2,3} and 2 was not there 1 and 3 were tho
>
> chet, i told you about not found bugs of lots, this is one
> what i meant with not reported bugs is really bugs but it was years
> ago where i didnt feel comfortable or didnt know about the mailing
> list
>
> since then a few bugs appeared
> this one is a big one that i can report
>
> conclusion
>
> i have aliases saveIFS and restoreIFS
> i do var1=bla saveIFS IFS=... var2=( $var1 ) restoreIFS
> then i do printf -v var3 with var2 as arg but seemfully it yet there
> didnt get set
> i do that in PROMPT_COMMAND
> and in PS1 i use $var3 and wanted to also have ${var2[1]} somewhere
>
> please if someone could take a look at 'as is', the archive is attached
>
> xbl stands for xmb bash linker
> usage is
>
> . xbl.bash extra/xmb_ps1_prompt
>
> to load xbl + prompt
>
> best hopes and wishes, xmb
>
> please also understand,workarounds such as ''bugfix of not setting
> IFS' etc i cannot use, i can only use 100% working, not 'uh it doesnt
> work so..'
>
> On Thu, Sep 23, 2021 at 3:42 PM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com> 
> wrote:
> >
> > as for the prptnow2 gone
> > im still trying to remove the \n eol in files, just began a minuseol .gawk
> >
> > On Thu, Sep 23, 2021, 15:39 Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com> wrote:
> >>
> >> the bash cmdline is recognition system
> >>
> >> cmd arr=( bla ) .. syntax err
> >> cmd=input arr=( bla ) .. works
> >>
> >> so the alias is what im saying..
> >>
> >> alias b=b=2
> >> a=1 b a=( 3 )
> >>
> >> 0 exit ..
> >>
> >> On Thu, Sep 23, 2021, 15:35 Greg Wooledge <greg@wooledge.org> wrote:
> >>>
> >>> On Thu, Sep 23, 2021 at 03:17:41PM +0200, Alex fxmbsw7 Ratchev wrote:
> >>> > ill test tho
> >>> > in my logic the newlines shouldnt matter
> >>>
> >>> Seriously, I DEMONSTRATED why they matter.
> >>>
> >>> In a normal command, in the absence of what I'm going to call "alias
> >>> insanity", you get this:
> >>>
> >>> unicorn:~$ string=value foo array=( $SHELL )
> >>> bash: syntax error near unexpected token `('
> >>>
> >>> But you're claiming that if "foo" is an alias with certain 
> >>> characteristics,
> >>> then you don't get a syntax error.  I have no idea what you're doing or
> >>> how it works.
> >>>