fish-shell/share/completions/j.fish

function __history_completions --argument limit
	if echo $limit | string match -q ""
	    set limit 25
	end

	set -l tokens (commandline --current-process --tokenize)
	history --prefix (commandline) | string replace -r \^$tokens[1]\\s\* "" | head -n$limit
end

complete -k -c j -a '(__history_completions 25)' -f
Implement limits for __history_completions in j completions 2017-10-04 23:52:58 +08:00			`function __history_completions --argument limit`
			`if echo $limit \| string match -q ""`
			`set limit 25`
			`end`

Add history-based completions for autojump's j command j does not have any "logical" source of completions, but it almost often called with arguments that have been seen before (since it is used to jump to favorite/recent directories). We can search the history for possible completions and use those. This is an example of the behavior mentioned in #4344 as a possible enhancement for fish 3.0, where completions can be provided from history if none are otherwise found. 2017-09-21 09:50:10 +08:00			`set -l tokens (commandline --current-process --tokenize)`
Implement limits for __history_completions in j completions 2017-10-04 23:52:58 +08:00			`history --prefix (commandline) \| string replace -r \^$tokens[1]\\s\* "" \| head -n$limit`
Add history-based completions for autojump's j command j does not have any "logical" source of completions, but it almost often called with arguments that have been seen before (since it is used to jump to favorite/recent directories). We can search the history for possible completions and use those. This is an example of the behavior mentioned in #4344 as a possible enhancement for fish 3.0, where completions can be provided from history if none are otherwise found. 2017-09-21 09:50:10 +08:00			`end`

Implement limits for __history_completions in j completions 2017-10-04 23:52:58 +08:00			`complete -k -c j -a '(__history_completions 25)' -f`