As of rev 4145, any non-word character may trigger the expansion of abbreviations. As before, alt/ctrl/meta keys never trigger expansion.
Previously, only blank triggered the expansion, and if the blank *did* trigger the expansion the blank was not inserted into the text. Now, any character that triggers the expansion *is* inserted into the text, except if the character ends the abbreviation. For example, I have an abbreviation that starts:: form_.= <a long expansion of an html form> The seemingly bizarre rule above means that the only way to expand the abbreviation is by typing "form_." which I think is good. Newlines may trigger expansions, which I find helpful. For instance, I have the following abbreviation:: ncn=@nocolor-node\n Previously, I had to define the abbreviation with an extra newline. It's possible that the new rules may not be convenient in all cases. If so, please let me know. There is plenty of time to tweak the rules. Edward P.S. Here are my abbreviations:: ncn=@nocolor-node\n atnc=@nocolor\n form_.=<form action="main_submit" method="get"\nacccept- charset="utf-8">\n\n<p><input type="submit"\nvalue="Continue →"></ p>\n</form>\n input_.=<input \ntype="text/submit/hidden/button" \nname="some_name" value="" \nid="some_name"> \n alr=@language rest\n EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
