Re: Statement reparsing

2018-02-21 Fir de Conversatie Nikolay Aleksandrovich Pavlov 
2018-02-22 0:07 GMT+03:00 Jason Felice :
> I've been thinking about the recent thread about vimscript and performance
> (after optimizing the heck out of a plugin that does a lot of text
> processing), and I'm curious about vim's reparsing of statements in
> functions and while loops and such for each execution.
>
> Is there something about the syntax that prevents caching parses?  Or
> another mechanism?  Or is it just that nobody's stepped up to do this?  Or
> something else, maybe it's not a good idea?

What do you mean by “caching parses”? There is no virtual machine
executing bytecode, no JIT and no AST - there is *nothing* to cache.
To be able to cache something you first need that something to cache,
and this is exactly the problem. As I said I am currently working on
adding all of that (minus JIT as it would be too complex for me) (to
Neovim), but this is done slowly and this is guaranteed to introduce
incompatibilities: e.g.

- Incompatibilities of the latest expressions parser:
https://github.com/ZyX-I/neovim/blob/389e4fc40f8cee4fa7be7f427fea277674bb2d79/src/nvim/viml/parser/expressions.c#L6-L51.
- Extreme example of function definitions that is completely
impossible to parse with a proper parser:
https://github.com/neovim/neovim/issues/425. Note that the same
technique may be used for :if blocks, unlike function definitions I
could theoretically keep `:execute 'if'` support if I was to drop the
idea of parsing `if|cmd|endif` as `if(cmd)` rather then
`if;cmd;endif`, but I do not like the idea.
- Collection of incompatibilities of a first attempt to create a
parser (code from there may be reused, but resulting AST structures
appeared to be too complex and the whole parser was both recursive and
rather limited (e.g. would not be able to provide highlighting)):
https://github.com/neovim/neovim/issues/387.

>
> Thanks,
> -Jason
>
> --
> --
> You received this message from the "vim_dev" 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_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
-- 
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Moving away from SourceForge

2018-02-21 Fir de Conversatie François Ingelrest 
On 22 February 2018 at 03:55, Christian J. Robinson wrote:
> _Please_ make it possible to use http://vim.org, even if it just
> automatically redirects to http://www.vim.org.  Your own reply here shows
> why it's needed.

It's been asked again and again for years, e.g.,
https://groups.google.com/d/topic/vim_dev/tyTTlowNg5s/discussion

For some reason, the person in charge of the DNS (I don't think it's
Bram) is kind of old-school and dogmatic, and has decided that vim.org
is the domain name and not the address of the website. While true,
this was and is still a ridiculous justification of a stubborn
behavior.

Oh well...

-- 
-- 
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Statement reparsing

2018-02-21 Fir de Conversatie Jason Felice 
I've been thinking about the recent thread about vimscript and performance
(after optimizing the heck out of a plugin that does a lot of text
processing), and I'm curious about vim's reparsing of statements in
functions and while loops and such for each execution.

Is there something about the syntax that prevents caching parses?  Or
another mechanism?  Or is it just that nobody's stepped up to do this?  Or
something else, maybe it's not a good idea?

Thanks,
-Jason

-- 
-- 
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Moving away from SourceForge

2018-02-21 Fir de Conversatie Logan Abbott 
On Wednesday, February 21, 2018 at 9:55:56 PM UTC-5, Heptite wrote:
> On Wed, 21 Feb 2018, Logan Abbott wrote:
> 
> > As of a couple hours ago, we've fixed the problems that were causing 
> > performance issues on vim.org.
> 
> _Please_ make it possible to use http://vim.org, even if it just 
> automatically redirects to http://www.vim.org.  Your own reply here 
> shows why it's needed.
> 
> - Christian
> 
> -- 
> Christian J. Robinson 
> "The trouble about trying to make yourself stupider than you really are is
> that you very often succeed."  -- C. S. Lewis

That looks like a DNS issue not on our end, but we're happy to work with Bram 
to make this work as well.

Thanks
Logan

-- 
-- 
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Moving away from SourceForge

2018-02-21 Fir de Conversatie Christian J. Robinson 

On Wed, 21 Feb 2018, Logan Abbott wrote:

As of a couple hours ago, we've fixed the problems that were causing 
performance issues on vim.org.


_Please_ make it possible to use http://vim.org, even if it just 
automatically redirects to http://www.vim.org.  Your own reply here 
shows why it's needed.


- Christian

--
Christian J. Robinson 
"The trouble about trying to make yourself stupider than you really are is
that you very often succeed."  -- C. S. Lewis

--
--
You received this message from the "vim_dev" 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_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Moving away from SourceForge

2018-02-21 Fir de Conversatie Logan Abbott 
On Tuesday, February 20, 2018 at 1:28:58 PM UTC-5, Bram Moolenaar wrote:
> Logan -
> 
> > Logan Abbott, president of SourceForge here. I am sincerely sorry
> > about hosting and other services being down this week. We ran into a
> > good deal of unforeseen issues with the new datacenter migration. Most
> > services are restored now, and we're working on getting web hosting up
> > too. I just had the team specifically focus on Vim, so vim.org is back
> > up as is vim.sourceforge.io and we're currently focusing on getting
> > vimdoc.sourceforge.net up as well.
> > 
> > With our new setup, we'll also be able to give you https://www.vim.org
> > very shortly on the new datacenter, if you should decide to stay with
> > us, which we really hope you do.
> > 
> > We've been improving SourceForge a lot since we took over, including
> > eliminating bundled adware, instituting malware scans for every
> > project, implementing https downloads and project web hosting, & more.
> > We just rolled out a big redesign too and enhanced download stats for
> > project admins. This planned maintenance did not go as well as we'd
> > hoped, but we're confident once our new datacenter is up and running
> > (very soon), our reliability will improve immensely compared to what
> > we were running on beforehand, which we inherited from previous
> > ownership.
> > 
> > We plan to continue to improve significantly, so we'd love you to stay
> > with us. Happy to speak with you directly as well.
> 
> Thank you for your response.  It's still completely open what we will
> decide to do.
> 
> A migration always has a few unforeseen complications.  Which is why it
> should always be done as a "dark launch", as far as possible.
> Unfortunately, the Vim site being down for several days is not a good
> display of being able to keep things running.
> 
> Now that the site is up again, I have noticed several problems.
> Sometimes images don't appear, sometimes a page does not respond,
> sometimes it's just slow.  Unfortunately, this again is not good for
> building trust.  For example, the page
> https://vim.sourceforge.io/scripts/add_script.php was not working, only
> after reloading several times it showed up correctly.
> 
> I hope your site engineers are able to see in the logs what the problems
> are and fix them soon.
> 
> - Bram

Hi Bram,

As of a couple hours ago, we've fixed the problems that were causing 
performance issues on vim.org.

We'd like to get vim.org on https as well. So please let me know if you'd like 
to move forward with that.

Thanks,
Logan

-- 
-- 
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[PATCH] Put dumps in SHADOWDIR/testdir

2018-02-21 Fir de Conversatie Elimar Riesebieter 
Building with $(SHADOWDIR) we need the dumps dir in testdir.

---
 src/Makefile | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/Makefile b/src/Makefile
index f814c83b2..1f609da0f 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -2882,7 +2882,8 @@ shadow:   runtime pixmaps
 ../../testdir/sautest \
 ../../testdir/samples \
 ../../testdir/test83-tags? \
-../../testdir/*.ok .
+../../testdir/*.ok \
+../../testdir/dumps .
 
 # Link needed for doing "make install" in a shadow directory.
 runtime:
-- 
2.16.1


-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--

-- 
-- 
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.