It should be no hassle to call speed-type-buffer within an org-file

[lordnik22]

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).

[lordnik22]

Adding filters per major-mode is out of scope and an endless story. Therefore going to close this issue. The text-pickers can certainly be improved, especially for code but rather in a general way then mode-specific.

speed-type-buffer-top-x provides a over normalized way which makes sure to only add words and not random org-tables or org-headers with tags and all the whitespace in between.

The idea originated from type-mode and the speed-type-buffer-top-x fulfills this idea.