Page 1 of 2
History cleaner for the wincmd.ini
Posted: 2024-02-14, 05:57 UTC
by mrbeeye
It is high time TC had its own builtin history cleaner.
Something like internet browsers have - invoked on-demand and clean whatever you wish by choosing respective checkboxes.
Re: History cleaner
Posted: 2024-02-14, 07:35 UTC
by jbcb
I like the idea.
Similar to the browser, options could be available for what to delete and in what time period when deleting.
Re: History cleaner
Posted: 2024-02-14, 08:00 UTC
by Horst.Epp
There is already a button "Delete now" in the Configuration / History
Re: History cleaner
Posted: 2024-02-14, 08:37 UTC
by mrbeeye
Horst.Epp wrote: ↑2024-02-14, 08:00 UTC
There is already a button "Delete now" in the Configuration / History
it omits deleting many history entries (searches, command line,...)
Re: History cleaner
Posted: 2024-02-14, 10:47 UTC
by Sir_SiLvA
Just put all stuff you want to delete in an extra ini with RedirectSection= and you have the ability to delete history whenever you want.
for example:
Code: Select all
[Command Line History]
RedirectSection=<path>\history.ini
[LeftHistory]
RedirectSection=<path>\history.ini
[MkDirHistory]
RedirectSection=<path>\history.ini
[NewFileHistory]
RedirectSection=<path>\history.ini
[OldConnections]
RedirectSection=<path>\history.ini
[RenameSearchFind]
RedirectSection=<path>\history.ini
[RenameSearchReplace]
RedirectSection=<path>\history.ini
[RenameTemplates]
RedirectSection=<path>\history.ini
[RightHistory]
RedirectSection=<path>\history.ini
[Searches]
RedirectSection=<path>\history.ini
[SearchIn]
RedirectSection=<path>\history.ini
[SearchName]
RedirectSection=<path>\history.ini
[SearchText]
RedirectSection=<path>\history.ini
[Selection]
RedirectSection=<path>\history.ini
[TargetList]
RedirectSection=<path>\history.ini
Re: History cleaner
Posted: 2024-02-14, 10:56 UTC
by petermad
Not that I am against the idea, but I can foresee a huge discussion about which history elements should be deleted with such a function.
Currently I redirect all wincmd.ini sections that I consider to be history to a wincmd_history.ini file - then I can easily just delete that file.
here is my list of what I consider history, hence redirect:
Code: Select all
[rename]
RedirectSection=wincmd_history.ini
[SyncOptions]
RedirectSection=wincmd_history.ini
[Selection]
RedirectSection=wincmd_history.ini
[SearchName]
RedirectSection=wincmd_history.ini
[SearchIn]
RedirectSection=wincmd_history.ini
[SearchText]
RedirectSection=wincmd_history.ini
[RenameTemplates]
RedirectSection=wincmd_history.ini
[RenameSearchFind]
RedirectSection=wincmd_history.ini
[RenameSearchReplace]
RedirectSection=wincmd_history.ini
[left]
RedirectSection=wincmd_history.ini
[right]
RedirectSection=wincmd_history.ini
[lefttabs]
RedirectSection=wincmd_history.ini
[righttabs]
RedirectSection=wincmd_history.ini
[Command line history]
RedirectSection=wincmd_history.ini
[RightHistory]
RedirectSection=wincmd_history.ini
[LeftHistory]
RedirectSection=wincmd_history.ini
[MkDirHistory]
RedirectSection=wincmd_history.ini
[NewFileHistory]
RedirectSection=wincmd_history.ini
[TargetList]
RedirectSection=wincmd_history.ini
[PluginDuplicates]
RedirectSection=wincmd_history.ini
[DirSelection]
RedirectSection=wincmd_history.ini
[LastTracks]
RedirectSection=wincmd_history.ini
[ButtonbarCache]
RedirectSection=wincmd_history.ini
I myself could debate whether [SyncOptions], [rename] and [ButtonbarCache] should be there.
Re: History cleaner
Posted: 2024-02-14, 10:57 UTC
by jbcb
Advanced history handling should be a built-in feature.
Re: History cleaner
Posted: 2024-02-14, 11:01 UTC
by petermad
jbcb wrote: ↑2024-02-14, 10:57 UTC
Advanced history handling should be a built-in feature.
Then let's see your suggestions as to which of TC's many histories that should be included.
Re: History cleaner
Posted: 2024-02-14, 11:15 UTC
by Sir_SiLvA
jbcb wrote: ↑2024-02-14, 10:57 UTC
Advanced history handling should be a built-in feature.
It is possible allready as I pointed out, you are just not willing to use it...
Re: History cleaner
Posted: 2024-02-14, 12:46 UTC
by AntonyD
2petermad
HOW in this approach I can redirect ALL current and ALL FUTURE possible sections regarding screen resolutions?
Like [800x600 (8x16)], [1024x768 (8x16)], [1152x864 (8x16)]
and so on....
Re: History cleaner
Posted: 2024-02-14, 13:52 UTC
by ghisler(Author)
Use AlternateUserIni in the [Configuration] section. It redirects all sections except [Configuration], [Layout], [Packer], [Confirmation], [Extensions], [Associations], [Shortcuts], [ShortcutsWin], [PackerPlugins], [FileSystemPlugins], [ListerPlugins], [ContentPlugins].
It also doesn't redirect sections containing RedirectSection=0.
Re: History cleaner
Posted: 2024-02-14, 16:52 UTC
by jbcb
Sir_SiLvA wrote: ↑2024-02-14, 11:15 UTC
jbcb wrote: ↑2024-02-14, 10:57 UTC
Advanced history handling should be a built-in feature.
It is possible allready as I pointed out, you are just not willing to use it...
But I'm talking about the built-in functionality available from the UI. I'm not talking about manually editing settings files.
Re: History cleaner
Posted: 2024-02-14, 17:11 UTC
by Fla$her
cm_ClearHistoryConfig — support.
We know the external cleaning methods, even without redirecting sections. But if you compare TC with browsers, then I think that a separate settings page will be quite appropriate here.
Re: History cleaner
Posted: 2024-02-14, 17:53 UTC
by petermad
Sir_SiLvA wrote: ↑2024-02-14, 10:47 UTC
for example:
Code: Select all
[OldConnections]
RedirectSection=<path>\history.ini
[OldConnections] is a wcx_ftp.ini section - sections in wcx_ftp.ini cannot be redirected.
Re: History cleaner
Posted: 2024-02-14, 20:01 UTC
by Sir_SiLvA
petermad wrote: ↑2024-02-14, 17:53 UTC
[OldConnections] is a wcx_ftp.ini section - sections in wcx_ftp.ini cannot be redirected.
I know, I just copy & pasted the names from my TC Inis History folder and I once tried to redirect that section.
PS: Has there ever been a reason given why sections in wcx_ftp cant be redirected (yet)?