|
From: Benito v. d. Z. <be...@be...> - 2012-05-30 14:45:26
|
> You mean, internally to TXS? Otherwise, it will be confusing. Externally... Since this is the only way I see without changing txs > In such a case (²+ctrl+space), it will be longer to reach completion > than with AltGr+8. That's not was I meant. You already can write a user script that insert \ and calls the ctrl+space completion, whenever ² is pressed. But, because the completion dialog doesn't open, if there is no letter after the \ that script has no effect. > Not sure what you mean here. You can define a macro with trigger ². that is called whenever the user writes ² followed by letter. Then the ² and letter is removed, and the script called. That script can activate the completion, but first it has to insert \ and the removed letter. However, the script has no way to determine, which letter was removed. But I could add such a way On 05/30/12 15:42, Denis Bitouzé wrote: > Le mercredi 30/05/12 à 15h32, > Benito van der Zander<be...@be...> a écrit : > >> Well, you can define those 52 user macros. > You mean, internally to TXS? Otherwise, it will be confusing. > >> Or we change one of the "bad" points, either show the completion >> list if the user calls it (presses ctrl+space) after a single \, > In such a case (²+ctrl+space), it will be longer to reach completion > than with AltGr+8. > >> or allow scripts to read its own trigger string > Not sure what you mean here. |