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
When calling speed-type-buffer within an org-buffer I often get "untypable" text. With "untypable" text I mean tables, tags with many preceding spaces, too many stars and whitespace in general. It isn't enjoyable to write it even though the text is relevant for me.
It would be nice to have a org-filter which is some magic content preparation and cleaning method which tries to tiddy up the text and tries to find better content if a sample happens to be just a table (skips tables when picking content).
It shouldn't not be cleaned up too much, if i want "clean text" I could just use speed-type-text. The feeling of writing org-file can't be replicated but characters more often used in org-files should be highlighted (uuid, PROPERTIES, Dates, Links).
The text was updated successfully, but these errors were encountered:
When calling
speed-type-buffer
within an org-buffer I often get "untypable" text. With "untypable" text I mean tables, tags with many preceding spaces, too many stars and whitespace in general. It isn't enjoyable to write it even though the text is relevant for me.It would be nice to have a org-filter which is some magic content preparation and cleaning method which tries to tiddy up the text and tries to find better content if a sample happens to be just a table (skips tables when picking content).
It shouldn't not be cleaned up too much, if i want "clean text" I could just use speed-type-text. The feeling of writing org-file can't be replicated but characters more often used in org-files should be highlighted (uuid, PROPERTIES, Dates, Links).
The text was updated successfully, but these errors were encountered: