m/d/topic/vim_dev/JZ_BC4tYotU/unsubscribe.
> To unsubscribe from this group and all its topics, 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/vim/vim/repo-discussions/13458/comments/7621864%4
On Tuesday, September 5, 2023 at 2:55:19 AM UTC-5 3nan@gmail.com wrote:
>
> On Mon, 4 Sep 2023 20:16:09 -0700 (PDT)
> Ben Fritz wrote:
> > This bit me while getting my TOhtml tests working on Windows with a
Visual
> > Studio build environment. I'm not sure if it&#
This bit me while getting my TOhtml tests working on Windows with a Visual
Studio build environment. I'm not sure if it's a bug or not, but I can't
find any description of it in the help and it isn't acting as I'd expect.
Vim seems to change path to the directory containing a file, if it is
pas
iling lists. I don't know yet how
> he managed this and how to request access specifically for
> vim-announce and vim-mac (is this actually still used?) Does anybody
> have a contact to the googlegroups admins?
>
> - The mailing lists vim-dev and vim-use are currently manag
to wait another day or so...
--
Ben
--
--
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 Tue, Aug 30, 2022 at 10:04 AM D. Ben Knoble wrote:
>
> On Fri, Aug 26, 2022 at 2:57 PM Bram Moolenaar wrote:
>
> > Thanks. Mostly OK, but I see that line continuation is used in the
> > ftplugin file, therefore the 'cpo' option should be set and restored.
On Fri, Aug 26, 2022 at 2:57 PM Bram Moolenaar wrote:
> Thanks. Mostly OK, but I see that line continuation is used in the
> ftplugin file, therefore the 'cpo' option should be set and restored.
> See other runtime files for examples.
Good catch. Will fix.
> > The improved ftdetect is not incl
Attached are improved syntax, ftplugin, indent, and compiler files for Racket.
These are extracted from https://github.com/benknoble/vim-racket with
the help of Doug Kearns.
The improved ftdetect is not included yet; it would change the way
*.rkt files are handled.
D. Ben Knoble
--
--
You
I wonder if it would be possible to record the window ids of the windows
overlapped by the completion pum and only redraw those with NOT_VALID rather
than all of them?
> On 20 Aug 2022, at 19:24, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> I have be
to recall that popup windows
have a clever way to minimise the redraw by storing what they are obscuring (or
did I imagine that?).
I’m may have some time/impetus to work on this if it’s a plausible direction.
Cheers,
Ben
--
--
You received this message from the "vim_dev" maillist.
OK, makes sense, thanks.
> On 18 Feb 2022, at 11:29, Bram Moolenaar wrote:
>
>
>>> Wether a function is script-local or global (when not using a "s:" or
>>> "g:" prefix) depends on the script it's defined in The rule is "at the
>>> script level, the type of script defines what the scope of the
Thanks Bram. Much appreciated. I’ll reach out to Charles.
> On 31 Dec 2021, at 23:13, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> I know it’s kind of tedious, but I have question about the vim license
>> (:help license) specifically relating to the runtime
Thanks,
Ben
--
--
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
&qu
Thanks, Bram, will do.
> On 25 Nov 2021, at 10:51, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> I proposed this patch a while back to Charles, but I don’t think I got a
>> response.
>> It adds support for "py3 << trim EOF” in vim.vim syntax f
Hi Bram,I proposed this patch a while back to Charles, but I don’t think I got a response.It adds support for "py3 << trim EOF” in vim.vim syntax file.I can make a GitHub PR if you prefer.TaBenBegin forwarded message:From: Ben Jackson <puremourn...@gmail.com>Subject: Re: syntax/
ssues with
doing so.
D. Ben Knoble
On Thu, Jul 1, 2021 at 4:09 PM Bram Moolenaar wrote:
>
> Ben Knoble wrote:
>
> > Consequently it breaks when switching filetypes with no indent settings.
> >
> > My suggested fix is to add the following line to the end of the fi
Consequently it breaks when switching filetypes with no indent settings.
My suggested fix is to add the following line to the end of the file:
let b:undo_indent = 'setl indentexpr< indentkeys<'
Best,
D. Ben Knoble
--
--
You received this message from the "vim_dev"
Yeah, thanks!
If eval_variable (via lookup_debug_var) or similar would return function args
for def functions, then that would be pretty neat and we can watch and inspect
them.
For my side I would need to add a list of locals and script vars for vim9
script contexts (for the scopes window) an
Hi Charles,
>
> Vim 8.1 has supported py3 < to the runtime file for syntax/vim.vim
>
> Would you consider including it?
>
> <0001-Runtime-vim-python-syntax-supports-trim.patch>
>
> THanks,
> Ben
--
--
You received this message from the "vim_dev&qu
roups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/DD68063A-F560-4B27-8446-15F65359733C%40gmail.com.
0001-Runtime-vim-python-syntax-supports-trim.patch
Description: Binary data
THanks,
Ben
--
--
You received this message from the "vim_dev" ma
> The "??" operator is used in TypeScript, JavaScript, C# and a few other
>
> languages.
Oh ok, fair enough, thanks. Shows how much I know :) I’d never seen it before.
> On 5 Oct 2020, at 14:20, Bram Moolenaar wrote:
>
>
>>> var name = Getname() ?? 'unknown'
>>
>> This `??` operator seems a
Great work, and much appreciated.
On Sunday, August 2, 2020 at 4:39:36 PM UTC+1, yega...@gmail.com wrote:
>
> Hi all,
>
> With patch 8.2.1354, all the old style tests (except for test49 which tests
> the vim script functionality) have been converted to new style tests.
>
> - Yegappan
>
>
--
--
In YCM we absolutely need byte offsets but we do end up doing a fair amount of
shenanigans the convert between bytes and characters depending on encodings and
things.
LSP for example regrettably uses UTF16 code units. Counting characters is made
tricky by things like combining marks IIRC
--
Reasonable (if subtle) change. Need to ensure there is a way to get a byte
index too eg a way to cast to blob ? Indexing a blob giving bytes and indexing
a string giving characters seems solid and easy to learn. Consistent with thing
like str/bytes in python for example.
--
--
You received t
f, 'echo g:global_var', [ 'global' ] )
" FIXME: Unexpected: global_var should be found
" call RunDbgCmd(buf,
" \'echo global_var',
" \[ 'global' ] )
call RunDbgCmd(buf,
\'echo global_
My opinion is that it's ok to drop double-quote comments in vim9 script. I
think it's good to only have 1 way to do things right, so having both
double-quote and hash comments feels off.
Vim is a somewhat of an outlier in using double-quote for comments, so it
would seem and feel natural to me
currently the only viable
GUI on the Mac.
My suggestion would be to remove the others unless anyone is out there
building recent versions of Vim for legacy OS versions (which is
probably futile, so I doubt it; building an older version of Vim for an
older OS would be a smoother road).
Smiles,
Ben
> register_cfunc is generic enough to also work for python and ruby which
would allow those languages to also extend if needed using this same
mechanism. Else one would need to create global functions in vimscript and
then use vim.funcref which isn't ideal.
That's interesting. I don't use the l
HOME =~ "^/home"
echo "GOT HERE#1"
else
echo "GOT HERE#2"
endif
let $HOME = "/some/home"
endfunction
It seems the function body impedes the other rules (??).
Best,
D. Ben Knoble
--
--
You received this message from the "vim_dev" maillist.
All,
I sent the following message to Dr. Chip RE: vim syntax files, and it
bounced back; do we know if there's a more current contact for him
(and whether or not he's ok)?
D. Ben Knoble
-- Forwarded message -
From: D. Ben Knoble
Date: Tue, May 26, 2020 at 11:13
I don't use `:marks` in any of my plugins, but if I did, I would _much_
prefer a function returning them as a list/dict than having to parse the
output of exectute( 'marks' )
So +1 to this, and +1 to adding one for popups too.
On Friday, May 1, 2020 at 4:52:27 PM UTC+1, yega...@gmail.com wrote:
I even posted a patch to support all-event mouse tracking, but no answer
from the PuTTY owner. https://github.com/puremourning/putty/pull/1
On Thursday, April 16, 2020 at 10:09:07 PM UTC+1, Christian Brabandt wrote:
>
> oh wow, thanks for digging it up!
>
> —
> You are receiving this because you
Thanks, Bram.
> On 13 Apr 2020, at 14:46, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> When we were discussing vim9script, I mentioned that an interface for
>> external/graphical debuggers for vimscript would be useful. Your response
>> at the
changes
in smaller tested pieces of course)
- get your general thoughts on the approach above
- gauge community reaction, thoughts, comments, insults etc.
Thanks for everything. If the general reaction is positive, I'll make a
proper plan and send some more detailed RFCs for the various aspe
At the risk of too much self-promotion, we _could_
mention https://github.com/puremourning/vimspector as an alternative for
multiple languages.
On Monday, April 13, 2020 at 11:45:19 AM UTC+1, Omri Sarig wrote:
>
> In the help file develop.txt, there is a line that references some
> optional too
It depends on the tracking mode being used. This reference (which I presume
you've seen) is most
useful:
https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Button-event-tracking
Note the SGR mode slightly modifies it as well.
Hope that's vaguely useful. I have to read that spec 3 or 4
> a restriction will be that script-local items
are defined once and not deleted. That makes it possible to find them
> by index, which is much faster than a dictionary lookup.
Does this mean "unlet" will no longer work for local variables if namespaces
are used? How about exists(), does this ad
> On 5 Jan 2020, at 18:55, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> Hi Bram, thanks for sharing. Looks really promising.
>>
>> Regarding https://github.com/brammool/vim9#3-better-vim-script, I have a
>> few ideas for your consideration:
hich improves sourcing_lineno and uses a proper stack.
I was planning to work on a patch to store source/line info when debugging
is enabled, but might hold off while vim 9 shakes down, as this is likely
required for the above debugger interface (assuming that's a goal).
Just a few ideas to
Bram, if you're going to be a doing a fair amount of work on the vimscript
side of things, one thing I would like to request is to have a mind towards
being able to support a full-on vimscript debugger. I realise there is a
built-in debugging mode, but it would be exceptionally cool to be able t
> what is your favorite improvement since Vim 8.1?
popup windows :) I guess I'm a little biased, but I think this is a great
improvement, and the API is really nice to use.
On Friday, November 29, 2019 at 9:13:22 PM UTC, Bram Moolenaar wrote:
>
>
> It appears the number of bug reports is getting
Maybe better off to use popup_beval these days.
--
--
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 subscribe
Very nice! Thanks! I had a bunch of fiddly code to approximate this.
--
--
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 beca
Raised; https://github.com/vim/vim/issues/4860
> On 21 Aug 2019, at 19:26, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> Thanks Bram. I like it a lot.
>>
>> One thing i would like is the ability to remove the borders. I’m not a
>> fan of the bor
I can still repro as of latest patch just now, so I will try and write a
minimal case.
> On 21 Aug 2019, at 19:26, Bram Moolenaar wrote:
>
>
> Ben Jackson wrote:
>
>> Thanks Bram. I like it a lot.
>>
>> One thing i would like is the ability to remove the
Thanks Bram. I like it a lot.
One thing i would like is the ability to remove the borders. I’m not a fan of
the borders in general due to the extra screen space they use (and this the
extra code they cover). I can also live without the X in the corner if the
popup goes away with Ctrl-y which I
On Thursday, June 6, 2019 at 3:57:41 PM UTC+1, Paul Jolly wrote:
> Hi all,
>
> I'm somewhat/extremely behind on the text properties work, which looks
> very exciting.
>
> In the context of govim (https://github.com/myitcv/govim), I'm
> considering using text properties as a way of showing a simpl
Might be a strange question, but does anyone have a good errorformat setting
for running vim's tests?
When editing tests, I use a mapping to run the test and populate the quick fix
list with any tests failures. Ultimately, I have a compiler plugin, but it
really just:
setlocal errorformat=Foun
On Saturday, May 18, 2019 at 1:39:15 PM UTC+1, Bram Moolenaar wrote:
> In a recent Vim you can see the current ideas of the popup window design
> with ":help popup". Or go to github:
> https://github.com/vim/vim/blob/master/runtime/doc/popup.txt
>
> I have been wondering about how to specify the
On Wednesday, February 20, 2019 at 4:18:33 PM UTC-6, Bram Moolenaar wrote:
>
> As mentioned, the fold code currently can't handle two folds without a
>
> line in between. Perhaps it can be made to work to consider a filler
>
> line something in between folds. No idea how difficult that is.
>
On Wednesday, February 13, 2019 at 1:03:10 PM UTC-6, John Marriott wrote:
> On 14-Feb-2019 03:51, Ben Fritz wrote:
> > I was trying to set up for building Vim on a Windows 10 installation where
> > I haven't done that before.
> >
> > I tried the Msys distributio
I was trying to set up for building Vim on a Windows 10 installation where I
haven't done that before.
I tried the Msys distribution of mingw-64 first, and after I installed make and
gcc using the package manager, I got compiler errors all over the place. Most
errors to start with were for pret
I suggest sending it to Bram directly.
--
--
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 G
Good to hear! I am still working on a couple other fixes before sending out a
new version to put in the runtime files. Hopefully I'll finish this week. I'll
try to remember to update this thread when done. :-)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
On Wednesday, December 5, 2018 at 9:44:30 AM UTC-6, jonshouse1 wrote:
> Unfortunately people are still unhappy, partly because it seems there are
> many people who do not use a user specific vimrc file and simply used the
> system wide vimrc config file (I had a similar discussion with several De
On Wednesday, November 28, 2018 at 5:11:35 AM UTC-6, Axel Bender wrote:
> Using GVim 8.1. (Windows 10 64-bit), after applying a syntax scheme,
> 2html.vim fails to correcly expand the tabs contained in the base document.
>
> Sample files:
>
> - sample.lang# The source file
> - lang.vim
On Wednesday, November 28, 2018 at 5:11:35 AM UTC-6, Axel Bender wrote:
> Using GVim 8.1. (Windows 10 64-bit), after applying a syntax scheme,
> 2html.vim fails to correcly expand the tabs contained in the base document.
>
> Sample files:
>
> - sample.lang# The source file
> - lang.vim
I also find myself wanting the vartabs feature any time I am working with
columned format or taking notes in tabular form. I haven't bothered myself to
go find and apply the patch because I need it so infrequently and for some use
cases can just go open up a spreadsheet in a different program.
On Monday, February 26, 2018 at 6:55:04 PM UTC-6, CoinCheung wrote:
> For markdown files, there can be other programming language coded embedded
> between the ``` ``` pair. however, in vim these code blocks does not have
> highlighted syntax. Did I have the wrong configuration to turn this featur
On Wednesday, December 27, 2017 at 7:21:38 PM UTC, Łukasz Jan Niemier wrote:
> Currently Vim allows only single line completions. This is quite limiting as
> there is also no way to determine beginning and end of the completed text so
> this leaves us in the limbo where we need to do some hackish
On Thursday, December 28, 2017 at 10:28:42 AM UTC, Christian Brabandt wrote:
> Alternatively we could allow List as 'word' parameter where each line would
> be one item.
>
>
> +1 for this
>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly
also replicated below for those that prefer plaintext :)
I'd be super grateful for any responses, comments, flames, ideas or even
insults ;)
Cheers,
Ben
---
# TL;DR
This RFC proposes introducing a second popup menu in insert mode to display
method argument hints, current parameter, etc.
On Wednesday, November 8, 2017 at 5:18:12 PM UTC-6, Wouter Verhelst wrote:
> Unluckily the defaults also set some things that I do think make sense, and
> so if I just want to switch off the IMHO broken mouse behavior I first have
> to copy most of defaults.vim to my own config file. That makes n
On Friday, October 20, 2017 at 10:08:33 PM UTC-5, WJH wrote:
> Introduction
>
> I found myself not really using the s key. Because I could simply use xi to
> achieve the samething.
Slightly off-topic, but actually xi doesn't do the same thing. In particular,
the change you make with 's' can be
On Wednesday, October 11, 2017 at 2:39:38 PM UTC-5, xtal8 wrote:
> Vim: v8.0.1184 x64
>
> Os: Windows 10 x64
>
> Steps to reproduce
>
> mkdir test
> vim --clean
> :e test\foobar
> :b test\fo
> completions are not provided
>
>
> If backslash is replaced with forward slash, completions also don'
On Saturday, October 7, 2017 at 2:30:32 AM UTC-5, Christian Brabandt wrote:
> On Fr, 06 Okt 2017, Ben Fritz wrote:
>
> > https://bitbucket.org/fritzophrenic/vim-tohtml/issues/14/add-support-for-strikethrough
> >
> > I am starting to get a backlog...I will try to get ou
On Thursday, October 5, 2017 at 1:03:04 AM UTC-5, Christian Brabandt wrote:
> On Di, 03 Okt 2017, Ben Fritz wrote:
>
> > I for one will definitely use it, I didn't remember that strikethrough
> > had been added! Thanks for the example, if nothing else!
>
> There
On Friday, October 6, 2017 at 9:57:28 AM UTC-5, daRAMA wrote:
> This was introduced somewhere between the first binary release of 8.0 and the
> second one with patches 1-586 included and can still be reproduced in the
> latest nighlty. Last tested with 1159.
>
> To reproduce:
>
> use a blank _v
On Tuesday, October 3, 2017 at 10:55:54 PM UTC-5, Manuel Ortega wrote:
>
>
> Am I the only one who looked at the screenshot and found it harder to read
> than the non-strikethough version of diff highlighting? Seriously, the
> *color* is what tells the reader which text is the old text.
Whic
On Wednesday, September 27, 2017 at 8:59:18 AM UTC-5, dor.azo...@safebreach.com
wrote:
> I would like to report a possible abuse one can perform on Vim's
> extensibility mechanism, that may lead to privilege escalation.
>
> In short, a malicious actor that can execute code as one of the sudoers
On Monday, October 2, 2017 at 1:05:03 PM UTC-5, Bram Moolenaar wrote:
> Christian wrote:
>
> > Bram,
> > since Vim can now display strikethrough attributes (in the gui), let's
> > make a bit more use of it.
> >
> > This patch adds the strikethrough attribute to the diff syntax file for
> > dele
On Friday, September 15, 2017 at 4:05:20 AM UTC-5, plbowers wrote:
> I couldn't get the au to work, but I just put unmap/iunmap/cunmap on separate
> lines in my Prog.../Vim/_vimrc after the mswin.vim and it solved the problem.
> Thanks for your help!
>
> I see this as a workaround - I really thi
On Friday, September 15, 2017 at 12:37:29 PM UTC-5, Ben Fritz wrote:
> On Friday, September 15, 2017 at 10:31:10 AM UTC-5, Sam Pagenkopf wrote:
> > It seems to be consistent across indentation methods.
> >
> >
>
> That doesn't make any sense, can you explain
On Friday, September 15, 2017 at 10:31:10 AM UTC-5, Sam Pagenkopf wrote:
> It seems to be consistent across indentation methods.
>
>
That doesn't make any sense, can you explain what options you actually tried?
'autoindent' obviously won't do that, 'smartindent' is somewhat deprecated and
does
On Sunday, September 10, 2017 at 5:17:02 PM UTC-5, Christian Brabandt wrote:
> What is the preferred way of getting rid of this? Do I have to go in and edit
> my mswin.vim file directly? Isn't that something you don't want people to do
> so as to keep updates easy? Suggestions how I can dump thes
On Monday, August 28, 2017 at 10:52:31 PM UTC-5, Ken Takata wrote:
> If you don't like it, you should create your own .vimrc (or _vimrc) in
> your home directory (normally C:\Users\\).
>
Even better (if you use plugins and the like) is to create
"C:\Users\\vimfiles\vimrc" so that everything is i
Off-topic: for some reason my (fritzophrenic's) latest comment on Github was
attributed to "Nikolai Alexsandrovich Pavlov" on the mailing list. Bug in a
script somewhere?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyi
Just had a feature idea, thought I'd throw it out here.
It would be nice if you could specify the various ++opt options to instruct vim
how to interpret the bytestreams of files opened right from the command-line.
Currently the only way to use ++opt options is when calling :edit or :read (as
fa
On Tuesday, August 8, 2017 at 5:06:25 AM UTC-5, zhao-lei Xiong wrote:
> when I execute command:
> source ~/.vimrc
>
> and it comes error like below:
>
> /Users/jdcrew/.vimrc:14: command not found: syntax
> /Users/jdcrew/.vimrc:15: command not found: syntax
> /Users/jdcrew/.vimrc:34: bad pattern:
:help design-not needs an update considering the recent work on running a
terminal in Vim (even recursive vim in vim apparently):
> VIM IS... NOT *design-not*
>
> - Vim is not a shell or an Operating System. You will not be able to run a
> shell inside Vi
On Monday, July 17, 2017 at 8:34:39 AM UTC-5, Tyler Akins wrote:
> /quote Is your Hexmode command defined to allow a | to separate it from
> another command? I.e. did you use "command -bar Hexmode ..." to define it?
>
> That's very interesting, and I'm glad that I asked. Yes, the command was
> a
On Sunday, July 16, 2017 at 1:53:54 PM UTC-5, Bram Moolenaar wrote:
> Ben Fritz wrote:
> >
> > I build version 8.0.724 and the behavior of "wincmd _" is now fixed, but
> > I don't see any patch description that seems to apply between 692 and
> > 724. An
On Saturday, July 15, 2017 at 1:59:52 PM UTC-5, Christian Brabandt wrote:
> On Sa, 15 Jul 2017, Ben Fritz wrote:
>
> > For determining whether a quickfix window is a location list or a
> > quickfix list, is there a different way to do that besides attempting
> > a ":c
On Saturday, July 15, 2017 at 6:27:27 AM UTC-5, Bram Moolenaar wrote:
> Ben Fritz wrote:
>
> > On Friday, July 14, 2017 at 12:09:42 PM UTC-5, Bram Moolenaar wrote:
> > > Daniel Hahler wrote:
> > >
> > >
> > >
> > > > Horsefly I can
On Friday, July 14, 2017 at 12:09:42 PM UTC-5, Bram Moolenaar wrote:
> Daniel Hahler wrote:
>
>
>
> > Horsefly I can use another auto command then.
>
>
>
> It might work to use the QuickFixCmdPost event and check if &filetype ==
>
> 'qf'
>
Not if you're trying to respond to a ":copen" comm
On Friday, July 14, 2017 at 7:55:31 AM UTC-5, Tyler Akins wrote:
> First off, I apologize for my lack of VimScript knowledge. I have adopted a
> plugin that will allow users to edit files in hex when using vim -b and it
> has the possibility of automatically editing files based on extensions or b
On Wednesday, June 7, 2017 at 1:55:14 PM UTC-5, kwizzz wrote:
>
> As this is a corporate laptop...in the end I cannot deinstall my virus scanner
>
I suggest asking IT if there is a whitelist folder pre-configured for the virus
scanner. If you're a software shop at least, it's useful to have a p
On Friday, June 2, 2017 at 3:36:40 PM UTC-5, kwizzz wrote:
> I am having troubles with vim (8.0.586 and 7.4 downloaded from www.vim.org)
> on Windows 7.
>
> There seems to be a time stamp issue with swap files where swap files will not
>
> get removed after closing vim with swap files being 1 se
On Sunday, May 28, 2017 at 3:10:42 AM UTC-5, Yubin Ruan wrote:
> empty lines are not deleted by "g/^\s*$/d".
It's because you used an unescaped '\' inside double quotes ('"'). Try either
of the following:
exec "g/^\\s*$/d"
g/^\s*$/d
Note that the 'g' by itself starts an ex command, ther
On Wednesday, May 24, 2017 at 9:00:23 AM UTC-5, Marius Gedminas wrote:
> I'm on vim 8.0.597. I've recently noticed that sometimes when I open a
> file from the quickfix list I get it without syntax highlighting. The
> &filetype is blank, and :verbose set filetype? doesn't show it being set
> by a
On Friday, May 19, 2017 at 9:11:16 AM UTC-5, Patrick Eigensatz wrote:
> Hi everybody!
>
>
> I use vim on a daily basis at work but also at home and I think as I write
> this e-mail anyway, it would be a good place to thank you for all the effort
> you put in it all the time! Thanks!
>
>
>
>
On Thursday, May 18, 2017 at 11:54:11 AM UTC-5, Jack Nagel wrote:
> I ran into what seems like a bug when setting the global value of a
> buffer-local option from my .vimrc.
>
> If I invoke vim this way.
> vim -N -i NONE -u NONE -c "setglobal autoindent" -- file
>
>
> I would expect the buffer
On Wednesday, May 17, 2017 at 5:42:19 PM UTC-5, David Larson wrote:
> On Thursday, May 11, 2017 at 2:36:43 PM UTC-7, David Larson wrote:
> > When pasting a line at the beginning of an open fold, the fold closes. To
> > reproduce:
> >
> > % vim -N --noplugin -u NONE -U NONE -c "set sw=2 fdm=indent
On Thursday, May 11, 2017 at 1:47:35 PM UTC-5, Bram Moolenaar wrote:
>
> The missing piece of information is how this is useful. Keep in mind
> that the actual key is also in memory (so that it can be used when
> writing the file). Not sure how clearing a derevative of it helps.
>
I think it w
On Thursday, May 4, 2017 at 10:56:21 AM UTC-5, Andy Stewart wrote:
>
> I believe this is because vim's filetype detection uses:
>
> runtime! ftdetect/*.vim
>
> I think that when that line is executed, the plugins in
> ~/.vim/pack/stuff/start/ are not on the runtimepath. So Vim falls back to
>
On Sunday, April 23, 2017 at 11:38:46 AM UTC-5, yegapp...@gmail.com wrote:
> Hi,
>
> On Sun, Apr 23, 2017 at 7:03 AM, LemonBoy wrote:
> >
> > This behavior is more intuitive IMO, full backward compatibility is
> > achieved by introducing a new option, a test is provided but makes no sense,
> > go
On Monday, April 17, 2017 at 9:02:30 PM UTC-5, Tallys Martins wrote:
> Up
>
>
Did you try going to Dr. Chip's website at
http://www.drchip.org/astronaut/vim/index.html#NETRW to download his latest
changes to netrw? If so, what was the result? If that version is still broken,
how about the oth
On Tuesday, April 11, 2017 at 10:31:52 AM UTC-5, Bruno Bronosky wrote:
> https://github.com/vim/vim/blame/e0720cbf63eb3045be8d965e3182c0c392c7b5e9/runtime/doc/options.txt#L505
>
>
>
>
> The second form (this is compatible with some versions of Vi):
>
>
>
>
> https://github.com/vim/vim/blame
On Monday, April 10, 2017 at 3:40:21 PM UTC-5, Wolfgang Jeltsch wrote:
> Am Montag, den 10.04.2017, 08:32 -0700 schrieb Ben Fritz:
> > My mistake. I CAN reproduce the issue, I tested the wrong thing. Sorry
> > about that! I also see that pasting from the unnamed register, after
On Monday, April 10, 2017 at 10:26:27 AM UTC-5, Wolfgang Jeltsch wrote:
> >
> > I can't reproduce this in 8.0.427 64-bit gvim on Windows. What version
> > of Vim are you using? Does it do the same thing without your
> > configuration loaded, e.g. when launching with "gvim -N -u NONE -i
> > NONE"?
>
1 - 100 din 1448 matches
Mail list logo
