- Autocomplete is active while typing comments → DEFEDIT-1608
- There’s no word wrap option in the editor → DEFEDIT-1609
- Automatically open whatever files I had open when the project was closed → DEFEDIT-1610
- The debugger regularly crashes when evaluating tables in the console → We have made several improvements to the debugger which all will be released in the coming days.
- The self table can’t be expanded in the debugger → Yes, this is unfortunate and I’m not really sure we can do anything to solve the case of trying to iterate self.
- Global variables aren’t listed in the debugger → The global table (_G) is pretty big with all loaded Lua modules in there etc. We could perhaps have it as a non-expanded entry in the Variables window. @vlaaad?
- Array tables list their numeric indices in alphabetical order in the debugger → I think we’ve already fixed this as part of the recent Debugger improvements. At least it looks correct when I try in the latest editor version.
- keyboard shortcut for jumping between functions → DEFEDIT-1611. We also plan to show all functions in the Outline panel (DEFEDIT-855)
- keyboard shortcut for moving selected lines up and down → DEFEDIT-1612
- Option to set an external diff viewer → We’re going to revise the entire git integration in the editor and either remove it completely or make it more stable and useful for beginners as well as powerusers.
- Done.
- Done.
- the forum doesn’t have a shortcut button for strikethrough text → There’s a lot of talk about strikethrough support in Discourse (the forum software we use) Strikeout threw out? Strikethrough strikes out, throughout? - Extensions - CommonMark Discussion
- Script-level variables aren’t exposed in the debugger → I don’t think there’s any way for us to access these values in the debugger. We use the debug functionality provided by the Lua language itself. @vlaaad?
7 Likes