Feature Request: custom mode for special and number sets, to allow for the practice of unique surrounds like [brackets] "quotations" and user-specific desired typing quirks

[mundanesign-netizen]

Currently users are unable to easily practice basic things like double "quotation" marks or useful things like [bracketed] text, or even "double quotes which aren't only surrounding a single word."

Not outside of specific and limiting funbox modes like 'special character only mode' or happening on luck of the draw with regular quotes practice or wikipedia funbox practice, which heavily limits the potential to actually practice certain user-specific symbols and numbers at a high-frequency.

My proposal is pretty simple, and should also cover a wide variety of potential future or past user requests for features, while also being simple to implement, or dead simple to implement:

Simple version first, I propose the user be allowed to enable a customise mode, present in the home screen as either a custom button or a pencil icon attached to the already extant buttons for special characters and numbers to be generated, and it should use, as much as possible the existing number and special character generation system, simply exposing some of it to the user so that they may add their own.
Essentially, while the current number and generation system is good as a standardised system, exposing to the user an ability to enter a 'custom' version of that system would be extremely useful to programmers, writers, and weirdos, since all typing enthusiasts will have certain ticks specific to the sorts of text they in particular have to write and that they'd like to practice. Having a unified way to allow for such weirdos, would be extremely useful: say a person wants to write [brackets] a lot or they use /slashes/ and \backslashes\ in their programs a lot. This system would cover all of those niche requests by being customisable.

Programmers in particular would get great utility out of increasing their speed at using special surrounds and appends in their typing practice. And since the sorts of special characters they might actually type with will be hyper-specific to their programming languages, so it might be best to allow the user to have a menu pop up, which allows them input and fiddle with things like:

Frequency, let the user adjust the percentage frequency of the generated surrounds/special characters they're adding to their special character mode set.
Whether the added item is a "basic" surround, or a or an <attach leading side, or an attach trailing side>.
Whether |other punctuation like commas|, goes "inside trailing edge," or "outside trailing edge", of their special surrounds.
Whether (other punctuation, such as commas, can be generated inside the surrounded text string), like how I just did.
It should also allow the user to determine if they would like their requested surrounds/attaches to generate associated with only numbers, or only words, since they might want to practice percentages, like 23% or monetary amounts like €523 but not words% $with $those attached%.

It should allow the user to input whatever weird Unicode characters they'd like, and accept whatever the user adds to their input box; like say a user wanted to practice using culturally specific quotation marks «example» or maybe they really need to type lots of basic mathematical powers² that their weirdo keyboard³ happens to have access to, they should be free to make those sorts of odd choices and not bother devs with their ultra-specific typing practice needs.

The system shouldn't be limited to accepting user-submitted single character surrounds, since users might want to, at a low frequency, practise using!? or more usefully, they might want to practise surrounding their text in something like multiple ***astrisks*** such as is the format for bolding/italicising in common text editors, like github uses or discord does.

Since adding a "custom" button to indicate custom special character character set (or an edit button under the special character/number buttons on the main page), might not be desirable for whatever reason, it would be nice if something like this system were at least crudely possible in regular custom mode.

So, barebones version of this request, would be to add allowances for Regex 'words' to be added to the word lists. Like you'd have regular | words | separated | by | bars | like | usual |, but then you'd pop in something like | 1word | "(\w+)" | 2word | 3word | and the odd one out regex 'word entry' would basically tell the customise list generator that, for that entry it's supposed to generate that, then insert inside it normal text, to create "surrounded" text, and so weird users like myself, who want to practice a wider variety of brackets and quotations and symbols and specials would have at least an outlet that includes both the symbols and regular text.

That's the super simplistic version of the idea and it's pretty crude, since the smaller version of the idea doesn't allow for easy percentage frequency, but it should be the dead-simplest version to implement, and I'd frankly be more than satisfied if it were simply extant as an option. (I'm aware the regex example I gave is a lookup and match thing, I just don't know that many regex off the top of my head or if asking for regex is even the right phrasing for this sort of request, but I hope whoever reads this at least get what I'm trying to say).

If you'd like a list of basic default options perhaps, the default surrounds in custom set could prefill to adding, [word] /word/ or "phrase" (phrase indicates "multiple words" in this example) and maybe show as an example, something like ***word*** to show the user they can make multi-character long strings for the surround system.

And basic default options for how to add user appends could show them trailing versus leading append entries like $numbers, %numbers, #words+numbers, words!?, making sure that if the user adds something like specific punctuation like... the user can denote whether the following generated word should be capitalised or not, since if you use the basic current system system, user added options like ellipsis... can be broken by grossly applying capitalisation rules to the following text. And if they want this?! sort of thing, ?! can be missed because it's generated as a separate entry from ! or ? in the system, presumably, which have already working handling that might conflict or misapply. Forcing the user to just tell the system how they want it to behave will take the impetus of figuring all that complexity out of the developer's hands and into the weirdos who want this sort of thing.

I think this system will address lots of edge case requests that you've recieved over the years. I've looked through other discussions, and have found lots of requests that could have probably been better served by this system, but which were served instead by simpler or more specific versions, or which were not addressed at all because the user request was super vague like asking for a 'coder version' of monkeytype, which is super ambiguous and too user-specific to what that means, and in the cases where something was added, it was simple, or somewhat niche and somewhat hidden things like the 'special character only' funbox/the various code-ish funbox modes, which while useful, are meaningfully different from practicing special characters naturally and correctly (by the user's own definition of correctly) generating within the randomly generated text they are currently practicing. And which is exposed to users as a 'customise' button or a little pencil 'edit' button attached to the homepage 'special' and 'number' modes on their normal typing practices.

If any one reads this, thank you for considering it.