> Yeah, with no spyware we don't know how many users there are for any Geany > features or plugins, maybe we should add it. smiling_imp
So this is the path to the dark side... > Indeed, irrespective of the metadata examination cost, executing a script off > disk for each keystroke is potentially a bigger issue. > > I would have thought a normal design would have scripts executing off signals > cached in memory by default, but I don't know how much effort that is for > embedded Lua. I don't expect scripts executing off Geany signals would be > very large so memory usage should not be excessive. Normally, scripts would be cached by the operating system, at least on Linux. It's the network device scenario where programs have to do their own caching that would be a problem. Unfortunately, since I'm starting to think about caching, I might end up implementing it... > Actually Geanylua is orphaned... so nobody is responsible for checking any > changes to it. There also seem to be a lot of plugins that just won't build anymore because dependencies are unavailable. Lua 5.1 is well over a decade old, and its final update was about 9 years ago. So it may not be long before distros stop including it. I recently saw, but haven't tried, another scripting plugin for Geany ([peasy](https://github.com/kugel-/peasy)). Since it uses gobject introspection, it presumably has access to all of the API. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1112#issuecomment-934073729
