Re: [dev] [st] problem reading man pages

2013-05-22 Thread Chris Down
On 22 May 2013 22:27, G David Modica wrote: > > On 11:06 Wed 22 May , Thorsten Glaser wrote: > > How about: > > > > script man foo q exit > > > gdm@gdmThink ~$ script man foo q exit > bash: syntax error near unexpected token `newline' > gdm@gdmThink ~$ I'm not sure whether to laugh or c

Re: [dev] [st] problem reading man pages

2013-05-22 Thread 7heo
On 05/22/2013 04:27 PM, G David Modica wrote: Guilty, systemd is one of the banes of my existence but I've not found anything I like better than Arch. Search again. -- 7heo

Re: [dev] [st] problem reading man pages

2013-05-22 Thread Thorsten Glaser
G David Modica dixit: >On 11:06 Wed 22 May , Thorsten Glaser wrote: >> How about: >> >> script man foo q exit >gdm@gdmThink ~$ script man foo q exit >bash: syntax error near unexpected token `newline' >gdm@gdmThink ~$ This is something to print out, frame and hang on the wall. … Hon

Re: [dev] [st] problem reading man pages

2013-05-22 Thread G David Modica
On 11:06 Wed 22 May , Thorsten Glaser wrote: > Fernando C.V. dixit: > > >rendered, but unreadable.. can you copy-paste the invisible spaces > >between the "[-c ]"? > > How about: > > script man foo q exit > gdm@gdmThink ~$ script man foo q exit bash: syntax error near unexpected

Re: [dev] [st] problem reading man pages

2013-05-22 Thread G David Modica
On 11:56 Wed 22 May , Fernando C.V. wrote: > Maybe you altered your st colors somehow and the highlights make the > characters hard to see... my guess is that the words are there > rendered, but unreadable.. can you copy-paste the invisible spaces > between the "[-c ]"? > Yes, the missing

Re: [dev] [st] problem reading man pages

2013-05-22 Thread G David Modica
On 11:50 Wed 22 May , Fernando C.V. wrote: > or better: > > set | grep LESS gdm@gdmThink ~$ set | grep LESS gdm@gdmThink ~$

Re: [dev] [st] problem reading man pages

2013-05-22 Thread G David Modica
On 11:48 Wed 22 May , Fernando C.V. wrote: > Maybe you have some custom less settings? > try this: > > echo $LESS > echo $LESS_TERMCAP_mb - $LESS_TERMCAP_md - $LESS_TERMCAP_so - > $LESS_TERMCAP_us > echo $LESS_TERMCAP_me - $LESS_TERMCAP_se - $LESS_TERMCAP_so - > $LESS_TERMCAP_ue >

Re: [dev] [st] problem reading man pages

2013-05-22 Thread Maximilian Dietrich
On Tue, May 21, 2013 at 08:52:52PM -0400, G David Modica wrote: > Hi, > > I just noticed that man pages are not rendered properly under st-0.4.1 tip. > For example in "man st" the SYNOPSYS line shows as: >st [-a] [-c ] [-f ] [-g ] [-o ] [-t ] [-w > ]

Re: [dev] [st] problem reading man pages

2013-05-22 Thread Thorsten Glaser
Fernando C.V. dixit: >rendered, but unreadable.. can you copy-paste the invisible spaces >between the "[-c ]"? How about: script man foo q exit Then send in the typescript, gzip(1)d. bye, //mirabilos -- Sorry, I’m annoyed today and you came by as an Arch user. These are the perfect

Re: [dev] [st] problem reading man pages

2013-05-22 Thread Fernando C.V.
Maybe you altered your st colors somehow and the highlights make the characters hard to see... my guess is that the words are there rendered, but unreadable.. can you copy-paste the invisible spaces between the "[-c ]"? (sorry for the 3 mails in a row... I just I kept thinking about it) --

Re: [dev] [st] problem reading man pages

2013-05-22 Thread Fernando C.V.
or better: set | grep LESS -- Fernando On Wed, May 22, 2013 at 11:48 AM, Fernando C.V. wrote: > On Wed, May 22, 2013 at 11:23 AM, G David Modica > wrote: >> I believe it defaults to "less". > > Maybe you have some custom less settings? > try this: > > echo $LESS > echo $LESS_TERMCAP

Re: [dev] [st] problem reading man pages

2013-05-22 Thread Fernando C.V.
On Wed, May 22, 2013 at 11:23 AM, G David Modica wrote: > I believe it defaults to "less". Maybe you have some custom less settings? try this: echo $LESS echo $LESS_TERMCAP_mb - $LESS_TERMCAP_md - $LESS_TERMCAP_so - $LESS_TERMCAP_us echo $LESS_TERMCAP_me - $LESS_TERMCAP_se - $LESS_TE

Re: [dev] [st] problem reading man pages

2013-05-22 Thread G David Modica
On 11:47 Wed 22 May , Chris Down wrote: > You have misunderstood the question -- what is your $PAGER? gdm@gdmThink ~$ echo $PAGER gdm@gdmThink ~$ I believe it defaults to "less".

Re: [dev] [st] problem reading man pages

2013-05-21 Thread Chris Down
On 22 May 2013 10:51, G David Modica wrote: > On 20:21 Tue 21 May , Anthony J. Bentley wrote: > > G David Modica writes: > > > On 19:01 Tue 21 May , Anthony J. Bentley wrote: > > > > Would be helpful to specify what program generates your manpages. > Manuals l > > > ook > > > > fine here

Re: [dev] [st] problem reading man pages

2013-05-21 Thread G David Modica
On 20:21 Tue 21 May , Anthony J. Bentley wrote: > G David Modica writes: > > On 19:01 Tue 21 May , Anthony J. Bentley wrote: > > > Would be helpful to specify what program generates your manpages. Manuals > > > l > > ook > > > fine here with st tip and mandoc... > > > > > > > No idea how

Re: [dev] [st] problem reading man pages

2013-05-21 Thread Anthony J. Bentley
G David Modica writes: > On 19:01 Tue 21 May , Anthony J. Bentley wrote: > > Would be helpful to specify what program generates your manpages. Manuals l > ook > > fine here with st tip and mandoc... > > > > No idea how man pages are generated. I am running Archlinux. Any idea how I > can te

Re: [dev] [st] problem reading man pages

2013-05-21 Thread G David Modica
On 19:01 Tue 21 May , Anthony J. Bentley wrote: > Would be helpful to specify what program generates your manpages. Manuals look > fine here with st tip and mandoc... > No idea how man pages are generated. I am running Archlinux. Any idea how I can tell how they are generated? David

Re: [dev] [st] problem reading man pages

2013-05-21 Thread Anthony J. Bentley
G David Modica writes: > Hi, > > I just noticed that man pages are not rendered properly under st-0.4.1 tip. > For example in "man st" the SYNOPSYS line shows as: >st [-a] [-c ] [-f ] [-g ] [-o ] [-t ] [-w > ] [-v] [-e...] > > st-0.3 shows th