v1.4.15

• Added log.getfile() to get the current log file path.
• Fixed match display to better accommodate escape codes for italics and underline, if present and supported by the terminal.
• Fixed #414; argument color doesn't reset for values in multi-column layout when colored-stats is off.
• PR #418; Fix crash caused by destruction of non detached threads.
• PR #417; Fix buffer overread caused by usage of strcmp on non null-terminated char arrays.

v1.4.14

• Fixed autosuggest to update again if matches are marked as volatile and the input line changed while matches were generated in the background (related to clink-completions#164).

v1.4.13

• Added more status information in clink-diagnostics Ctrl-X,Ctrl-Z.
• Fixed quoting in the insert-completions Alt-* command.
• Fixed quoting for non-filename completions.
• Fixed a CPU busy-loop after match_builder:setvolatile() was called during an auto-suggest strategy.
• Fixed #411; setting %CLINK_HISTORY_LABEL% after Clink started didn't take effect (regression introduced in v1.3.18).

v1.4.12

• Additional improvements and logging for East Asian ambiguous width characters.
• Running clink inject no longer empties the log file, so that AutoRun doesn't result in the log file being cleared over and over, which interferes with diagnostic efforts.
• Fixed #407; the complete command gets confused by . prefix on files.

v1.4.11

• Fixed #406; the "lambdagenerated.omp.json" theme for Oh-My-Posh has problems in CJK codepages. The East Asian Ambiguous support has been rewritten to solve multiple subtle issues; the fix in v1.4.9 exposed other inaccuracies.

v1.4.10

• Added optional level argument to log.info() to facilitate more accurate reporting about the calling code.
• Fixed extra duplicate log entry when the updater finds that Clink is already up to date.
• Fixed #405; vi search gives unexpected results (regression introduced in v1.4.7).
• Fixed #402; for convenience, print the Clink Releases page URL after a successful update (takes effect on the next upgrade after v1.4.10).

v1.4.9

• Improved the problematic character reporting in the clink-diagnostics command.
• Fixed measurements for the East Asian ambiguous width characters (this should solve the Cmder problems with lambda in the CMD.exe prompt text, including the space after the lambda).

v1.4.8

• Added rl.needquotes() function to check whether text needs quotes in a command line.
• Changed the terminal.color_emoji setting auto mode to more broadly support accurate width measurements for color emoji (regardless whether the terminal program is capable of actually drawing the color emoji).
• Now clink-diagnostics Ctrl-X,Ctrl-Z automatically analyzes the prompt text for problematic characters, reports them, and offers suggestions for how to solve problems they might be causing.
• Fixed the completion autosuggest strategy so it doesn't provide a suggestion that requires quoting if the command line input is not currently quoted.
• Fixed overly aggressive detection of color emoji (regression introduced in v1.4.7).

v1.4.7

• Clink now supports ARM64.
• Clink now recognizes when the terminal host is WezTerm.
• Clink now supports color emoji in Windows Terminal and WezTerm, according to the Unicode v15.0 standard. The new terminal.color_emoji setting controls when Clink assumes the terminal supports color emoji (color emoji are rendered using double-width characters, which can interfere with cursor positioning math, so Clink needs to know whether the terminal supports color emoji).
• Enabled Readline's support for non-incremental vi-mode search (N, n) to search for a shell pattern using fnmatch(), as Posix specifies.
• Fixed obscure issue when a "luafunc:" macro modifies the input line and then invokes a completion command.
• Fixed line_state:getword() and line_state:getendword() to not strip quotes during generator:getwordbreakinfo() functions (regression introduced in v1.1.24).
• Fixed #393; backward compatibility issue when clink.arg.register_parser() is passed something that is not a parser at all.
• Fixed #111 again; cd ..Tab didn't complete to ..\ (regression introduced in v1.3.1).

v1.4.6

• Added a more informative exit code from clink inject. It returns 0 if successful, 2 if a fatal error occurred, or 1 if a non-fatal error occurred (such as Clink was already present; related to cmderdev/cmder#2800).
• Fixed #382; %CLINK_PROFILE% doesn't supersede --profile (regression introduced in v1.0.0).