Steffen Daode Nurpmeso dixit:
>Thorsten Glaser <[email protected]> wrote:
> |> - no tab completion over / boundary in upward direction
> |
> |Eh, *what*?
>
>E.g.,
>
> ?0[steffen@sherwood mksh.cvs_git]$ cd ..<Tab>
>
>Doesn't do anything, only
That’s correct because a Korn Shell never(!) matches
the dot or dotdot entries, and tab completion is
chiefly based on globbing; you can see that by
doing 'cd .'<tab> which will show your dotfiles
but not ./ as directory entry.
But if you have .. typing / is as much work as
typing Tab (well, adding Shift on some keyboard
layouts)…
>I must admist that i really hate this behaviour, i always get
>stuck; personal preference of course..
Hm okay. But I guess this ends up really being a matter of
taste, over which discussing is difficult.
You can just type a space to get out of it, if that helps.
>And well, all that is on my todo list for some time now, maybe
>i can write some patches soon.
OK ;-)
>- if (p->flags & TF_DFL_INTR) {
>+ if (! Flag(FLOGIN) && p->flags & TF_DFL_INTR) {
^ no space
> /* eg, SIGINT, SIGQUIT, SIGTERM, etc. */
I think this one is too over-zealous: even if it’s a login
shell I’d like to have a SIGTERM exit it.
Changing the signal behaviour as suggested in that feature
request might not be so detrimental (but, as I said, I fear
other issues with it, so it’s only on my long-term TODO).
> exstat = (int)ksh_min(128U + (unsigned)i, 255U);
> unwind(LINTR);
bye,
//mirabilos
--
Support mksh as /bin/sh and RoQA dash NOW!
‣ src:bash (257 (276) bugs: 0 RC, 178 (192) I&N, 79 (84) M&W, 0 (0) F&P)
‣ src:dash (84 (98) bugs: 3 RC, 39 (43) I&N, 42 (52) M&W, 0 F&P)
‣ src:mksh (1 bug: 0 RC, 0 I&N, 1 M&W, 0 F&P)
http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit?
