Re: [dev] structural regular expression support for vis

From: Marc André Tanner <>
Date: Thu, 5 May 2016 13:09:29 +0200

Hi all,

While there are still some bugs left, I'm quite happy how structural
regexp support for vis is progressing. Known issues include:

 - relative line specifiers are in some cases wrongly interpreted,
   as a consequence -0+,+0- rounds dot up instead of down to whole

 - s (substitute) is implemented in terms of sed(1) called without any
   arguments, hence:

    * the count in s2/foo/bar is not supported

    * it defaults to basic regular expression syntax whereas the rest of
      vis uses the extended variation. Specifying which kind of regexp
      to use doesn't seem portable (GNU sed uses -r, BSD -E, POSIX does
      not specify it). As a result this requires ugly escaping:
      s/\(a\),\(b\)/\2,\1/ instead of simply s/(a),(b)/\2,\1/ as is
      possible in sam.

      This particular case can be achieved by means of selection content
      rotation in vis, but still it is an ugly inconsistency which should
      be fixed at some point. All of vis should use the same regex syntax.

 - multiple file support is still completely untested/broken

 - with the current command prompt it is kind of hard to enter multi line
   commands. It is possible by using <C-v><Enter> to insert a literal
   newline. To execute the command it has to be selected, <Enter> then
   executes the active selection.

 - grouped commands { .. } do not operate on the same (initial) text state.
   As previously discussed in this thread this will likely remain that way
   for the foreseeable future.

It would be nice to get some more feedback, what annoys you the most?

Current git master can be considered as a release candidate of vis-0.3:


 Marc André Tanner >< >< GPG key: 10C93617
Received on Thu May 05 2016 - 13:09:29 CEST

This archive was generated by hypermail 2.3.0 : Thu May 05 2016 - 13:12:12 CEST