JdeBPWhich shell is that?
The alternative is to make the shell handle the un-escaping:
echo hello,there |sed 's/,/'"\n"'/g'
It's undocumented in several ksh flavours, but nonetheless works. However, those flavours also (trying a quick few tests) support the better way, which is also undocumented though:
echo hello,there |sed $'s/,/\n/g'
I was about to write the same thing.
And as @steeph pointed out, getopt in shell script does not allow one to do several things, including take advantage of the Z shell's ability to automatically construct command-line completions for anything that supports --help .
JdeBPIt's going to get less accurate as the months go by. It's a simple #arithmetic trick, and you can tell which year the image was faked for.
The number, in repetitions on the WWW, goes as low as 78, so you can tell what year this trick began doing the rounds, too.
Now for true mentalist tricks, look at how the GNU date command and a POSIX-conformant shell can magically, with just one line, work out the year that you were born:
date -r "-$(((2+1)*3*2*5*487*6*10*9<<4))" +'%Y'
EloshaI just read about MUSH (Microsoft User Shell) – which is the keyboard-based pre-pulldown menu system that existed in Multiplan, Word or XTree – and early drafts of Microsoft Interface Manager, an text UI precursor of Windows which resembled DOSShell from MS-DOS 4, on the website of @nina_kali_nina . I remembered there actually was a Visual Shell, vsh in Microsoft Xenix (their Unix OS). Sadly, browsing was not very intuitive … #softwarearcheology #unix #unixshells
@rl_dane hit the nail on the head.
This isn't really specific to completion. It's just general overlong input line editing behaviour.
The PD #KornShell and its derivatives (e.g. the #MirBSD Korn Shell) only have line editing with a single line that sideways scrolls.
ksh93, however, has a
set -o multiline
option for switching to a multiple-line line editing mode. (The Z and Bourne Again shells have similar.)
You might like the Watanabe shell. It's in ports.
I was curious as to what this meant, so I fired up PD ksh and tried what I thought long command-prompt entries meant.
The PD #KornShell uses a column width greater than the terminal width (which I set to 50 columns here, just to make things easier) because it SPC-pads everything to the length of the longest string; and ends up double-spacing most rows in the table as a consequence.
I couldn't figure out how to get it to specifically clip rows, though.
Tried it. It didn't clear the screen.
