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:
Francois Desrochers <[log in to unmask]>
Reply To:
Date:
Fri, 14 Jun 2002 14:17:20 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
Roy Brown wrote:

> 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'?

To be honest, I don't know exactly why this is not an error. If it were an
error, the following command would stop immediately and not list lines 200
and 300:

   /List 100,200,300

Again, is this good or bad?

> There doesn't seem to be any way I can find to change this behaviour,
> either in List or Set List, though I might have missed some other
> setting that will do it..

There is no way to change this at the moment.

> A colleague has kindly pointed me to 'VI 100' - which
> *will* start its display from the next nearest line after 100 without
> complaint, when 100 doesn't exist. Although this difference doesn't seem
> to be documented in the QEdit manual..... :-(

Here is the difference: when you enter "/List 100", you are requesting one
specific line. When you enter "/Vi 100", you are requesting one or more
lines (as specified by the Set Vis Above and Below settings) around line
100. Line 100 is only a reference point. Similarly, "/L 100/" would also
work as you are specifying the starting point.

> Can I get 'L' to do what I want, or are there drawbacks in this?

As mentioned above, there is no way to change this behavior at the moment.
We can change it in a future version however. For compatibility reasons, the
current behavior would be the default and the "new" behavior would have to
be enabled via a Set command. For example:

    /Set List Nearest On

If you think the current behavior should generate an error instead of a
warning, let me know. Again, this would be a settable option. For example,

    /Set List Nolineerror On

Tracy Pierce replied:
> Ray presents a helpful hint, but imho Roy makes a valid
> point, and the correct and quite correctable behavior would be
> "Warning: no line" followed by the near-as-possible response of
> displaying line 100+1. I bet Robelle is watching, and will have a custom
> tape ready for Roy before this thread dies.

Yes, we are watching! And listening. Unfortunately, the custom tape is not
ready yet. How about first thing tomorrow morning? ;-)

Seriously, since at least 2 people think this is not correct behavior, we'll
consider it for the next release. If someone else wants this functionality,
please let us know. Send an email to [log in to unmask] and mention this
thread.

Francois Desrochers
Robelle Solutions Technology Inc.
email: francois<dot>desrochers<at>robelle<dot>com

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

ATOM RSS1 RSS2