Topic: TEMP file handling (1 of 24), Read 31 times
Conf: VEDIT Beta Test
From: Ian Binnie
Date: Tuesday, January 17, 2006 01:49 AM

I was trying to restore the old Temp file handling

{CONFIG, File handling, Temp file directory} was set to 4.
I changed this to 0 & saved using {CONFIG, Save config}, but every time I reopened Vedit it was back at 4.

I checked using another tool, and the file did indeed seem to have changed.

In the end I manually edited the vedit.cfg found Config( F_TEMP_DIR, "Temp file directory", 4 ), changed this and it seems to work.


While I can see the merit in having local temp files when editing remote (LAN or WAN) files this is something I rarely if ever do.

I think the default should remain as before, while offering the option for those who want it.
I look forward to the new help to see what the 4/26 options mean.

On a related manner I can see no justification for Vedit to create yet another Temp directory.
IMHO it should use %TEMP%, or if felt necessary %TEMP%\Vedit, as other programs do.

Again I think this should be the default, and have changed my VEDIT.INI to VeditTempDir=%TEMP%.
This would be the best for any user putting Vedit on a USB key.

PS I like the new driveless configuration. This will make it easier to try multiple configurations.
Why not make this the default?

 


Topic: Re: TEMP file handling (2 of 24), Read 24 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Tuesday, January 17, 2006 10:23 AM

At 01:49 AM 1/17/2006, you wrote:
>I was trying to restore the old Temp file handling
>
>{CONFIG, File handling, Temp file directory} was set to 4.
>I changed this to 0 & saved using {CONFIG, Save config}, but every time I reopened Vedit it was back at 4.

I check into this and correct it as needed.

>While I can see the merit in having local temp files when editing remote (LAN or WAN) files this is something I rarely if ever do.
>
>I think the default should remain as before, while offering the option for those who want it.
>I look forward to the new help to see what the 4/26 options mean.

A top complaint has long been the existence of temp files in current directory; they show up in the file-open dialog box and this is annoying.
Hence the new default, which has no negative sideeffects, will be the new default.

>On a related manner I can see no justification for Vedit to create yet another Temp directory.
>IMHO it should use %TEMP%, or if felt necessary %TEMP%\Vedit, as other programs do.

I have considered this. I am concerned about huge temp files being left there should there be a problem. This directory is also non-trivial to locate; on the other hand a VEDIT novice wouldn't know that VEDIT is using its own temp directory.

I will therefore ask for other feedback on this. Lets vote...

>PS I like the new driveless configuration. This will make it easier to try multiple configurations.
>Why not make this the default?

Once I have time to change the installation and thoroughly test it, I may very well make it the default.

Ted.

 


Topic: Re: TEMP file handling (4 of 24), Read 25 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Tuesday, January 17, 2006 03:51 PM

On Tue, 17 Jan 2006 10:23:00 -0500, Ted Green wrote:

>At 01:49 AM 1/17/2006, Ian Binnie wrote:
>
>>While I can see the merit in having local temp files when editing
>>remote (LAN or WAN) files this is something I rarely if ever do.
>
>A top complaint has long been the existence of temp files in current
>directory; they show up in the file-open dialog box and this is
>annoying.

And often there is not enough space for the temp file(s) (e.g. on
floppy disks (you know those old fashioned thingies?)) and it is slow.

I prefer the new config: temp files always on a main disk.


>>On a related manner I can see no justification for Vedit to create
>>yet another Temp directory.
>>IMHO it should use %TEMP%, or if felt necessary %TEMP%\Vedit,

Hmmm, it's not easy to decide for me what I like most.

But in the end it seems to be more consistent to have no temp files in
the program (c:\vedit\...) path but in the standard temp.

To be exact: I would prefer %TEMP%\vedit

(What about VEDIT_TEMP? Is that the same? I don't think so.
Perhaps there should be an additional new variable TEMP_FILES or so.)


>I have considered this. I am concerned about huge temp files being
>left there should there be a problem.

That problem exists with every location for temp files.

What about a little macro/function ClearTempDir which deletes all
files in TEMP_FILES older than the last reboot (provided that this
timestamp can be determined easily).
Such a function could be executed manually from time to time.

Or perhaps automatically on startup:
- get date of last boot
- check if own flag file exists in TEMP_FILES
and it is younger than reboot: then do nothing now
- else delete all files here in TEMP_FILES older than boot
- write own flag file here

(Just a quick shot!)


>I will therefore ask for other feedback on this. Lets vote...

Done.


Christian

 


Topic: Re: TEMP file handling (7 of 24), Read 25 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Wednesday, January 18, 2006 11:29 PM

At 03:51 PM 1/17/2006, you wrote:
>What about a little macro/function ClearTempDir which deletes all
>files in TEMP_FILES older than the last reboot (provided that this
>timestamp can be determined easily).
>Such a function could be executed manually from time to time.
>
>Or perhaps automatically on startup:
> - get date of last boot
> - check if own flag file exists in TEMP_FILES
> and it is younger than reboot: then do nothing now
> - else delete all files here in TEMP_FILES older than boot
> - write own flag file here

A simpler way would be to place a command in the "RunOnce" section of the registry which deletes these files on the next reboot.

Ted.

 


Topic: Re: TEMP file handling (8 of 24), Read 28 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, January 19, 2006 03:39 PM

On Wed, 18 Jan 2006 23:29:00 -0500, Ted Green wrote:

>>[Deleting Vedit's temp files automatically]
>
>A simpler way would be to place a command in the
>"RunOnce" section of the registry which deletes
>these files on the next reboot.

Oh, yes the registry. Good idea.
(I don't like the registry and so usually I don't think about using it by myself...)


After playing around with some ideas I'm now no longer thinking that an automatic deletion is a good plan.
It is not easy to make it absolutely foolproof and errorfree.
And deleting files via wildcard may have unwanted results...


Anyway, here are some snippets for other people's playing.

Something like the following may reside in VEDIT's USTARTUP.VDM:


// if the RunOnce entry of Vedit doesn't exist in the registry:
// create it

if (Registry_Get_Item (103, "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Runonce\VeditAuto") == -2) {

//---- first determine the summary size if the files in the temp. directory

// Oops, not so easy, especially if used globally (in different languages)
// (the below used variable TEMP_FILES doesn't exist yet!)
//
// Something like a System("dir TEMP_FILES > outfile", DOS)
// with additional checking of the outfile for the second last line
// e.g. "12 file(s) 12.346.346 Bytes"
// should make it possible.

// if (Summary size greater_than configurable threshold) {

//---- let Windows simply delete the files at next reboot (oh, oh!)
// (the below used variable TEMP_FILES doesn't exist yet!)

Reg_Set(103, TEMP_FILES)
Registry_Set_Item("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Runonce\VeditAuto=cmd /c delete |@(103)\*.*")

//------- or

//---- let Vedit do some work at next reboot
// (the below called macro ClearTemp.vdm has to be created, of course)

Reg_Set(103, VEDIT_EXE)
Registry_Set_Item("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Runonce\VeditAuto=|@(103) -q -x ClearTemp.vdm")

//------- or

//---- let start Explorer at next reboot with the temp. directory in focus
// and let the user decide what to do with the files
// (the below used variable TEMP_FILES doesn't exist yet!)

Reg_Set(103, "%windir%\explorer.exe /e,")
Reg_Set(103, TEMP_FILES, APPEND)
Registry_Set_Item("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Runonce\VeditAuto=|@(103)")

}
}


Use at your own risk!


Christian

 


Topic: Re: TEMP file handling (9 of 24), Read 29 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Thursday, January 19, 2006 04:51 PM

At 03:38 PM 1/19/2006, you wrote:
>After playing around with some ideas I'm now no longer thinking that
>an automatic deletion is a good plan.

Why not. Its seems very reasonable to delete temp files on a reboot.

>Something like the following may reside in VEDIT's USTARTUP.VDM:

Perhaps I should add the registry code into the startup.vdm file (not the optinal ustartup.vdm). Then it will be possible for users to make changes if needed.

----------------

BTW - I have added an installation option for USB drives. It then leaves the drive letter off the directory parameters in vedit.ini. I know that some suggested this as the default, but I also want to "advertise" that VEDIT can be installed on a USB drive.

The interaction between USB drive operation, temp files and the registry becomes "interesting".

If anyone would like to try this, a new test version is at:

www.vedit.com/download/beta/vpw-prod.exe

I am still working on the on-line help...

Ted.

 


Topic: Re: TEMP file handling (11 of 24), Read 28 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Friday, January 20, 2006 02:55 AM

On 1/19/2006 4:51:49 PM, Ted Green wrote:
>At 03:38 PM 1/19/2006, you wrote:
>>After playing around with some ideas I'm now no longer thinking that
>>an automatic deletion is a good plan.
>
>Why not. Its seems very reasonable to delete temp
>files on a reboot.

Your way of doing this (in the other message) seems to be save (that was my biggest fear: delete too much).


>----------------
>
>BTW - I have added an installation option for USB drives.

>If anyone would like to try this, a new test version is at:
>www.vedit.com/download/beta/vpw-prod.exe

That one seems to have the [OPTION] bug fixed. Good!

Christian

 


Topic: Re: TEMP file handling (13 of 24), Read 30 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Friday, January 20, 2006 10:08 AM

At 02:56 AM 1/20/2006, you wrote:

>That one seems to have the [OPTION] bug fixed. Good!

Yes, most things we have discussed are fixed.
There is still a problem with split window editing when rulers are enabled. :-(

Ted.

 


Topic: Re: TEMP file handling (12 of 24), Read 26 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Friday, January 20, 2006 07:57 AM

On 1/19/2006 4:51:49 PM, Ted Green wrote:

>BTW - I have added an installation option for USB drives.
>
>The interaction between USB drive operation, temp files
>and the registry becomes "interesting".

I can imagine...


The USB thing isn't so easy to test for me:
I'll have to use a PC without VEDIT installed to be sure all works from USB drive.

But where should I find a PC *without* VEDIT??? ;-)


>If anyone would like to try this, a new test version is at:
>
>www.vedit.com/download/beta/vpw-prod.exe

A first test worked fine here!


Christian

 


Topic: Re: TEMP file handling (14 of 24), Read 27 times
Conf: VEDIT Beta Test
From: Ian Binnie
Date: Saturday, January 21, 2006 01:33 AM

On 1/19/2006 4:51:49 PM, Ted Green wrote:
>
>BTW - I have added an
>installation option for USB
>drives. It then leaves the
>drive letter off the directory
>parameters in vedit.ini. I
>know that some suggested this
>as the default, but I also
>want to "advertise" that VEDIT
>can be installed on a USB
>drive.
>
>The interaction between USB
>drive operation, temp files
>and the registry becomes
>"interesting".
>
>If anyone would like to try
>this, a new test version is
>at:
>
>www.vedit.com/download/beta/vp
>w-prod.exe
>
>I am still working on the
>on-line help...
>
I loaded the new VEDIT (32-Bit) Ver. 6.15.1 01/18/06 using the USB option.

It worked well, even if loading was a little slow (my USB key is not the fastest).

A couple of comments:-

I did not load Vedit into the Registry.
This should probably be the default if USB option is used, but an intelligent user should know not to do this.

I noted that vedit.ini contained:-
VeditTempDir=\vedit\temp

I changed this to %TEMP%. (It would be far too slow if temporary files were in the USB key - mine writes at about 64kbps.)

I noted that vedit.cfg contained:-
Config( F_TEMP_MODE, "Temp file creation options", 2 )
Config( F_TEMP_DIR, "Temp file directory", 2 )
I am not sure what these do, but did not experiment.

Config( U_AUTO_CFG, "Auto-save config", 1 )
It would seem to be best to set to 0 - it is always possible to manually save if you want to change configuration.

I was running with -kr, as there seems to be little reason to save recent files on an external computer.
I found this a little strange, missing the list of Most Recently Used files in the {FILE} menu while I was editing.
I will have to play with this setting, and see what I like.

It would be good if Vedit could save a working copy of vedit.ini in the temporary directory, if invoked with -kr or a RO vedit.ini, so MRU would be available until exiting Vedit.

Like Christian, I have not tested on a computer without Vedit.

PS The Version Property is still 6.13.1
I include a version.h in all my programs, so there is only one place to change it, and I can't forget.
I include this in the .rc file

 


Topic: Re: TEMP file handling (15 of 24), Read 30 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Saturday, January 21, 2006 10:33 AM

At 01:34 AM 1/21/2006, you wrote:
>A couple of comments:-
>
>I did not load Vedit into the Registry.
>This should probably be the default if USB option is used, but an intelligent user should know not to do this.

Hmmm. Forgot about that. I should say "Removable USB drive" and state that it will not be added to the registry.

>I noted that vedit.ini contained:-
>VeditTempDir=\vedit\temp
>
>I changed this to %TEMP%. (It would be far too slow if temporary files were in the USB key - mine writes at about 64kbps.)

I haven't changed the default to %TEMP%/vedit yet.

>I noted that vedit.cfg contained:-
>Config( F_TEMP_MODE, "Temp file creation options", 2 )
>Config( F_TEMP_DIR, "Temp file directory", 2 )

Don't know how F_TEMP_DIR could get set to 2, it defaults to 4.

>Config( U_AUTO_CFG, "Auto-save config", 1 )
>It would seem to be best to set to 0 - it is always possible to manually save if you want to change configuration.

I'll consider that.

>I was running with -kr, as there seems to be little reason to save recent files on an external computer.
>I found this a little strange, missing the list of Most Recently Used files in the {FILE} menu while I was editing.
>I will have to play with this setting, and see what I like.

Don't fully agree with you here. A consultant is likely to repeatedly plug the USB drive into the same computer.

>It would be good if Vedit could save a working copy of vedit.ini in the temporary directory, if invoked with -kr or a RO vedit.ini, so MRU would be available until exiting Vedit.

Yes, I have been thinking the same thing, especially when VEDIT is run from a CDROM.

>PS The Version Property is still 6.13.1

Grrr. I thought I had fixed it. It is fixed now.

Thank you for your thoughts and feedback.

Ted.

 


Topic: Re: TEMP file handling (19 of 24), Read 25 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Tuesday, January 24, 2006 11:10 PM

At 01:34 AM 1/21/2006, you wrote:
>A couple of comments:-
>I did not load Vedit into the Registry.
>This should probably be the default if USB option is used, but an intelligent user should know not to do this.

Done. The USB option also does not create a new program group nor icons. In other words, you can repeat the installation onto a USB drive without ruining your current installation.

>I noted that vedit.ini contained:-
>VeditTempDir=\vedit\temp
>
>I changed this to %TEMP%. (It would be far too slow if temporary files were in the USB key - mine writes at about 64kbps.)

This will be changed soon.

>Config( U_AUTO_CFG, "Auto-save config", 1 )
>It would seem to be best to set to 0 - it is always possible to manually save if you want to change configuration.

Since the changes are saved onto the USB drive, I think Auto-save is fine as the default.

>It would be good if Vedit could save a working copy of vedit.ini in the temporary directory, if invoked with -kr or a RO vedit.ini, so MRU would be available until exiting Vedit.

Still working on this, especially when running from a CDROM.

Ted.

 


Topic: Re: TEMP file handling (16 of 24), Read 24 times
Conf: VEDIT Beta Test
From: Ian Binnie
Date: Sunday, January 22, 2006 06:16 PM

On 1/19/2006 4:51:49 PM, Ted Green wrote:
>At 03:38 PM 1/19/2006, you
>wrote:
>


>www.vedit.com/download/beta/vp
>w-prod.exe

Is this available by ftp?

 


Topic: Re: TEMP file handling (17 of 24), Read 25 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Sunday, January 22, 2006 06:41 PM

At 06:17 PM 1/22/2006, you wrote:

>>www.vedit.com/download/beta/vpw-prod.exe
>Is this available by ftp?

No, no one has requested downloads via ftp in many years.

Ted.

 


Topic: Re: TEMP file handling (18 of 24), Read 27 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Monday, January 23, 2006 02:55 AM

On 1/22/2006 6:41:56 PM, Ted Green wrote:
>At 06:17 PM 1/22/2006, Ian wrote:
>
>>>www.vedit.com/download/beta/vpw-prod.exe
>>Is this available by ftp?
>
>No, no one has requested downloads via ftp in many years.

Oh, FTP would be nice!

For example then we could see the last-changed-date of the files. Especially helpful for beta testing.


Christian

 


Topic: Re: TEMP file handling (10 of 24), Read 30 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Thursday, January 19, 2006 05:28 PM

Here is my current thinking:

* The default temp directory will be %TEMP%\vedit.

* The startup.vdm will make sure that the specified temp directory exists,
creating the %TEMP%/vedit subdirectory if needed.

* Startup.vdm will check that the file "vedit-cleanup.bat" exists in the
%TEMP% directory. If not, it will create the file to contain:

del /q vedit\*

* Startup.vdm will ensure that the registry "RunOnce" section has an item like:

VEDIT_Cleanup=cmd /y /c "c:\documents and settings\name\local settings\temp\vedit-cleanup.bat"

----------

This handles several cases:

* Running VEDIT directly from a CDROM where the %TEMP% directory must be used and VEDIT was never installed.

Even if VEDIT is only run one single time, all temp files will be removed on the next reboot.

* Similarly, VEDIT can be run from a USB drive.

* The "del /q vedit\*" command is safe! Even if the Windows environment variables somehow got corrupted, this command could not delete anything else.

Ted.

 


Topic: Re: TEMP file handling (5 of 24), Read 25 times
Conf: VEDIT Beta Test
From: Ian Binnie
Date: Tuesday, January 17, 2006 06:33 PM

On 1/17/2006 10:23:16 AM, Ted Green wrote:
>At 01:49 AM 1/17/2006, you
>wrote:
>A top complaint has long been
>the existence of temp files in
>current directory; they show
>up in the file-open dialog box
>and this is annoying.
>Hence the new default, which
>has no negative sideeffects,
>will be the new default.
>
There seems to be a deep feeling behind this - so be it.
I was influenced by "Since this is inefficient when editing huge files on other local drives"


>>On a related manner I can see no justification for Vedit to create yet another Temp directory.
>>IMHO it should use %TEMP%, or if felt necessary %TEMP%\Vedit, as other programs do.
>
>I have considered this. I am
>concerned about huge temp
>files being left there should
>there be a problem.

Other programs do this why should Vedit feel guilty?
Actually Vedit seems much better behaved in leaving temp files behind.

One of my routines is cleaning out "temp" files. It is easier if they are all in the one place.

>This
>directory is also non-trivial
>to locate;

I have never tried to do this in a program, but:-
VeditTempDir=VeditTempDir=%TEMP%
works, and will be essential for USB or CD installations.

>I will therefore ask for other
>feedback on this. Lets vote...
>
Provided the configuration option is there I guess it won't affect most users, but I will use %TEMP%

 


Topic: Re: TEMP file handling (6 of 24), Read 26 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Tuesday, January 17, 2006 06:42 PM

At 06:34 PM 1/17/2006, you wrote:
>>>On a related manner I can see no justification for Vedit to create yet another Temp directory.
>>>IMHO it should use %TEMP%, or if felt necessary %TEMP%\Vedit, as other programs do.
>>
>>I have considered this. I am concerned about huge temp files being left there should
>>there be a problem.
>
>Other programs do this why should Vedit feel guilty?
>Actually Vedit seems much better behaved in leaving temp files behind.
>
>One of my routines is cleaning out "temp" files. It is easier if they are all in the one place.
>
>>This >directory is also non-trivial >to locate;
>
>I have never tried to do this in a program, but:-
>VeditTempDir=VeditTempDir=%TEMP%
>works, and will be essential for USB or CD installations.

I have already changed the installation to allow this, but am still waiting for more feedback before making it the default.

Ted.

 


Topic: Re: TEMP file handling (3 of 24), Read 25 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Tuesday, January 17, 2006 11:59 AM

At 01:49 AM 1/17/2006, you wrote:
>I was trying to restore the old Temp file handling
>
>{CONFIG, File handling, Temp file directory} was set to 4.
>I changed this to 0 & saved using {CONFIG, Save config}, but every time I reopened Vedit it was back at 4.

Fixed.

>Again I think this should be the default, and have changed my VEDIT.INI to VeditTempDir=%TEMP%.
>This would be the best for any user putting Vedit on a USB key.

Awaiting everyone's vote....

Ted.

 


Topic: problem with Spy Sweeper (20 of 24), Read 19 times
Conf: VEDIT Beta Test
From: Rich Hureau
Date: Friday, May 19, 2006 08:41 AM

I have just started using the anti-spyware program Spy Sweeper. Every time I boot my system and then start Vedit, Spy Sweeper reports to me that I am running a NEW program in the system startup routines called vedit-cleanup.bat. It has options to remove it, keep it (which I do), etc.

It seems that this is caused because this routine is in a temp dir and gets recreated over and over. I see from this thread that this is deliberate, but I don't want to wade thru the whole issue to really understand it. :-(

I do not want to disable this function in Spy Sweeper, nor do I want to disable it in Vedit. Any way to get it to stop giving this error message (e.g. make it permanent)?

 


Topic: Re: problem with Spy Sweeper (21 of 24), Read 15 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Friday, May 19, 2006 04:33 PM

On Fri, 19 May 2006 08:41:00 -0400, Rich Hureau wrote:

>I have just started using the anti-spyware program Spy Sweeper.
>Every time I boot my system and then start Vedit, Spy Sweeper
>reports to me that I am running a NEW program in the system
>startup routines called vedit-cleanup.bat.

Rich:

The reason seems to be that VEDIT's File_Copy() command - used in
STARTUP.VDM to create that file - changes the file's date to "now".

File_Copy("|(HOME)\vcleanup.cmd","|@(103)\vedit-cleanup.bat",NOERR+OK)

That indeed is not so good - not only in this case.

One possible workaround would be to change STARTUP.VDM to use Sys()
and Windows own copy command.

Something like (untested!!!):

Sys('copy "|(HOME)\vcleanup.cmd |@(103)\vedit-cleanup.bat" ',
DOS+SIMPLE)


Better would it be to enhance VEDIT to leave the file date untouched.


Ted:

Just for your info: I already suggested that change to File_Copy()
some time ago and you wrote it to your list.


Christian

 


Topic: Re: problem with Spy Sweeper (22 of 24), Read 14 times
Conf: VEDIT Beta Test
From: Rich Hureau
Date: Saturday, May 20, 2006 07:39 AM

Christian,
Thanks for the info. I guess I can live with it for now. Hopefully the change you suggested will be included in a later release. :-)

Rich

 


Topic: Re: problem with Spy Sweeper (23 of 24), Read 14 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Monday, May 22, 2006 04:47 PM

At 08:41 AM 5/19/2006, you wrote:
>I do not want to disable this function in Spy Sweeper, nor do I want to disable it in Vedit. Any way to get it to stop giving this error message (e.g. make it permanent)?

As Christian Ziemski explained, the problem is that VEDIT File_Copy() command changes the time/date stamp. We will fix that this week and the next release will have this problem fixed.

Ted.

 


Topic: Re: problem with Spy Sweeper (24 of 24), Read 14 times
Conf: VEDIT Beta Test
From: Rich Hureau
Date: Monday, May 22, 2006 10:02 PM

Ted,
Sounds good! :-)