On Wednesday, October 31, 2018 10:19 PM, Joseph Mayer
wrote:
> On Tuesday, October 30, 2018 4:33 PM, Sebastien Marie sema...@online.fr wrote:
>
> > On Tue, Oct 30, 2018 at 08:11:24AM +, Joseph Mayer wrote:
> >
> > > On a quick sourcecode check I didn't see any code paths e.g.
> > > "if
On Tuesday, October 30, 2018 4:33 PM, Sebastien Marie wrote:
> On Tue, Oct 30, 2018 at 08:11:24AM +, Joseph Mayer wrote:
>
> > On a quick sourcecode check I didn't see any code paths e.g.
> > "if (argv[0] matches "ksh") { something } else { something else }"
> > however I presume I missed
On Tue, Oct 30, 2018 at 08:11:24AM +, Joseph Mayer wrote:
>
> On a quick sourcecode check I didn't see any code paths e.g.
> "if (argv[0] matches "ksh") { something } else { something else }"
> however I presume I missed something.
>
yes, the check was too quick, it seems :)
Hi misc@,
I noticed that sh and ksh have different behaviors from doing
"export PS1='\[\033[01;35m\]COLOR\$ '", here "sh" shows
"\[\033[01;35m\]COLOR#" in gray, while "ksh" shows "COLOR#" in purple.
sh and ksh's binaries are equivalent.
I do see that sh's and ksh's man pages differ, e.g.
4 matches
Mail list logo