Re: Persistent undo and swapfile

Manfred Lotz wrote:

> I have persistent undo configured and it helped me a lot in various situations
> over the last 5 or so years.
>
> I also have swapfile configured but I am actually not sure if it is really
> required if persistent undo is active.
>
> Any thoughts?

You do need both.

The persistent undo is great to be able to back in time, even when you
unload the buffer, quit Vim and come back another day. I especially use
it to add debugging commands, try lots of things, and finally just undo
the changes. No version control system needed.

The swapfile is a safety net for the unexpected. Vim might crash. I
know, for normal users this hardly ever happens, still I keep fixing
crashes all the time (fuzzers try just about any random input to look
for these problems). Or your computer might die. Hopefully that
doesn't happen either. But still, it happens when you least expect it.

--
Living in Hollywood is like living in a bowl of granola. What ain't
fruits and nuts is flakes.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211231233317.487E01C0A5B%40moolenaar.net.

Persistent undo and swapfile

I have persistent undo configured and it helped me a lot in various situations
over the last 5 or so years.

I also have swapfile configured but I am actually not sure if it is really
required if persistent undo is active.

Any thoughts?


--
Manfred

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/74a37d11-e216-74d9-0adb-65fca4e3235c%40posteo.de.

Re: Vim9 script feature-complete

Bram Moolenaar said on Thu, 30 Dec 2021 20:39:52 +0000


>The work on Vim9 script is coming to a point where the syntax and
>semantics are practially done.

[snip]

>
>The information about Vim9 script and many of the choices made can be
>found in a recent build with ":help vim9". Or see it online (without
>concealing):
>https://github.com/vim/vim/blob/master/runtime/doc/vim9.txt

I read through both :h vim9 and the github address above, and saw
nothing about that awful "localleader" thing that has caused so much
political trouble for the VimOutliner project. With Vim9, has the need
for "localleader" gone away?

Thanks,

SteveT

Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211231140111.5494b0cd%40mydesk.domain.cxm.

Re: :so should take a range ?

пт, 31 дек. 2021 г., 11:48 Marc Chantreux <mc@unistra.fr>:

hello people,

Years ago, i wrote a [range]Source so you can type some viml in your
current buffer and run it. This is useful in many situations (for
exemple cd to a directory refered in a log).

https://github.com/eiro/rcfiles/blob/master/vim/vimfiles/plugin/source_range.vim

I made a demo of this to some colleagues and someone asked why isn't it
a core feature. I have to admit i never thought about that but it makes
sense:

* doesn't conflict with another feature
* sourcing viml is obviously already implemented so i imagine adding a
  range shouldn't be that hard

maybe none got the idea to ask so i do now :)

happy new year everyone.

regards
marc

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/Yc68VArXcuLwMilG%40prometheus.u-strasbg.fr.

Hello,

Builtin :source adds file into the scripts list (cf. :scriptnames) and assigns script id (aka SID) which is essential for s: scope support. It won't be easy to reuse this SID by "a ranged source". And bringing "an incomplete feature" into the core could be too much confusing.

BTW. Using getline()+execute() or simply yanking and then executing a register with :@0 looks nicer, imo, then storing data into temporary file.

Regards,

Matvey

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAFsTB%2BKRyKtx9Uo5kNzFDma0xZXVguf_F%3DMbrNpJV1a925ahMw%40mail.gmail.com.

:so should take a range ?

hello people,

Years ago, i wrote a [range]Source so you can type some viml in your
current buffer and run it. This is useful in many situations (for
exemple cd to a directory refered in a log).

https://github.com/eiro/rcfiles/blob/master/vim/vimfiles/plugin/source_range.vim

I made a demo of this to some colleagues and someone asked why isn't it
a core feature. I have to admit i never thought about that but it makes
sense:

* doesn't conflict with another feature
* sourcing viml is obviously already implemented so i imagine adding a
range shouldn't be that hard

maybe none got the idea to ask so i do now :)

happy new year everyone.

regards
marc

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/Yc68VArXcuLwMilG%40prometheus.u-strasbg.fr.

Re: Vim9 script feature-complete

Sorry for sending to Bran directly: I didn't notice till it was too late
that ThUnderbird ignored the Reply-to line.

--
Stan Brown
Tehachapi, CA, USA
https://BrownMath.com


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/2cf92d24-4bee-888f-4307-c8650f5f26b6%40fastmail.fm.

Vim9 script feature-complete

[it appears this message did not reach the list, sending it again]

The work on Vim9 script is coming to a point where the syntax and
semantics are practially done. There might be some more tests
uncovering problems that need to be fixed and perhaps some tiny tweaks,
but otherwise it has been quite stable for the past months.

If you have remarks on something in Vim9 script that you think should be
different, speak up now! Soon we'll only make backwards compatible
changes to avoid breaking existing plugins.

The information about Vim9 script and many of the choices made can be
found in a recent build with ":help vim9". Or see it online (without
concealing): https://github.com/vim/vim/blob/master/runtime/doc/vim9.txt

In a few days I will add the "vim9script" feature, so that plugins can
check for Vim9 script being supported and rely on it working. From that
moment Vim9 script needs to be backwards compatible!

This is not the end, I plan to add more features later. But these will
be backwards compatible. That is why some commands such as "class" and
"interface" have been reserved for future use.

I will now work on including remarks about the Vim9 syntax throughout
the help text.

--
hundred-and-one symptoms of being an internet addict:
115. You are late picking up your kid from school and try to explain
to the teacher you were stuck in Web traffic.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211230203952.4FBD51C0A5B%40moolenaar.net.

Get Terminal current directory for a specific window

Hello,

I am using GVIM in Windows.
In a terminal window via ':terminal' (shell is cmd.exe), is there a way to return a string that is the actual dynamic current directory?
getcwd() and expand() always return the current working directory, which for ':terminal' is the path of cmd.exe, not the actual current directory in the terminal buffer/window.
Cmd.exe with command extensions enabled has access to the dynamic environment variable %CD%, but Vim does not appear to see the dynamic environment variables (unless there is a way).
What would be perfect is something like getenv('CD'), but somehow also target the buffer/window of a specific active terminal.
One use I have in mind is titlestring, so it needs to be efficient/fast.

Thanks,
Chainsaw

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211229143628.00002781%40cfl.rr.com.

Re: GVIM replace from clipboard woes!

On Mo, 27 Dez 2021, Mike Schleif wrote:

> NOTE: I created a 2nd post, when this one didn't appear for several hours. In that post, I remembered to describe the undesired behavior:
>
> On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the originally copied string!
>
> Please, advise. Thank you.

Not sure what exact problem you are facing. Please check (or show) the
following options:

:set guioptions?
:set clipboard?

Also note, you can check what is in your register by using the :register
command. That show the clipboard (+) as well as the various other
internal Vim registers

Best
Christian
--
Wer sich von jeher erlaubt hätte, die Welt so schlecht
anzusehen, wie uns die Widersacher darstellen, der müsste ein
miserables Subjekt geworden sein.
-- Goethe, Maximen und Reflektionen, Nr. 422

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211228082812.GH3308345%40256bit.org.

Re: GVIM replace from clipbrard?

On 2021-12-26, Mike Schleif wrote:
> I use VIM on various *NIX platforms.
>
> I use GVIM on various MS Windows hosts.
>
> I often do this:
> 1. Copy a string to the clipboard
> 2. Visual mode select a string
> 3. :s/<type a string to be replaces>/<Ctrl-v the clipboard string>/g
> 4. Enter - replace all substrings
>
> This works delightfully everywhere - EXCEPT on Windows host!
>
> On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the
> originally copied string!
>
> I'm sure that I've got something in that host's VIMRC; but, what is it?

One way to find out the difference between the configurations on
working and non-working hosts would be to run vim or gvim on both
hosts and execute the following on both:

:set nomore
:redir >> hostname.redir
:set! all

Then use vimdiff to compare the two .redir files.

Regards,
Gary

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211228051050.GD26168%40phoenix.

Re: GVIM replace from clipbrard?

There  are three questions in-lined below.

On 12/27/2021 3:15 PM, Mike Schleif wrote:

On Mon, Dec 27, 2021 at 12:12 PM 'Paul' via vim_use <vim_use@googlegroups.com> wrote:

On Sun, Dec 26, 2021 at 08:42:41AM -0800, Mike Schleif wrote:
>I use VIM on various *NIX platforms.
>
>I use GVIM on various MS Windows hosts.
>
>I often do this:
>1. Copy a string to the clipboard
>2. Visual mode select a string

How exactly do you do get into visual mode on the troublesome windows computer?

>3. :s/<type a string to be replaces>/<Ctrl-v the clipboard string>/g
>4. Enter - replace all substrings
>
>This works delightfully everywhere - EXCEPT on Windows host!
>
>On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the
>originally copied string!
>

After issuing the command ":registers" do you see the copied text in some register? If so, which register?

>I'm sure that I've got something in that host's VIMRC; but, what is it?

What do you find if you search in that vimrc file for "-v" (case in-sensitive)?

See :help CTRL-Q

Although I think I understand :help CTRL-Q, I fail to understand how that resolves the different behavior on one host.

Please, advise. Thank you.

~ Mike

Re: GVIM replace from clipbrard?

On Mon, Dec 27, 2021 at 12:12 PM 'Paul' via vim_use <vim_use@googlegroups.com> wrote:

On Sun, Dec 26, 2021 at 08:42:41AM -0800, Mike Schleif wrote:
>I use VIM on various *NIX platforms.
>
>I use GVIM on various MS Windows hosts.
>
>I often do this:
>1. Copy a string to the clipboard
>2. Visual mode select a string
>3. :s/<type a string to be replaces>/<Ctrl-v the clipboard string>/g
>4. Enter - replace all substrings
>
>This works delightfully everywhere - EXCEPT on Windows host!
>
>On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the
>originally copied string!
>
>I'm sure that I've got something in that host's VIMRC; but, what is it?

See :help CTRL-Q

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/YcoCF8m5JLPWM1W1%40rainslide.net.

Although I think I understand :help CTRL-Q, I fail to understand how that resolves the different behavior on one host.

Please, advise. Thank you.

~ Mike

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACNUArBY25y4ZN19mAY6w5F2vL0%3D42_4st3hjSjuveCYnpy_Nw%40mail.gmail.com.

Re: GVIM replace from clipboard woes!

source $VIMRUNTIME/mswin.vim
" Last change: 2017 Oct 28

if has("clipboard")
    " CTRL-X and SHIFT-Del are Cut
    vnoremap <C-X> "+x
    vnoremap <S-Del> "+x

    " CTRL-C and CTRL-Insert are Copy
    vnoremap <C-C> "+y
    vnoremap <C-Insert> "+y

    " CTRL-V and SHIFT-Insert are Paste
    map <C-V> "+gP
    map <S-Insert> "+gP

    cmap <C-V> <C-R>+
    cmap <S-Insert> <C-R>+
endif


NOTE: I created a 2nd post, when this one didn't appear for several hours. In that post, I remembered to describe the undesired behavior:

On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the originally copied string!

Please, advise. Thank you.

~ Mike

On Mon, Dec 27, 2021 at 6:29 AM Bram Moolenaar <Bram@moolenaar.net> wrote:

Mike Schleif wrote:

> I use VIM on various *NIX platforms.
>
> I use GVIM on various MS Windows hosts.
>
> I often do this:
> 1. Copy a string to the clipboard
> 2. Visual mode select a string
> 3. :s/<type a substring to be replaced>/<Ctrl-v the clipboard string>/g
> 4. Enter - replace all substrings
>
> This works delightfully everywhere - EXCEPT one Windows host!
>
> I'm sure that I've got something in that host's VIMRC; but, what is it?
>
> This has been plaguing me for months ...
>
> Please, advise. Thank you.

Did you check the value of the 'clipboard' option?

--
An actual excerpt from a classified section of a city newspaper:
"Illiterate?  Write today for free help!"

 /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \\\
///                                                                      \\\
\\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACNUArDxd3YYQBFuW3EBU9-30FR8%2BaD3eDH_EFu4UthNfAF3wg%40mail.gmail.com.

Re: GVIM replace from clipbrard?

On Sun, Dec 26, 2021 at 08:42:41AM -0800, Mike Schleif wrote:
>I use VIM on various *NIX platforms.
>
>I use GVIM on various MS Windows hosts.
>
>I often do this:
>1. Copy a string to the clipboard
>2. Visual mode select a string
>3. :s/<type a string to be replaces>/<Ctrl-v the clipboard string>/g
>4. Enter - replace all substrings
>
>This works delightfully everywhere - EXCEPT on Windows host!
>
>On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the
>originally copied string!
>
>I'm sure that I've got something in that host's VIMRC; but, what is it?

See :help CTRL-Q

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/YcoCF8m5JLPWM1W1%40rainslide.net.

Re: GVIM replace from clipboard woes!

Mike Schleif wrote:

> I use VIM on various *NIX platforms.
>
> I use GVIM on various MS Windows hosts.
>
> I often do this:
> 1. Copy a string to the clipboard
> 2. Visual mode select a string
> 3. :s/<type a substring to be replaced>/<Ctrl-v the clipboard string>/g
> 4. Enter - replace all substrings
>
> This works delightfully everywhere - EXCEPT one Windows host!
>
> I'm sure that I've got something in that host's VIMRC; but, what is it?
>
> This has been plaguing me for months ...
>
> Please, advise. Thank you.

Did you check the value of the 'clipboard' option?

--
An actual excerpt from a classified section of a city newspaper:
"Illiterate? Write today for free help!"

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211227122957.1468A1C0642%40moolenaar.net.

GVIM replace from clipbrard?

I use VIM on various *NIX platforms.

I use GVIM on various MS Windows hosts.

I often do this:
1. Copy a string to the clipboard
2. Visual mode select a string
3. :s/<type a string to be replaces>/<Ctrl-v the clipboard string>/g
4. Enter - replace all substrings

This works delightfully everywhere - EXCEPT on Windows host!

On that host, Ctrl-v pastes the entire Visual Mode selection - NOT the originally copied string!

I'm sure that I've got something in that host's VIMRC; but, what is it?

This has been plaguing me for months ...

Please, advise. Thank you.

~ Mike

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/a0f3be33-731a-4d13-8ccd-a9f4ca311f60n%40googlegroups.com.

GVIM replace from clipboard woes!

I use VIM on various *NIX platforms.

I use GVIM on various MS Windows hosts.

I often do this:
1. Copy a string to the clipboard
2. Visual mode select a string
3. :s/<type a substring to be replaced>/<Ctrl-v the clipboard string>/g
4. Enter - replace all substrings

This works delightfully everywhere - EXCEPT one Windows host!

I'm sure that I've got something in that host's VIMRC; but, what is it?

This has been plaguing me for months ...

Please, advise. Thank you.

~ Mike

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/99a9252f-ba0d-4526-a759-c914fc58dde2n%40googlegroups.com.

Re: vim9 | how to force legacy vimscript execution

resolved by porting just plugin part of this plugin in vim9script

https://github.com/niva-xx/vim9tagbar.git

Le jeudi 23 décembre 2021 à 15:00:22 UTC+1, Ni Va a écrit :

It seems that the problem is in interaction between vim9script | vimscript through vimrun launch command. 

eg : my _vimrc is written in vim9script and the fact that Startuptime command (autoload part of https://github.com/tweekmonster/startuptime.vim. ) launches 

a vimrun.exe of all plugin as TagBar which is written in vimscript legacy.

Le jeudi 23 décembre 2021 à 13:55:53 UTC+1, Ni Va a écrit :

Hum, I got a doubt on my used version of gvim x86 build mingw under Win10.

It seems to be daily updated as described:

:ver
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Dec 23 2021 10:21:53)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-3877
Compiled by nicolas.v
Huge version with GUI.  Features included (+) or not (-):
+acl                +eval               +multi_byte_ime/dyn +tag_binary
+arabic             +ex_extra           +multi_lang         -tag_old_static
+autocmd            +extra_search       -mzscheme           -tag_any_white
+autochdir          -farsi              +netbeans_intg      -tcl
+autoservername     +file_in_path       +num64              -termguicolors
+balloon_eval       +find_in_path       +ole                +terminal
-balloon_eval_term  +float              +packages           -termresponse
+browse             +folding            +path_extra         +textobjects
++builtin_terms     -footer             -perl               +textprop
+byte_offset        +gettext/dyn        +persistent_undo    -tgetent
+channel            -hangul_input       +popupwin           +timers
+cindent            +iconv/dyn          -postscript         +title
+clientserver       +insert_expand      +printer            +toolbar
+clipboard          +ipv6               +profile            +user_commands
+cmdline_compl      +job                -python             +vartabs
+cmdline_hist       +jumplist           +python3/dyn        +vertsplit
+cmdline_info       +keymap             +quickfix           +virtualedit
+comments           +lambda             +reltime            +visual

Le jeudi 23 décembre 2021 à 13:47:17 UTC+1, antoine.m...@gmail.com a écrit :

On Thu, Dec 23, 2021 at 1:33 PM Ni Va <niva...@gmail.com> wrote:
>
> Hi
> This issue is general.
>
> This is for TagBar plugin : Plug 'https://github.com/preservim/tagbar.git'
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 39: E10: \ should be followed by /, ? or &
> line 40: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[133]..function <SNR>63_setup_options: line 35: E697: Missing end of List ']':
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 136: E15: Invalid expression: "has('multi_byte') && has('unix') && &encoding
> ==# 'utf-8' &&" line 137: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[178]..function <SNR>63_setup_keymaps: line 1: E697: Missing end of List ']':
>
>
>
> This is for coc.vim : Plug 'neoclide/coc.nvim'
>
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\coc.nvi
> m\plugin\coc.vim[49]..function coc#rpc#start_server[17]..<SNR>48_start:
>
> line 10: E723: Missing end of Dictionary '}':
> line 11: E10: \ should be followed by /, ? or &
> line 12: E10: \ should be followed by /, ? or &
> line 13: E10: \ should be followed by /, ? or &
> line 14: E10: \ should be followed by /, ? or &
> line 15: E10: \ should be followed by /, ? or &
> line 16: E10: \ should be followed by /, ? or &
> line 17: E10: \ should be followed by /, ? or &
> line 18: E10: \ should be followed by /, ? or &
> line 19: E10: \ should be followed by /, ? or &
>
> Le jeudi 23 décembre 2021 à 13:23:06 UTC+1, antoine.m...@gmail.com a écrit :
>>
>> On Thu, Dec 23, 2021 at 10:55 AM Ni Va <niva...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.
>> >
>> > It is managed by Plug.vim plugins' manager in my vim9script _vimrc.
>> >
>> > It appears startuptime.vim warns on some script code such as :
>> >
>> > echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
>> > \ 'that prevents this version of Tagbar from working.'
>> > \ 'Please use the alternate version posted on the website.'
>> >
>> >
>> > identically warns on if brackets spread on multiple lines.
>> >
>> > How can I fix it or fix this call of legacy vimscript ?
>> >
>> > Thank you
>> > NiVa
>>
>> I can't find this echomsg statement in startuptime.vim as linked. I
>> suppose it comes from somewhere in Tagbar. Could you please tell us
>> what code (if statement etc.) triggers this message? (I suppose you
>> are using Vim 8.2 aren't you?)
>>
>> Best regards,
>> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

This is the code in Tagbar where the error message you previously
mentioned was produced:

if v:version == 700 && !has('patch167')
echohl WarningMsg
echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
\ 'that prevents this version of Tagbar from working.'
\ 'Please use the alternate version posted on the website.'
echohl None
finish
endif

It means you are using Vim 7.0 without patch 7.0.167. That version of
Vim is obsolete. Please upgrade to at least version 8.2 (the current
patchlevel as of this writing is 8.2.3877 AFAIK).

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/da007e43-4672-40d8-8929-9ba5b0458839n%40googlegroups.com.

Re: vim9 | how to force legacy vimscript execution

It seems that the problem is in interaction between vim9script | vimscript through vimrun launch command. 

eg : my _vimrc is written in vim9script and the fact that Startuptime command (autoload part of https://github.com/tweekmonster/startuptime.vim. ) launches 

a vimrun.exe of all plugin as TagBar which is written in vimscript legacy.

Le jeudi 23 décembre 2021 à 13:55:53 UTC+1, Ni Va a écrit :

Hum, I got a doubt on my used version of gvim x86 build mingw under Win10.

It seems to be daily updated as described:

:ver
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Dec 23 2021 10:21:53)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-3877
Compiled by nicolas.v
Huge version with GUI.  Features included (+) or not (-):
+acl                +eval               +multi_byte_ime/dyn +tag_binary
+arabic             +ex_extra           +multi_lang         -tag_old_static
+autocmd            +extra_search       -mzscheme           -tag_any_white
+autochdir          -farsi              +netbeans_intg      -tcl
+autoservername     +file_in_path       +num64              -termguicolors
+balloon_eval       +find_in_path       +ole                +terminal
-balloon_eval_term  +float              +packages           -termresponse
+browse             +folding            +path_extra         +textobjects
++builtin_terms     -footer             -perl               +textprop
+byte_offset        +gettext/dyn        +persistent_undo    -tgetent
+channel            -hangul_input       +popupwin           +timers
+cindent            +iconv/dyn          -postscript         +title
+clientserver       +insert_expand      +printer            +toolbar
+clipboard          +ipv6               +profile            +user_commands
+cmdline_compl      +job                -python             +vartabs
+cmdline_hist       +jumplist           +python3/dyn        +vertsplit
+cmdline_info       +keymap             +quickfix           +virtualedit
+comments           +lambda             +reltime            +visual

Le jeudi 23 décembre 2021 à 13:47:17 UTC+1, antoine.m...@gmail.com a écrit :

On Thu, Dec 23, 2021 at 1:33 PM Ni Va <niva...@gmail.com> wrote:
>
> Hi
> This issue is general.
>
> This is for TagBar plugin : Plug 'https://github.com/preservim/tagbar.git'
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 39: E10: \ should be followed by /, ? or &
> line 40: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[133]..function <SNR>63_setup_options: line 35: E697: Missing end of List ']':
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 136: E15: Invalid expression: "has('multi_byte') && has('unix') && &encoding
> ==# 'utf-8' &&" line 137: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[178]..function <SNR>63_setup_keymaps: line 1: E697: Missing end of List ']':
>
>
>
> This is for coc.vim : Plug 'neoclide/coc.nvim'
>
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\coc.nvi
> m\plugin\coc.vim[49]..function coc#rpc#start_server[17]..<SNR>48_start:
>
> line 10: E723: Missing end of Dictionary '}':
> line 11: E10: \ should be followed by /, ? or &
> line 12: E10: \ should be followed by /, ? or &
> line 13: E10: \ should be followed by /, ? or &
> line 14: E10: \ should be followed by /, ? or &
> line 15: E10: \ should be followed by /, ? or &
> line 16: E10: \ should be followed by /, ? or &
> line 17: E10: \ should be followed by /, ? or &
> line 18: E10: \ should be followed by /, ? or &
> line 19: E10: \ should be followed by /, ? or &
>
> Le jeudi 23 décembre 2021 à 13:23:06 UTC+1, antoine.m...@gmail.com a écrit :
>>
>> On Thu, Dec 23, 2021 at 10:55 AM Ni Va <niva...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.
>> >
>> > It is managed by Plug.vim plugins' manager in my vim9script _vimrc.
>> >
>> > It appears startuptime.vim warns on some script code such as :
>> >
>> > echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
>> > \ 'that prevents this version of Tagbar from working.'
>> > \ 'Please use the alternate version posted on the website.'
>> >
>> >
>> > identically warns on if brackets spread on multiple lines.
>> >
>> > How can I fix it or fix this call of legacy vimscript ?
>> >
>> > Thank you
>> > NiVa
>>
>> I can't find this echomsg statement in startuptime.vim as linked. I
>> suppose it comes from somewhere in Tagbar. Could you please tell us
>> what code (if statement etc.) triggers this message? (I suppose you
>> are using Vim 8.2 aren't you?)
>>
>> Best regards,
>> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

This is the code in Tagbar where the error message you previously
mentioned was produced:

if v:version == 700 && !has('patch167')
echohl WarningMsg
echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
\ 'that prevents this version of Tagbar from working.'
\ 'Please use the alternate version posted on the website.'
echohl None
finish
endif

It means you are using Vim 7.0 without patch 7.0.167. That version of
Vim is obsolete. Please upgrade to at least version 8.2 (the current
patchlevel as of this writing is 8.2.3877 AFAIK).

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/70d91755-f6fd-4340-a9ac-0f229685039dn%40googlegroups.com.

Re: vim9 | how to force legacy vimscript execution

Hum, I got a doubt on my used version of gvim x86 build mingw under Win10.

It seems to be daily updated as described:

:ver
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Dec 23 2021 10:21:53)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-3877
Compiled by nicolas.v
Huge version with GUI.  Features included (+) or not (-):
+acl                +eval               +multi_byte_ime/dyn +tag_binary
+arabic             +ex_extra           +multi_lang         -tag_old_static
+autocmd            +extra_search       -mzscheme           -tag_any_white
+autochdir          -farsi              +netbeans_intg      -tcl
+autoservername     +file_in_path       +num64              -termguicolors
+balloon_eval       +find_in_path       +ole                +terminal
-balloon_eval_term  +float              +packages           -termresponse
+browse             +folding            +path_extra         +textobjects
++builtin_terms     -footer             -perl               +textprop
+byte_offset        +gettext/dyn        +persistent_undo    -tgetent
+channel            -hangul_input       +popupwin           +timers
+cindent            +iconv/dyn          -postscript         +title
+clientserver       +insert_expand      +printer            +toolbar
+clipboard          +ipv6               +profile            +user_commands
+cmdline_compl      +job                -python             +vartabs
+cmdline_hist       +jumplist           +python3/dyn        +vertsplit
+cmdline_info       +keymap             +quickfix           +virtualedit
+comments           +lambda             +reltime            +visual

Le jeudi 23 décembre 2021 à 13:47:17 UTC+1, antoine.m...@gmail.com a écrit :

On Thu, Dec 23, 2021 at 1:33 PM Ni Va <niva...@gmail.com> wrote:
>
> Hi
> This issue is general.
>
> This is for TagBar plugin : Plug 'https://github.com/preservim/tagbar.git'
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 39: E10: \ should be followed by /, ? or &
> line 40: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[133]..function <SNR>63_setup_options: line 35: E697: Missing end of List ']':
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 136: E15: Invalid expression: "has('multi_byte') && has('unix') && &encoding
> ==# 'utf-8' &&" line 137: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[178]..function <SNR>63_setup_keymaps: line 1: E697: Missing end of List ']':
>
>
>
> This is for coc.vim : Plug 'neoclide/coc.nvim'
>
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\coc.nvi
> m\plugin\coc.vim[49]..function coc#rpc#start_server[17]..<SNR>48_start:
>
> line 10: E723: Missing end of Dictionary '}':
> line 11: E10: \ should be followed by /, ? or &
> line 12: E10: \ should be followed by /, ? or &
> line 13: E10: \ should be followed by /, ? or &
> line 14: E10: \ should be followed by /, ? or &
> line 15: E10: \ should be followed by /, ? or &
> line 16: E10: \ should be followed by /, ? or &
> line 17: E10: \ should be followed by /, ? or &
> line 18: E10: \ should be followed by /, ? or &
> line 19: E10: \ should be followed by /, ? or &
>
> Le jeudi 23 décembre 2021 à 13:23:06 UTC+1, antoine.m...@gmail.com a écrit :
>>
>> On Thu, Dec 23, 2021 at 10:55 AM Ni Va <niva...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.
>> >
>> > It is managed by Plug.vim plugins' manager in my vim9script _vimrc.
>> >
>> > It appears startuptime.vim warns on some script code such as :
>> >
>> > echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
>> > \ 'that prevents this version of Tagbar from working.'
>> > \ 'Please use the alternate version posted on the website.'
>> >
>> >
>> > identically warns on if brackets spread on multiple lines.
>> >
>> > How can I fix it or fix this call of legacy vimscript ?
>> >
>> > Thank you
>> > NiVa
>>
>> I can't find this echomsg statement in startuptime.vim as linked. I
>> suppose it comes from somewhere in Tagbar. Could you please tell us
>> what code (if statement etc.) triggers this message? (I suppose you
>> are using Vim 8.2 aren't you?)
>>
>> Best regards,
>> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

This is the code in Tagbar where the error message you previously
mentioned was produced:

if v:version == 700 && !has('patch167')
echohl WarningMsg
echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
\ 'that prevents this version of Tagbar from working.'
\ 'Please use the alternate version posted on the website.'
echohl None
finish
endif

It means you are using Vim 7.0 without patch 7.0.167. That version of
Vim is obsolete. Please upgrade to at least version 8.2 (the current
patchlevel as of this writing is 8.2.3877 AFAIK).

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/0e38bfd2-632a-4f90-ae91-a959a91cdc87n%40googlegroups.com.

Re: vim9 | how to force legacy vimscript execution

On Thu, Dec 23, 2021 at 1:33 PM Ni Va <nivaemail@gmail.com> wrote:
>
> Hi
> This issue is general.
>
> This is for TagBar plugin : Plug 'https://github.com/preservim/tagbar.git'
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 39: E10: \ should be followed by /, ? or &
> line 40: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[133]..function <SNR>63_setup_options: line 35: E697: Missing end of List ']':
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim: line 136: E15: Invalid expression: "has('multi_byte') && has('unix') && &encoding
> ==# 'utf-8' &&" line 137: E10: \ should be followed by /, ? or &
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
> plugin\tagbar.vim[178]..function <SNR>63_setup_keymaps: line 1: E697: Missing end of List ']':
>
>
>
> This is for coc.vim : Plug 'neoclide/coc.nvim'
>
> Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\coc.nvi
> m\plugin\coc.vim[49]..function coc#rpc#start_server[17]..<SNR>48_start:
>
> line 10: E723: Missing end of Dictionary '}':
> line 11: E10: \ should be followed by /, ? or &
> line 12: E10: \ should be followed by /, ? or &
> line 13: E10: \ should be followed by /, ? or &
> line 14: E10: \ should be followed by /, ? or &
> line 15: E10: \ should be followed by /, ? or &
> line 16: E10: \ should be followed by /, ? or &
> line 17: E10: \ should be followed by /, ? or &
> line 18: E10: \ should be followed by /, ? or &
> line 19: E10: \ should be followed by /, ? or &
>
> Le jeudi 23 décembre 2021 à 13:23:06 UTC+1, antoine.m...@gmail.com a écrit :
>>
>> On Thu, Dec 23, 2021 at 10:55 AM Ni Va <niva...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.
>> >
>> > It is managed by Plug.vim plugins' manager in my vim9script _vimrc.
>> >
>> > It appears startuptime.vim warns on some script code such as :
>> >
>> > echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
>> > \ 'that prevents this version of Tagbar from working.'
>> > \ 'Please use the alternate version posted on the website.'
>> >
>> >
>> > identically warns on if brackets spread on multiple lines.
>> >
>> > How can I fix it or fix this call of legacy vimscript ?
>> >
>> > Thank you
>> > NiVa
>>
>> I can't find this echomsg statement in startuptime.vim as linked. I
>> suppose it comes from somewhere in Tagbar. Could you please tell us
>> what code (if statement etc.) triggers this message? (I suppose you
>> are using Vim 8.2 aren't you?)
>>
>> Best regards,
>> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

This is the code in Tagbar where the error message you previously
mentioned was produced:

if v:version == 700 && !has('patch167')
echohl WarningMsg
echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
\ 'that prevents this version of Tagbar from working.'
\ 'Please use the alternate version posted on the website.'
echohl None
finish
endif

It means you are using Vim 7.0 without patch 7.0.167. That version of
Vim is obsolete. Please upgrade to at least version 8.2 (the current
patchlevel as of this writing is 8.2.3877 AFAIK).

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXtbGbx0dP3Q1Y3D-MhBoJCymi9hB6UKrugo89AByqUgGw%40mail.gmail.com.

Re: vim9 | how to force legacy vimscript execution

Hi 

This issue is general.

This is for TagBar plugin : Plug 'https://github.com/preservim/tagbar.git'

Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\

plugin\tagbar.vim:  line   39:  E10: \ should be followed by /, ? or &

line   40:  E10: \ should be followed by /, ? or &
Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
plugin\tagbar.vim[133]..function <SNR>63_setup_options: line   35: E697: Missing end of List ']': 

Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
plugin\tagbar.vim: line  136: E15: Invalid expression: "has('multi_byte') && has('unix') && &encoding
==# 'utf-8' &&" line  137: E10: \ should be followed by /, ? or &
Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\tagbar\
plugin\tagbar.vim[178]..function <SNR>63_setup_keymaps:  line    1:  E697: Missing end of List ']':

This is for coc.vim  :  Plug 'neoclide/coc.nvim'

Error detected while processing D:\Logiciels\Vim\vimfiles\plugged\coc.nvi
m\plugin\coc.vim[49]..function coc#rpc#start_server[17]..<SNR>48_start:

line   10: E723: Missing end of Dictionary '}':
line   11: E10: \ should be followed by /, ? or &
line   12: E10: \ should be followed by /, ? or &
line   13: E10: \ should be followed by /, ? or &
line   14: E10: \ should be followed by /, ? or &
line   15: E10: \ should be followed by /, ? or &
line   16: E10: \ should be followed by /, ? or &
line   17: E10: \ should be followed by /, ? or &
line   18: E10: \ should be followed by /, ? or &
line   19:  E10: \ should be followed by /, ? or &

Le jeudi 23 décembre 2021 à 13:23:06 UTC+1, antoine.m...@gmail.com a écrit :

On Thu, Dec 23, 2021 at 10:55 AM Ni Va <niva...@gmail.com> wrote:
>
> Hi,
>
> I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.
>
> It is managed by Plug.vim plugins' manager in my vim9script _vimrc.
>
> It appears startuptime.vim warns on some script code such as :
>
> echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
> \ 'that prevents this version of Tagbar from working.'
> \ 'Please use the alternate version posted on the website.'
>
>
> identically warns on if brackets spread on multiple lines.
>
> How can I fix it or fix this call of legacy vimscript ?
>
> Thank you
> NiVa

I can't find this echomsg statement in startuptime.vim as linked. I
suppose it comes from somewhere in Tagbar. Could you please tell us
what code (if statement etc.) triggers this message? (I suppose you
are using Vim 8.2 aren't you?)

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/3887a327-54ff-4f1e-af14-cb5935aecf4bn%40googlegroups.com.

Re: vim9 | how to force legacy vimscript execution

On Thu, Dec 23, 2021 at 10:55 AM Ni Va <nivaemail@gmail.com> wrote:
>
> Hi,
>
> I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.
>
> It is managed by Plug.vim plugins' manager in my vim9script _vimrc.
>
> It appears startuptime.vim warns on some script code such as :
>
> echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
> \ 'that prevents this version of Tagbar from working.'
> \ 'Please use the alternate version posted on the website.'
>
>
> identically warns on if brackets spread on multiple lines.
>
> How can I fix it or fix this call of legacy vimscript ?
>
> Thank you
> NiVa

I can't find this echomsg statement in startuptime.vim as linked. I
suppose it comes from somewhere in Tagbar. Could you please tell us
what code (if statement etc.) triggers this message? (I suppose you
are using Vim 8.2 aren't you?)

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXu96_-3xOVWBWRZPzut27e8WyuoPCnyKTUhrJs%2B25MdOw%40mail.gmail.com.

vim9 | how to force legacy vimscript execution

Hi,

I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim.

It is managed by Plug.vim plugins' manager in my vim9script _vimrc.

It appears startuptime.vim warns on some script code such as :

    echomsg 'Tagbar: Vim versions lower than 7.0.167 have a bug'
          \ 'that prevents this version of Tagbar from working.'
          \ 'Please use the alternate version posted on the website.'

identically warns on if brackets spread on multiple lines.

How can I fix it or fix this call of legacy vimscript ?

Thank you

NiVa

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/3de45482-4169-45d9-a133-d347407107ffn%40googlegroups.com.

Re: vim9 Benchmark

Understood.

Thank you Bram.

Le mardi 21 décembre 2021 à 10:13:09 UTC+1, Bram Moolenaar a écrit :

> Do you know if the stats displayed in https://github.com/brammool/vim9 are
> updated ?

I have not touched them for a long time. I expect Vim9 might be a bit
slower now, with the extra checks for errors that were added.
I might spend some time on finding bottlenecks, but priority is still
with finishing the specification.

--
From "know your smileys":
;-0 Can't find shift key
,-9 Kann Umschalttaste nicht finden

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d51690fb-476d-4b81-98ae-97d4b23df6c1n%40googlegroups.com.

Re: vim9 Benchmark

> Do you know if the stats displayed in https://github.com/brammool/vim9 are
> updated ?

I have not touched them for a long time. I expect Vim9 might be a bit
slower now, with the extra checks for errors that were added.
I might spend some time on finding bottlenecks, but priority is still
with finishing the specification.

--
From "know your smileys":
;-0 Can't find shift key
,-9 Kann Umschalttaste nicht finden

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20211221091259.E39BB1C0F5C%40moolenaar.net.

vim9 Benchmark

Hi All,

Do you know if the stats displayed in https://github.com/brammool/vim9 are updated ?

Thank you

NiVa

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/5fe4cdfb-be68-413f-9dde-89f658215794n%40googlegroups.com.

Chain two job_start()?

Hi!

Is it possible to pass the results from one job to another?

Like, if i have to 'ls -la ~ | grep vim', and don't want to invoke shell with 'sh -c "exec ls -la ~ | grep vim"' -- then, I'd define jobs like this:

let com1 = ["ls", "-la", expand("~/")]
let com2 = ["grep", "vimrc"]

Can start the first one like this:

let job = job_start(com1, {"out_cb": "Handler", "err_cb" : "ErrHandler"})

And what's next? How do I connect the second job and how do I define Handler() in this case? :)

Thanks

--

RRR

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d2160d9a-0f30-42ff-b18e-b6197090a4a1n%40googlegroups.com.

Learn more about our updated Terms of Service

rebbe.malachi.mailfeed@blogger.com On January 5, 2022, we're making some changes to our Terms of Service. These changes won't affect the way you use Google services, but they'll make it easier for you to understand what to expect from Google — and what we expect from you — as you use our services. You can review the new terms here. At a glance, here's what this update means for you: More clarity on what you can expect from Google and what we expect from you: We're providing more examples to describe the mutually respectful conduct that we expect from all our users. Revised warranty disclaimers and limitations of liability: We're including new warranty disclaimers and limitations of liability to reflect industry standards. Increased clarity and certainty in case of problems or disagreements: We changed some of the language in the Taking action in case of problems and Settling disputes, governing law, and courts sections to make it clearer what would happen in those situations. Improved readability: While our terms remain a legal document, we've done our best to make them easier to understand, including reorganizing some topics so that they're easier to find. If you use Family Link to manage a Google Account for someone else, please take some time to talk to them about these changes. Thank you for using Google! Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA, 94043 You have received this email to update you about important changes to Google's Terms of Service.

Re: how to disable autocmd and augroup from plugin / autoload

I have coded this instead to remove all autocommands of the group

    echomsg "EnhancedDiffLayout_autocmd disabled"

    augroup difflayout

      autocmd!

    augroup END

Le lundi 6 décembre 2021 à 13:36:41 UTC+1, Ni Va a écrit :

Hi,

I the plugin directory vim9script of a plugin of mine, i would like to toggle autocmd.

In plugin part, I got this augroup

foobar/plugin/foobar.vim

....

augroup difflayout

  au!

  autocmd CursorHold *.tmp call EnhancedDiffLayout()

augroup END

....

meanwhile in the following autoload part I got this to toggle autocmd.

foobar/autoload/foobar.vim

export def EnhancedDiffLayout_Toggle() #{{{

  g:EnhancedDiffLayout_Options.autocmd_enabled = !g:EnhancedDiffLayout_Options.autocmd_enabled

  if !g:EnhancedDiffLayout_Options.autocmd_enabled

    echomsg "EnhancedDiffLayout_autocmd disabled"

    autocmd! CursorHold *.tmp call EnhancedDiffLayout()

    augroup! difflayout

  else

    echomsg "EnhancedDiffLayout_autocmd enabled"

    augroup difflayout

      au!

      autocmd CursorHold *.tmp call EnhancedDiffLayout()

    augroup END

  endif

enddef #}}}

It seems at runtime that augroup cannot be deleted because autocmd! does not delete the autocmd. 

How can I fix it ?

Thank you

NiVa

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/685086c3-e097-4d76-a673-ba2ecf9b24d7n%40googlegroups.com.

how to disable autocmd and augroup from plugin / autoload

Hi,

I the plugin directory vim9script of a plugin of mine, i would like to toggle autocmd.

In plugin part, I got this augroup

foobar/plugin/foobar.vim

....

augroup difflayout

  au!

  autocmd CursorHold *.tmp call EnhancedDiffLayout()

augroup END

....

meanwhile in the following autoload part I got this to toggle autocmd.

foobar/autoload/foobar.vim

export def EnhancedDiffLayout_Toggle() #{{{

  g:EnhancedDiffLayout_Options.autocmd_enabled = !g:EnhancedDiffLayout_Options.autocmd_enabled

  if !g:EnhancedDiffLayout_Options.autocmd_enabled

    echomsg "EnhancedDiffLayout_autocmd disabled"

    autocmd! CursorHold *.tmp call EnhancedDiffLayout()

    augroup! difflayout

  else

    echomsg "EnhancedDiffLayout_autocmd enabled"

    augroup difflayout

      au!

      autocmd CursorHold *.tmp call EnhancedDiffLayout()

    augroup END

  endif

enddef #}}}

It seems at runtime that augroup cannot be deleted because autocmd! does not delete the autocmd. 

How can I fix it ?

Thank you

NiVa

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1f80c947-970b-4cec-850e-c6c881d40107n%40googlegroups.com.