Increase contents of history sections

[ts4242]

Currently all history sections are limited to 20 items only (from 0 to 19), it will be great if this can configured via global setting that apply for all history sections.

[sqa_wizard]

Sounds reasonable, but you may take in account that INI files have a 64K file size limit.

By using a increased limit, you are forced to use a redirection for each section, otherwise it gets unusable after a short time.

To overcome this drawback a (often discussed) design change is needed to write the "dynamic" entries to a separate file, while the "static" options remain at wincmd.ini ...

[Clo]

2sqa_wizard

Hello !

Sounds reasonable, but you may take in account that INI files have a 64K file size limit. …

• That is true with FAT32 only. With NTFS, there is no limit about the file size, only each [Section] is limited to 64 KiB (65,536 Bytes).

• I support an enhancement of the current items number, that might not make so big files…

 VG
Claude
Clo

[sqa_wizard]

each [Section] is limited to 64 KiB

... resulting in a maximum number of 64 at 1024 Bytes for each entry (1022 name + CR + LF)

But just half of it regarding unicode notation => 32

Hey stop. is the filename is limited to 1022 Byte or character ?

[Hacker]

Clo,

That is true with FAT32 only. With NTFS, there is no limit about the file size

That does not really sound true.

Roman

[ts4242]

INI file limits are depend on operating system not file system

Win9x based system
File size: 64 KB
Section size: 32 KB

NT based system
File size: unlimited
Section size: 32 KB

Therefore the suggested setting could be applied on NT based system only

[Boofo]

2ts4242,

Fat32 is limited to 4 GB, no matter what the OS is, I believe.

[ts4242]

2ts4242,

Fat32 is limited to 4 GB, no matter what the OS is, I believe.

That is true but here I'm talking about the INI file limitation not the file system limitation, in other word the Win9x API's cannot handle INI file greater than 64 KB

[Balderstrom]

To overcome this drawback a (often discussed) design change is needed to write the "dynamic" entries to a separate file, while the "static" options remain at wincmd.ini ...

I'd rather see a .css like approach wherein you can define (i.e.) maxhistory=100 item that would be applied to any history section that tracks via numeric items (1=foo\n 2=bar\n 3=foobar\n). But each section could in turn put an alternate (i.e.) maxhistory=10

It would be nice if this setting had to be within wincmd.ini, much like the redirect line has to be within the wincmd.INI.

--> Like css as it allows a global setting that can be further customized for each child item, or child-of-child...

I have since redirected all of the following to wincmdHistory.ini

[left]
[right]
[Command line history]
[MkDirHistory]
[RenameTemplates]
[SearchText]
[Selection]
[RenameSearchReplace]
[SearchName]
[SearchIn]
[RenameSearchFind]
[lefttabs]
[righttabs]
[RightHistory]
[LeftHistory]

For ease of non-SAVY users it would be nice if redirecting ALL history-related .ini sections could be accomplished from TC's config GUI with a simple editBox
--> AlternateHistoryFile: [ wincmdHistory.ini ]

That would internally do the "work" of inserting the redirect-lines into each related wincmd.ini section. And move the contents of the sections to said file.