Re: The package you uploaded (vim-noweb.tgz) is empty
> > > Just curious if this works with a zip extension or a simple .vmb for > > > vimball. > > > > Great question. I had not heard of vimball. I will try it and see if > > that gets around the error. > > See :h vimball > > > Is vimball the most portable format? Should the example be updated > > on vim.org? > > I think vimball format was invented to have a nice way to distribute > plguins in some kind of archive form (but only works well for text > files). Nowadays, it seems it is rarely used and github plugin links > have become the de-facto standard. Right, those who don't mind pulling plugins directly from github, using a plugin manager, won't use vimballs. Those who prefer the good old "download & install" will find vimball fits their usage better. It's mostly a choice the plugin writer makes and usually finds it less work to just keep doing the same. But some support both, it's a little work up front but little maintenance. > That document should shows an example. It may make sense to update this: > ping @bram This was written by Charles Campbell. Is the help for ":MkVimball" not sufficient? If someone wants to propose an improvement then ask Charles to review it. -- >From "know your smileys": % Bike accident. A bit far-fetched, I suppose; although... o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230531213005.351E31C1B27%40moolenaar.net.
Re: passing vim9 vars to python3
>- From vim9 help I see *Functions and variables are script-local by >default* > > So s: is no mandatory no?, because if I put s: I see E1268: > Cannot use s: in Vim9 script: s:yml_f = yml_fpath. You need to declare the variable at the script level first. You cannot create a script variable in a function. This is so that when accessing the variable from a compiled function it knows where it is, it does not need to be looked up by name (which is much faster). >- So I delete s: and obtain this > >3.12.0b1 (tags/v3.12.0b1:5612078, May 22 2023, 16:20:31) [MSC > v.1934 64 bit (AMD64)] > > > regarding this code : > vim9script > > def Py3_SimpleMinimalTest(yml_fpath: string): void > var yml_f: string = yml_fpath > exe 'py3 print(sys.version)' > exe 'py3 print(vim.current.buffer.vars)' > exe 'py3 print(vim.current.buffer.vars[''yml_f''])' >enddef This will certainly not work, since "vim.current.buffer.vars[]" refers to buffer-local variables. You could change the first line in this function: b:yml_f = yml_fpath But is this really buffer related? And it does require a runtime lookup by name. Using a script-local variable will work better. -- There's no place like $(HOME)! /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230531213005.3A2D11C1B32%40moolenaar.net.
Re: Multiple windows get corrupted
Ok. So as expected it happened again. And I followed the steps you (Bram) mentioned. I have following diffs between the bad (left side) and good (right side): columns=258 <-> columns=120 lines=72 <-> lines=60 modified <-> nomodified scroll=35 <-> scroll=29 window=71 <-> window=59 lines, columns, and window are set in my .gvimrc. I am experimenting with commenting them out to see if any effect. Any ideas from your side? Thanks. On Wednesday, May 31, 2023 at 10:11:40 AM UTC-4 Ben Mehmet wrote: > Thank you. I will follow the troubleshooting steps you highlighted. > > On Wednesday, May 31, 2023 at 7:48:24 AM UTC-4 Bram Moolenaar wrote: > >> >> > Everybody FYI... I thank all the replies I have gotten related to this >> > issue which I should mention I have not figured out what the cause is. >> I >> > followed the suggestion provided and was not able to find which, if >> any, >> > plugin caused it. However, by pure chance I recently discovered one >> thing. >> > So when that text garbling happened (and happened very often), I just >> used >> > exit my vim session and open all files in session until next time it >> > misbehaved again. Well the discovery that I made recently is that when >> that >> > happened to me, instead of exiting, I could either *pull *the right >> edge of >> > the window either in or out for a pixel or two OR *snap *the vim >> session >> > window to either left or right (on linux like using super key and >> > left/right arrow keys) of the screen and it refreshed my >> windows/buffers >> > and things would look normal until next time it misbehaved. >> > Does this discovery point in any direction as to what my issue is and >> how >> > to remedy it permanently? >> >> Perhaps a window resize event makes Vim recompute some things and then >> it works again? Just guessing. >> >> If some option gets a wrong value, such as 'lines' or 'columns', that >> would cause display errors. You could do the following: >> >> redir > /tmp/settings_1 >> set! all >> redir END >> >> Do this when everything works OK and later when things are wrong, using >> a different file name. Then compare the output and try to spot the >> difference. If you see an option with a suspect value, you can possibly >> find out where it was set with e.g.: >> >> :verbose set lines? >> >> -- >> From "know your smileys": >> 8<}} Glasses, big nose, beard >> >> /// 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/92d48f21-370c-4e61-a589-d01540070420n%40googlegroups.com.
Re: passing vim9 vars to python3
- From vim9 help I see *Functions and variables are script-local by
default*
So s: is no mandatory no?, because if I put s: I see E1268:
Cannot use s: in Vim9 script: s:yml_f = yml_fpath.
- So I delete s: and obtain this
3.12.0b1 (tags/v3.12.0b1:5612078, May 22 2023, 16:20:31) [MSC
v.1934 64 bit (AMD64)]
regarding this code :
vim9script
def Py3_SimpleMinimalTest(yml_fpath: string): void
var yml_f: string = yml_fpath
exe 'py3 print(sys.version)'
exe 'py3 print(vim.current.buffer.vars)'
exe 'py3 print(vim.current.buffer.vars[''yml_f''])'
enddef
Py3_SimpleMinimalTest('foobar.yml')
Then I got
3.12.0b1 (tags/v3.12.0b1:5612078, May 22 2023, 16:20:31) [MSC
v.1934 64 bit (AMD64)]
Traceback (most recent call last):
File "", line 1, in
KeyError: 'yml_f'
Le mercredi 31 mai 2023 à 16:13:20 UTC+2, Bram Moolenaar a écrit :
>
> > Thank you I knew, this is working
> >
> > vim9script
> >
> > def g:Py3_SimpleMinimalTest(yml_fpath: string): void
> > w:yml_f = yml_fpath
> > exe 'py3 print(sys.version)'
> > exe 'py3 print(vim.current.window.vars[''yml_f''])'
> > enddef
> >
> > and what about making this works
> >
> > def g:Py3_SimpleMinimalTest(yml_fpath: string): void
> > *var yml_f:string =* yml_fpath
> > exe 'py3 print(sys.version)'
> > exe 'py3 print(vim.current.**.vars[''yml_f''])'
> > enddef
>
> Do you mean you want to access variables local to a compiled function by
> name? That is not possible. The "l:" namespace that exists in legacy
> functions was intentionally left out in compiled functions, because it
> adds quite a bit of overhead. You can use a script-local variable to
> make this work. It does mean you go outside of the function scope, but
> it's still inside the scope of the script file. That means it won't
> interfere with what happens in other scripts.
>
> --
> From "know your smileys":
> <>:-) Bishop
>
> /// 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/77f05256-1798-48fd-a794-265031be87e2n%40googlegroups.com.
Re: The package you uploaded (vim-noweb.tgz) is empty
On Di, 30 Mai 2023, Edward McGuire wrote: > On Tuesday, May 30, 2023 at 12:38:34 PM UTC Christian Brabandt wrote: > > What is the script id? I might be able to check it on the server (no > > promises > however). > > Originally "vim-noweb", and also when I ran into the problem I tried making > the > ID the same as the filename "vim-noweb.tar.gz" and "vim-noweb.tgz". No, I was referring to the vim.org URL, which should contain a script id. > > > Also is there a reason, you are using the tgz/tar.gz extension? > > I was following "https://www.vim.org/scripts/add_script.php;. There I see the > example, "if I was writing a script foo.vim that also had vim help file and a > README file I would name the script foo.vim but my script package would be > foo.tar.gz". So of course that is the example I followed. I would just call it "foo" or in your case "vim-noweb" > > Just curious if this works with a zip extension or a simple .vmb for > > vimball. > > Great question. I had not heard of vimball. I will try it and see if that gets > around the error. See :h vimball > Is vimball the most portable format? Should the example be updated on vim.org? I think vimball format was invented to have a nice way to distribute plguins in some kind of archive form (but only works well for text files). Nowadays, it seems it is rarely used and github plugin links have become the de-facto standard. That document should shows an example. It may make sense to update this: ping @bram Best, Christian -- In der Realität ist die Wirklichkeit ganz anders. -- -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ZHdZA15n4Qv2c7OU%40256bit.org.
Re: passing vim9 vars to python3
> Thank you I knew, this is working > > vim9script > > def g:Py3_SimpleMinimalTest(yml_fpath: string): void > w:yml_f = yml_fpath > exe 'py3 print(sys.version)' > exe 'py3 print(vim.current.window.vars[''yml_f''])' > enddef > > and what about making this works > > def g:Py3_SimpleMinimalTest(yml_fpath: string): void > *var yml_f:string =* yml_fpath > exe 'py3 print(sys.version)' > exe 'py3 print(vim.current.**.vars[''yml_f''])' > enddef Do you mean you want to access variables local to a compiled function by name? That is not possible. The "l:" namespace that exists in legacy functions was intentionally left out in compiled functions, because it adds quite a bit of overhead. You can use a script-local variable to make this work. It does mean you go outside of the function scope, but it's still inside the scope of the script file. That means it won't interfere with what happens in other scripts. -- >From "know your smileys": <>:-) Bishop /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230531141312.17DE91C0916%40moolenaar.net.
Re: Multiple windows get corrupted
Thank you. I will follow the troubleshooting steps you highlighted. On Wednesday, May 31, 2023 at 7:48:24 AM UTC-4 Bram Moolenaar wrote: > > > Everybody FYI... I thank all the replies I have gotten related to this > > issue which I should mention I have not figured out what the cause is. I > > followed the suggestion provided and was not able to find which, if any, > > plugin caused it. However, by pure chance I recently discovered one > thing. > > So when that text garbling happened (and happened very often), I just > used > > exit my vim session and open all files in session until next time it > > misbehaved again. Well the discovery that I made recently is that when > that > > happened to me, instead of exiting, I could either *pull *the right edge > of > > the window either in or out for a pixel or two OR *snap *the vim session > > window to either left or right (on linux like using super key and > > left/right arrow keys) of the screen and it refreshed my windows/buffers > > and things would look normal until next time it misbehaved. > > Does this discovery point in any direction as to what my issue is and > how > > to remedy it permanently? > > Perhaps a window resize event makes Vim recompute some things and then > it works again? Just guessing. > > If some option gets a wrong value, such as 'lines' or 'columns', that > would cause display errors. You could do the following: > > redir > /tmp/settings_1 > set! all > redir END > > Do this when everything works OK and later when things are wrong, using > a different file name. Then compare the output and try to spot the > difference. If you see an option with a suspect value, you can possibly > find out where it was set with e.g.: > > :verbose set lines? > > -- > From "know your smileys": > 8<}} Glasses, big nose, beard > > /// 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b99aad18-784a-4267-b505-e65f3a415d57n%40googlegroups.com.
Re: passing vim9 vars to python3
Hi Bram, Thank you I knew, this is working vim9script def g:Py3_SimpleMinimalTest(yml_fpath: string): void w:yml_f = yml_fpath exe 'py3 print(sys.version)' exe 'py3 print(vim.current.window.vars[''yml_f''])' enddef and what about making this works def g:Py3_SimpleMinimalTest(yml_fpath: string): void *var yml_f:string =* yml_fpath exe 'py3 print(sys.version)' exe 'py3 print(vim.current.**.vars[''yml_f''])' enddef Thank you Le mercredi 31 mai 2023 à 13:48:23 UTC+2, Bram Moolenaar a écrit : > > > Seeing the legacy vimscript func* Test_python3_vars()* in > > *src\testdir\test_python3.vim*, > > > > Can you confirm that in vim9script, those setlines test are no possible > to > > be written in same way to be passed to python3 world ? > > > > func Test_python3_vars() > > let g:foo = 'bac' -- << -- THE ONLY ONE CAN BE USED in vim9 ? > > let w:abc3 = 'def' -- << -- NOT POSSIBLE in vim9 > > let b:baz = 'bar' -- << -- NOT POSSIBLE in vim9 > > let t:bar = 'jkl' -- << -- NOT POSSIBLE in vim9 > > I guess you mean that in Vim9 script and in a :def function the "let" > command doesn't work. You can just leave it out, e.g.: > > w:abc3 = 'def' > > > Beyond a simple variable, is it possible to move a VIM9 class to the > > python3 world? > > You mean to pass a reference of the class and use it in Python? No, > that is not possible. The class implementation is only halfway, but > even when the work has been done a Python script will not be able to > access a Vim class directly. You can only use it in a Vim script > context, such as using "vim.eval()". > > -- > Do not trust atoms, they make up everything. > > /// 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d1af74ca-a97b-4e41-8069-e37d10ff68ddn%40googlegroups.com.
Re: Multiple windows get corrupted
> Everybody FYI... I thank all the replies I have gotten related to this > issue which I should mention I have not figured out what the cause is. I > followed the suggestion provided and was not able to find which, if any, > plugin caused it. However, by pure chance I recently discovered one thing. > So when that text garbling happened (and happened very often), I just used > exit my vim session and open all files in session until next time it > misbehaved again. Well the discovery that I made recently is that when that > happened to me, instead of exiting, I could either *pull *the right edge of > the window either in or out for a pixel or two OR *snap *the vim session > window to either left or right (on linux like using super key and > left/right arrow keys) of the screen and it refreshed my windows/buffers > and things would look normal until next time it misbehaved. > Does this discovery point in any direction as to what my issue is and how > to remedy it permanently? Perhaps a window resize event makes Vim recompute some things and then it works again? Just guessing. If some option gets a wrong value, such as 'lines' or 'columns', that would cause display errors. You could do the following: redir > /tmp/settings_1 set! all redir END Do this when everything works OK and later when things are wrong, using a different file name. Then compare the output and try to spot the difference. If you see an option with a suspect value, you can possibly find out where it was set with e.g.: :verbose set lines? -- >From "know your smileys": 8<}} Glasses, big nose, beard /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230531114816.C4F711C1B27%40moolenaar.net.
Re: passing vim9 vars to python3
> Seeing the legacy vimscript func* Test_python3_vars()* in > *src\testdir\test_python3.vim*, > > Can you confirm that in vim9script, those setlines test are no possible to > be written in same way to be passed to python3 world ? > > func Test_python3_vars() > let g:foo = 'bac' -- << -- THE ONLY ONE CAN BE USED in vim9 ? > let w:abc3 = 'def'-- << -- NOT POSSIBLE in vim9 > let b:baz = 'bar' -- << -- NOT POSSIBLE in vim9 > let t:bar = 'jkl' -- << -- NOT POSSIBLE in vim9 I guess you mean that in Vim9 script and in a :def function the "let" command doesn't work. You can just leave it out, e.g.: w:abc3 = 'def' > Beyond a simple variable, is it possible to move a VIM9 class to the > python3 world? You mean to pass a reference of the class and use it in Python? No, that is not possible. The class implementation is only halfway, but even when the work has been done a Python script will not be able to access a Vim class directly. You can only use it in a Vim script context, such as using "vim.eval()". -- Do not trust atoms, they make up everything. /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230531114816.CA8211C1B32%40moolenaar.net.
passing vim9 vars to python3
Hi, Seeing the legacy vimscript func* Test_python3_vars()* in *src\testdir\test_python3.vim*, Can you confirm that in vim9script, those setlines test are no possible to be written in same way to be passed to python3 world ? func Test_python3_vars() let g:foo = 'bac' -- << -- THE ONLY ONE CAN BE USED in vim9 ? let w:abc3 = 'def'-- << -- NOT POSSIBLE in vim9 let b:baz = 'bar' -- << -- NOT POSSIBLE in vim9 let t:bar = 'jkl' -- << -- NOT POSSIBLE in vim9 Beyond a simple variable, is it possible to move a VIM9 class to the python3 world? Thank you N i c o l a s -- -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/9e8fa53c-df9b-4f71-b3ee-01c03aed5e42n%40googlegroups.com.
