On Tue, Jan 19, 2016 at 01:56:32PM +0100, Marc André Tanner wrote:
> On Sun, Jan 17, 2016 at 07:59:50PM +0100, Silvan Jegen wrote:
> > On Sun, Jan 17, 2016 at 07:23:06PM +0100, Marc André Tanner wrote:
> > > The current source tree contains a `vis-open` shell script which
> > > provides basic file system navigation by means of fuzzy matching using
> > > either slmenu or dmenu. It is invoked by default if you open a directory
> > >
> > > :split .
> > >
> > > or supply a path containing other shell wildcards such as *, {, or [.
> >
> > I have seen the script but I was not sure how to use it from vis itself.
> > Being able to open a file to edit in the same vis instance using
> > "vis-open" (using the :edit command) would be welcome. I will look into
> > it when I have I access to my desktop.
>
> :e .
> :e *.c
>
> should work if vis-open and slmenu is in your $PATH.
I like that a lot.
I could not find anything about this in the README so I wrote a short
quip about that feature.
diff --git a/README.md b/README.md
index aa159e6..5bf3d3d 100644
--- a/README.md
+++ b/README.md
@@ -320,8 +320,16 @@ Operators can be forced to work line wise by specifying
`V`.
* the current selection, equivalent to '<,'>
History support, tab completion and wildcard expansion are other
- worthwhile features. However implementing them inside the editor
- feels wrong.
+ worthwhile features. However implementing them inside the editor feels
+ wrong. For now you can use the `:edit` command with a pattern or a
+ directory like this.
+
+ :e *.c
+ :e .
+
+ vis will call the `vis-open` script which invokes dmenu or slmenu
+ with the files corresponding to the pattern. The file you select in
+ dmenu/slmenu will be opened in vis.
### Tab <-> Space conversion and Line endings \n vs \r\n
