Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #35728 > unrolled thread

Re: Gvim, bug or feature?

Started byPengfei Hao <intijk@gmail.com>
First post2012-12-28 19:59 -0600
Last post2012-12-28 19:59 -0600
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Gvim, bug or feature? Pengfei Hao <intijk@gmail.com> - 2012-12-28 19:59 -0600

#35728 — Re: Gvim, bug or feature?

FromPengfei Hao <intijk@gmail.com>
Date2012-12-28 19:59 -0600
SubjectRe: Gvim, bug or feature?
Message-ID<mailman.1416.1356746384.29569.python-list@python.org>

[Multipart message — attachments visible in raw view] — view raw

Sorry, this seems a temporary bug of gvim, and they already fix it, post
closed.


2012/12/28 Pengfei Hao <intijk@gmail.com>

> When you are using gvim, the command line vim can not open a current
> directory os.py, do you think this is a bug or a feature? I like python and
> I like gvim, but the vim of gvim is now a python program , it will import
> module like  os.py first in current directory, so any file the same name as
> os.py will cause the vim startup failure. I find this today and I was
> shocked about the truth, a editor will be affected by the filename you want
> to edit!!!!!
>
> What do you think about this?
>

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web