You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking about if there was an easy way to set up new tables within the tool, or if that easy way was only to manually build a giant match file. One where you keep copying and pasting the example template and filling it out with a unique regex, piping the args to _core, and adding the name of the txt file or weighted table file in args as well.
Then I realized this may be a good candidate for putting together a "wizard" that:
Draft suggestion for approach:
Remind the user they must first upload their new simple (txt) or weighted (psv) table file into the espanso/tables directory
Asks user to select the file (if UI) or asks for the filename to make sure it can get to it and that it the name input matches
Asks the user if they are setting up a new simple or new weighted table
Asks for a new, unique regex that will be used to call your table
5a. The " : " should probably be displaced by default since it is needed for the front-end of the command so the user knows they don't have to include it
5b. It should probably scan/search to make sure it is unique and return for a different input if not
Auto appending all this (including the new table file name) as a new entry to the correct locations in a common .yml file.
Saves the file so it is ready for testing and use in the user's text editor
The text was updated successfully, but these errors were encountered:
I was thinking about if there was an easy way to set up new tables within the tool, or if that easy way was only to manually build a giant match file. One where you keep copying and pasting the example template and filling it out with a unique regex, piping the args to _core, and adding the name of the txt file or weighted table file in args as well.
Then I realized this may be a good candidate for putting together a "wizard" that:
Draft suggestion for approach:
5a. The " : " should probably be displaced by default since it is needed for the front-end of the command so the user knows they don't have to include it
5b. It should probably scan/search to make sure it is unique and return for a different input if not
The text was updated successfully, but these errors were encountered: