This is probably a question for any Atom experts out there but The autocomplete doesn't seem to be working as I expected.
According to the Atom documentation, autocomplete should include words in the file you're editing, so for example if I have a local declaration, it should suggest the names of the variables for autocompletion but that's not happening. It's also a little odd that the suggestions include words that include the letters I'm typing anywhere in them so if I start typing "tVa", the suggestions include "toplevel stack", "twelveHourTime to trueORfalse", and "traversalOn". I'm hoping there are some settings to control this but haven't found any yet. Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Wed, Oct 21, 2015 at 1:15 PM, Mike Kerner <mikeker...@roadrunner.com> wrote: > This conversation is exactly why we need to develop some better > instructions for the non-command-liners. > > On Wed, Oct 21, 2015 at 3:49 PM, Peter Haworth <p...@lcsql.com> wrote: > > > Thanks Mark and Monte. I'm now up and running but have not tried to deal > > with the linter/livecode server yet. > > > > Pete > > lcSQL Software <http://www.lcsql.com> > > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and > > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> > > > > On Wed, Oct 21, 2015 at 12:20 PM, Monte Goulding < > > mo...@sweattechnologies.com> wrote: > > > > > > > > > On 22 Oct 2015, at 5:05 am, Mark Wieder <mwie...@ahsoftware.net> > > wrote: > > > > > > > > Open Atom > > > > Go to Preferences > > > > Select Install > > > > Make sure Packages is selected (it's the default) > > > > Type livecode into the search box and press return > > > > "language-livecode" should be top of the list > > > > Press Install > > > > > > And you also need the linter package if you want to see script errors > and > > > then check the livecode package settings and you will see some > additional > > > setup for the linter. For livecode script & server it needs to know > > where a > > > server engine is. If you symlink it to somewhere on $PATH as > > > livecode-server then you can leave it as default. For livecode builder > it > > > needs to know where lc-compile and the standard modules are. These > > default > > > assuming you have the livecode repo installed but I assume you can > > extract > > > them from a livecode install. I mentioned to Peter B it might be nice > if > > LC > > > had an install command line tools option to handle this stuff. > > > > > > Cheers > > > > > > Monte > > > _______________________________________________ > > > use-livecode mailing list > > > use-livecode@lists.runrev.com > > > Please visit this url to subscribe, unsubscribe and manage your > > > subscription preferences: > > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > > > _______________________________________________ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode