4 ms·

Looks promising, and support for huge files is a weak point in vim, so I gave it a try. My usual workflow with big logfiles is to zoom into certain types of mes

by dhoe 11y ago

Looks promising, and support for huge files is a weak point in vim, so I gave it a try. My usual workflow with big logfiles is to zoom into certain types of messages with e.g. :v/error/d and back out with u, and alternatively jump from one occurrence of a string to the next with *. That doesn't seem to work, so for the moment it's not the right 80% for me. But I do think it's a worthy project, so I'll keep an eye on this

chris_wot 11y ago
What does :v do?
- richy_rich 11y ago
  It's the same as :g!/error/d I believe
- efaref 11y ago
  :help :v will tell you: :[range]v[global]/{pattern}/[cmd] Same as :g!. Where: :[range]g[lobal]!/{pattern}/[cmd] Execute the Ex command [cmd] (default ":p") on the lines within [range] where {pattern} does NOT match. So :v/error/d will delete all lines that don't contain the string "error".
  - creshal 11y ago
    Which neatly maps to grep's -v option that does the same.
    - amelius 11y ago
      I always thought "-v" meant "verbose" traditionally in Unix command line options.
      - creshal 11y ago
        No tradition without exceptions.
  - chris_wot 11y ago
    Oh! I've been messing about with a bit of splitting up of C++ classes into seperate headers as a bit of a test and I recently did a: sed -i "/#include <vcl\/button\.hxx>/d" $(git grep -l "vcl\/button\.hxx" *.hxx | grep -v precompiled) Knowing about a :v might have been helpful...
martanne 11y ago
Everything involving searching is currently probably very slow for large files, this is especially true for backward searches. The reason being that we currently rely on the regexp engine of libc and thus have to copy the underlying text to a contiguous memory area. Navigating large files with motions like 50%, 70% should however be instantaneous. Navigating by line number is again somewhat slower, because the file actually needs to be read in this case. Aside from that :v/ has a different meaning in vis.

by dhoe 11y ago

chris_wot 11y ago

What does :v do?

richy_rich 11y ago
It's the same as :g!/error/d I believe
efaref 11y ago
:help :v will tell you: :[range]v[global]/{pattern}/[cmd] Same as :g!. Where: :[range]g[lobal]!/{pattern}/[cmd] Execute the Ex command [cmd] (default ":p") on the lines within [range] where {pattern} does NOT match. So :v/error/d will delete all lines that don't contain the string "error".
- creshal 11y ago
  Which neatly maps to grep's -v option that does the same.
  - amelius 11y ago
    I always thought "-v" meant "verbose" traditionally in Unix command line options.
    - creshal 11y ago
      No tradition without exceptions.
- chris_wot 11y ago
  Oh! I've been messing about with a bit of splitting up of C++ classes into seperate headers as a bit of a test and I recently did a: sed -i "/#include <vcl\/button\.hxx>/d" $(git grep -l "vcl\/button\.hxx" *.hxx | grep -v precompiled) Knowing about a :v might have been helpful...

martanne 11y ago

Everything involving searching is currently probably very slow for large files, this is especially true for backward searches. The reason being that we currently rely on the regexp engine of libc and thus have to copy the underlying text to a contiguous memory area. Navigating large files with motions like 50%, 70% should however be instantaneous. Navigating by line number is again somewhat slower, because the file actually needs to be read in this case. Aside from that :v/ has a different meaning in vis.