Re: `perldoc` and terminal size

2013-04-19 Thread Andy Koppe
On 18 April 2013 22:27, terminatorul wrote: > Hello > > I am using `perldoc` to read the perl manual pages.I can use the black > background it gives in mintty with a full-screen console, with low light > intensity so I can read it during night o > > > I can use the bl

`perldoc` and terminal size

2013-04-18 Thread terminatorul
Hello I am using `perldoc` to read the perl manual pages.I can use the black background it gives in mintty with a full-screen console, with low light intensity so I can read it during night o I can use the black background in mintty with a full-screen console window with low-light conditions

Re: Can't run perldoc

2011-03-31 Thread Andrew DeFaria
On 3/31/2011 7:26 AM, Reini Urban wrote: 2011/3/22 Andrew DeFaria: Why is it when I do something like: $ perldoc perlre I get a bunch of: 14 [main] sh 72132 C:\Cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x71, top 0x78, reserve_size 4

Re: Can't run perldoc

2011-03-31 Thread Andrew DeFaria
On 03/31/11 07:26, Reini Urban wrote: 2011/3/22 Andrew DeFaria: Why is it when I do something like: $ perldoc perlre I get a bunch of: 14 [main] sh 72132 C:\Cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x71, top 0x78, reserve_size 4

Re: Can't run perldoc

2011-03-31 Thread Reini Urban
2011/3/22 Andrew DeFaria: > Why is it when I do something like: > > $ perldoc perlre > > I get a bunch of: > >     14 [main] sh 72132 C:\Cygwin\bin\sh.exe: *** fatal error - couldn't > allocate heap, Win32 error 487, base 0x71, top 0x78, reserve_size

Can't run perldoc

2011-03-21 Thread Andrew DeFaria
Why is it when I do something like: $ perldoc perlre I get a bunch of: 14 [main] sh 72132 C:\Cygwin\bin\sh.exe: *** fatal error - couldn't allocat e heap, Win32 error 487, base 0x71, top 0x78, reserve_size 454656, alloc size 458752, page_const 4096 Stack trace:

Re: Perldoc issue with perl-5.8.8-3 - missing pod2man5.8.8

2007-07-19 Thread Reini Urban
[EMAIL PROTECTED] schrieb: Hi all, after upgrading perl to the version 5.8.8 I can't use perldoc to wiew perl documentation. perldoc is searching for pod2man5.8.8 instead of pod2man which is already preset in /usr/bin. Creating symbolic link pod2man5.8.8 -> /usr/bin/pod2man solve th

Perldoc issue with perl-5.8.8-3 - missing pod2man5.8.8

2007-07-19 Thread roman . vasicek
Hi all, after upgrading perl to the version 5.8.8 I can't use perldoc to wiew perl documentation. perldoc is searching for pod2man5.8.8 instead of pod2man which is already preset in /usr/bin. Creating symbolic link pod2man5.8.8 -> /usr/bin/pod2man solve this issue. Example: $ perldo

Re: Perl documentation inaccessible via 'perldoc'.

2007-07-05 Thread Thomas Berger
Andrew Schulman wrote: >> >> [EMAIL PROTECTED] /cygdrive/c/_32/working/math-gmpz/Math-GMPz-0.22 >> >> $ perldoc ExtUtils::MakeMaker >> >> Error in tempfile() using ./XX: Parent directory (./) is not >> >> writable >> >> at /usr/

RE: Perl documentation inaccessible via 'perldoc'.

2007-07-05 Thread Dave Korn
On 05 July 2007 10:15, Sisyphus wrote: > How do I make that alteration a permanent fixture, so that I don't have to > do it every time I open a new shell ? I tried editing etc/profile (in > wordpad), but only succeeded in stuffing up the line endings - and had to > replace that file with a copy of

Re: Perl documentation inaccessible via 'perldoc'.

2007-07-05 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Sisyphus on 7/5/2007 3:15 AM: > Yep - that fixes it. Both TEMP and TMP were set, but not TMPDIR. > > How do I make that alteration a permanent fixture, so that I don't have > to do it every time I open a new shell ? I tried editing etc/pr

Re: Perl documentation inaccessible via 'perldoc'.

2007-07-05 Thread Sisyphus
- Original Message - From: "Andrew Schulman" <[EMAIL PROTECTED]> . . I wonder, do you have TMPDIR set? Try setting it, e.g. export TMPDIR=/tmp/Rob Yep - that fixes it. Both TEMP and TMP were set, but not TMPDIR. How do I make that alteration a permanent fixture, so that I don't

Re: Perl documentation inaccessible via 'perldoc'.

2007-07-05 Thread Andrew Schulman
> [EMAIL PROTECTED] /cygdrive/c/_32/working/math-gmpz/Math-GMPz-0.22 > $ perldoc ExtUtils::MakeMaker > Error in tempfile() using ./XX: Parent directory (./) is not > writable > at /usr/lib/perl5/5.8/Pod/Perldoc.pm line 1483 tempfile() is trying to create the tempfile

Perl documentation inaccessible via 'perldoc'.

2007-07-04 Thread Sisyphus
Hi, Just installed the latest cygwin (including Cygwin's build of perl 5.8.7) on Windows Vista Business (64) on an AMD64 box. Trying to access perl documentation using 'perldoc' throws an error: --- [EMAIL PROTECT

Re: perldoc

2005-04-05 Thread beau
On Apr 5, 2005 2:17 PM, Igor Pechtchanski <[EMAIL PROTECTED]> wrote: > export PERLDOC_PAGER="less -+C -e -isrR" You da man; thanks. Speaking of man, I read the less manpage so as to actually understand the options you've picked. Rock on. beau -- Unsubscribe info: http://cygwin.com/ml/#unsu

Re: perldoc

2005-04-05 Thread Igor Pechtchanski
On Tue, 5 Apr 2005, beau wrote: > Anyone else having trouble with perldoc? I've got perl 5.8.6-4; > trying perldoc perldoc in rxvt. What I get is: > > ESC[1mNAMEESC[0m > > with "ESC" reversed. > > Don't even know where to start on this; as always,

perldoc

2005-04-05 Thread beau
Anyone else having trouble with perldoc? I've got perl 5.8.6-4; trying perldoc perldoc in rxvt. What I get is: ESC[1mNAMEESC[0m with "ESC" reversed. Don't even know where to start on this; as always, all help appreciated. beau -- Unsubscribe info: http://cygwin

Re: Cygwin Perl bug -- perldoc Pod::Usage

2005-01-16 Thread Yitzchak Scott-Thoennes
On Sun, Jan 16, 2005 at 07:02:56PM -0800, David Christensen wrote: > The documentation displayed by 'perldoc Pod::Usage' is malformed -- > the majority of the text between ARGUMENTS and EXAMPLES is bold, and > if I exit less when the colon is bold, my terminal gets stuck in &

Cygwin Perl bug -- perldoc Pod::Usage

2005-01-16 Thread David Christensen
Cygwin: The documentation displayed by 'perldoc Pod::Usage' is malformed -- the majority of the text between ARGUMENTS and EXAMPLES is bold, and if I exit less when the colon is bold, my terminal gets stuck in bold. 'reset' and 'clear' don't fix it. I

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Gerrit P. Haase
Brian Dessent wrote: Elvin Peterson wrote: I don't get any color highlighting when I use LESS=R, but as I said in another post, perldoc didn't have highlighting to begin with. Does anyone here get color in the terminal for, say, perldoc CPAN? As it is, I am using man for everyth

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Brian Dessent
Elvin Peterson wrote: > I don't get any color highlighting when I use LESS=R, > but as I said in another post, perldoc didn't have > highlighting to begin with. Does anyone here get > color in the terminal for, say, perldoc CPAN? As it > is, I am using man for eve

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Elvin Peterson
--- "Gerrit P. Haase" <[EMAIL PROTECTED]> wrote: > Elvin Peterson wrote: > > >>>Hello, > >>>The perl documentation viewed using the > >>> perldoc commands has escape characters inserted > into it. > >>> The same

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Gerrit P. Haase
Elvin Peterson wrote: Hello, The perl documentation viewed using the perldoc commands has escape characters inserted into it. The same pages view with the man command are OK. I >>> think this is cygwin specific, so I am posting it here. Not really a problem with perldoc, try: expo

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Elvin Peterson
--- Yaakov Selkowitz <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Elvin Peterson wrote: > | Hello, > | The perl documentation viewed using the > perldoc > | commands has escape characters inserted into it. > The > |

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Elvin Peterson
--- "Gerrit P. Haase" <[EMAIL PROTECTED]> wrote: > Elvin Peterson wrote: > > > Hello, > > The perl documentation viewed using the > perldoc > > commands has escape characters inserted into it. > The > > same pages view with the man comman

Re: bug in perldoc (escape characters in output)

2004-10-31 Thread Gerrit P. Haase
Elvin Peterson wrote: Hello, The perl documentation viewed using the perldoc commands has escape characters inserted into it. The same pages view with the man command are OK. I think this is cygwin specific, so I am posting it here. Not really a problem with perldoc, try: export LESS=R

Re: bug in perldoc (escape characters in output)

2004-10-30 Thread Yaakov Selkowitz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Elvin Peterson wrote: | Hello, | The perl documentation viewed using the perldoc | commands has escape characters inserted into it. The | same pages view with the man command are OK. I think | this is cygwin specific, so I am posting it here

bug in perldoc (escape characters in output)

2004-10-30 Thread Elvin Peterson
Hello, The perl documentation viewed using the perldoc commands has escape characters inserted into it. The same pages view with the man command are OK. I think this is cygwin specific, so I am posting it here. Thanks. __ Do you Yahoo

Re: perldoc unreadable

2003-08-29 Thread waxmop
I changed the permissions on / to 777, and now I can use perldoc. I suspect that having / set to 777 is a security problem, and at some later point I'll revisit this. However, since my computer sits behind a firewall and I'm the only one using it, I'm ok with this for now.

Re: perldoc unreadable

2003-08-29 Thread Gerrit P. Haase
Hallo waxmop, > I use perl version 5.8.0. Please try to reinstall perl with setup.exe, probably you want to upgrade to perl-5.8.0-4, once it is available on the mirrors. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.c

Re: perldoc unreadable

2003-08-28 Thread [EMAIL PROTECTED]
I use perl version 5.8.0. On Thu, 28 Aug 2003 23:24:09 +0200 "Gerrit P. Haase" <[EMAIL PROTECTED]> wrote: > Hallo waxmop, > > Am Donnerstag, 28. August 2003 um 21:42 schriebst du: > > > Hi - > > > > perldoc isn't working for m

Re: perldoc unreadable

2003-08-28 Thread Gerrit P. Haase
Hallo waxmop, Am Donnerstag, 28. August 2003 um 21:42 schriebst du: > Hi - > perldoc isn't working for me: > [EMAIL PROTECTED] ~ > $ perldoc perldoc > Ignored /usr/bin/perldoc: unreadable > Ignored /usr/bin/perldoc: unreadable > Ignored /bin/perldoc: unreadable &g

perldoc unreadable

2003-08-28 Thread waxmop
Hi - perldoc isn't working for me: [EMAIL PROTECTED] ~ $ perldoc perldoc Ignored /usr/bin/perldoc: unreadable Ignored /usr/bin/perldoc: unreadable Ignored /bin/perldoc: unreadable No documentation found for "perldoc". Here's the permissions information for the perldoc fil

Re: perldoc can't read module

2003-07-11 Thread Gerrit P. Haase
Hello Ronald, > $ perldoc File::Find > perldoc complains >Ignored /usr/lib/perl5/5.8.0/File/Find.pm: unreadable > Although the file seems to have correct permission rights > $ ls -l /usr/lib/perl5/5.8.0/File/Find.pm > -rwx--+ 1 Administ mkgroup_34332 Ju

Re: perldoc can't read module

2003-07-11 Thread Brian Dessent
Ronald Fischer wrote: > $ ls -l /usr/lib/perl5/5.8.0/File/Find.pm > -rwx--+ 1 Administ mkgroup_34332 Jun 2 15:41 > /usr/lib/perl5/5.8.0/File/Find.pm Try running 'mkgroup -l /etc/group' (and the same for mkpasswd if you haven't done that either.) Brian -- Unsubscribe info: h

perldoc can't read module

2003-07-11 Thread Ronald Fischer
I've installed perl, v5.8.0 built for cygwin-multi-64int When I request a module documentation, say by $ perldoc File::Find perldoc complains Ignored /usr/lib/perl5/5.8.0/File/Find.pm: unreadable Although the file seems to have correct permission rights $ ls -l /usr/lib/

Re: perldoc prints control characters

2003-04-05 Thread Harald . Maier . BW
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > In perl-5.8.0-2 perldoc is patched to always use the -t switch, > your perldoc is not the perldoc from perl-5.8.0-2. Uups, you are right. It was a 4 year old perldoc from /usr/local/bin. I have cleaned up the files and now

Re: perldoc prints control characters

2003-04-05 Thread Gerrit P. Haase
Hallo Harald, Am Samstag, 5. April 2003 um 13:50 schriebst du: > If I run the following command: > $ perldoc Getopt::Long > Then I get too printed the nasty control characters, e.g.: > ESC[1mNAMEESC[0m > Getopt::Long - Extended processing of command line options

perldoc prints control characters

2003-04-05 Thread Harald . Maier . BW
If I run the following command: $ perldoc Getopt::Long Then I get too printed the nasty control characters, e.g.: ESC[1mNAMEESC[0m Getopt::Long - Extended processing of command line options I am not sure if this is related to perl 5.8.0-2 I looked into my

Problem with perldoc output (was: Re: two problems w/ new perl encountered)

2003-03-17 Thread Gerrit P. Haase
t;> >> > Is there a way to dump the exact pipeline that perldoc uses? >> > It says something in the man page about nroff, etc ... >> > Does it use nroff or groff? >> >> /usr/bin/nroff >> >> From perldoc -h: >> >> Options: >&

Re: less-378-1 : ANSI escape sequences in perldoc output

2003-01-15 Thread Tommy Butler
Christopher Faylor wrote: >>However, following the link to msg00511.html doesn't correlate: > > This should now be fixed. We had a mysterious out-of-disk-space condition > that caused some archive corruption. HOORAY! -- -Tommy Butler see if I'm online »http://ooopps.sourceforge.net/onli

Re: less-378-1 : ANSI escape sequences in perldoc output

2003-01-14 Thread Christopher Faylor
On Mon, Jan 13, 2003 at 03:32:43PM -0500, [EMAIL PROTECTED] wrote: >Using the cygwin.com search of the email archives just now to verify >the pointer has shown *something* is amiss at least. Searching for >'perldoc' in January returns: > >Christopher Faylor - Re:

RE: less-378-1 : ANSI escape sequences in perldoc output

2003-01-13 Thread Robert Praetorius
> If this one doesn't move before you get there, this should help. If it > seems unrelated to your plight, "search the archives!" ;-) Just use > google or gmane instead of cygwin.com! ;-) Catch 22 here. Assuming the relevant search terms are perldoc le

RE: less-378-1 : ANSI escape sequences in perldoc output

2003-01-13 Thread [EMAIL PROTECTED]
written a new shuffle routine for the email archives. But then again, maybe they have. Using the cygwin.com search of the email archives just now to verify the pointer has shown *something* is amiss at least. Searching for 'perldoc' in January returns: Christopher Faylor - Re: less-3

RE: less-378-1 : ANSI escape sequences in perldoc output

2003-01-13 Thread jurgen . defurne
ROTECTED]" http://sources.redhat.com/ml/cygwin/2003-01/msg00211.html Larry Original Message: - From: [EMAIL PROTECTED] Date: Fri, 10 Jan 2003 15:53:29 +0100 To: [EMAIL PROTECTED] Subject: less-378-1 : ANSI escape sequences in perldoc output Hello, After upgrading to less 3.78-1, ANSI escape s

Re: less-378-1 : ANSI escape sequences in perldoc output

2003-01-10 Thread Christopher Faylor
On Fri, Jan 10, 2003 at 10:52:51AM -0500, [EMAIL PROTECTED] wrote: >The email archives is your friend: Well, we used to be friends but, yesterday, I was like talking to my friend Gmane and I just said something like "Those email archives are slow" and, like, the email archives overheard? And the

RE: less-378-1 : ANSI escape sequences in perldoc output

2003-01-10 Thread [EMAIL PROTECTED]
The email archives is your friend: http://sources.redhat.com/ml/cygwin/2003-01/msg00211.html Larry Original Message: - From: [EMAIL PROTECTED] Date: Fri, 10 Jan 2003 15:53:29 +0100 To: [EMAIL PROTECTED] Subject: less-378-1 : ANSI escape sequences in perldoc output Hello

less-378-1 : ANSI escape sequences in perldoc output

2003-01-10 Thread jurgen . defurne
Hello, After upgrading to less 3.78-1, ANSI escape sequences are visible in the output of perldoc. I do not have this problem with the 'man' command. I tried to have a look at perldoc itself, but I am not that fresh anymore. Anyway, this is not priority stuff, maybe someone of you h

Re: perl 5.8.1: perldoc perl fails

2002-12-28 Thread Jörg Schaible
Hi Gerrit, > perldoc perl.pod works well Meanwhile I found out that too. > Yes, please fix it :-) rm /bin/perl.exe > I just figured that calling: perldoc perl.pod works well. > I tried to understand what happens in the perldoc script > and I have no idea why it doesn&#x

Re: perl 5.8.1: perldoc perl fails

2002-12-27 Thread Gerrit P. Haase
he new experimental Perl 5.8.1 release, the command >> >> > $ perldoc perl >> > Can't open /usr/bin/perl: No such file or directory at /bin/perldoc line >> > 206. >> >> perldoc perl.pod works well >> >> > fails to present the Perl manual overview

Re: perl 5.8.1: perldoc perl fails

2002-12-27 Thread Igor Pechtchanski
On Sat, 28 Dec 2002, Gerrit P. Haase wrote: > Hallo Joerg, > > Am Freitag, 20. Dezember 2002 um 17:55 schriebst du: > > > Hi Perl maintainer, > > > using the new experimental Perl 5.8.1 release, the command > > > $ perldoc perl > > Can't open /

Re: perl 5.8.1: perldoc perl fails

2002-12-27 Thread Gerrit P. Haase
Hallo Joerg, Am Freitag, 20. Dezember 2002 um 17:55 schriebst du: > Hi Perl maintainer, > using the new experimental Perl 5.8.1 release, the command > $ perldoc perl > Can't open /usr/bin/perl: No such file or directory at /bin/perldoc line > 206. perldoc perl.pod wo

perl 5.8.1: perldoc perl fails

2002-12-20 Thread Joerg R. Schaible
Hi Perl maintainer, using the new experimental Perl 5.8.1 release, the command $ perldoc perl Can't open /usr/bin/perl: No such file or directory at /bin/perldoc line 206. fails to present the Perl manual overview. Calling the manual pages directly, anything works well: perldoc perlfu