Command window history not updated 1

[sebes]

Hi all,

I use RESOURCE=OFF in my config.fpw to avoid creating FOXUSER.* files.
This is good for that purpose BUT I think it also stops updating _command.prg with the new commands I type or are echoed in command windows.
Is this possible ?

Is there a way to avoid the creatin of FOXUSER.* and in the same time update _command.prg ?

Thanks

 

[Mike Lewis]

Doesn't look like it.

This is from the Help file:

The contents of the Command window are saved to a file, _command.prg, automatically unless the noRecentDocHistory system policy is enabled or you are not using a FoxUser resource file.

So, if you can get past the double negatives, it looks like the same setting controls both the resource file and the _Command.PRG file.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy

 

[TamarGranor]

Why would you want to avoid creating a FoxUser file in the development environment? It's so handy to position things where you want them and know that the next time you open them, they're where you left them.

Tamar

 

[Dan Freeman]

I haven't used a FoxUser file since FPD since they cause so many flaky problems.

And, FWIW, I have no problem at all with _command.prg and command windows history. They're not linked.

 

[Mike Lewis]

Well, each to his own. Personally, I hate it when I lose the resource files (in the development environment). It means that I lose all my carfully-docked Command, Properties, Document View and Data Session windows.

It's another matter when running in a distributed application, of course.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy

 

[Dan Freeman]

Well, I spent so many years in training rooms moving from new installation to new installation and always having "virgin" VFP so it would agree with what students were seeing on their machines I just learned to work that way. <shrug>