Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

This is a bug in the way perldoc interacts with groff (it first appeared in Red Hat Linux 8.0, becuase this is the first version with UTF-8 support), it is fixed in the latest rawhide version of Red Hat Linux (which means the fix will be in the next release), but in the meantime the easiest way to work around it is to set the environment variable LESS to 'isr'.

There are several ways you can do this:

For bash, add to your .bashrc: export LESS='isr'

For csh or tcsh, add your .cshrc or .tcshrc: setenv LESS isr

Or you can just specify it on the command line when you run perldoc: LESS=isr perldoc perlop

Update: I should mention that only the -r option is really necessary to fix this problem, I just used -isr because that's what I have in my own settings, -i tells less to be case-insensitive when searching, and -s says to compress runs of multiple blank lines to a single blank line. The -r option causes the formatting escape codes to be passed through directly to the terminal.

Update: Oops, has nothing to do with UTF-8, it's caused by new options in groff... The bugzilla.redhat.com entry has some more information.


We're not surrounded, we're in a target-rich environment!

In reply to Re: Perldoc Problem: Linux or Perl? by jasonk
in thread Perldoc Problem: Linux or Perl? by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (3)
As of 2024-04-25 23:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found