FWIW I'm (slowly) working on an AutoHotkey helper program to replace FARR's built in methods for editing aliases. Not ready for release yet, but working good so far in my test use. Some features:
- jump directly to alias editor window from FARR
- search/filter box with live filter (very useful when you have a lot of aliases)
- some syntax syggestions in the alias edit window
- shortcuts to create regex aliases
- FARR is still usable while the alias editor window is open
Here are some notes on where and in what format FARR stores its aliases, based on me testing things and from looking around in FARR files. Mouser can correct me if I'm wrong on anything here.
FARR stores aliases in .alias XML files. The default user file is
<MyDocuments> \DonationCoder\FindAndRunRobot\AliasGroups\MyCustom\myaliases.alias
other FARR settings including the list of disabled (uncheckboxed) aliases are in
C:\Users\ <user> \Documents\DonationCoder\FindAndRunRobot\FindAndRunRobot.ini
You can edit the .alias file in Notepad++ or any code editor, but it is a bit clunky to manually edit .xml. However if you for example want to change a folder path in a lot of aliases then it'll be easy to do a find/replace all in this file.
Some more notes on interacting with the above files:
- Edits to myaliases.alias have effect when FARR starts.
- Important: FARR adds to .alias the line "<Disabled>true</Disabled>" for each disabled alias. But that only mirrors the authoritative setting in FindAndRunRobot.ini > [Settings] > DisabledAliasStrings
- Edits to FindAndRunRobot.ini only stick when made while FARR is not running, otherwise FARR restores the old values from working memory.
To prevent FARR from restoring old values use this method to change aliases from an external script:
1 exit FARR (commandline -exit)
2 edit .alias / .ini and save
3 run FARR (commandline -hide)
Edit: it is easy to mess up with direct edits to the .alias / .ini files so make sure you create backups of them first.