In 13.24.1, initiating a CLI QUICKSEARCH command from a locked or a locked (reuse unlocked tab) tab places the cursor at the end of the query string in the FAYT in the new tab, regardless of whether noselect: or {cp} is included in the CLI command.
This doesn't quite make sense to me. The CLI QUICKSEARCH command will open the FAYT in the current tab, it doesn't open it in a new tab, whether or not the current tab is locked.
Sorry, I meant that this happens when the full command is run through a button or FAYT command mode, for example:
CLI QUICKSEARCHENGINE=everythingglobal QUICKSEARCH comment:"{cp}"
Running a button:
FAYT Command Mode:
Notice how the cursor is initially between the double quotes in the locked tab, but when the new tab opens, it moves to the end of the query string.
When the command doesn't include noselect: or {cp}, the text in the locked tab is initially selected for typing over, but when the new tab opens, it moves to the end of the query string.
Ok I see what you mean. We'll try to preserve the cursor position in the next beta.