Hi Jean,
>Sorry for the late reply, I have been away from home due to unexpected
>family issues.
no problem.
>for -e must be fairly limited. As I understand it, the only purpose of
>the option is to cancel a previous -r, which is kind of a corner case.
The ksh93 manpage documents it as such,
Hi Thorsten,
Sorry for the late reply, I have been away from home due to unexpected
family issues.
On ven., 2017-02-17 at 22:37 +, Thorsten Glaser wrote:
> Jean Delvare dixit:
> >Our previous products included ksh93.
>
> OK. (Found out as well that ksh93 has print -e, which we had code
>
Jean Delvare dixit:
>So, what is the next step?
Me getting any spare time…
Sorry,
//mirabilos, currently under high pressure for two customer projects
--
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
On Fri, 10 Feb 2017 13:10:20 + (UTC), Thorsten Glaser wrote:
> That’s ksh88 where you(r customer) come(s) from?
Our previous products included ksh93.
> >> We have the echo you mean in POSIX mode though…
> >
> >Not sure what you mean here. I see that the echo command behavior is
> >changed if
Jean Delvare dixit:
>I din't think -R currently emulates either properly (but I suppose I
>can't complain, as "to some degree" could be read as implying just
>that.) BSD echo will print arguments starting with a dash, other than a
Hmm, okay. In that case (I’ll recheck with legacy BSD sources
Hi Thorsten,
Thanks for your quick answer.
On jeu., 2017-02-09 at 18:46 +, Thorsten Glaser wrote:
> Jean Delvare dixit:
> >In mksh, "print -R" is not as close to "echo" as it was in original
> >ksh. Specifically, after "-R", mksh's print command keeps parsing
> >the command line in search of
Jean Delvare dixit:
>Hello mksh developer,
Hi!
>In mksh, "print -R" is not as close to "echo" as it was in original
>ksh. Specifically, after "-R", mksh's print command keeps parsing the
>command line in search of options, and stops as soon as it finds an
Indeed, this is as documented:
