Re: [vim/vim] [proposal] Introducing TextMate grammar system for syntax highlighting ? (Issue #9087)

[Blay263]

Any update on this?

On Saturday, April 15, 2023 at 12:00:54 PM UTC-4 Bram Moolenaar wrote:

>
> [...]
>
> > > > - Tree sitter's AST allows other functionality.
> > > > [nvim-treesitter-textobjects](
> https://github.com/nvim-treesitter/nvim-treesitter-textobjects)
> > > > allows for key combinations like `daf` (delete around function) and
> > > > motions like `ic` (inside class). I don't believe these are 
> impossible
> > > > with Textmate grammars, but I can't find any precedent of this 
> either.
> > > Isn't this a matter of naming rules properly? Just like we currently
> > > have the convention that "fooComment" is used for comments in the "foo"
> > > filetype.
> > 
> > I'm not sure. If you have one function nested inside another, can you
> > determine where the inner one beings and ends?
>
> This depends on how the result of parsing can be accessed. Currently we
> only have synstack(), which is insufficient. It requires returning more
> information about each syntax item. At least the start position.
> Getting the end position would be nice, but it can be expensive if the
> file was only partly parsed (to optimize performance). E.g. if the
> window shows the start of a long file, which contains a class that takes
> up the whole file, the text could be shown by only parsing a limited
> number of lines (window height), while parsing until the end of the
> class can be a hundred times slower. We probably need some option to
> tell Vim whether speed is more important than complete information, or
> the other way around. I believe treesitter implementations always
> parse the whole file anyway.
>
> > > Just looking at the c/highlights.scm file, it seems that it's not just
> > > translation, this also defines tokens such as "__attribute__". Does
> > > this mean there is duplication between files?
> > 
> > There's a few different ones. I'm not good at explaining what they 
> translate
> > because I'm missing terminology with some internals here. Here are all 
> the
> > queries for `C`:
> > 
> > 
> https://github.com/nvim-treesitter/nvim-treesitter/tree/f499a711fa5c573b5ba0af09a3c9955a6c14b062/queries/c
>
> That's what I was referring to, the "highlights.scm" file in that
> directory.
>
> > > > - Given that the above mentioned queries are only guaranteed to work
> > > > with the same version of the parser for which they were written, the
> > > > version of the query and the parsers needs to be kept in sync (neovim
> > > > addresses this by downloading a pinned version of the parser).
> > >And how does an end user find out what highlight group to use for an
> > >item? Searching the files, what you can do with the current Vim syntax
> > >plugins and a bit of guessing, seems too complicated.
> > 
> > `highlights.scm` translate tree sitter nodes into capture groups.
> > These capture groups map directly to well-known highlight groups.
>
> However, besides "tree sitter nodes" there are literal keywords here.
> It looks like the syntax file has been split in two parts that carefully
> need to be kept in sync. And errors will be quite hard to track down.
> Would there be an error if the highlights.scm file uses a name that is
> not a treesitter node?
>
> > I do think having support for multiple syntax sources is the best, 
> because a
> > slow one can enhance the results of a fast one. There's also semantic
> > highlighting on top of syntax highlighting. For example, an LSP can
> > point out unused or deprecated tokens which can be highlighted as
> > greyed-out and strikethrough respectively.
>
> I expect LSP to provide much more information, we don't intend to go
> that way with syntax highlighting. E.g., a variable name could be
> highlighted if recognized, but there is no reference to where it is
> declared. LSP does provide that information.
>
> > On a separate note, some of the examples in this thread has proved
> > that Vim's current APIs are sufficient to implement any kind of
> > highlighter as a plugin; I don't think there's anything that needs to
> > be done right now (aside from writing plugins and continuing refining
> > on them).
>
> The two main goals I see are:
>
> 1. Add grammers that are used by other editors, to avoid having to
> maintain a Vim-specific implementation. And the other way around:
> a grammer written for Vim can also be used by other editors.
>
> 2. Provide a complete parsed syntax tree. The current implementation
> has some caching, but synstack() returns very limited information and
> can be quite slow. We would want something that allows for movement
> commands, e.g. "jump to start of function".
>
> -- 
> BEDEVERE: Look! It's the old man from scene 24 - what's he Doing here?
> ARTHUR: He is the keeper of the Bridge. He asks each traveler five
> questions ...
> GALAHAD: Three questions.
> "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
>
> /// Bram Moolenaar -- ***@***.*** -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- 

Re: New features added since the Vim 8.2 release

[Blay263]

Just curious, does Vim 9 have a release date?

On Friday, June 24, 2022 at 12:41:44 PM UTC-4 yegapp...@gmail.com wrote:

> Hi all,
>
> The version9.txt file has been updated to include all the notable
> new features introduced since the Vim 8.2 release:
>
> https://vimhelp.org/version9.txt.html
>
> If any feature that you have contributed is not mentioned, then
> send a patch to Bram.
>
> Regards,
> Yegappan
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/2eaa6b44-5bf8-4ecf-b73a-9b05f532e0den%40googlegroups.com.

Re: Popup teminal background color

[Blay263]

[image: 2021-12-20_17-10-29.png]

On Monday, December 20, 2021 at 5:11:05 PM UTC-5 Blay263 wrote:

> My popup terminal now defaults to a black color, did the option to change 
> to match my colorscheme change?
>
>   *call setwinvar(winid, '', 'Special') *
>
> *FUNCTION:*
> function! Flt_term_win(cmd, width, height, border_highlight) abort
> let width = float2nr( * a:width)
> let height = float2nr( * a:height)
> let bufnr = term_start(a:cmd, {'hidden': 1, 'term_finish': 'close', 
> 'cwd': getcwd()})
>
> let winid = popup_create(bufnr, {
> \ 'minwidth': width,
> \ 'maxwidth': width,
> \ 'minheight': height,
> \ 'maxheight': height,
> \ 'border': [],
> \ 'borderchars': ['─', '│', '─', '│', '┌', '┐', '┘', '└'],
> \ 'borderhighlight': [a:border_highlight],
> \ 'padding': [0,1,0,1],
> \ 'highlight': a:border_highlight
> \ })
>
> " Optionally set the 'Normal' color for the terminal buffer
>  call setwinvar(winid, '', 'Special')
>
> return winid
> endfunction
>
> *RESULT:*
> :call Flt_term_win('wsl',0.9,0.6,'Todo')
>
> [image: 2021-12-20_17-06-47.png]
>
> *VIM:*
> [image: 2021-12-20_17-10-29.png]
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f4814fc0-07ca-4718-b755-3c0662911943n%40googlegroups.com.

Popup teminal background color

[Blay263]

My popup terminal now defaults to a black color, did the option to change 
to match my colorscheme change?

  *call setwinvar(winid, '', 'Special') *

*FUNCTION:*
function! Flt_term_win(cmd, width, height, border_highlight) abort
let width = float2nr( * a:width)
let height = float2nr( * a:height)
let bufnr = term_start(a:cmd, {'hidden': 1, 'term_finish': 'close', 
'cwd': getcwd()})

let winid = popup_create(bufnr, {
\ 'minwidth': width,
\ 'maxwidth': width,
\ 'minheight': height,
\ 'maxheight': height,
\ 'border': [],
\ 'borderchars': ['─', '│', '─', '│', '┌', '┐', '┘', '└'],
\ 'borderhighlight': [a:border_highlight],
\ 'padding': [0,1,0,1],
\ 'highlight': a:border_highlight
\ })

" Optionally set the 'Normal' color for the terminal buffer
 call setwinvar(winid, '', 'Special')

return winid
endfunction

*RESULT:*
:call Flt_term_win('wsl',0.9,0.6,'Todo')

[image: 2021-12-20_17-06-47.png]

*VIM:*
[image: 2021-12-20_17-10-29.png]

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6a759ebf-845d-4290-be22-b51ab4fe55b8n%40googlegroups.com.

Re: [vim/vim] Make popup behave like a normal window (#5639)

[Blay263]

I think the use cases have been detailed above and are limited. Neovim 
provides a proof of concept. Not having the popup focusable is blocking 
specific functionality that is already available in Neovim.

On Monday, October 5, 2020 at 10:28:08 AM UTC-4 Bram Moolenaar wrote:

>
> > +1 I would also like the popup to be focusable so that it can be used 
> like 
> > a normal window/buffer. Neovim doesn't have this issue.
> > 
> > Here is another use case for me. This is vim-lsp 
> >  using hover to show 
> > information about the word under the cursor. Most rust projects have big 
> > docs including great examples and I would like to move around and copy 
> text 
> > from popup, search inside the popup and use all my vim knowledge there. 
> > 
> > Right now the solution for me is to open the website or use neovim.
>
> I have been thinking of this, but it raises many questions:
>
> - How to focus a popup? I imagine in most cases you want to switch
> between the current window and the popup, back and forth. This
> matters especially if you already have a dozen split windows, you
> don't want to cycle through all of them to reach the popup, and you
> don't want to cycle through all windows to end up in the one you were
> coming from.
>
> - If there is more than one focusable popup, how to reach each of them?
> Perhaps some are connected to a specific window (e.g. for completion
> or anchored to text), or some are unrelated to a specific window (e.g.
> help).
>
> - What if the focused popup window closes? What if it closes while you
> are typing (since they might be under control of some async plugin)?
>
> - How to avoid this turns into an avalanche of more feature requests?
> Aka creeping featurism.
>
> -- 
> He who laughs last, thinks slowest.
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/865bff3b-7dd9-42b3-8198-cb21e382bf20n%40googlegroups.com.

Re: Feature request: Support popup menu for wildmenu

[Blay263]

 Bump

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/9dced2c7-08f1-4fba-81e7-f05e8e0ea7ba%40googlegroups.com.

Re: Feature request: Support popup menu for wildmenu

[Blay263]

So the options:


*set wildmenuset wildoptions=pum*


Would show:

Which I feel is natural and consistent with how completion generally works 
in Vim as opposed to:




Maybe* set wildmenupum *can be used for backward compatability

https://imgur.com/a/hfb4xe8

On Sunday, December 15, 2019 at 8:56:14 AM UTC-5, Bram Moolenaar wrote:

>
> > Is this still in the works? 
>
> It will be quite a bit of work, and probably cause some regressions. 
> Is it worth it?  What will be the advantage? 
>
>
> -- 
> ARTHUR: (as the MAN next to him is squashed by a sheep) Knights!  Run 
> away! 
>Midst echoing shouts of "run away" the KNIGHTS retreat to cover with 
> the odd 
>cow or goose hitting them still.  The KNIGHTS crouch down under cover. 
>  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES 
> LTD 
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   
> \\\ 
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ 
> \\\ 
> \\\  an exciting new programming language -- http://www.Zimbu.org   
>  /// 
>  \\\help me help AIDS victims -- http://ICCF-Holland.org   
>  /// 
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f67d6535-7e8f-421e-8266-5a737b5835ec%40googlegroups.com.

Re: Feature request: Support popup menu for wildmenu

[Blay263]

On Sunday, December 15, 2019 at 10:41:59 AM UTC-5, Blay263 wrote:
>
> So the options below:
>
>
> *set wildmenuset wildoptions=pum*
>
>
>
> Will show:
>
> Which I feel will be more natural and consistent with how completion 
> generally works than:
>
> I am not sure how backward compatibility will work maybe: 
>
>
> *set wildmenupum*
>
>
> On Sunday, December 15, 2019 at 8:56:14 AM UTC-5, Bram Moolenaar wrote:
>>
>>
>> > Is this still in the works? 
>>
>> It will be quite a bit of work, and probably cause some regressions. 
>> Is it worth it?  What will be the advantage? 
>>
>>
>> -- 
>> ARTHUR: (as the MAN next to him is squashed by a sheep) Knights!  Run 
>> away! 
>>Midst echoing shouts of "run away" the KNIGHTS retreat to cover with 
>> the odd 
>>cow or goose hitting them still.  The KNIGHTS crouch down under cover. 
>>  "Monty Python and the Holy Grail" PYTHON (MONTY) 
>> PICTURES LTD 
>>
>>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   
>> \\\ 
>> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ 
>> \\\ 
>> \\\  an exciting new programming language -- http://www.Zimbu.org   
>>  /// 
>>  \\\help me help AIDS victims -- http://ICCF-Holland.org   
>>  /// 
>>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/efb060b9-64de-434a-a44f-977998cfa679%40googlegroups.com.

Re: Feature request: Support popup menu for wildmenu

[Blay263]

So the options below:


*set wildmenuset wildoptions=pum*



Will show:

Which I feel will be more natural and consistent with how completion 
generally works than:

I am not sure how backward compatibility will work maybe: 


*set wildmenupum*


On Sunday, December 15, 2019 at 8:56:14 AM UTC-5, Bram Moolenaar wrote:
>
>
> > Is this still in the works? 
>
> It will be quite a bit of work, and probably cause some regressions. 
> Is it worth it?  What will be the advantage? 
>
>
> -- 
> ARTHUR: (as the MAN next to him is squashed by a sheep) Knights!  Run 
> away! 
>Midst echoing shouts of "run away" the KNIGHTS retreat to cover with 
> the odd 
>cow or goose hitting them still.  The KNIGHTS crouch down under cover. 
>  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES 
> LTD 
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   
> \\\ 
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ 
> \\\ 
> \\\  an exciting new programming language -- http://www.Zimbu.org   
>  /// 
>  \\\help me help AIDS victims -- http://ICCF-Holland.org   
>  /// 
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6a6b6558-4fa3-4e15-819e-bc86a060b2fd%40googlegroups.com.

Re: Feature request: Support popup menu for wildmenu

[Blay263]

Is this still in the works?

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/3c090f58-3286-4645-8f76-283259c0e095%40googlegroups.com.

Re: [vim/vim] netrw's "gx" functionality doesn't open URLs anymore in macOS (#4738)

[Blay263]

This doesn't work anymore on windows, was gx fix reverted??

On Saturday, October 19, 2019 at 6:17:20 AM UTC-4, SRGOM wrote:
>
> So can I version check-in defaults.list and then link 
> ~/.local/share/applications/defaults.list to that? I remember that there 
> was at least one file out of the 799 that xdg-defaults reads which was 
> deleted and rewritten. I hope defaults.list isn't that? I can mark the 
> other 798 read only if only it helps me get consistent behaviour . Or just 
> edit whichever is the highest priority
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub 
> ,
>  
> or unsubscribe 
> 
> .
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6cccb472-da78-4b6c-b0c9-a493b8ea0775%40googlegroups.com.

Re: Popup windows mostly done

[Blay263]

You read my mind lol

On Thursday, September 5, 2019 at 11:01:23 AM UTC-4, Christian Brabandt 
wrote:
>
>
> On Sa, 31 Aug 2019, Bram Moolenaar wrote: 
>
> > Please read the help at ":help popup" and check it out. 
>
> I haven't had a look at it yet. However I would be interested to know of 
> any plugins making use of it already. So please showcase some scripts ;) 
>
> Best, 
> Christian 
> -- 
> Alles fließt und nichts bleibt. 
> -- Heraklit von Ephesus (540-480 v. Chr.) 
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/607beee7-e8ad-43df-a20f-5bf976fb31db%40googlegroups.com.

Re: Popup windows mostly done

[Blay263]

Are you still planning a showcase 
https://groups.google.com/forum/#!msg/vim_dev/o1rzzF5nCRw/LUBiSQ7_BQAJ

On Thursday, September 5, 2019 at 5:47:58 AM UTC-4, Paul Jolly wrote:
>
> > The popup window feature has been implemented.  Only a few minor things 
> > remain. 
>
> Thanks again for all the work on this, Bram. 
>
> We're just about to fully switch to popups i.e. upgrade min version of 
> Vim required for govim with no fallback option to use balloons/other. 
> No problems seen so far, works really well. 
>
> And we're just about to use the completeopt+=popup support with the 
> completepopup=align:menu option to bolster the completion side of 
> things. 
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ae840185-2de5-4f5d-b434-50dded86d405%40googlegroups.com.

Re: Popup windows mostly done

[Blay263]

Are you still planning a showcase. 
https://groups.google.com/forum/m/#!searchin/vim_dev/Popup/vim_dev/o1rzzF5nCRw

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/b6a3b170-cba4-4617-bb3b-5374f0ca97c6%40googlegroups.com.

Re: [vim/vim] All text is highlighted when starting a substitute with very magic when hlsearch and incsearch are active (#3363)

[Blay263]

On Saturday, May 25, 2019 at 2:17:59 AM UTC-4, Christian Brabandt wrote:
> Yes, it works just like a normal search. 
> 
> 
> BTW please ask user questions at the vim_use ml or use vi.stackexchange.com. 
> 
> 
> 
> 
> 
> > Am 25.05.2019 um 02:09 schrieb blayz3r :
> 
> 
> > 
> 
> 
> > All text is highlighted with :call matchadd("IncSearch", '\v'), is this 
> > intentional?
> 
> 
> > 
> 
> 
> > —
> 
> 
> > You are receiving this because you modified the open/close state.
> 
> 
> > Reply to this email directly, view it on GitHub, or mute the thread.
> 
> 
> 
> 
> 
> 
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.

Sure will do. My point was that shouldn't :call matchadd("IncSearch", '\v') 
highlight nothing as 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/617cc16b-a8f1-4d7b-b6dc-1da13a823fea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: E484 after GVIM update

[Blay263]

On Tuesday, April 30, 2019 at 11:36:39 AM UTC-4, Blay263 wrote:
> On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote:
> > Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit :
> > > Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit :
> > > > On Mo, 29 Apr 2019, Blay263 wrote:
> > > > 
> > > > > After updating my vim version I am getting the error below: 
> > > > > 
> > > > > E484: Can't open file C:\Users\\AppData\Local\Temp\VIoCC2F.tmp
> > > > > 
> > > > > I am using GVIM on windows with the WSL subsytem. It looks like the 
> > > > > way the escape sequences work has changed.
> > > > 
> > > > So what is in that particular line of your .vimrc? Might already be 
> > > > fixed by 8.1.1239
> > > > 
> > > > 
> > > > Best,
> > > > Christian
> > > > -- 
> > > > Bauer Pichler fährt zur Kur. Schon bald bekommt er Post von seiner 
> > > > Frau:  
> > > > "Heute ist unser Ochse eingegangen. Nun weiß ich nicht so recht, soll 
> > > > ich  
> > > > einen neuen kaufen oder auf Dich warten?"
> > > 
> > > Same problem at startup
> > > 
> > > E484: Can't open file C:\Users\NICOLA~1.VAL\AppData\Local\Temp\VIo9A
> > > 54.tmp
> > > 
> > > line  184 of _vimrc:
> > >   let g:Explorer_RubyLibPath=substitute(fnamemodify(system('which 
> > > '.g:Explorer_RubyLibName),":p"),':..',':',"")
> > 
> > Same problem with Vim.8.1.1239 patch
> 
> Line 645:
> let g:startify_custom_header =
> \ map(split(system('fortune -s'), '\n'), '" ". v:val') + ['']

This version works fine:


-- 
-- 
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: E484 after GVIM update

[Blay263]

On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote:
> Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit :
> > Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit :
> > > On Mo, 29 Apr 2019, Blay263 wrote:
> > > 
> > > > After updating my vim version I am getting the error below: 
> > > > 
> > > > E484: Can't open file C:\Users\\AppData\Local\Temp\VIoCC2F.tmp
> > > > 
> > > > I am using GVIM on windows with the WSL subsytem. It looks like the way 
> > > > the escape sequences work has changed.
> > > 
> > > So what is in that particular line of your .vimrc? Might already be 
> > > fixed by 8.1.1239
> > > 
> > > 
> > > Best,
> > > Christian
> > > -- 
> > > Bauer Pichler fährt zur Kur. Schon bald bekommt er Post von seiner Frau:  
> > > "Heute ist unser Ochse eingegangen. Nun weiß ich nicht so recht, soll ich 
> > >  
> > > einen neuen kaufen oder auf Dich warten?"
> > 
> > Same problem at startup
> > 
> > E484: Can't open file C:\Users\NICOLA~1.VAL\AppData\Local\Temp\VIo9A
> > 54.tmp
> > 
> > line  184 of _vimrc:
> >   let g:Explorer_RubyLibPath=substitute(fnamemodify(system('which 
> > '.g:Explorer_RubyLibName),":p"),':..',':',"")
> 
> Same problem with Vim.8.1.1239 patch

Line 645:
let g:startify_custom_header =
\ map(split(system('fortune -s'), '\n'), '" ". v:val') + ['']

-- 
-- 
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.

E484 after GVIM update

[Blay263]

After updating my vim version I am getting the error below: 

E484: Can't open file C:\Users\\AppData\Local\Temp\VIoCC2F.tmp

I am using GVIM on windows with the WSL subsytem. It looks like the way the 
escape sequences work has changed.

-- 
-- 
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: [vim/vim] compiled python should not set `sys.executable` to vim (#3707)

[Blay263]

On Friday, December 28, 2018 at 3:25:20 AM UTC-5, Boris Staletic wrote:
> I bet utils.OnWindows() would return FALSE on Mac OSX so IIUC the YCM 
> workaround wouldn't work unchanged there.
> 
> 
> utils.OnWindows() just returns sys.platform == 'win32'.  If sys.executable 
> didn't work on macOS, I'm sure we (YCM maintainers) would notice by now. Even 
> if we didn't have tests and macOS CI set up, on of the core developers is a 
> macOS user.
> 
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub

Can confirm py3 print(sys.executable) points to executable of the vim binary 
instead of python in GVIM windows 10.

-- 
-- 
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: [vim/vim] compiled python should not set `sys.executable` to vim (#3707)

[Blay263]

On Friday, December 28, 2018 at 3:25:20 AM UTC-5, Boris Staletic wrote:
> I bet utils.OnWindows() would return FALSE on Mac OSX so IIUC the YCM 
> workaround wouldn't work unchanged there.
> 
> 
> utils.OnWindows() just returns sys.platform == 'win32'.  If sys.executable 
> didn't work on macOS, I'm sure we (YCM maintainers) would notice by now. Even 
> if we didn't have tests and macOS CI set up, on of the core developers is a 
> macOS user.
> 
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub

Can confirm py3 print(sys.executable) points to executable of the vim binary 
instead of python. 

-- 
-- 
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: [vim/vim] ConPTY support (#3474)

[Blay263]

On Sunday, November 18, 2018 at 9:02:22 AM UTC-5, Blay263 wrote:
> Bump

-- 
-- 
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: [vim/vim] ConPTY support (#3474)

[Blay263]

Bump

-- 
-- 
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: [vim/vim] ConPTY support (#3474)

[Blay263]

So is ConPTY support dead? Any plans on continuing the PR

-- 
-- 
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.

[vim/vim] Detect child process Vim with ConPTY etc (#3521)

[Blay263]

Does vim use conPTY automatically already

-- 
-- 
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: [vim/vim] ConPTY support (#3474)

[Blay263]

On Wednesday, October 3, 2018 at 12:09:17 PM UTC-4, Nobuhiro Takasaki wrote:
> Windows 10 (1809) has been released. how is it?
> 
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub

Has the patch been merged? Terminal/cmd still works the same

-- 
-- 
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: RFC: Signature help/argument hints in a second popup menu

[Blay263]

On Thursday, February 1, 2018 at 7:47:28 AM UTC-5, skywind3000 wrote:
> +1
> +1

+1

-- 
-- 
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: [patch] SAS syntax and indent scripts

[Blay263]

On Sunday, June 24, 2018 at 5:45:43 PM UTC-4, Christian Brabandt wrote:
> On So, 24 Jun 2018, Blay263 wrote:
> 
> > As i mentioned above issuing the command gg=G in a sas file removes all 
> > indention and the text is left aligned.
> 
> With what file? Did you start with vim --clean?
> 
> 
> Best,
> Christian
> -- 
> Letzte Worte eines Grillmeisters:
>   "Hein, gib mal den Spiritus rüber."

So just to give more context about a year ago the SAS vim files were updated. 
For the most part the updates were great but indenting hasn't worked since 
then.To reproduce: gvim --clean test.sas(attached). Then =G.indentation is 
removed . Expect indentation .

-- 
-- 
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.


test.sas
Description: Binary data

Re: [patch] SAS syntax and indent scripts

[Blay263]

As i mentioned above issuing the command gg=G in a sas file removes all 
indention and the text is left aligned.

-- 
-- 
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: [patch] SAS syntax and indent scripts

[Blay263]

On Thursday, June 21, 2018 at 11:49:18 AM UTC-4, Zhen-Huan Hu wrote:
> Is the SAS file type correctly recognized? What's the output of ":filetype" 
> command in your SAS file? If it shows "filetype detection:off" you would need 
> to have somthing like this: 
> https://github.com/akanosora/vimfiles/blob/master/ftdetect/sas.vim under your 
> /vimfiles/ftdetect folder (I don't think Vim automatically recognizes SAS 
> files). Otherwise, you can try to switch auto indent on by typing ":filetype 
> indent on".
> 
> 
> On Thu, Jun 21, 2018 at 9:33 AM, Chris Glessner  wrote:
> On Sunday, August 27, 2017 at 7:55:50 PM UTC-4, Zhen-Huan Hu wrote:
> 
> > I don't know what's causing the issue. Does it happen to all SAS files? 
> > Could you replicate the issue without any third-party plugins?
> 
> >  
> 
> > 
> 
> > 
> 
> > On Sun, Aug 27, 2017 at 9:03 AM, Blay263  wrote:
> 
> > Any update on the indenting issue
> 
> > 
> 
> > 
> 
> > 
> 
> > 
> 
> > 
> 
> > --
> 
> > 
> 
> > --
> 
> > 
> 
> > 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 a topic in the 
> > Google Groups "vim_dev" group.
> 
> > 
> 
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/vim_dev/CflWb5jChQ4/unsubscribe.
> 
> > 
> 
> > To unsubscribe from this group and all its topics, send an email to 
> > vim_dev+u...@googlegroups.com.
> 
> > 
> 
> > For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> Sorry to be posting to this a year later, but I just found this thread.  I'm 
> facing the same issue with the indent plugin not working properly.  
> Specifically, it seems no text automatically indents and normal gg=G removes 
> all indentation, as Blay263 pointed out.
> 
> 
> 
> I am running 32-Bit gVim 8.1 on Windows.  For me, this affects all SAS files. 
>  I was able to confirm I get the same behavior running no plugins in both Vim 
> and gVim (vim -u NONE).  I checked that the plugin was indeed loaded (echo 
> exists("*GetSASIndent")), but it will not indent.
> 
> 
> 
> 
> 
> -- 
> 
> -- 
> 
> 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 a topic in the Google 
> Groups "vim_dev" group.
> 
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/vim_dev/CflWb5jChQ4/unsubscribe.
> 
> To unsubscribe from this group and all its topics, send an email to 
> vim_dev+u...@googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.

This file works sometimes 
.https://github.com/EricGebhart/SAS-Vim/blob/master/indent/sas.vim. There is 
clearly something wrong with the "new" indent file.

-- 
-- 
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: !command error when buffer is split

[Blay263]

Nope. Just tried running the file.

-- 
-- 
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: !command error when buffer is split

[Blay263]

On Sunday, April 1, 2018 at 6:57:13 AM UTC-4, Bram Moolenaar wrote:
> > Sorry so you can open a file xxx.py and then :sp .then run :!python %.(with 
> > the guioption=!)
> 
> What is in xxx.py then?
> 
> -- 
> From "know your smileys":
>  *<|:-)   Santa Claus (Ho Ho Ho)
> 
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org///

xxx.py has print("hello") and a blank line after.

-- 
-- 
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: !command error when buffer is split

[Blay263]

Sorry so you can open a file xxx.py and then :sp .then run :!python %.(with the 
guioption=!)

-- 
-- 
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: Add history in Find dialog

[Blay263]

On Thursday, March 22, 2018 at 2:17:14 PM UTC-4, bee wrote:
> I am using GVIM, and I got a development request for the next version of VIM.
> 
> On the command line (after :) we can scroll through our last command.
> 
> Similarily, it would be great if the field "Search for" ("Suchen nach") in 
> the dialog "Find & Replace" has a history of the strings searched for before. 
> This could be shown in a drop-down-list.

q:,:history

-- 
-- 
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: [vim/vim] Improve color emoji (#2401)

[Blay263]

On Saturday, December 9, 2017 at 12:40:29 PM UTC-5, Blay263 wrote:
> On Thursday, December 7, 2017 at 8:34:17 AM UTC-5, Ken Takata wrote:
> > Hi,
> > 
> > 2017/12/7 Thu 19:56:43 UTC+9 David Kotchan wrote:
> > > On Saturday, December 2, 2017 at 7:03:33 AM UTC-8, K.Takata wrote:
> > > 
> > > > Hi,
> > > > 
> > > > This pull-request is a supplemental patch for #2375 (v8.0.1343).
> > > > 
> > > > This introduces some performance improvements and fixes a bug:
> > > > 
> > > > Improve performance when underlines, strikethroughs or undercurls are 
> > > > used.
> > > > 
> > > > v8.0.1343 uses GDI to draw these lines, however, switching between 
> > > > DirectX and GDI causes terrible slowdown.
> > > > 
> > > > This PR uses Direct2D APIs to draw the lines.
> > > > 
> > > > Improve performance when GDI fallback occurs by using a raster font.
> > > > 
> > > > This PR draws texts on top of a Direct2D surface even if a raster font 
> > > > is selected.
> > > > 
> > > > Add 'scrlines' suboption to the 'rop' option for performance tuning.
> > > > 
> > > > On some environments, redrawing is faster than scrolling. (On my 
> > > > environment, redrawing is about 2x faster.)
> > > > 
> > > > Users can optimize scrolling behavior by using this suboption.
> > > > 
> > > > Fix a bug that the 'mFallbackDC' variable was not properly updated.
> > > > ...
> > > 
> > > I very much appreciate the work that went into the rendering 
> > > improvements. This is great stuff.
> > > 
> > > But after compiling Vim 8 up to patch 1376 (Huge version with GUI; Visual 
> > > Studio 2017), I am finding that rendering is quite slow on some systems.
> > > 
> > > On my machine at work, which is: Win10 Enterprise, OS build 15063.726, 
> > > 64-bit, with an AMD Radeon R9 M370X video card, the rendering is much 
> > > slower than (say) Vim 8 patched to 1366. The screen scrolling cannot keep 
> > > up with ordinary j/k {up/down} keys held down, for example. Window 
> > > refreshes are noticeably slow. There are various flickers here and there 
> > > as the cursor redraws text items on screen during scrolling. These 
> > > flickers are absent (or are so fast, as to be visually absent) on Vim 8 
> > > patch 1366 for example.
> > 
> > Oh, that is totally unexpected.
> > Does the behavior depends on the text you are editing?  The patch 8.0.1369
> > should have improved the performance when showing underlines, undercurls, 
> > etc.
> > Does the scroll speed change when the following setting is used?
> > 
> > set rop=type:directx,scrlines:1
> > 
> > 
> > > On the other hand, on my machine at home, which is: Win10 Pro, OS build 
> > > 15063.726, 64-bit, with an NVidia GeForce GTX 745 video card, there are 
> > > no problems at all(!) Vim 8 patch 1376 is just as fast as patch 1366, and 
> > > the new colored Emoji show up fine.
> > > 
> > > Both systems use the same monospace font (Roboto Mono) and have the same 
> > > _vimrc, _gvimrc and plugins. No Vim functionality is impaired, just the 
> > > drawing speed.
> > > 
> > > Does anyone has any ideas why rendering performance would be so different 
> > > on what would seem to be two essentially identical operating systems and 
> > > (I would have thought) more or less equally capable video cards?
> > 
> > 
> > Regards,
> > Ken Takata
> 
> After this update, I am having several issues :
> -y and g are cutoff
> -artifacts are left behind (see after pic below the status line)
> -status line is miss aligned

The alignment is better but it is still slightly out of position at the top

-- 
-- 
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: [vim/vim] Improve color emoji (#2401)

[Blay263]

On Thursday, December 7, 2017 at 8:34:17 AM UTC-5, Ken Takata wrote:
> Hi,
> 
> 2017/12/7 Thu 19:56:43 UTC+9 David Kotchan wrote:
> > On Saturday, December 2, 2017 at 7:03:33 AM UTC-8, K.Takata wrote:
> > 
> > > Hi,
> > > 
> > > This pull-request is a supplemental patch for #2375 (v8.0.1343).
> > > 
> > > This introduces some performance improvements and fixes a bug:
> > > 
> > > Improve performance when underlines, strikethroughs or undercurls are 
> > > used.
> > > 
> > > v8.0.1343 uses GDI to draw these lines, however, switching between 
> > > DirectX and GDI causes terrible slowdown.
> > > 
> > > This PR uses Direct2D APIs to draw the lines.
> > > 
> > > Improve performance when GDI fallback occurs by using a raster font.
> > > 
> > > This PR draws texts on top of a Direct2D surface even if a raster font is 
> > > selected.
> > > 
> > > Add 'scrlines' suboption to the 'rop' option for performance tuning.
> > > 
> > > On some environments, redrawing is faster than scrolling. (On my 
> > > environment, redrawing is about 2x faster.)
> > > 
> > > Users can optimize scrolling behavior by using this suboption.
> > > 
> > > Fix a bug that the 'mFallbackDC' variable was not properly updated.
> > > ...
> > 
> > I very much appreciate the work that went into the rendering improvements. 
> > This is great stuff.
> > 
> > But after compiling Vim 8 up to patch 1376 (Huge version with GUI; Visual 
> > Studio 2017), I am finding that rendering is quite slow on some systems.
> > 
> > On my machine at work, which is: Win10 Enterprise, OS build 15063.726, 
> > 64-bit, with an AMD Radeon R9 M370X video card, the rendering is much 
> > slower than (say) Vim 8 patched to 1366. The screen scrolling cannot keep 
> > up with ordinary j/k {up/down} keys held down, for example. Window 
> > refreshes are noticeably slow. There are various flickers here and there as 
> > the cursor redraws text items on screen during scrolling. These flickers 
> > are absent (or are so fast, as to be visually absent) on Vim 8 patch 1366 
> > for example.
> 
> Oh, that is totally unexpected.
> Does the behavior depends on the text you are editing?  The patch 8.0.1369
> should have improved the performance when showing underlines, undercurls, etc.
> Does the scroll speed change when the following setting is used?
> 
> set rop=type:directx,scrlines:1
> 
> 
> > On the other hand, on my machine at home, which is: Win10 Pro, OS build 
> > 15063.726, 64-bit, with an NVidia GeForce GTX 745 video card, there are no 
> > problems at all(!) Vim 8 patch 1376 is just as fast as patch 1366, and the 
> > new colored Emoji show up fine.
> > 
> > Both systems use the same monospace font (Roboto Mono) and have the same 
> > _vimrc, _gvimrc and plugins. No Vim functionality is impaired, just the 
> > drawing speed.
> > 
> > Does anyone has any ideas why rendering performance would be so different 
> > on what would seem to be two essentially identical operating systems and (I 
> > would have thought) more or less equally capable video cards?
> 
> 
> Regards,
> Ken Takata

After this update, I am having several issues :
-y and g are cutoff
-artifacts are left behind (see after pic below the status line)
-status line is miss aligned

-- 
-- 
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: [patch] SAS syntax and indent scripts

[Blay263]

Any update on the indenting issue

-- 
-- 
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: [patch] SAS syntax and indent scripts

[Blay263]

On Saturday, August 26, 2017 at 2:06:42 AM UTC-4, Zhen-Huan Hu wrote:
> Please try the attached syntax file and let me know if it solves the syntax 
> issue.
> 
> 
> On Sat, Aug 26, 2017 at 12:59 AM, Blay263 <tate...@gmail.com> wrote:
> 
> 
> On Saturday, August 26, 2017 at 12:58:12 AM UTC-4, Zhen-Huan Hu wrote:
> 
> > On Friday, August 25, 2017 at 6:50:09 PM UTC-5, Blay263 wrote:
> 
> > > The indent file is not working on my windows machine.and the syntax file 
> > > doesn't highlight anything after a datelines statement.
> 
> > >
> 
> > > I tried the files 
> > > https://github.com/EricGebhart/SAS-Vim/blob/master/indent/sas.vim here 
> > > they work but have limitations.
> 
> >
> 
> > Are your SAS files recognized correctly by Vim? What is the "filetype" 
> > value?
> 
> >
> 
> > Does this happen to all SAS files or just some specific files? Could you 
> > send me a sample file with indent/syntax issue to see if I can reproduce 
> > the issue?
> 
> >
> 
> > As for the dataline syntax, do you have a semicolon at the start of a 
> > newline to mark the end of a dataline block? A dataline block in SAS needs 
> > to be written as:
> 
> >
> 
> > dataline
> 
> > xx xx xx
> 
> > xx xx xx
> 
> > ;
> 
> >
> 
> > The semicolon must be the first character in a new line to form a null 
> > statement; otherwise SAS will throw an error.
> 
> 
> 
> I have added the before and after issuing the command gg=G in normal mode.As 
> you can see there is no indenting at all.
> 
> 
> 
> I have also added a file with no syntax highlighting.It works in sas 9.4

Perfect Thanks,syntax works

-- 
-- 
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: [patch] SAS syntax and indent scripts

[Blay263]

On Saturday, August 26, 2017 at 12:58:12 AM UTC-4, Zhen-Huan Hu wrote:
> On Friday, August 25, 2017 at 6:50:09 PM UTC-5, Blay263 wrote:
> > The indent file is not working on my windows machine.and the syntax file 
> > doesn't highlight anything after a datelines statement.
> > 
> > I tried the files 
> > https://github.com/EricGebhart/SAS-Vim/blob/master/indent/sas.vim here they 
> > work but have limitations.
> 
> Are your SAS files recognized correctly by Vim? What is the "filetype" value?
> 
> Does this happen to all SAS files or just some specific files? Could you send 
> me a sample file with indent/syntax issue to see if I can reproduce the issue?
> 
> As for the dataline syntax, do you have a semicolon at the start of a newline 
> to mark the end of a dataline block? A dataline block in SAS needs to be 
> written as:
> 
> dataline
> xx xx xx
> xx xx xx
> ;
> 
> The semicolon must be the first character in a new line to form a null 
> statement; otherwise SAS will throw an error.

I have added the before and after issuing the command gg=G in normal mode.As 
you can see there is no indenting at all.

I have also added a file with no syntax highlighting.It works in sas 9.4

-- 
-- 
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: [patch] SAS syntax and indent scripts

[Blay263]

On Thursday, March 23, 2017 at 5:17:26 PM UTC-4, Bram Moolenaar wrote:
> Keny Hu wrote:
> 
> > I have talked to James Kidd who maintains the SAS syntax script. He kindly
> > agreed to have me assume the maintenance task for him. Please let me know
> > if this is okay with you.
> 
> Very good, thanks for taking over.
> 
> 
> -- 
> % cat /usr/include/sys/errno.h
> #define   EPERM   1   /* Operation not permitted */
> #define   ENOENT  2   /* No such file or directory */
> #define   ESRCH   3   /* No such process */
> [...]
> #define EMACS 666 /* Too many macros */
> %
> 
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org///

The indent file is not working on my windows machine.and the syntax file 
doesn't highlight anything after a datelines statement.

I tried the files 
https://github.com/EricGebhart/SAS-Vim/blob/master/indent/sas.vim here they 
work but have limitations.

-- 
-- 
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: Gvim wont open files with trailing blank lines

[Blay263]

On Sunday, February 19, 2017 at 7:55:25 AM UTC-5, Bram Moolenaar wrote:
> Blay263 wrote:
> 
> > Here is an example with no vimrc.
> > File has three words and three blank lines.
> > 
> > This is on a Windows 10 machine
> 
> Probably a plugin causes this.  Try starting Vim with -u NONE.
> 
> 
> -- 
> You can test a person's importance in the organization by asking how much RAM
> his computer has.  Anybody who knows the answer to that question is not a
> decision-maker.
>   (Scott Adams - The Dilbert principle)
> 
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org///

Yet it was , not sure which one it was but Gvim works now.

-- 
-- 
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.

Gvim wont open files with trailing blank lines

[Blay263]

Here is an example with no vimrc.
File has three words and three blank lines.

This is on a Windows 10 machine

-- 
-- 
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.
one
two
three

Re: Nightly builds

[Blay263]

On Friday, February 3, 2017 at 1:48:28 PM UTC-5, Christian Brabandt wrote:
> On Fr, 03 Feb 2017, Blay263 wrote:
> 
> > On Friday, February 3, 2017 at 2:27:02 AM UTC-5, Christian Brabandt
> > wrote:
> > > On Do, 02 Feb 2017, Blay263 wrote:
> > > 
> > > > Windows 10 blocks you from running the actual  .exe files.I just
> > > > found it odd that the .exe files from vim.org install without any
> > > > problems but the nightly builds are untrusted and thus blocked.
> > > > Both the standalone and the .exe in the zip folders. 
> > > 
> > > I don't know of any way to fix this. If there is and we can actually
> > > do anything about it, I love to hear.
> > 
> > The only thing that comes to mind is that do the executables from the
> > main website have a trusted digital signature that can be transferred
> > to the nightly builds ??
> 
> Don't you have to type a password for signing? I admit I have never 
> looked into how to sign a binary and I don't know if Bram did that with 
> the official builds
> 
> Best,
> Christian
> 
> -- 
> In den meisten Fällen ist Glück kein Geschenkt, sordern ein Darlehen.
>   -- Albrecht Goes

ok turns out it was a bug Windows 10 November update (version 1511).An update 
of my OS solved this issue. Thanks for your help 

-- 
-- 
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: Nightly builds

[Blay263]

On Friday, February 3, 2017 at 2:27:02 AM UTC-5, Christian Brabandt wrote:
> On Do, 02 Feb 2017, Blay263 wrote:
> 
> > Windows 10 blocks you from running the actual  .exe files.I just found
> > it odd that the .exe files from vim.org install without any problems
> > but the nightly builds are untrusted and thus blocked. Both the
> > standalone and the .exe in the zip folders. 
> 
> I don't know of any way to fix this. If there is and we can actually do 
> anything about it, I love to hear.
> 
> 
> Best,
> Christian
> -- 
> Es steht mancher vor seinem Glück und ist unfähig es zu begreifen.
>   -- Martin Kessel

The only thing that comes to mind is that do the executables from the main 
website have a trusted digital signature that can be transferred to the nightly 
builds ??

-- 
-- 
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: Nightly builds

[Blay263]

Windows 10 blocks you from running the actual  .exe files.I just found it odd 
that the .exe files from vim.org install without any problems but the nightly 
builds are untrusted and thus blocked. Both the standalone and the .exe in the 
zip folders.
If there is no easy fix .I will have to resort to more primitive ways of 
editing thanks

-- 
-- 
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: Nightly builds

[Blay263]

Windows 10 blocks you from running the actual  .exe files.I just found it odd 
that the .exe files from vim.org install without any problems but the nightly 
builds are untrusted and thus blocked. Both the standalone and the .exe in the 
zip folders. 

If there us no easy fix .I will have to resort to more peimitive ways of 
editing thanks

-- 
-- 
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: Nightly builds

[Blay263]

On Friday, February 3, 2017 at 1:21:55 AM UTC-5, Christian Brabandt wrote:
> Hi Blay263!
> 
> On Do, 02 Feb 2017, Blay263 wrote:
> 
> > I work on windows machines and I appreciate the nightly builds here
> > https://github.com/vim/vim-win32-installer. I am currently working on
> > a windows 10 machine without admin privileges and am wondering if the
> > executable could be created so as not to require admin privileges to
> > install.
> > 
> > The executables on the main site work ok but they are not compiled
> > with the features contained in the above.
> 
> Download the zip file, unzip them to a writable path and click on 
> gvim.exe. You don't need any admin rights for that.
> 
> Best,
> Christian
> -- 
> Ein Bilderbuch ist diese Welt, das manchem herzlich wohl gefällt, der
> blätternd Bild um Bild genießt, vom Text nicht eine Zeile liest.
>   -- Paul von Heyse

You are right but you can't open the .exe files because windows smart-screen 
marks them as untrusted files.

-- 
-- 
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.

Nightly builds

[Blay263]

I work on windows machines and I appreciate the nightly builds here 
https://github.com/vim/vim-win32-installer.
I am currently working on a windows 10 machine without admin privileges and am 
wondering if the executable could be created so as not to require admin 
privileges to install.

The executables on the main site work ok but they are not compiled with the 
features contained in the above.

Thanks in advance

-- 
-- 
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.

Nightly builds

[Blay263]

I work on windows machines and I appreciate the nightly builds here 
https://github.com/vim/vim-win32-installer.

I am currently working on a windows 10 machine without admin privileges and am 
wondering if the executable could be created so as not to require admin 
privileges to install.

The executables on the main site works ok but they are not compiled with the 
features contained in the above.

Thanks in advance

-- 
-- 
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: [vim/vim] Optimize HiDPI Screen on GVim Windows (#1059)

[Blay263]

On Wednesday, September 14, 2016 at 2:41:42 PM UTC-4, nor...@googlegroups.com 
wrote:
> I am not sure, what you are seeing, probably some kind of this: 
> dcpurton/regfont#1
> 
> 
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub

Yep,was an issue with my font.Fixed thanks

-- 
-- 
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.