-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stopped inputting text at v1.3.5 #14
Comments
Hi, what command did you try to use? |
[ctrl] + [alt] + n Ah, just tried "\n" and noticed in the status bar, "No text found for InsertText, canceled" |
Thanks for the quick reply! There was a change in 1.3.5: text insert will only be executed if we have a list of three or more words in it. So atm, the threshold of words required to execute/insert text is 3. This was changed for future commands to work properly (in the next version). If you want to insert two words, please use the words command:
|
|
Great... works fine now... and you managed to answer my next question with your last... Many thanks, Issue closed? |
Yes, thanks for using Text Pastry! |
I've just released 1.3.6, you can change the threshold by setting this in your TextPastry.sublime-settings file:
Change this value to 2 to make "foo bar" work like in previous versions (without using the words command). You could even set it to 1 to restore the behaviour of Text Pastry to < 1.3.5 |
You mentioned that "This was changed for future commands to work property (in the next version)"... So how would
affect these new features? |
To be honest, it shouldn't. I've had the problem that TP couldn't distinct a command from a list of words, so if we would enter a command name (like I've further reduced the problem by using a lexer instead of a regular expression; so setting the threshold to 1 should be safe as well. tl;dr: it shouldn't affect the new features in 1.4.0. As worst case, Text Pastry will put the text into our selections when the command was not found... |
All of a sudden the plugin stopped inserting the text...
No error logged in console...
Background to the input area lost it's dark background...
Reverted to 1.3.4 and it's working again...
Running ST2 on Windows 8...
The text was updated successfully, but these errors were encountered: