Marko wrote: ↑Oct 12th, ’21, 05:15
This is really a big file.
Do you really use all the commands? Maybe consider creating another fdb settings file with only the essential commands. Use File/Save As... to create another file and then remove the commands you only rarely use. You can always open a large file (File/Open) when you would need all.
I definitely can't say that I use all of them, all the time, but I'd say it's more period/activity dependent.
I may for example not use a certain command (or a set of commands) for a month or so, but then need it/wish that I had it later on... and thus, I usually do.
Switching between different .fdbs would thus kind of break the 'flow' for me I feel... I'll probably start noting my thoughts about this, as in by what criteria I can divide the commands, so that I won't at some point have to go through like 5 or more .fdbs, to check whether I have X command present...
On average, I also probably do like 2-10 edits on a daily basis... but luckily it's been getting 'quieter' and 'quieter' in that regard.
⁂
Overall, it has seemingly been some years now, of pretty to relatively active FK addition (I'd say I'm overall getting close to 3k commands, all in all, including the text expansions). But in my perhaps somewhat delusional mind... as long as I keep on using FK in the way that I do, that quite significant time investment, will really pay off big in the long run...
Having a strict naming convention and over 30 meta pages on FK (inside of a noting software such as OneNote), has also, certainly been very crucial, to supporting this seemingly massive 'structure'... looking back at it now, it's almost hard to not get a little teary-eyed, on the journey and the attachment that I have come to have with this software.
⁂
"Through thick and thin, FK commands beget I on a whim.
And though gradations with uncertainties, are ofttimes bit too much,
There's evidently wisdom, in this notion of a thought-out clutch."