import – EmEditor (Text Editor)

Option for filters.Import() to append to current filter rather than only replace

Sat, 28 Oct 2017 01:32:20 +0000

It would be extremely useful to have an option for document.filters.Import() that would allow it to append the imported filter to the (possibly) already applied filter of the current document, rather than always just replacing it, as it currently does.

This option could typically be implemented as a second (optional) flags parameter to the filters.Import() method, which would make it fully backwards compatible too.

As you can understand, this would make it possible for macros to perform extremely complex dynamic filtering of documents, depending on the logic of the macro itself, while the filter templates that it uses can still be originally created by humans and stored in the different filter files that are imported by the macro, step-by-step, in this way.

Pretty please with sugar on top could we have this new flag for document.filters.Import()? :-)

]]>

Macro scripting import/export of filter settings?

Thu, 14 Apr 2016 11:22:48 +0000

The (very useful) filtering feature of EmEditor has import/export buttons in the “Advanced Filter” dialog.
I’ve been trying to script these operations with macros, but as soon as I perform an import/export while recording a macro, I only get the separate filter operations that I import dumped to the macro, instead of the import operation itself.

Scripting the import (and export) operation itself (with a possibility to provide the filename to be imported/exported) would be highly useful, so my question is if this is already possible, or if it could otherwise be implemented in the macro capabilities of EmEditor?

]]>

Exported filters containing TAB cannot be re-imported

Wed, 10 Feb 2016 20:34:50 +0000

If an exported filter contains (or at least begins with) a TAB, it cannot be re-imported again (or rather, it will just result in an empty line in the filter dialog).

The apparent reason is that the filter data is exported to a TAB-separated file, while TAB characters in the data itself are not escaped, thus messing up the structure of the TAB-separated line.

Therefore, please look into escaping TAB-characters in the exported filter TSV files.

]]>