Hi! I haven't had time to try out your completion system yet, but one thing I could imagine would be a single completion window for a whole acme session. While you type in any other window, it gives you suggestions for completions/insertions. You insert simply by right clicking in the completion window. Or the system could even watch for a specific control character to be typed and replace it by the current top suggestion or the shortest common prefix of all suggestions. For the people who don't like using the mouse but still like acme (I don't know if they exist, but maybe). A good fallback for non-Go files could be to simply list words in the current window that match the current prefix. Or words that are likely to follow the preceding word. Or something like that.
~Fritz Am 11.02.2014 12:33, schrieb uvelichi...@gmail.com: > Hi, > It's mostly proof of concept and for personal needs. To say, it do its > work. As noticed any suggestion how to organize UI in more meaningful way > very appreciated and can be implemented. > Best regards. > >> I don't think anyone objects to it as an external command. >> >> 2014-02-10 21:46 GMT+01:00, Uvelichitel <uvelichi...@gmail.com>: >>> Hi. I know acme authors mean autocompletion destructive (excluding >>> ctl-F for filepath). Anyway an attempt. >>> >>> http://mandrillapp.com/track/click.php?u=30146375&id=637c617246ba4c3fb9eb418beabdb76f&url=https%3A%2F%2Fbitbucket.org%2Fuvelichitel%2Fcompl&url_id=1c283bd86851c7a519a5f2b172f46b33bb44a65b >>> It implemented as external command 'compl' executing in tag. It written >>> in Go lang and specifically for Go lang. It based on proven engine. It >>> tested on p9p. Feel free to try. It was not two difficult to make >>> things working, but I can not clear imagine how autocompletions should >>> _looks_like_ in acme without hotkeys and floating windows. Suggestion >>> appreciated and can be implemented. >>> Best regards. >>> >>> >
