public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] debugging init scripts
Date: Mon, 16 Jul 2007 11:28:17 +0930	[thread overview]
Message-ID: <1184551097.6934.41.camel@orpheus> (raw)
In-Reply-To: <20070716021336.7f8da8e6@gadget.local.net>

On Mon, 2007-07-16 at 02:13 +0100, Ian Hastie wrote:
> On Mon, 16 Jul 2007 09:37:26 +0930
> Iain Buchanan <iaindb@netspace.net.au> wrote:
> 
> > it's a funny workaround, but sometimes you have to type
> > 
> > cat file | less
> > 
> > to stop less being "intelligent".  Or you could disable it's input
> > preprocessor:
> > 
> > LESSOPEN="" less /usr/bin/echo-client-2
> 
> Or you can use the -L, aka --no-lessopen, switch.  It does the same
> thing, but with less typing...
> 
> : -L or --no-lessopen
> :               Ignore  the  LESSOPEN  environment  variable  (see
> : the  INPUT PREPROCESSOR section below).  This option can be set from
> : within less, but it will apply only  to  files opened subsequently,
> : not to the file which is currently open.

ahh, thanks.  I searched the options for "input preprocessor", but it's
formatted "INPUT<space><space>PRE-" in my particular terminal, so less
didn't locate a match until the Input Preprocessor seciton, which
doesn't mention the option!

thanks,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Matz's Law:
	A conclusion is the place where you got tired of thinking.

-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2007-07-16  2:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 15:32 [gentoo-user] debugging init scripts Frank Wilson
2007-07-12 16:15 ` Uwe Thiem
2007-07-12 17:06   ` Thomas Tuttle
2007-07-16  0:07     ` Iain Buchanan
2007-07-16  1:13       ` Ian Hastie
2007-07-16  1:58         ` Iain Buchanan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1184551097.6934.41.camel@orpheus \
    --to=iaindb@netspace.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox