Releases: chrisant996/clink
v1.1.30
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
If this release candidate survives for 1 week without needing to be updated, the version number will be updated and it will become an official release version.
So, moving forward, releases will include the installer as well.
v1.1.30
- Fixed history compacting on x86 (regression introduced in v1.1.2-alpha).
v1.1.29
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
v1.1.29
- Added
clink installscripts
andclink uninstallscripts
to make it easy for package managers like Scoop to install/uninstall script packages for use with Clink. The installed script paths are stored in the registry for the current user. - Fixed
bold
vsbright
colors to more accurately follow generally accepted ANSI escape code conventions:- Renamed
dim
tonobold
for clarity (thoughdim
is still recognized for backward compatibility). bold
adds intensity to a non-intense color (e.g.cyan
which is 36).nobold
removes intensity added bybold
(e.g.1;36
becomes36
), but does not remove intensity from an explicit intense color (such asbright cyan
which is96
).
- Renamed
- Fixed support for
--file=
flags in argmatchers. - Fixed match display filtering on the first try for a word (regression introduced in v1.1.19).
- Fixed the
clink --profile
flag (regression introduced in v1.1.10). - Fixed
clink info
to accurately report the script dirs (it didn't account for theclink.path
setting correctly).
v1.1.28
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
v1.1.28
- Renamed the
log.rl_terminal
setting todebug.log_terminal
; it has already been repeatedly very useful in multiple was since it was added, so it stays. - Fixed #70; ctrl+c not working (regression introduced in v1.1.25).
v1.1.27
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
v1.1.27
- Added
color.argmatcher
setting which, when set, is used to color a command name if it has an associated argmatcher (this supersedescolor.cmd
,color.doskey
, andcolor.input
). By default it's not set. - Added
log.rl_terminal
setting which logs all terminal input and output for Readline (this setting may be renamed or removed in the future).
v1.1.26
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
(v1.1.25 almost managed to survive a week without fixes! Clink is very close to an official release. Alas, an important issue was found. But that enabled another feature to make it in: the ability for a "luafunc:" key binding to invoke other Readline commands, and to override match completions.)
Highlights for v1.1.26:
- Added
rl.invokecommand()
which can invoke a Readline command from inside a "luafunc:" key binding. - Added
rl.setmatches()
which can override match completions from inside a "luafunc:" key binding. - Worked around UTF8 key binding problem with Readline which had been causing some meta key bindings (M-x, M-C-x, etc) to sometimes produce garbled key bindings and garbled entries in
clink-show-help
(Alt+H). - Fixed crash if "luafunc:" key binding macro refers to a symbol that doesn't exist.
v1.1.25
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
(Yes, it's been hovering in release candidates for a while. That's because bugs keep being found that are important enough to fix before an official release. The goal is for this to be a quality-driven release, more than a date-driven release.)
Highlights for v1.1.25:
- Added
clink-find-conhost
command that, when in a default (conhost) console window, is equivalent to picking "Find..." from the system menu. - Added
clink-mark-conhost
command that, when in a default (conhost) console window, is equivalent to picking "Mark" from the system menu. clink-copy-word
now copies the current word by default, but copies the nth word if a numeric argument is entered (see "Readline Arguments" in the Readline manual).- Fixed match display filtering to not exceed the screen width (regression introduced in v1.1.12).
- Fixed multi-key sequences; in some cases it could get confused about whether an input key is part of a multi-key binding sequence (regression introduced in v1.1.1-alpha).
- Fixed stray input processing by conhost (holding Ctrl+A or Ctrl+F or etc could accidentally trigger conhost's shortcut keys).
- Fixed popup window location and size when using Windows Terminal.
- Fixed input coloring after
operate-and-get-next
; also fixes brief flicker of incorrect coloring whenever the input line is modified.
v1.1.24
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
(Yes, it's been hovering in release candidates for a while. That's because bugs keep being found that are important enough to fix before an official release. The goal is for this to be a quality-driven release, more than a date-driven release.)
Highlights for v1.1.24:
auto
forterminal.emulation
now uses native VT support on Windows 10 build 15063 and higher, unless the HKCU\Console\ForceV2 regkey is 0.- Special quote handling now enables
"dir\"fi
to complete to"dir\file"
. CMD simply strips quotes during completion, and now Clink behaves similarly. - Breaking Change:
line:getword()
andline:getendword()
now strip quotes from the word. This should generally automagically make existing match generators work even with embedded quotes, but there's a chance that some match generator might need to be updated. This seems like a reasonable compromise, given the general benefit purchased by this breaking change. os:globdirs()
andos:globfile()
strip quotes from the globpattern in order to behave more like CMD. Embedded quotes are nonsensical and the intended interpretation is clear, so the APIs now help out with that.- Fixed #66; crash when injecting into 32 bit cmd.
- Fixed #64; wrong cursor position when PROMPT contains BEL character.
- Fixed #62; argmatchers should color
-x:"foo"
as a flag if-x:
is a flag. - Fixed #61; argmatchers should not handle completion for text immediately following
-flag:
. Instead it always uses file completion. A custom generator can be used to override that behavior. - Fixed #60; completion fails with multiple slashes.
- Fixed completion in some circumstances. Readline and Clink didn't always agree on where the word breaks were; now Clink always tells Readline where the word breaks are (so that completion, input colorization, and lua scripts can all work properly and consistently).
- Fixed 256 color ANSI codes.
v1.1.23
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
Highlights for v1.1.23:
v1.1.22
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
Highlights for v1.1.22:
- Added
menu-complete-wraparound
(on by default) that controls whether completion commands wrap around when cycling past an end (affects popup windows as well). - Fixed match completion getting stuck (regression introduced in v1.1.19).
- Fixed active mark region so it gets deactivated appropriately (it wasn't hooked up fully for Readline's callback mode, which is how Clink uses it).
- Fixed
clink-show-help
(Alt+H) so it's able to listC-@
bindings. - Fixed inconsistent mark color.
v1.1.21
This is a release candidate build.
This release candidate build seems to be working very well for me, even when copied into an existing Cmder\vendor\clink directory. Be sure to make a backup copy of your Cmder installation before copying Clink into an existing Cmder installation!
Highlights for v1.1.21:
- Added
clink.oninject()
so scripts can register a callback function to run when Clink is injected into CMD. - Added
console.linehascolor()
function that returns whether the specified line contains any of the specified colors. - Added
console.findprevline()
andconsole.findnextline()
functions that can search backwards or forwards for text and/or colors in the screen buffer. Regular expressions may be used. - Fixed doskey alias parsing for match generators and input line coloring (Clink had been using slightly different parsing rules than CMD does).
- Fixed the "-- More --" prompt while listing key bindings; Esc didn't quit, and unexpected keys weren't ignored.