You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many issues like #508 pointing out that non-executables don't autocomplete.
A current workaround exists: set exec_match_style to -1
# name: Executable match style
# type: enum
# 0 = PATH only
# 1 = PATH and CWD
# 2 = PATH, CWD, and directories
# Changes how Clink will match executables when there is no path separator on
# the line. 0 = PATH only, 1 = PATH and CWD, 2 = PATH, CWD, and directories. In
# all cases both executables and directories are matched when there is a path
# separator present. A value of -1 will disable executable matching completely.
exec_match_style = 2
This is a feature request to allow autocompletion for local files either:
All local files could auto-complete.
Allow us to define executables (*.exe, *.cmd, etc)
The text was updated successfully, but these errors were encountered:
On Windows in cmd.exe sessions executeable file extensions are configured by the PATHEXT environment variable. Mine is currently set to:
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
I'll leave this item opened - can we have this automatically populated by cmder instead of all of us adding to this environment? Maybe another config such as exec_extensions = ...?
There are many issues like #508 pointing out that non-executables don't autocomplete.
A current workaround exists: set exec_match_style to -1
This is a feature request to allow autocompletion for local files either:
The text was updated successfully, but these errors were encountered: