On Mon, May 13, 2019 at 5:38 PM Paul Jolly wrote:
>
> Hi all,
>
> I've tried searching using various terms, but I can't find anything specific
> on this question.
>
> Is there a way to get the Vim version number, short of redirecting the output
> of :version to a variable?
>
> I want the major,
Gary,
Yes I was thinking of that - a special check - but any perceptible
delay on the part of vim for what is such a common operation
(basically any operation) really goes against what I'm trying to get
at here usability wise. I really want this to be as close to a zero
cost operation as
i do it the brittle way
On Mon, May 13, 2019 at 10:38 AM Paul Jolly wrote:
>
> Hi all,
>
> I've tried searching using various terms, but I can't find anything specific
> on this question.
>
> Is there a way to get the Vim version number, short of redirecting the output
> of :version to a
On 2019-05-13, Ed Peschko wrote:
> Gary,
>
> thanks for this tip, yes it looks like I could use it to do what I
> want but my concern is speed. I don't want to trigger a potentially
> expensive macro each time the cursor moves anytime, just when the line
> number changes.
>
> So perhaps there is
Gary,
thanks for this tip, yes it looks like I could use it to do what I
want but my concern is speed. I don't want to trigger a potentially
expensive macro each time the cursor moves anytime, just when the line
number changes.
So perhaps there is a need for CursorLineMoved? I see in vim where I
On 2019-05-13, Mathieu Roux wrote:
> 2) when i go to :h g*, i can read:
>
>
> g* Like "*", but don't put "\<" and "\>" around
> the word.
> This makes the search also find matches that are not a
> whole word. {not in Vi}
>
> Really, i don't
On 2019-05-13, Ed Peschko wrote:
> All,
>
> I just found :set nolazyredraw, which is *very* nice in speeding up
> user interaction time, and which helps immensely with my goal of a
> quickfix-like editing mode (see the post that I made earlier), so the
> only thing left is if there is a way to
On ven., 2019-05-10 at 17:05 +0200, 'Andy Wokula' via vim_use wrote:
> Am 09.05.2019 um 20:20 schrieb Mathieu Roux:
> > I have so many questions:
> >
> > 1) map :set isk+=#-normal *
> > Vim's help about "bar" does not allow me to understand what it
> > means.
>
> Relevant help sections are
>
On sam., 2019-05-11 at 20:28 +1000, Erik Christiansen wrote:
> On 11.05.19 14:34, Erik Christiansen wrote:
> > On 10.05.19 19:29, Mathieu Roux wrote:
> > > 1) |plouf| is colored is blue, and *plouf* is colored in red when
> > > open
> > > with vi. It is function of hightlight, right? How can i use
All,
I just found :set nolazyredraw, which is *very* nice in speeding up
user interaction time, and which helps immensely with my goal of a
quickfix-like editing mode (see the post that I made earlier), so the
only thing left is if there is a way to trigger an action when you go
to a new line,
All,
I had an idea in mind for how I would like to use vim. On a regular
basis we generate logs of scripts which have 'quickfix-like' elements
in them - stack-traces and the like.
I'd like to be able to navigate to a given line of the file containing
the stack-traces and based off of a
Hi all,
I've tried searching using various terms, but I can't find anything specific on
this question.
Is there a way to get the Vim version number, short of redirecting the output
of :version to a variable?
I want the major, minor and patch details to ultimately build a semver version.
I
On Sun, May 12, 2019 at 11:08:16AM +0200, tu...@posteo.de wrote:
every time, when I do this und Linux:
* copy some text from a terminalo
* start another terminal
* start vim (vim in an terminal, not gvim)
* go into insert mode
* click the middle mouse button to insert
I get the text inserted
13 matches
Mail list logo
