Topic: File Open (Starting @ EOF) - Large file. (1 of 8), Read 24 times
Conf: Startup, File Open, Exit
From: Jim Fay
Date: Thursday, March 30, 2006 04:37 PM

Wondering if anyone knew of a way to have vedit open a file starting at the end-of-file.

Work w/ data files as large as 16GB from an outside source and sometimes use vedit to view the last record, to confirm complete. Would save time, if could open file at the end.

Thanks,
-JIM

 

Topic: Re: File Open (Starting @ EOF) - Large file. (2 of 8), Read 27 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Thursday, March 30, 2006 06:46 PM

At 04:37 PM 3/30/2006, you wrote:
>Wondering if anyone knew of a way to have vedit open a file starting at the end-of-file.
>
>Work w/ data files as large as 16GB from an outside source and sometimes use vedit to view the last record, to confirm complete. Would save time, if could open file at the end.

Simple, invoke with the command:

vpw -b -c"eof" filename

The "-b" enables browse-only mode.
The "-c" specifes the startup command(s).

With a file that large, you need the VEDIT Pro64:

vpw64 -b -c"eof" filename

Ted.

 

Topic: Re: File Open (Starting @ EOF) - Large file. (3 of 8), Read 33 times
Conf: Startup, File Open, Exit
From: Jim Fay
Date: Friday, March 31, 2006 02:06 PM

That works, but it takes 9minutes, before the file opens (as if its reading thru the file). I was hoping it would (behind the scenes) read the file property byte size & start from the end & open the file immediately @ the eof (without loading the whole file -- as it does w/out
-c"eof", from the beginning). This might not be a wish that makes since.

I'm using VEDIT Pro (64-bit) Ver 6.13.1. Running WindowsXP(sp2).

Thanks,
-JIM

 

Topic: Re: File Open (Starting @ EOF) - Large file. (4 of 8), Read 39 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Friday, March 31, 2006 02:25 PM

At 02:07 PM 3/31/2006, you wrote:
>That works, but it takes 9minutes, before the file opens (as if its reading thru the file). I was hoping it would (behind the scenes) read the file property byte size & start from the end & open the file immediately @ the eof (without loading the whole file -- as it does w/out
>-c"eof", from the beginning). This might not be a wish that makes since.
>I'm using VEDIT Pro (64-bit) Ver 6.13.1. Running WindowsXP(sp2).

I tried it on a huge file and it opened instantly.
Be sure {CONFIG, File handling, Enable fast browse mode} is checked.

Of course, the Line: number should then read "????" as it did not
count the lines.

Your 9-minute delay indicates it did not open in fast-browse mode.

Ted.

 

Topic: Re: File Open (Starting @ EOF) - Large file. (5 of 8), Read 27 times
Conf: Startup, File Open, Exit
From: Jim Fay
Date: Monday, April 03, 2006 10:40 AM

That was my problem (didn't check "Enable fast browse mode"). Tried this & my large file opened instantly @ eof.

Thanks,
-JIM

 

Topic: Re: File Open (Starting @ EOF) - Large file. (6 of 8), Read 17 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Monday, April 03, 2006 11:37 AM

At 10:40 AM 4/3/2006, you wrote:That was my problem (didn't check "Enable fast browse mode"). Tried this & my large file opened instantly @ eof.

Glad that solved it.
Since that is the default setting, you need to prevent Gremlins from changing settings in the middle of the night. ;-))

Ted.

 

Topic: Re: File Open (Starting @ EOF) - Large file. (7 of 8), Read 14 times
Conf: Startup, File Open, Exit
From: Pauli Lindgren
Date: Tuesday, April 04, 2006 03:13 AM

On 3/31/2006 2:25:50 PM, Ted Green wrote:
>
>Your 9-minute delay indicates it did not open in fast-browse mode.

It might be good idea to have some kind of progress bar when slow operations like this are performed, instead of just the text "Waiting for disk". And maybe text on status line saying something like "Scanning for newlines".

--
Pauli

 

Topic: Re: File Open (Starting @ EOF) - Large file. (8 of 8), Read 12 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Tuesday, April 04, 2006 10:50 AM

At 03:14 AM 4/4/2006, you wrote:
>It might be good idea to have some kind of progress bar when slow operations like this are performed, instead of just the text "Waiting for disk". And maybe text on status line saying something like "Scanning for newlines".

Tom worked several months on implementing a progress bar, but ended up with too many strange problems for us to release it. We will work on it again (it is a compilation option.)

Ted.