Skip to content

v1.6.3
Compare
Choose a tag to compare
@chrisant996 chrisant996 released this 01 Feb 10:02
· 149 commits to master since this release
v1.6.3
af47db5
  • Breaking Change: For the four Ctrl-- key combinations, Clink got the Shift key backwards and generated inaccurate input codes. And that broke the Readline/bash default key binding for undo (the Windows default key binding of Ctrl-z works fine). If your .inputrc file has bindings for any of the Ctrl-- key combinations then you can keep the keys working the same by updating the key bindings. You can even use the $if clink_version >= 1.6.3 syntax in your .inputrc file to make it define the key bindings differently in different versions of Clink.
    Key Combination Old Code New Code
    Ctrl-- "\C-_" or C-_ "\e[27;5;189~"
    Ctrl-Shift-- "\e[27;6;189~" "\C-_" or C-_
    Ctrl-Alt-- "\e\C-_" or "\M-\C-_" or M-C-_ or etc "\e[27;7;189~"
    Ctrl-Alt-Shift-- "\e[27;8;189~" "\e\C-_" or "\M-\C-_" or M-C-_ or etc
  • Completions for all clink set settings include the current value in the description field (e.g. type clink set Alt-= to see Clink settings and their current values).
  • Fixed to differentiate between undo and vi-undo commands again (they do the same thing, but are technically different commands).
  • Fixed execute-named-command to also accept Ctrl-- for undo (the emacs binding for undo).
  • Fixed redisplaying multi-line prompts after using completion during execute-named-command.
  • Fixed accidentally loading the history file twice on each prompt; now it loads once, as intended.
  • Fixed another double-free and potential crash in the Readline library; after navigating through history entries and then editing a history entry, pressing Ctrl-c or Ctrl-Break could cause a crash or memory corruption (regression exposed by changes in Readline 8.2).
  • Applied fixes for 6 Lua bugs, curated by @goodusername123 (thank you!) from Lua.org:
    • "Dead keys with nil values can stay in weak tables."
    • "Expression list with four or more expressions in a 'for' loop can crash the interpreter."
    • "Label between local definitions can mix-up their initializations."
    • "Return hook may not see correct values for active local variables when function returns."
    • "Suspended __le metamethod can give wrong result."
    • "Wrong code generated for a 'goto' followed by a label inside an 'if'."
  • Fixed the Lua debugger so 5-digit line numbers don't break indentation when showing source code lines.
Assets 5