🚀 go-pugleaf

[Bash 1.12] Below we see how when it comes time to list completions,
bash crudely fills our 300 baud friends' screens with mucho blanks at
the end of lines [as revealed by cat -v].  Furthermore, ksh smartly
tells us if a file is a directory, by appending a slash/ like/ so/,
whilst bash takes the plain jane approach.

bash$ bla <TAB><TAB>
xxxyyyx.Pin                     moers2.edu.tw                   ^M
RMS                             moers2.edu.tw-chinese-pub.ls-R  ^M
ST.CATHARINES                   mule                            ^M
TaiBunThongSin                  new                             ^M
a                               new.p                           ^M
a.p                             newImm                          ^M
address.b                       purdue-fonts                    ^M
bitNewsgroups                   ransom.ps                       ^M
hz2ps-2.1.tar.Z                 ^M
jaco5a                          ^M

$ ksh -o emacs^M
$ <ESC>=
 9) RMS                               37) moers2.edu.tw-chinese-pub.ls-R^M
10) ST.CATHARINES                     38) moers2.edu.tw/^M
11) TaiBunThongSin                    39) mule^M
12) a                                 40) new^M
13) a.p                               41) new.p^M
14) address.b                         42) newImm^M
15) bitNewsgroups                     43) purdue-fonts/^M
16) check.addr                        44) ransom.ps^M
17) cxterm/                           45) scr.RFPI^M
[...]

However, both ksh and bash fail to put@ an@ "@" at@ the@ end@ of@
filenames@ to indicate symbolic link!  Infact, the observant observer
would spot this as an opportunity for bash to pull ahead in the
completion sparkle department, however I wouldn't go so far as adding
all) those) wonderful) choice) numbers) [33) 34) 35)] a) la) ksh).