Forgive me, I don't spend my life using ksh esoterica But I do use ssh all the time
man AddKeysToAgent man AddressFamily man BatchMode man BindAddress man CanonicalDomains man CanonicalizeFallbackLocal man CanonicalizeHostname man CanonicalizeMaxDots man CanonicalizePermittedCNAMEs man CASignatureAlgorithms man CertificateFile man CheckHostIP man Ciphers man ClearAllForwardings man Compression man ConnectionAttempts man ConnectTimeout man ControlMaster man ControlPath man ControlPersist man DynamicForward man EscapeChar man ExitOnForwardFailure man FingerprintHash man ForkAfterAuthentication man ForwardAgent man ForwardX11 man ForwardX11Timeout man ForwardX11Trusted man GatewayPorts man GlobalKnownHostsFile man GSSAPIAuthentication man GSSAPIDelegateCredentials man HashKnownHosts man Host man HostbasedAcceptedAlgorithms man HostbasedAuthentication man HostKeyAlgorithms man HostKeyAlias man Hostname man IdentitiesOnly man IdentityAgent man IdentityFile man IPQoS man KbdInteractiveAuthentication man KbdInteractiveDevices man KexAlgorithms man KnownHostsCommand man LocalCommand man LocalForward man LogLevel man MACs man Match man NoHostAuthenticationForLocalhost man NumberOfPasswordPrompts man PasswordAuthentication man PermitLocalCommand man PermitRemoteOpen man PKCS11Provider man Port man PreferredAuthentications man ProxyCommand man ProxyJump man ProxyUseFdpass man PubkeyAcceptedAlgorithms man PubkeyAuthentication man RekeyLimit man RemoteCommand man RemoteForward man RequestTTY man RequiredRSASize man SendEnv man ServerAliveInterval man ServerAliveCountMax man SessionType man SetEnv man StdinNull man StreamLocalBindMask man StreamLocalBindUnlink man StrictHostKeyChecking man TCPKeepAlive man Tunnel man TunnelDevice man UpdateHostKeys man User man UserKnownHostsFile man VerifyHostKeyDNS man VisualHostKey man XAuthLocation those are ssh builtins there is no manual page. am i being punished in the same way as you??? No, I am not. When you are using ksh, you can read the ksh manual page. You cannot assume the commands you type in are entirely ksh, in the $PATH, but you can use your brain and suspect that some of them are builtins, and check the damn man page for ksh. Whan I am in ssh, I can do the same. What should we do to settle this outrage? We could do is take every word found in the ksh manual page, and make it a keyword the man command will find. man if -> obviously ksh man while -> obviously ksh man the -> obviously ksh, also Obviously there is a cluster of people who will be satisfied until we do that. Reuben mac Saoidhea <ancatm...@outlook.com> wrote: > i feel i ought to repeat myself: you really ought to use: > > type [command ...] > > some problems with the manual: > > * you have to type `man sh'. you cant type `man type'. > * sh(1) does not explain that `tracked alias' in the output of > `type' relates to the output of `hash'. see `hash' in sh(1). > > some problems with the other commands: > > * some are not a part of the shell. they cant tell you about shell stuff. > * some just echo back function names, etc. > * some are ksh(1) features. ksh(1) features are often buggy, etc. >
