Hi,
My school provide a server from which we can run code. I pulled the newest
version of git from GitHub since their version was outdated and I wanted
one with python3 support so I could use YCM.
After during this I have had issues where I got the following error:
BadAccess (attempt to acces
On Thursday, 24 May 2018 12:33:49 UTC+2, Tony Mechelynck wrote:
> On Thu, May 24, 2018 at 11:38 AM, Andreas wrote:
> > What about just testing sizeof(void *)==8 ?
> > Regards
> > anst
>
> That won't work, because we want a solution for vimscript, not for C:
On Wednesday, 23 May 2018 15:33:37 UTC+2, Tony Mechelynck wrote:
> On Wed, May 23, 2018 at 3:14 PM, Ken Takata wrote:
> > Hi,
> >
> > 2018/5/23 Wed 21:29:43 UTC+9 Ni Va wrote:
> >> I build both 32 and 64 bits version of gvim but always 1 is returned when
> >> from 32bits or 64bits I do :
> >>
>
ed back after being able to exchange xvi for vim on my
PC.
Thanks a lot for 25 years of a great effort.
Andreas
--
--
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.vi
On Friday, 1 April 2016 15:33:03 UTC+2, Ken Takata wrote:
> Hi Andreas,
>
> 2016/4/1 Fri 21:51:38 UTC+9 Andreas wrote:
> > On Friday, 1 April 2016 10:36:17 UTC+2, Ken Takata wrote:
> > > Hi Andreas,
> > >
> > > 2016/4/1 Fri 17:11:12 UTC+9 Andreas wro
On Friday, 1 April 2016 10:36:17 UTC+2, Ken Takata wrote:
> Hi Andreas,
>
> 2016/4/1 Fri 17:11:12 UTC+9 Andreas wrote:
> > I remember now why. When I try to do the patch using TortoiseGit I get the
> > message:
> > git.exe am --3way --ignore-space-change --keep-cr
On Friday, 1 April 2016 10:01:08 UTC+2, Andreas wrote:
> On Thursday, 31 March 2016 11:08:42 UTC+2, Ken Takata wrote:
> > Hi Andreas,
> >
> > Thank you for trying the patches!
> >
> > 2016/3/30 Wed 21:22:05 UTC+9 Andreas wrote:
> > > On Tuesday, 29 Ma
On Thursday, 31 March 2016 11:08:42 UTC+2, Ken Takata wrote:
> Hi Andreas,
>
> Thank you for trying the patches!
>
> 2016/3/30 Wed 21:22:05 UTC+9 Andreas wrote:
> > On Tuesday, 29 March 2016 03:30:40 UTC+2, Ken Takata wrote:
> > > Hi Bram,
> > >
en the
> > > num64
> > > patch is included.)
> >
> > I hope to get back to including patches soon. Just a bit more cleanup
> > for new features to do.
>
> Regards,
> Ken Takata
I tried these pathces on version 1685 on windows 10 using Visual Studio
On Monday, 22 February 2016 12:21:12 UTC+1, Ken Takata wrote:
> Hi Andreas,
>
> 2016/2/22 Mon 19:44:25 UTC+9 Ken Takata wrote:
> > Thank you for testing my patches.
> > Did you apply 0002_fix-off_T-display.patch? Without this, character count
> > will not be shown pr
On Sunday, 21 February 2016 16:20:48 UTC+1, Andreas wrote:
> On Friday, 19 February 2016 13:00:39 UTC+1, Ken Takata wrote:
> > Hi Andreas,
> >
> > 2016/2/19 Fri 20:47:20 UTC+9 anst...@gmail.com wrote:
> > > I have a text file (dc.epd) that is nearly 8GB. Whe
*, const char *, PyObject *);
static PyObject* (*py3_PyObject_CallFunctionObjArgs)(PyObject *, ...);
static PyObject* (*py3__PyObject_CallFunction_SizeT)(PyObject *, char *, ...);
static PyObject* (*py3_PyObject_Call)(PyObject *, PyObject *, PyObject *);
--
Andreas Schwab, SUSE Labs, sch...@suse.de
Added missing abiflags to epfx include path and removed an unused python
variable from the configure.in
see https://github.com/codedreality/vim/commits/fix-python3x-support
--- a/src/configure.in Sun Jun 12 22:13:41 2011 +0200
+++ b/src/configure.in Mon Jun 13 00:13:10 2011 +0200
@@ -1063,7 +106
They changed the order as of python version 3.2.
Changing the order of the two calls even works with 3.1.x (short test with
mac osx)
I attached a changeset with some minor changes to configure.in and
if_python.c to get a more general python 3.x support in vim (see PEP 3149)
--
You received th
troduce (yet another) key binding for your new
feature, for example CTRL-W_CTRL-= or CTRL-W_CTRL-+.
Cheers,
--
Andreas.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
one. Right now the buffer's name is appended inside parentheses to the
> command name.
Great.
> Thank you for a scrupulous review!
:-)
Thanks for the patch.
--
Andreas.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
name = (char_u *)buf_spname(curbuf))
>
> For maintainability reasons, it is better to assign the bname variable
> outside of this
> function call.
I'm curious: what's the rationale to have the assignment outside the
function call/if-condition?
--
Andreas.
--~--~--
title just
say '/tmp/errors' or ':cfile /tmp/errors'. This would give a visual hint
that the error list was loaded with a vim command and not by a program called
'cfile'. Ditto for 'lfile', 'cgetfile', 'lgetfile'.
* Loading the error list f
called.
It looks like this bug was introduced with 7.2.055.
The attached patch against 7.2.127 seems to fix this.
--
Andreas.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist
It looks like this bug was introduced with 7.2.055.
The attached patch against 7.2.127 seems to fix this.
I CC vim-dev to include the patch.
--
Andreas.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist
binary representation, things will probably go havoc.
Without having looked into it, I guess the undo parts contain text that has been
undone plus some extra information such as location and time, all of which could
be represented in a text format.
Cheers,
--
Andreas.
--~--~-~--~~---
Yukihiro Nakadaira wrote:
> This command causes crash.
>
> :call substitute('', '\(.\@<=\)*', '\=submatch(1)', '')
>
Confirmed for vim 7.2.108
(called as vim -u NONE)
--
Andreas.
--~--~-~--~~~---~--~
apply your local changes.
I could not think of a better way to handle this situation and it's so simple,
just 'git pull --rebase' instead of 'git pull', that's all.
--
Andreas.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
c. (I've tested on Mac OS X, and sc confirmed the
> problem on Linux).
I can't confirm this behavior for vim 7.2.095 on Linux 2.6.24 (in either gui or
console mode). :grep interrupts as soon as I press Ctrl-C.
--
Andreas.
--~--~-~--~~~---~--~~
You received t
Tony Mechelynck wrote:
> On 04/02/09 11:08, Andreas Bernauer wrote:
>> Hi,
>>
>> when I apply a reversed patch on an open file with 'diffpatch', gvim opens a
>> window with an empty buffer instead of the patched file. 'godlygeek' on IRC
>&
Andreas Bernauer wrote:
> when I apply a reversed patch on an open file with 'diffpatch', gvim opens a
> window with an empty buffer instead of the patched file. 'godlygeek' on IRC
> suggested reporting this bug on this mailing list.
[...]
>
> vim-7.2 is the
rom the homepage
(ftp://ftp.vim.org/pub/vim/unix/vim-7.2.tar.bz2)
I added the '-u NONE -U NONE -i NONE --noplugin' flags only to keep
bugreport.txt small; the bug still appears when these flags are missing.
Cheers,
Andreas.
--~--~-~--~~~---~--~~
Y
27 matches
Mail list logo
