michael dixit:

>So far so good. Seems on par with dash's quickness and far more capable. I 

Right. More robust (and less buggy), too.

>just wish I could get to the next line with CTRL-V CTRL-J. It's a stupid 

There is no “next line” in mksh, at least not interactively.
But with ^Xe, you can spawn an editor on the current input line,
and writing and sending multiline input there should™ work.
(Disclaimer: only somewhat tested, amounting to what $PS2 does.)

>habit I picked up rather than using a proper editor. Guess it's time to 
>break that habit, anyway. I do particularly like the dex editor, though.

You won’t win me over, what with jupp and all that ;-)
(And if there’s no jupp, I just use ed.)

>> This also works in GNU bash and AT&T ksh93.
>
>I know, but it's where it doesn't work that bugs me.

Sure. It’s just that AT&T ksh93 is the model for most of mksh’s
behaviour, and GNU bash is something to keep in the eye as it’s
what GNU users expect, which is why I mentioned it.

>I've been experimenting with writing out a shell sourceable argument array 
>that I can call on from any shell. Here's one way I *think* I have managed 

Oh *wow*.

I tend to keep my scripts mksh-specific (but portable across
systems) and the shell portable, not the scripts portable to
various shells… living without certain amenities, especially
arrays often, makes me crazy ;)

>So far it caters to three shells' peculiarities, though I have no doubt that 
>list will grow as I discover them, and I don't have a ksh93 to work with. 2 

Right. For example, avoid printf(1) on mksh, but use the print
builtin (on all Korn shells).

ksh93, for small test things, is available though shbot on
Freenode IRC. Example:

20:26⎜>shbot< k# echo ${.sh.version}
20:26⎜[[shbot]] Version AJM 93u+ 2012-08-01

The first line is me writing
        /msg shbot k# echo ${.sh.version}
and the second line is shbot running
        ksh93 <<-'EOF'
                echo ${.sh.version}
        EOF
in a VM, displaying its output.

>Anyway, regarding mksh, I have only to check if the very first split char is 
>the split delimiter, and, if so, add another. It isn't difficult to do. The 

If this is about the bug you reported, it’s unwise to do this
by a check on the shell, as the bug is likely to eventually
get fixed, making your code buggy ;-)

>Thanks again, mirabilos.

You’re welcome.

bye,
//mirabilos
-- 
<theftf> Ich gebs zu, jupp ist cool
        -- theftf zu Natureshadow beim Fixen von Debian

Reply via email to