{"ops":[{"insert":"Hello, I'm a new RDM user and I have created a few rules to try out syntax highlighting in RDM.\n\nThere are two issues I've come across - one is a UX issue, the other seems to be a bug.\n\nTo start with the user experience issue (and this seems to be a fundamental design issue with RDM itself, not just with syntax highlighting), you can't do anything in RDM when the settings dialogue window is open. So, for every change to any setting, I have to:\nOpen settings"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Navigate to the item within settings (usually nested within some sub-tree) (for instance, it takes 8 mouse clicks to get to the syntax highlighting section, every single time, or 5 clicks if you search the settings for \"colors\")"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Make the changes, then save/close out of settings"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Test"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"This wouldn't be a poor user experience if I could keep the settings window open independently of the main UI to quickly make and test changes.\n\nNow, the potential bug with the syntax highlighting is that rules with matching substrings seems to override each other. The UI has up/down arrows to imply order, and even "},{"attributes":{"link":"https://forum.devolutions.net/topics/35196/cisco-ios--iosxe--iosxr-syntax-highlighting"},"insert":"the XML file from an older forum post"},{"insert":" with syntax highlighting rules suggests there was an order to rules, but in my testing, either the order is not respected, or there's a problem with the logic when it comes to parsing rules with the \"Complete word\" option checked.\n\n "},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" #000000"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" Transparent"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" BlackBold"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" b474c0d9-2145-4672-a4dc-cf15258ab7ff"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" administratively down"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" admin down - administratively down"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" #000000"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" "},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" "},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" #000000"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" Transparent"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" Red"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" 21fa4909-63a2-4202-8ef0-1b84bcaf5d5e"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" down"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" interface down"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" #000000"},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":" "},{"attributes":{"code-block":"plain"},"insert":"\n"},{"insert":"\nAs you can see, there's a separate rule for `down` vs `administratively down`, with the former being defined first. Yet, in my terminal, the specific rule for `down` is taking priority over the earlier defined rule for `administratively down`.\n\n"},{"insert":{"image":"https://forum-api.devolutions.net/api/messages/217834/attachments/9b229fa1-8e30-49e7-ab75-afda06093654.png"}},{"insert":"\nResult in terminal:\n"},{"insert":{"image":"https://forum-api.devolutions.net/api/messages/217834/attachments/c02d5f72-8367-4400-8f26-1864f31b0a80.png"}},{"insert":"\nI would expect the string \"administratively down\" to match the rule named \"admin down - administratively down\" and use the ANSI Black Bold foreground color.\n"}]}

Issues with Syntax Highlighting

Issues with Syntax Highlighting