Though Leo is limited to Leo source and the Python standard library. Rob's interest was in two things, taken from your quote::
- "everywhere in the current file" - "the lexer that corresponds to the computer language of the file" Rob was talking about an expansion of the autocompleter, to be not limited to Leo's source or the standard library but also to include "words" from the current file and also include language agnostic completions. For clarification, Leo doesn't do either of these things, unless I'm sorely mistaken, in which case I ask your pardon. On Friday, April 22, 2016 at 11:18:25 AM UTC-4, Edward K. Ream wrote: > > On Wed, Apr 20, 2016 at 2:19 PM, Largo84 <[email protected] <javascript:>> > wrote: > >> Just now reading up on Leo's Autocompletion feature >> <http://leoeditor.com/tutorial-scripting.html#autocompletion> and >> comparing to how Notepad++ does it >> <http://docs.notepad-plus-plus.org/index.php/Auto_Completion>. >> > > Here is the essence of how Notepad++ handles autocompletion: > > QQQ > There are two sets of candidate words that Notepad++ uses to create > suggestions; these are referred to as "words" and "functions". > > "Words" are taken from the current file—everywhere in the current file, > comments and code... > > "Functions" are pre-defined and loaded along with the lexer that > corresponds to the computer language of the file. > > QQQ > > At present, Leo doesn't add keywords (functions). Leo's present code > completer finds most words as it its, but maybe not all. > In short, I think Leo already does pretty well in the regard. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
