HP3000-L Archives

June 2002, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Fri, 14 Jun 2002 14:55:33 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Roy...great minds think alike :)
> Fair enough, but it *doesn't* move me to the nearest line to 100 - it leaves
> the '*' line exactly where it was. So why not 'Error: No Line'?
>
> Can I get 'L' to do what I want, or are there drawbacks in this?

I was fighting that problem this weekend, after texting in a 100,000+ line
file.

In my case, QEDIT assigned non-predictable line numbers (e.g., 1.003, 1.027),
so I could'nt even say "list X.01".  (I submitted an enhancement request to
default the line number increment to integral divisors of 1, rather than
to the closed possible value.)

However, I have a workaround for you, which doesn't require using the VI cmd:

To list the line closest to 100, try:

   list 100+1

The drawback there is that if 100 *existed*, you won't see it.

So, try:

   list 100/100+1

Hope that helps!

Stan
--
Stan Sieler
           [log in to unmask]
www.allegro.com/sieler/wanted/index.html
       www.allegro.com/sieler

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2