How about filter(d, “0”) ?
To my understanding it clears the dictionary in place.
--
--
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
On Wed, Jan 29, 2020 at 12:58 PM Bram Moolenaar wrote:
...
> Try or . Shift is a separate modifier.
That works great, thank you!
> > Another observation - in a command or insert mode
> > produces accented character "á", 225, Digr a', which is to my
understanding
> > a translated keycode. Map
On Tue, Jan 28, 2020 at 10:24 PM Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:
...
> The problem is that when running Vim in a console (as opposed to gvim)
> any keys and key combos you hit have to go through a console interface
> before they reach Vim… or don't. Some of these are passed t
Hello,
I am using a fairly recent XTerm(348) on Debian linux.
I have noticed that the modifyOtherKeys feature in vim
makes mappings of meta keys (produced with Alt modifier)
work out of the box, for example, `map :echo "meta-a"`.
This however seems to work only for lowercase letters,
defining `ma
On Tuesday, February 7, 2017 at 2:09:23 AM UTC-5, jott...@googlemail.com wrote:
...
> from ":help {subject}":
>
> | *{subject}* *E149* *E661*
> | :h[elp] {subject} Like ":help", additionally jump to the tag {subject}.
> | {subject}
On Wed, Dec 21, 2016 at 12:45 PM, Tony Mechelynck
wrote:
> Unary + and unary - are accepted as operators for Numbers in
> vimscript. Floats are not expressly mentioned under ":help expr7" but
> I would expect them to be "some kind of number", thus + 1.2 should be
> a legitimate expression (1.2, un
On Wed, Dec 21, 2016 at 12:05 PM, Dominique Pellé
wrote:
...
> I also think that it's odd to accept spaces between the
> sign and the digits. However, Vim already accepts spaces
> after the - sign and not after the + sign (inconsistency addressed
> in patch in this thread). If we instead give
On Friday, December 16, 2016 at 1:58:59 PM UTC-5, Dominique Pelle wrote:
...
> While testing, I found what looks like a possible small bug:
>
> :echo str2float(" + 1.2")
> 1.2
>
> :echo str2float(" - 1.2")
> 0.0
>
> I would expect 2nd command to print -1.2, or is
> there a reason for non-symmetr
Hello,
I have a Vim plugin that needs to access a persistent variable stored in
viminfo. The viminfo file is however loaded _after_ the plugins therefore the
script has to use the VimEnter autocommand to get to the global variable. I
have wrapped this autocommand in a single-use augroup, whic
On Tue, Jan 19, 2016 at 3:03 AM, John Little
wrote:
> > The simplest thing to do would be to reset the tags file to its
> > versioned state before pulling in the latest changes from Bram.
> >
> > $ git checkout runtime/doc/tags
>
> I just learned about git checkout recently. This is a nuisance
On Fri, Jan 15, 2016 at 4:03 PM, Ben Fritz wrote:
> Ah, but we don't WANT a merge. The customized changeset is simply acting
> as a stash that we don't need to manually push/pop from. Thus I suggested
> rebasing, and Matteo improved with using "git pull --rebase" instead of a
> second manual reba
On Friday, January 15, 2016 at 1:32:05 PM UTC-5, Bram Moolenaar wrote:
...
> Please keep in mind that people who don't know git and just want to
> build Vim without learning the (complex and confusing) git commands
> need step-by-step instructions that "just work".
>
> From the above line "commit"
On Wednesday, August 19, 2015 at 9:03:52 AM UTC-4, Olaf wrote:
> On 19-Aug-15, Bram Moolenaar wrote:
> >
> > Justin M. Keyes wrote:
...
> > > Why was the _mercurial_ tag format changed in the google code
> > > repository? This breaks all URLs using the old tag format:
> > >
> > > https://code.goo
On Thursday, July 23, 2015 at 2:11:05 PM UTC-4, Roland Eggner wrote:
> Hi Bram
...
> v4:
> Further improvements based on imput from Pavol Juhas (mail thread “Issue 385
> in
> vim: expansion of environment variables fails in Vim backtick expression”).
>
> For easier revi
On Monday, July 20, 2015 at 5:38:10 PM UTC-4, Roland Eggner wrote:
...
> I reproduced with vim-7.4.529:
>
> :e `=$HOME . '/.vimrc'`
> E15: Invalid expression: /home/roland . '/.vimrc'
> "`=/home/roland . '/.vimrc'`" [New DIRECTORY]
> :e `=expand('$HOME') . '/vimrc'`
> :ls
> 1 #"`=/home/rolan
On Fri, Jul 17, 2015 at 09:44:55AM +0200, Roland Eggner wrote:
...
> On 2015-07-16 Thursday at 18:52 + v...@googlecode.com wrote:
...
> > What steps will reproduce the problem?
> >
> > vim -u NONE -i NONE -N
> > :e `=$HOME . '/.vimrc'`
> >
> > What is the expected output? What do yo
--
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/groups/opt_out.
#
Indeed, resetting the iskeyword option or installing the latest
syntax/tex.vim solved the problem. It might be good to push
the tex syntax file to the hg repository.
Thank you all,
Pavol
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text y
Hello,
I found a strange behavior in vim 7.3.146 when adding insert-mode
abbreviations with the tex syntax loaded. Given a test.tex file that
contains just one line
\begin{article}
The following command gives error "E474: Invalid argument":
vim -N -i NONE -u NONE -c "syntax on" -c "iabbrev
Hello,
The latest version of vim73b does not build with aap, because
blowfish.c and sha256.c are not included in the sources list in
main.aap. The attached patch should fix that. Perhaps main.aap
could be improved to parse the Filelist file, so there is just one
list of sources to maintain.
Che
No problems with question marks with netrw v135c.
Thank you for fixing this.
Pavol
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~
On Nov 8, 11:25 pm, Tony Mechelynck <[EMAIL PROTECTED]>
wrote:
...
> & in a query string should be passed as & or as %26 though many web
> pages don't use this, even though the W3C HTML guidelines require it.
>
> I suppose that ifnetrwhas problems with the question mark (maybe for
> internal reaso
Hello,
I just found that URLs that contain question mark cannot be loaded
with the latest netrw v134.
For example
:view http://www.vim.org/scripts/script_search_results.php?keywords=netrw
shows an empty buffer, because the URL that is passed to wget contains '\?'.
The problem seems to go away
23 matches
Mail list logo
