Re: EditAutoBrackets

On 27/01/2025 12:29, Martin Cuno wrote:
> But do I understand correctly that this can never replace "asymmetric"
> $GUIButtons (which I have equipped with shortcuts) because the FIRST
> character is immediately reacted to when entering? For example, I use
> the extended link format [[Target|Text|:+:]] (recipe "LinkCSSToolTip")
> and other "asymmetric" markup of my own.

$EnableEditAutoText and $EditAutoBrackets only react to keyboard 
presses, not to GUI buttons, and only when they are enabled in 
config.php.

What do you mean "asymmetric" markup, what are the $GUIButtons entries?

The change for GUI buttons is that if you have text selected before you 
press the button, and the text will stay selected, while the 2nd (open) 
and 3rd (close) arguments in the $GUIButtons entry will appear before 
and after the selected text. Previously the selection was cleared and 
the cursor moved at the end of the "close" text.

If you don't have text selected, the 2nd (open), 4th (default), and 3rd 
(close) arguments will be inserted, with the default text selected. It 
works the same way as before.

For example I have a button that inserts the date like 2025-01-27 as the 
second argument of the $GUIButtons entry and after that, the cursor is 
after the inserted date, nothing is selected. All my other core and 
custom buttons like adding links, bold, italic, and custom markup, also 
work.

Petko

-- 
If you upgrade :  https://www.pmwiki.org/Upgrades