A separate INI for history

[MVV]

I think it will be good, the main ini won't contain garbage and temp data, so will be more compact, and loading or cleaning history and temp data will be easier.
For compatibility TC may load history both from main and special file. But save only to special.

Blocks to be placed into separate file: [MkDirHistory], [SearchIn], [SearchText], [RenameTemplates], [SearchName], [Selection], [SplitPerFile], all [1280x1024 (8x16)] and similar.

Maybe it will be good to add a param to main ini with path to this file.

[Mikefield]

What do you think about RedirectSection like that:

Code: Select all

[Command line history]
RedirectSection=%COMMANDER_PATH%\wincmd_History.ini

[LeftHistory]
RedirectSection=%COMMANDER_PATH%\wincmd_History.ini

[MkDirHistory]
RedirectSection=%COMMANDER_PATH%\wincmd_History.ini

[RightHistory]
RedirectSection=%COMMANDER_PATH%\wincmd_History.ini

It's just implemented and works fine.

mf

[MVV]

Thanx, I never seen this before. I had missed this feature.
I guess, AlternateUserIni param is enough for my suggestion. I'll try to realize it.

Yea, it's cool thing!

[Hacker]

[mod]Moved to the English forum.

Hacker (Moderator)[/mod]

[Boofo]

2Mikefield

Wouldn't it be better to use %COMMANDER_INI%?

[karlchen]

Hello, Boofo.

Wouldn't it be better to use %COMMANDER_INI%?

I do not think so, because %COMMANDER_INI% expands to a filename, whereas %COMMANDER_PATH% expands to a foldername.
Yet, in the end, it all depends on what you want to achieve and where you store your %COMMANDER_INI% and the redirected INI files.

Cheers,
Karl

[m^2]

%COMMANDER_INI%\.. points to a directory.
Yes, using this would be more generic. Yes, it depends on particular needs of each user. Both %COMMANDER_INI% and %COMMANDER_PATH% are viable options here.

[Boofo]

I tried

RedirectSection=%COMMANDER_INI%\wincmd_History.ini

but it didn't seem to work.

[m^2]

%COMMANDER_INI%\..\wincmd_History.ini
As Karl noted, %COMMANDER_INI% is a file path.

[Boofo]

2m^2,
Thanks for the correction. It is still confusing to me, but it works. Isn't %COMMANDER_PATH% a file path also?

2karlchen,
I thought it would be better to have the history file in the same directory as the other INI files.

I think I understand better now after thinking about it.

Code: Select all

%COMMANDER_INI%= <path to INI directory>/wincmd.ini

and

Code: Select all

%COMMANDER_PATH%= Totalcmd directory (No filename)

Ok, that makes sense now. But I didn't understand the \..\ for the %COMMANDER_INI%. That part is what confuses me.

[karlchen]

Hello, Boofo.

cd .. means: go one folder level back up.
cd %COMMANDER_PATH%\.. means: go to %COMMANDER_PATH% and one level back up.
cd %COMMANDER_INI%\.. means: go to %COMMANDER_INI% and one level back up. This works, because apparently the routine does not check whether %COMMANDER_INI% is a folder. So as a result it simply cuts off the (wincmd.ini) filename and takes you to the folder where %COMMANDER_INI% is located.

Example:
%COMMANDER_INI%=C:\Dokumente und Einstellungen\Karl\wincmd.ini
%COMMANDER_INI%\..=C:\Dokumente und Einstellungen\Karl

Kind regards,
Karl

[Mikefield]

2Boofo Please open in TC a DOS window (cm_ExecuteDOS) and type follwing command and a return on the end in the Dos Window:

Code: Select all

set c

This should solve all your confusion.

mf

[karlchen]

<offtopic>

a DOS window

Command prompt window (cmd.exe by default). NT based Windows systems do not bring along any MS-DOS any longer.
</offtopic>

[Boofo]

2karlchen,

Thank for the explanation. the \.. threw me off because that usually takes you to the root of the drive. It seems it just cancels the wincmd.ini and basically makes %COMMANDER_INI% a path instead of the INI file.

2Mikefield

Thanks for that. I'll have to remember that. It gives a clear list.

[Mikefield]

2Karlchen Thanks for clarification. The cm command should be renamed in cm_ExecuteCMD.
But we didn't know what Boofo use. It could be Windows 98 and this is Dos based!

mf