.. regarding a $notset <( .. wouldnt that display in set -x on that line,
rather when the cat or gawk is ran
On Tue, Nov 2, 2021, 06:03 Alex fxmbsw7 Ratchev wrote:
> i dont see the 63, its inside that tho
>
> i post the code, as i saw its fairly short, 'xbl' file
> the tgz with required awks
i dont see the 63, its inside that tho
i post the code, as i saw its fairly short, 'xbl' file
the tgz with required awks and support files is also sent
but anyway in the xbl the affected part are the cat or kopi.gawk if parts
inside $xblpp <( here )
$xblpp is either cat or .
cat for 'display me
to answer around what was written, i dont have a cat alias
but what mr andreas wrote seems much similiar to what i do, process sub..
ill check the vars carefully but i dont get it fully
but, on your all tries to produce command not found, can u set -x the
tries, .. in mine it shows cat ...
Date:Mon, 1 Nov 2021 16:31:51 -0400
From:Greg Wooledge
Message-ID:
| unicorn:~$ alias cat=' '
no I meant
alias cat="' '"
though which quote in inside doesn't matter,
and using \ quoting is possible too
nx$ alias xx='\ '
jinx$ xx
-bash: : command not
As you know, POSIX requires tilde expansion following an an unquoted colon in
an assignment [1]. A bug was reported [2] against bash 5.1-alpha that the
tildes in
$ echo foo=~:~
foo=~:~
should not be expanded in POSIX mode, because this is not an assignment. That
was fixed in 5.1-beta.
On Tue, 2 Nov 2021 at 02:37, Rikke Rendtorff wrote:
>
> I'm very new to linux
[...]
> I went to the https://linuxmint.com community website and joined their IRC
> chat to see if they had an explanation and they told me it may be a bug,
> since they couldn't reproduce it for other commands.
>
>
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
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
> |
> | Because this is you, I can't be sure whether you
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
> |
> | Because this is you, I can't be sure whether you
Date:Mon, 1 Nov 2021 12:03:48 -0400
From:Greg Wooledge
Message-ID:
| > bash: : command not found
| > bash: : command not found
|
| Because this is you, I can't be sure whether you are correctly pasting
| the output from your terminal into email,
Actually,
On Mon, Nov 01, 2021 at 06:34:45PM +0100, Alex fxmbsw7 Ratchev wrote:
> the hd one gives me, i think its the only two cat cases :
>
> 0410 0a 6d 76 20 2d 2d 20 22 24 74 74 22 20 22 24 74 |.mv -- "$tt"
> "$t|
> 0420 74 74 22 0a 0a 24 78 62 6c 70 70 20 3c 28 0a 20 |tt"..$xblpp
> <(. |
to add the small info, its from phone and wsl, no pure linix anymore
but on windows wsl i only vim, no this
On Mon, Nov 1, 2021, 18:34 Alex fxmbsw7 Ratchev wrote:
> the hd one gives me, i think its the only two cat cases :
>
> 0410 0a 6d 76 20 2d 2d 20 22 24 74 74 22 20 22 24 74 |.mv --
On 11/1/21 11:26 AM, Chet Ramey wrote:
> On 10/31/21 12:06 PM, Roger Morris wrote:
>> Thanks for the reply. Though POSIX may allow this, still the last
>> line of the following example is rather unexpected behavior
>>
>> $
>> $ echo echo MY LOCAL tmp/date SCRIPT > tmp/date
>> $ chmod +x tmp/date
the hd one gives me, i think its the only two cat cases :
0410 0a 6d 76 20 2d 2d 20 22 24 74 74 22 20 22 24 74 |.mv -- "$tt"
"$t|
0420 74 74 22 0a 0a 24 78 62 6c 70 70 20 3c 28 0a 20 |tt"..$xblpp
<(. |
0430 69 66 20 5b 5b 20 2d 73 20 24 74 20 5d 5d 20 3b |if [[ -s $t ]]
;|
On Mon, Nov 01, 2021 at 05:29:08PM +0100, Alex fxmbsw7 Ratchev wrote:
> how, or what, is a non breaking space
https://en.wikipedia.org/wiki/Non-breaking_space
In HTML it's represented by
In Unicode it's code point U+00A0
In UTF-8 it's encoded as 0xc2 0xa0
On my system, with Debian's X
how, or what, is a non breaking space
to try your command for a cmd not found
i identified the file is in the main script sourced
got a suggestion for a hexdump cmd ? i know of none with args
On Mon, Nov 1, 2021, 17:05 Alex fxmbsw7 Ratchev wrote:
> please give me half a day to study that
please give me half a day to study that english
gg =)
On Mon, Nov 1, 2021, 17:04 Greg Wooledge wrote:
> On Mon, Nov 01, 2021 at 04:53:12PM +0100, Alex fxmbsw7 Ratchev wrote:
> > coming from non -x :
> >
> > . ~/.bashrc
> >
> > bash: : command not found
> > bash: : command not found
>
> Because
On Mon, Nov 01, 2021 at 04:53:12PM +0100, Alex fxmbsw7 Ratchev wrote:
> coming from non -x :
>
> . ~/.bashrc
>
> bash: : command not found
> bash: : command not found
Because this is you, I can't be sure whether you are correctly pasting
the output from your terminal into email, or retyping it
i use a bootstrap thingy that i source via .bashrc and .profile
i have a shell open it sourced np'ly, but then now i tried reloading via '.
~/.bashrc' but it says on two commands not found
its the xbashlink i dont wish to repost cause no good replies to so, but
the set -x is
it says
cat
On Mon, Nov 01, 2021 at 04:23:32PM +0100, Rikke Rendtorff wrote:
> I'm very new to linux, so I apologize if I'm reporting a non-bug.
>
> I wanted to do this: date > `date +"%Y-%m-%d"`.txt to put the date into a
> file called 2021-10-16.txt
>
> But I accidentally forgot the backticks, so it
I'm very new to linux, so I apologize if I'm reporting a non-bug.
I wanted to do this: date > `date +"%Y-%m-%d"`.txt to put the date into a
file called 2021-10-16.txt
But I accidentally forgot the backticks, so it became date > date
+"%Y-%m-%d".txt. And it created a file called "date" and it put
On 10/31/21 12:06 PM, Roger Morris wrote:
> Thanks for the reply. Though POSIX may allow this, still the last
> line of the following example is rather unexpected behavior
>
> $
> $ echo echo MY LOCAL tmp/date SCRIPT > tmp/date
> $ chmod +x tmp/date
> $
> $ PATH=.:/bin
> $ date
> Sun 31 Oct 2021
On Mon, Nov 01, 2021 at 03:42:11PM +0700, Robert Elz wrote:
> ...
> which is how it should be - the hash table is intended to speed PATH
> searches for commonly used commands, nothing should be found there
> which wouldn't be found from a PATH search - with the sole exception
> that the shell
On 11/1/21 4:42 AM, Robert Elz wrote:
> I agree, this looks to be broken in bash - "command -p cmd" is (logically)
>
> oldpath=$PATH
> PATH=/standard:/system:/path
> cmd
> PATH=$oldpath
>
> and should act (as if) that way.
Clearly that's not the case. None of the side
On Mon, Nov 1, 2021 at 1:33 PM Mike Jonkmans wrote:
> Temporarily using a default value of PATH is akin to modifying it.
But they are not the same thing, and you know this. The standard is
neither on your side nor mine.
On Mon, Nov 01, 2021 at 12:21:41PM +0300, Oğuz wrote:
> On Mon, Nov 1, 2021 at 10:58 AM Mike Jonkmans wrote:
> > This wording does not cover it wholly, in my opinion.
> > Because when the utility's hashed path is not in $PATH,
> > then the utility should not have been searched for at all.
> > It
On Mon, Nov 1, 2021 at 10:58 AM Mike Jonkmans wrote:
> This wording does not cover it wholly, in my opinion.
> Because when the utility's hashed path is not in $PATH,
> then the utility should not have been searched for at all.
> It should not be found, even if it is remembered.
Is the rest of
I agree, this looks to be broken in bash - "command -p cmd" is (logically)
oldpath=$PATH
PATH=/standard:/system:/path
cmd
PATH=$oldpath
and should act (as if) that way.
What's more, from all the shells I have tested, bash is the only one
to behave like this,
On Mon, Nov 01, 2021 at 09:09:19AM +0300, Oğuz wrote:
> On Sun, Oct 31, 2021 at 10:26 PM Mike Jonkmans wrote:
> > POSIX is also silent on this.
>
> I think ``Once a utility has been searched for and found [...], an
> implementation may remember its location and need not search for the
> utility
On Sun, Oct 31, 2021 at 10:26 PM Mike Jonkmans wrote:
> POSIX is also silent on this.
I think ``Once a utility has been searched for and found [...], an
implementation may remember its location and need not search for the
utility again unless the PATH variable has been the subject of an
30 matches
Mail list logo
