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 write a lot of vocab lists and the TSV format with ElasticTabstops makes that very pleasant. The auto-alignment is very helpful for editing. But I'd like to be able to save the files without the extra spaces, so the saved files are valid.
I wrote a simple plugin to do this myself, but newer versions of ElasticTabstops fire immediately after my plugin runs, putting all the spaces back in :(
Would it be possible for ElasticTabstops to have a remove_spaces_on_save option, so correct TSV files are saved, and the spaces are only added to help with editing?
The text was updated successfully, but these errors were encountered:
My plugin is not good enough to be merged into ElasticTabstops. It is basically broken for anything beyond my very simple needs—it just naively mashes the text through csv.reader and csv.writer.
I'm honestly not sure how I would go about doing it properly (i.e. not deleting spaces inside quotes etc.)
If I were writing it, I wouldn't make it tsv-aware (i.e., ignoring quotes and so forth), I would simply search for something like the following regex: +\t
and replace it with a tab character. I would do it this way because the formatting isn't tsv-aware (i.e. it also breaks if you put a tab inside of quotes).
I write a lot of vocab lists and the TSV format with ElasticTabstops makes that very pleasant. The auto-alignment is very helpful for editing. But I'd like to be able to save the files without the extra spaces, so the saved files are valid.
I wrote a simple plugin to do this myself, but newer versions of ElasticTabstops fire immediately after my plugin runs, putting all the spaces back in :(
Would it be possible for ElasticTabstops to have a
remove_spaces_on_save
option, so correct TSV files are saved, and the spaces are only added to help with editing?The text was updated successfully, but these errors were encountered: