Olivier Duchateau | 21 May 2012 23:09
Picon

Unexpected error with mksh R40d

Hi,

In console (without X), under NetBSD 5.1.2, with mksh R40d, when I
want to see man pages (e.g man mksh), I've got this error.

man: Formatting manual page...
sh: Syntax error: "(" unexpected
sh: Syntax error: "(" unexpected

I can't see man pages.

--

-- 
olivier

Thorsten Glaser | 21 May 2012 23:32
Picon
Gravatar

Re: Unexpected error with mksh R40d

Olivier Duchateau dixit:

>man: Formatting manual page...
>sh: Syntax error: "(" unexpected
>sh: Syntax error: "(" unexpected

Please *temporarily* move your /bin/sh out of the way and
put a link to mksh there and see whether the error persists.

If not, my first guess is that PS1 is exported.

bye,
//mirabilos
--

-- 
  “Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool.”
						-- Edward Burr

Olivier Duchateau | 22 May 2012 00:08
Picon

Re: Unexpected error with mksh R40d

2012/5/21 Thorsten Glaser <tg@...>:
> Olivier Duchateau dixit:
>
>>man: Formatting manual page...
>>sh: Syntax error: "(" unexpected
>>sh: Syntax error: "(" unexpected
>
> Please *temporarily* move your /bin/sh out of the way and
> put a link to mksh there and see whether the error persists.

Yeah, it works, but I use default mksh's configuration file.

>
> If not, my first guess is that PS1 is exported.

PS1 is not exported, no export PS1 in ~/.mkshrc

olivier <at> judas:~ $ env | grep PS1
1|olivier <at> judas:~ $

>
> bye,
> //mirabilos
> --
>  “Having a smoking section in a restaurant is like having
>          a peeing section in a swimming pool.”
>                                                -- Edward Burr

--

-- 
olivier
(Continue reading)

Thorsten Glaser | 22 May 2012 02:08
Picon
Gravatar

Re: Unexpected error with mksh R40d

Olivier Duchateau dixit:

>> Please *temporarily* move your /bin/sh out of the way and
>> put a link to mksh there and see whether the error persists.
>
>Yeah, it works

OK, then it’s at least not a bug in mksh *phew*.

>but I use default mksh's configuration file.

This happens. For example, we changed this:

>> If not, my first guess is that PS1 is exported.

So, config files need to be updated occasionally, too.

>PS1 is not exported, no export PS1 in ~/.mkshrc
>
>olivier <at> judas:~ $ env | grep PS1

OK, then something else, $ENV maybe. Just look in the exported
environment for mkshisms. (Note that $ENV should be totally
unset for normal mksh operation.)

bye,
//mirabilos
--

-- 
13:22⎜«neurodamage» mira, what's up man? I have a CVS question for you in #cvs
13:22⎜«neurodamage» since you're so good w. it │ «neurodamage:#cvs» i love you
(Continue reading)


Gmane