home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!news2.cis.umn.edu!gopher-news-request@boombox.micro.umn.edu
- Message-ID: <9207221650.AA25931@boombox.micro.umn.edu>
- Date: Wed, 22 Jul 92 12:38:41 EDT
- From: BDESIMON@uga.cc.uga.edu (bert desimone)
- Subject: Is Less Really More?
- Original-To: Gopher Folks <gopher-news@boombox.micro.umn.edu>
- Newsgroups: alt.gopher
- Distribution: alt
- Sender: news@news2.cis.umn.edu
- Approved: alt.gopher@news.cis.umn.edu
- Lines: 28
-
- A colleague of mine has noticed an interesting little problem with the
- Unix Gopher client and the PAGER_COMMAND. It goes like this...
-
- OK, let's say you have an environment varaible set for PAGER. Some
- people like to set this to less so that man and other utilites that
- look for this variable will use less. Now, you leave the PAGER_COMMAND
- for the Gopher client -- set in conf.h -- as more. Crank up Gopher,
- and behold the Pager command. It is less. No problem?? Well, there
- seem to be a few. The main one has to do with the way that less
- handles, or rather doesn't handle, the character sequences used for
- toggling screen highlighting for search terms in retrieved documents.
- Instead of the highlighting action taking place, the highlighting
- characters are displayed (..this is the ^[[7mterm^[[m searched for..).
-
- So, you say, don't use less. But, even if you change the Pager Command
- to more within the client (shift-o) the Pager Command is not written
- to .gopherrc like Telnetcmd, Mailcmd, etc.
-
- If I may be so bold as to suggest a change, have Gopher not read the
- PAGER environment variable and save Pagercmd in .gopherrc like
- Telnetcmd, Mailcmd, etc. In addition, an environment variable for
- GOPHER_PAGER could be added, like GOPHER_TELNET, GOPHER_MAIL, etc.
-
- ---------------------------------------
- | Albert DeSimone, Jr. |
- | BITNET: bdesimon@uga |
- | Internet: bdesimon@uga.cc.uga.edu |
- ---------------------------------------
-