Diamen wrote: Mon Sep 07, 2026 6:35 pmCoder have any function that XBrackets has?
I don't understand your question exactly, so I'm trying to answer what I believe is related.
XBrackets and Coder are different plugins with different purpose. What is more important, Coder has its own key bindings in its Settings window, and XBrackets allow to specify key bindings in the Plugins window. Thus, nothing forbids to use these two plugins in parallel.
Coder works with file syntax - in fact, it parses a document using a file syntax. So, Coder is aware of function signature and blocks of code.
XBrackets does not know anything about file syntax. My primary usage of XBrackets is:
- Brackets (and quotes) auto-completion: when you type an opening bracket or quote, a closing one is automatically added.
- Selecting a string within quotes - e.g. "some string" - via SelToNearestBrackets. Coder can't do that since it operates with function blocks, and quotes are not function blocks.
- Selecting an expression in brackets - e.g. (a+b+c) - and a section name - e.g. [section name]. Coder can't do that since it operates with function blocks, and text within round/square brackets is not a function block.
- Jumping between the starting and ending quote or bracket. Coder can't do that unless we are talking about { } that specify a function block.
Now, to confuse you, I should add that XBrackets actually communicates with Coder when Coder is active.
Why? Because different file syntax rules may create confusions in identifying of which exact opening bracket or quote matches which exact closing bracket or quote.
Consider the following text: { " } { " }. When you look at this text from the beginning to the end, it's obvious what bracket and quote corresponds to what. But if the caret is at the very trailing closing brace and you want XBrackets to find the matching opening one, it may mistakenly find the one inside the quotes because, unlike Coder, XBrackets does not parse the file from the very beginning to the very end.
That's why XBrackets first asks Coder: does the bracket/quote under the caret have the pairing bracket/quote that you are aware of? And if Coder confirms the pairing character, XBrackets uses that information for jumping or selecting between the brackets/quotes. If Coder does not have such information, then XBrackets parses the text until the very first character that seems to be a pairing one. So XBrackets parses only small part of the file, and takes into account only brackets and quotes, nothing else.