tcDirFrq.txt

[lneam]

hi,

with last version tc1100 b2, i removed both commands
- FrequentlyUsedLen=0
- DirUsageLocation=0
and there is no saved file tcDirFrq.txt

can any one confirm this ?

into > configuration > operation > save on exit
all of 4 options is OFF. But that was in the same wincmd.ini from version of totalcmd 1052. I have backup file

[AntonyD]

I have the opposite situation and this makes it even more incomprehensible.
I have set
ShowFrequentlyUsed=0
FrequentlyUsedLen=0
and now at the next opening for control of the file tcDirFrq.txt (which suddenly does exist!) - instead of emptiness,
because I forbade any records to be created there - I see more than 30 such records.
This new feature is starting to piss me off.
There must be a real option and available from the "GUI interface" of settings wizard, which simply disables the even FACT of maintaining of such list!
And not as it is now - specify the wrong path or set 0 records for storage. These are all "Workarounds", not solutions.

P.S. Yes, looks like Totals is constantly internally updates this list and upon the exit - re-saves this file on a disk. Of course - because there is only ONE gui 'option'/checkbox for saving history of dirs - and the regular items so and Freq.UsedDirs. Which are both simultaneously being saved in the appropriate files. Which is a bad design of course.
Again: history of FreqUsedDirs should NOT be collected/updated during TC working state and saved upon the exit. And vice versa - regular history of visited dirs should be collected/updated during TC working state and saved upon the exit.

[Hacker]

lneam,

into > configuration > operation > save on exit
all of 4 options is OFF

there is no saved file tcDirFrq.txt

That is the expected behavior of b2.

HTH
Roman

[lneam]

lneam,

into > configuration > operation > save on exit
all of 4 options is OFF

there is no saved file tcDirFrq.txt

That is the expected behavior of b2.

HTH
Roman

thanks

[ghisler(Author)]

I have the opposite situation and this makes it even more incomprehensible.
I have set
ShowFrequentlyUsed=0
FrequentlyUsedLen=0
and now at the next opening for control of the file tcDirFrq.txt (which suddenly does exist!) - instead of emptiness,
because I forbade any records to be created there - I see more than 30 such records.

These two values are just about SHOWING the frequently used entries. They are not about saving them.
You need to either disable saving "history" on exit as lneam reported, or set
DirUsageLocation=0
if you want to have a directory history but no tcDirFrq.txt.

[Stefan2]

I have the opposite situation and this makes it even more incomprehensible.
I have set
ShowFrequentlyUsed=0
FrequentlyUsedLen=0
and now at the next opening for control of the file tcDirFrq.txt (which suddenly does exist!) - instead of emptiness,
because I forbade any records to be created there - I see more than 30 such records.

These two values are just about SHOWING the frequently used entries. They are not about saving them.
You need to either disable saving "history" on exit as lneam reported, or set
DirUsageLocation=0
if you want to have a directory history but no tcDirFrq.txt.

2ghisler(Author)

Why the name "DirUsageLocation" ? why not start the name with "FrequentlyUsed" ?
And use "FrequentlyUsedShow" instead of "ShowFrequentlyUsed".


Right now
ShowFrequentlyUsed=0
FrequentlyUsedLen=0
DirUsageLocation=0

me think better would be to be consistently
FrequentlyUsedDirsShow=0 ------- 1: Enable the view additional the old history list.
FrequentlyUsedDirsShowLen=0 -- 20: How many to show in that list.
FrequentlyUsedDirsLogPath=0 --- storage location of most frequently used directories file tcDirFrq.txT,
default to %LOCALAPPDATA%\GHISLER\ ; use e.g. 0 to disabled the creation of that file.
This will store the last 200 ((*)) dirs in that text file.

And "tcFreqDirs.txt" instead of "tcDirFrq.txt"

((*)) is 200 correct?
I think I have read it like this?





 

[jinsight]

Support++ the naming conventions suggested by Stefan2

[lneam]

Support++ the naming conventions suggested by Stefan2

me too

[tuska]

Since there are already many setting options that contain the word "history", e.g.

SaveHistory
ReverseHistory
HistoryLen
HistoryLenStored
HistoryCut
HistoryThinning
HistoryThinningDelta

it is questionable for me whether, in the case of a possible change of the new terms
- even if the name is significantly lengthened again - the term "History" should be
be placed in front of the new setting names.

One advantage would be that when searching in Help - F1 after entering the search term "History"
you would find all the parameters, including the new ones.

For example:
HistoryShowFrequentlyUsed
HistoryFrequentlyUsedLen
HistoryFrequentlyUsedDirsPath
HistorytcDirFrq.txt

[Horst.Epp]

Support++
for tuskas version.

[Dalai]

Keep in mind that renaming options that have existed for years calls for trouble, i.e. people complaining (rightfully so) that TC changed a setting on its own without the user's consent or knowledge. To avoid that TC would have to support both the old term and the new one. Is that worth the added complexity and maybe confusion among users?

To be clear, I'm not saying prefixing multiple options of the same category with that category's name doesn't have an advantage. But it's not that the CHM help system doesn't have a search feature either. Sure, the split of all wincmd.ini options into multiple pages a couple of years ago makes it a little harder to find every option of the same category, but it's still possible.

[EDIT]
It seems I read tuska's suggestion a little hastily. It's only about the new options, not existing ones. Oh well, never mind. But still keep the above in mind.
[/EDIT]

Regards
Dalai