vis - a neat vi-like editor

Age	Commit message (Collapse)	Author	Files	Lines
2016-10-28	vis-complete: allow custom input not matching any completion candidate	Marc André Tanner	1	-1/+1
	See also discussion in #402.
2016-10-11	File completion updates	Richard Burke	1	-5/+11

2016-10-08	Teach vis-complete that ".." path segments in the prefix are acceptable.	Tim Allen	1	-2/+9
	Instead of trying to filter out path-segments-beginning-with-dot from the entire path (including the prefix, which would be perfectly legitimate), tell find to prune hidden directories and ignore hidden file as it walks the tree.
2016-10-08	Quote meta-characters in the completion pattern.	Tim Allen	1	-2/+7
	Because we're completing text from the document, we can't assume it's going to be a sensible regex pattern, or glob pattern, let alone both, so we should quote the pattern before we hand it off to helper tools like grep and find.
2016-10-08	Handle completing absolute paths, not just relative ones.	Tim Allen	1	-2/+20

2016-10-07	Don't use repeated shell evaluation in vis-complete.	Tim Allen	1	-11/+3
	Previously, vis-complete built up a command-line by repeated subtitution into a shell variable, then executing that shell variable in a subshell. I'm not entirely sure what shell-meta-character mischief would have been possible, but now we just do all the piping in the same shell which is much safer.
2016-10-05	Harden vis-complete	Richard Burke	1	-2/+7

2016-10-05	vis-complete - Use different delimiter in sed command	Richard Burke	1	-1/+1
	This is to avoid issues when handling file paths
2016-09-25	vis: move file name and word completion logic to a shell script	Marc André Tanner	1	-0/+35
	The shell script should be reviewed for quoting issues, currently it allows command injections as in: $ vis-complete "'; rm -f some-file; echo " However it is intended for interactive usage and from within vis it is only ever called with a valid completion prefix. The file name completion logic now supports nested directories. Close #347