Partial and full configurations were distributed as reg import files in times of Far1 and Far2.

So, what to look out for to spot outdated manuals / macro recipes?ġ) *.reg files. It always stored macros in external files. It used to overlay old macro language, but then switched to LUA as well. It provides extended macro features on top of built-in system. In addition to that, there is a very popular plugin called 'MacroLib'. Also, parallel to moving macro definitions to external files, the macro language was changed to LUA. But later it was decided that it would be better to allow users simpler access to macros and they were moved from a database to individual files (still inside user's profile folder). In Far3 configuration was moved to SQLite database files located in user's profile folder. In Far1 and Far2 the configuration was stored in Windows registry, including macros. As of right now, a script has most of functional capabilities a plugin has, it has access to both macro API and plugin API, in the latest builds a macro script can be started by an event, not just by a key pressed and so forth.įAR Manager has traveled a long way from its early versions and so did its macro capabilities. With the course Far development is following now the gap between a complex script and a full fledged plugin is closing rapidly. Requires programming skills to create, but luckily the are many scripts already written and you may find one just fitting your needs. A script has means to analyze current situation and affect Far Manager in non-trivial ways. Script involves logic and decision making, not just some fixed reaction. You press a key - it is treated as if you pressed some fixed predefined string of keys. Its not much different from just a hot key. Press one key to emulate a sequence of many keys.

You want one custom key (or combination with Ctrl, Shift, Alt modifiers) do what another key (combination) already does. Assigning hotkeys / remapping key bindings.

For the sake of simplicity, let me divide them into several use cases:ġ. The 'macro' term is used loosely in Far to describe a broad range of user-made modifications of the application's behavior.

Macro in your FAR Manager? It's more likely than you think. Gather round, boys and girls, for I am about to tell you a story.

Far manager clear history