Thorsten Glaser <[email protected]> wrote:
|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.
Hmmm; i'm really not experienced with all the subtleties, the
refined distinctions in between the different shells… but
sh (AT&T Research) 1993-12-28
actually does expand to the CDUP.
|>- 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.
If that is only entered on the three mentioned then i think it's
ok for a login shell to simply ignore them; just as mksh(1) R40
did ? ;)
Ciao,
--steffen
