On Feb 12 11:12:46, j...@johnmerriam.net wrote:
> On 2015-02-12 10:50, Jan Stary wrote:
> >On Feb 12 10:15:08, j...@johnmerriam.net wrote:
> >>What does it show when you run the alias command with no arguments to
> >>display your current aliases?
> >>
> >>I noticed that in the error message there is no space between -m and the
> >>path. That seems a bit odd.
> >
> >$ alias
> >autoload='typeset -fu'
> >diff='diff -Nup'
> >functions='typeset -f'
> >hash='alias -t'
> >history='fc -l'
> >integer='typeset -i'
> >ll='ls -lAp'
> >local=typeset
> >login='exec login'
> >ls='ls -p'
> >man='man -m /home/hans/man'
> >nohup='nohup '
> >pdftops='pdftops -paper A4'
> >r='fc -e -'
> >stop='kill -STOP'
> >type='whence -v'
> >
> >
> >In particular, the space is there, as specified in the alias command.
> >But the problem is probably not in the aliases:
> >
> >$ unalias man
> >$ man -m ~/man ls
> >man: -m/home/hans/man: Bad argument
> >
> > Jan
>
> I would assume it would cause you more problems than just man if it were the
> case, but, if you do a `vis /etc/passwd`, are there any funny characters in
> the home directory for your username? Just a thought since that space
> between -m and the path seems to disappear in the error.
No.
> If you leave out -m /path and just run `man ls`, does that work?
With man unaliased, it works just fine.
With 'man -m ~/man', or with man aliased to that,
'man ls' gave me the error above.
> Also, which version of OpenBSD are you running on this machine?
> 5.6 or -current?
current/amd64
Jan
