Only one Syntax Editor Macro usable per editor?

Tobias Persson_
Tera Expert

Hey all!

 

We're currently running on Utah release. I have defined some macros in System Definitions > Syntax Editor Macros. But when I want to execute them only one works. As soon as I try to do a second macro the macro doesn't show up in Intellisense and after hitting tab it just inserts a tab but not the macro.

 

As an example: if I enter "for" and hit tab I get the for loop inserted. But if I then want to use "vargr" + tab before that loop it only writes "vargr" followed by a tab. Nothing is replaced.

 

Any idea what's wrong here?

 

Regards,

Tobias

1 ACCEPTED SOLUTION

Community Alums
Not applicable

Hi @Tobias Persson_ ,

The issue seems to be addressed in PRB1645468: Code editor / Syntax editor is not loading correctly when Polaris is enabled

 

The fix target is Utah patch 4

Please try the following workaround:

1. Add the system property 'glide.ui.syntax_editor.polaris' and set its value to 'false'.
2. Clear the instance cache [cache.do]

OR

Set the value of the system property "glide.ui.escape_all_script" to 'true'.

 

View solution in original post

5 REPLIES 5

Community Alums
Not applicable

Hi @Tobias Persson_ ,

The issue seems to be addressed in PRB1645468: Code editor / Syntax editor is not loading correctly when Polaris is enabled

 

The fix target is Utah patch 4

Please try the following workaround:

1. Add the system property 'glide.ui.syntax_editor.polaris' and set its value to 'false'.
2. Clear the instance cache [cache.do]

OR

Set the value of the system property "glide.ui.escape_all_script" to 'true'.

 

Hi @Community Alums ,

 

thanks for replying so quickly. I checked the problem you posted and have to say that glide.ui.escape_all_script is already set to true. Also this problem seems to address the issue that the syntax highlighting and autocomplete features are not working correctly. But in our case the autocomplete is showing up - it is just not showing the macros  when trying to add more than one. 

Of course it may be solved in Patch 4 but as the suggested workaround doesn't work I am not sure if this is the only reason. Or does the workaround not solve all autocomplete issues maybe?

 

Any other ideas?

 

Thanks,

Tobias

Community Alums
Not applicable

Hi @Tobias Persson_ ,

workaround not solves all autocomplete issues unfortunately.

 

Hi @Community Alums ,
that's what I was hoping not to hear. 😉 But it's okay. I guess we can wait for Patch 4 which hopefully solves the issue.

Regards,

Tobias