Hi, All
I run into one issue when running with :pyfile command.
here is my test.py file:
import os
print os.path.dirname(os.path.abspath(__file__)
I saved it in c:\test.py
Then I run :pyf c:\test.py. I suppose it should return c:\
However, it will say:
Traceback (most recent call last):
在 2014年1月16日星期四UTC+8下午5时45分24秒，驼峰写道：
Hi, All
I run into one issue when running with :pyfile command.
here is my test.py file:
import os
print os.path.dirname(os.path.abspath(__file__))
I saved it in c:\test.py
Then I run :pyf c:\test.py. I suppose it should return c:\
However,
在 2014年1月16日星期四UTC+8下午5时45分24秒，驼峰写道：
Hi, All
I run into one issue when running with :pyfile command.
here is my test.py file:
import os
print os.path.dirname(os.path.abspath(__file__)
I saved it in c:\test.py
Then I run :pyf c:\test.py. I suppose it should return c:\
However,
On Thu, Jan 16, 2014 at 5:58 AM, Bram Moolenaar b...@moolenaar.net wrote:
Yukihiro Nakadaira wrote:
On Tue, Dec 31, 2013 at 6:54 PM, Bram Moolenaar b...@moolenaar.net
wrote:
Yukihiro Nakadaira wrote:
After patch 7.4.045, substitute('xxx', 'x\zs', 'y', 'g') returns
xyxxy.
Similar previous post:
https://groups.google.com/forum/#!searchin/vim_dev/internals/vim_dev/NDfhZs-364M/R1O4gD-uxksJ
This thread was made earlier, but never went everywhere. Sample response:
If you don't just want to spend your time on something you should
also consider talking about the
On Thu, Jan 16, 2014 at 01:45:24AM -0800, 驼峰 wrote:
Hi, All
[...]
I run into one issue when running with :pyfile command.
Traceback (most recent call last):
File string, line 1, in module
File c:/test.py, line 3, in module
print os.path.dirname(os.path.abspath(__file__))
Excerpts from Tony's message of Thu Jan 16 07:07:35 +0100 2014:
Can someone open a gist / wiki / create an INTERNALS.txt or doc file
for developers to have a broad overview of how vim works internally?
I've started this wiki to document patches / efforts / idea to improve
the situation. I
On Thu, 16 Jan 2014 16:14:31 +0100
Marc Weber marco-owe...@gmx.de wrote:
I've started this wiki to document patches / efforts / idea to improve
the situation. I started by documenting why vim sucks:
http://vim-wiki.mawercer.de/wiki/index.html
Looks like the wiki is using kind of SCM as a
On Thursday, January 16, 2014 9:14:31 AM UTC-6, MarcWeber wrote:
One of the main issues is:
- documenting source does not add value
I'd argue that documenting the source DOES add value. It makes the code easier
to maintain and develop.
It's just not a fun job. Documenting why the code
On 16/01/14 07:07, Tony wrote:
Similar previous post:
https://groups.google.com/forum/#!searchin/vim_dev/internals/vim_dev/NDfhZs-364M/R1O4gD-uxksJ
This thread was made earlier, but never went everywhere. Sample response:
If you don't just want to spend your time on something you should
also
(Sorry, have only mail currently, so can't reply on the web)
On Thu, January 16, 2014 01:48, v...@googlecode.com wrote:
Comment #3 on issue 193 by dominiqu...@gmail.com: Insert in Visual mode
gives wrong result
http://code.google.com/p/vim/issues/detail?id=193
Christian wrote:
This is to
On 16/01/14 17:01, Ben Fritz wrote:
On Thursday, January 16, 2014 9:14:31 AM UTC-6, MarcWeber wrote:
[...]
I even think about 'what would happen splitting runtime from Vim, and
upload it to bitbucket / github' ?
I like this idea and it's been discussed in the past.
If I recall, Bram was
@Sergey Avseyev
I've granted github access to you (github.com/MarcWeber/vim-git-wiki).
Syncing with the web frontend is only done once every 10min.
See contributing page:
http://vim-wiki.mawercer.de/wiki//this-wiki/contributing.html
C may be the wrong tool, if you wanted to start a brand-new
On 15/01/14 11:10, Aidan Marlin wrote:
Vim devs,
I have discovered a bug which affects at least 7.4.135 and (likely) 7.3.547.
Example file is available at
https://mega.co.nz/#!ndVjXZTY!aMX_9ll-0ce861tQwNZBaFveb_kONCJxvAT2GZOvzlc
(1.2MB in size) which will crash vim when attempting the
On 16/01/14 17:56, Marc Weber wrote:
@Sergey Avseyev
I've granted github access to you (github.com/MarcWeber/vim-git-wiki).
Syncing with the web frontend is only done once every 10min.
See contributing page:
http://vim-wiki.mawercer.de/wiki//this-wiki/contributing.html
C may be the wrong
Lately I've been hacking vim a lot, and the YouCompleteMe plugin has
been very useful(semantic completion, jumping and syntax errors).
Here's the configuration for other YouCompleteMe users who also happen
to be hacking vim: https://gist.github.com/tarruda/8459816
Hope it helps
--
--
You
Hi,
On Thursday, January 16, 2014 10:05:58 AM UTC+4, Suresh Govindachar wrote:
When running vim inside ConEmu, although lazyredraw is OFF (nolazydraw),
I still find the need to hit Ctrl-L or execute :redraw! (with
shriek) to clear up the screen that has been messed-up by some bug with
Christian Brabandt wrote:
Bram,
consider this:
cat /tmp/dict
catharsis
catechism
catastrophe
vim -u NONE -N -c 'set cpt=k,. dictionary=/tmp/dict'
$put ='canz'
$put ='canq'
0put ='ca'
Got to the end of the first line, and press C-N
Note, how Vim hangs. This happens, because in
winnr() returns the index of the window 1-based while v:beval_winnr
(:help 'bexpr') is 0-based. I believe the latter should be fixed. The
attached patch adds increments the value of v:beval_winnr by 1.
--
Lech Lorens
--
--
You received this message from the vim_dev maillist.
Do not
On 1/16/2014 10:24 AM, Maximus ConEmu wrote:
On Thursday, January 16, 2014 10:05:58 AM UTC+4, Suresh Govindachar
wrote:
When running vim inside ConEmu, although lazyredraw is OFF
(nolazydraw),
I still find the need to hit Ctrl-L or execute :redraw!
(with shriek) to clear up the screen
20 matches
Mail list logo
