Loading ...
Sorry, an error occurred while loading the content.
Advanced Search
Author
Subject
Message
Special notice only

199 results from messages in vimdev

Advanced Search
  • ZyX: Usually you're rigth with what you're saying. So please help find the best forum to place your "style guides" about "how to write unobstrusive perfect python based vim plugins". You all know that I've introduced this wiki: http://vim-wiki.mawercer.de/ I think such (and making such official) would be the best way to tell users how to write plugins - it should be open to...
    Marc Weber May 31, 2013
  • Excerpts from Bram Moolenaar's message of Fri May 31 20:49:45 +0200 2013: > Then :pyx would really work. Is that possible without getting errors > for some code that works only in one versin? Example taken from UltiSnips: ./py-code/UltiSnips/compatibility.py ./py-code/UltiSnips/compatibility_py2.py ./py-code/UltiSnips/compatibility_py3.py Everything else is shared. Of course if...
    Marc Weber May 31, 2013
  • Not having read the implemeentation details: using expressions you can have "closures", using functions this is harder and requires much more typing. Whether this is important for sorting, I don't know. let sort_opts = {'ignore_spaces': 1} sort(foo, 'sort_stuff(v:1, v:2, sort_opts)') try the same with function references. There are ways to make it work, but they are more...
    Marc Weber May 31, 2013
  • Fetching Sponsored Content...
  • Excerpts from James McCoy's message of Fri May 31 18:39:13 +0200 2013: > This is only true if you don't support older versions of Python 2.x. Such a > suggestion was already discussed in this thread: > http://thread.gmane.org/gmane.editors.vim.devel/38261 I didn't see a clear winner. We have py and py3, so people can choose whatever they like. Things like let dir = 'foo pyx 'import...
    Marc Weber May 31, 2013
  • There are two important problems with python support: 1) you still have to use .viml in order to load python 2) when using python its you having to remember which python to use despite most codes may work with python and python3 interpreter. Using the same (only one) interpreter is very important, because many vims will only support one, and loading both is slower So this patch...
    Marc Weber May 31, 2013
  • follow up: I've tried getting started with cmake and vim. I ran into two problems: P1 if_config.py and if_config3.py require different C flags to be compiled with. P2 configure has many "magic" I don't want to rewrite (not at all using cmake) Solutions to P1) 1) set_property (sucks, because I don't know how to pass many flags as list of arguments, which I cannot imagine being...
    Marc Weber May 31, 2013
  • Just thinking about "backward compatibility" - does it make sense to not be backward compatible forever? Eg what about be-backward-compatible-to 7.3 patchlevel 997 Thene there would be a chance to set saner defaults in the future without breaking vim for old users. But I agree that this could be implemented as plugin at the beginning. Marc Weber -- -- You received this message from...
    Marc Weber May 31, 2013
  • Excerpts from Shougo's message of Thu May 30 02:30:12 +0200 2013: > How do you think about this feature? Can you try providing use cases when which option is likely to be preferred by users? Eg when do you want option "no selecetd candidate" ? So can you talk about the use case which made you implement this patch? Marc Weber -- -- You received this message from the "vim_dev...
    Marc Weber May 29, 2013
  • We could also make vim inject those idomatic lines automatically. But I don't think its important enough to worry about - unless somebody prooves me wrong. We don't have to forget: yzis failed. Whatever we do, we have to make sure community follows. For those who know it: yzis is a Vim clone written in C++ trying to get things right. However they ditched VimL, using lua only. Marc...
    Marc Weber May 29, 2013
  • > ZyX you're right. It might break some plugins who have put .py files into plugin/ The idea behind "plugin" was is that people know that things in plugin/ get sourced. Its like "keeping things simple". I've no idea how many plugins would break. I'd also agree on a different directory. That's an implementation detail from my point of view. Its simpler for the user, because he/she...
    Marc Weber May 29, 2013