On 7/23/13, Bram Moolenaar wrote:
>
> Vlad Irnov wrote:
>
>> I confirm that this issue has been fixed by Patch 7.4a.027 and
>> subseqent, but only partially.
>> The same errors can occur when Python deletes lines in another buffer.
>> The following tests show how to reproduce (also attached).
>> T
On Friday, July 19, 2013 9:59:38 AM UTC-4, Bram Moolenaar wrote:
> Does the pattern actually match in the wrong place?
Of course it does, because the pattern is wrong. See my other reply just now.
> Translations will change over time, so the syntax file gets outdated.
> It's only worth the effort
On Thursday, July 25, 2013 5:15:05 PM UTC-4, Dmitry Vasiliev wrote:
> I think accuracy is not the right reason for changing the code which have no
> complaints for 7 years. Especially when this change will make maintenance
> harder. So if accuracy is the only reason it's better to not touch this
On Tuesday, July 23, 2013 8:16:39 AM UTC+2, studog wrote:
> On Friday, July 19, 2013 6:14:18 PM UTC-4, Dmitry Vasiliev wrote:
> > On 07/18/2013 08:15 PM, studog wrote:
> > > I'd like to update the regex so it's accurate,
>
> > Why exactly do you want to change the regexp?
>
> It's not accurate.
Comment #6 on issue 157 by octopusg...@gmail.com: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
Once netwr.vim is replaced with the non-debug statements, the behavior
returns. Re-read file comes back
Comment #5 on issue 157 by octopusg...@gmail.com: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
Chip:
I got output and with DEcho on, the file is re-read back in as Unix.
-
Decho Tab /usr/sha
Comment #4 on issue 157 by octopusg...@gmail.com: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
I've got Decho installed, but am confused as to what script to write for
netrw. This is reproduceable b
On Jul 25, 2013 9:23 PM, "Sergey Khorev" wrote:
>
>
>> Make sure you have a recent version of the source and clean up before
you build.
>>
>
> Thanks, there really is no need to waste time teaching me how to build
Vim.
> Anyway I found the cause: it is Python that is broken, not Vim. If
Python3 is
On Thu, Jul 25, 2013 at 4:03 PM, Bram Moolenaar wrote:
> Markus Mottl wrote:
>> Btw., the compiler-settings don't load unless I enter ":compiler
>> ocaml". This may be annoying for beginners who might expect things to
>> work without having to change their Vim-configuration. What would be
>> the
Markus Mottl wrote:
> Thanks, Hirotaka, this was indeed a weird issue that seems fixed now.
>
> Bram, please disregard the OCaml-ftplugin file I've sent earlier. The
> one I've attached now should have all patches (including the removal
> of the efm-setting).
Thanks, I'll include this soon.
>
Marc Weber wrote:
> Something like this: -> NEW LINE
>
> [...]
>
> ==
> 6. Profiling*profile*
> *profiling*
>
> Profiling means that Vim measures the time that i
Hiroshi Shirosaki wrote:
> On Monday, July 15, 2013 7:47:42 AM UTC+9, Hiroshi Shirosaki wrote:
> > I've updated the patch since the following issue is reported.
> >
> > If lua executable is not exist in the PATH and configure cannot find
> > liblua.so, strange library name `liblua.so.` (end wit
> Anyway I found the cause: it is Python that is broken, not Vim. If Python3 is
> installed properly (as opposed to python3X.dll simply copied over),
> everything works.
You'd need a Python standard library along with your pythonXY.dll, i.e. create
a pythonXY.zip with contents of your Python's
Comment #3 on issue 157 by drc...@campbellfamily.biz: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
Since I didn't say previously, I used gvim 7.4a.35 to perform the test on a
Scientific Linux system
Comment #2 on issue 157 by octopusg...@gmail.com: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
First, thanks for your prompt reply.
In /home/cnorton, I moved the .vim directory and .vimrc to other re
> Make sure you have a recent version of the source and clean up before you
> build.
>
>
Thanks, there really is no need to waste time teaching me how to build Vim.
Anyway I found the cause: it is Python that is broken, not Vim. If Python3
is installed properly (as opposed to python3X.dll simply co
On Thu, Jul 25, 2013 at 12:53 AM, Bram Moolenaar wrote:
>
> Yukihiro Nakadaira wrote:
>
> > On Mon, Jul 8, 2013 at 9:51 AM, wrote:
> >
> > > Bram Moolenaar wrote:
> > >
> > > > Announcing: Vim (Vi IMproved) version 7.4a BETA
> > > >
> > > > This is the first BETA release of Vim 7.4.
> > > >
> >
On Thursday, July 25, 2013 7:09:38 AM UTC+2, Sergey Khorev wrote:
> Hi,
>
>
> Apparently it's not only I who can't get Python3 support working in Windows
> (at least Win7 x64), neither dynamic nor static one, and neither x86 nor
> amd64. Here are options I tried:
>
>
>
>
>
> All of these b
Updates:
Status: Started
Comment #1 on issue 157 by drc...@campbellfamily.biz: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
Using the attached file (which I called simple6.vimrc):
and runnin
19 matches
Mail list logo
