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
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
>
[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:*
> f
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( *
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
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.
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
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:
>
>
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,
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
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
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
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
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
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
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 écr
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:
> > >
&g
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"
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,
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,
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
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
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
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
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
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
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 v
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
18 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?
>
> >
&g
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
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
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
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
>
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.T
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).
> >
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
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, 2
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.
&
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,
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
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
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:
> > >
> &
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
> >
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
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
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 wor
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
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
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
49 matches
Mail list logo
