On Jun 5, 2013 7:50 PM, "Ken Takata" wrote:
>
> Hi,
>
> 2013/06/05 Web 13:07:20 UTC+9 ZyX wrote:
> > vim._*chdir is holding original implementations: I do not want to
collect references at exit in python*_end() functions if I can just record
them in the vim module and be sure that they both won’t
On Jun 5, 2013 7:50 PM, "Ken Takata" wrote:
>
> Hi,
>
> 2013/06/05 Web 13:07:20 UTC+9 ZyX wrote:
> > vim._*chdir is holding original implementations: I do not want to
collect references at exit in python*_end() functions if I can just record
them in the vim module and be sure that they both won’t
On Jun 5, 2013 1:22 AM, "Marc Weber" wrote:
>
> You've been missing documenting default settings ..
>
> > Does not run ``&pythoninstallprg`` if bang was specified.
> May be counter intuitive. ! usually means "force it".
> I understand the idea "make things work by default".
> But i think it sh
On Jun 4, 2013 5:34 PM, "Christian Wellenbrock" <
christian.wellenbr...@gmail.com> wrote:
>
> On Tuesday, June 4, 2013 3:12:20 PM UTC+2, Kazunobu Kuriyama wrote:
> > Hi,
> >
> >
> >
> > I'm the maintainer of the Objective-C syntax file, syntax/objc.vim. As
the new features that have been added to
On Jun 4, 2013 3:26 AM, "Marc Weber" wrote:
>
> Excerpts from ZyX ZyX's message of Mon Jun 03 23:11:58 +0200 2013:
> > The discussion has now gone into the direction when I will be against
> > automatic sourcing of anything related to python.
> Wow.. peace. I don't want to be offensive. And its ha
On Jun 4, 2013 12:54 AM, "Marc Weber" wrote:
>
> I still vote for the module solution, because you can import it into
global
> namespace for debugging and testing.
>
> While writing plugins being able to
>
> :py import my-module
> :py my-module.do_thing(foo)
>
> is important to me.
>
> Using
On Jun 4, 2013 12:38 AM, "Marc Weber" wrote:
>
> Excerpts from ZyX ZyX's message of Mon Jun 03 13:28:10 +0200 2013:
> > What for?
> Stupid simple plugins which want to have minimal state such as
> "incermental counter" ?
?! How my proposal is against this? When you create a python function that
u
On Jun 3, 2013 7:42 PM, "Bram Moolenaar" wrote:
>
>
> Ben Fritz wrote:
>
> > On Monday, June 3, 2013 4:16:12 AM UTC-5, Bram Moolenaar wrote:
> > > ZyX wrote:
> > >
> > > > On Jun 3, 2013 1:09 AM, "Bram Moolenaar" wrote:
> > >
> > > > > Glts wrote:
> > >
> > > > > > On Sunday, June 2, 2013 9:30:20
On Jun 3, 2013 6:42 PM, "LCD 47" wrote:
>
> On 3 June 2013, Josh Hoff wrote:
> > On Jun 3, 2013, at 6:25 AM, LCD 47 wrote:
> [...]
> > > About GitHub now. GitHub project started in ~2008. Back then, some
> > > of us have been writing code for ~20 years, and we were generally
> > > doing fine i
On Jun 3, 2013 6:40 PM, "Bram Moolenaar" wrote:
>
>
> Charles Peacech wrote:
>
> > On Mon, Jun 3, 2013 at 1:06 AM, Bram Moolenaar
wrote:
> > >
> > > This item has been in the todo list for a very long time:
> > >
> > > Python: ":py raw_input('prompt')" doesn't work. (Manu Hack)
> > >
> >
On Jun 3, 2013 3:14 PM, "ashwin sathya" wrote:
>
> Hi,
> I run windows 8 64 bit, with Vim 32 bit latest from
http://tuxproject.de/projects/vim/ patched till 1105.
> With python 32 bit 2.7.5
>
> When i do a ":py import os" i get the following error message
"AttributeError: 'module' object has no at
On Jun 3, 2013 9:55 AM, "Marc Weber" wrote:
>
> Excerpts from ZyX's message of Sun Jun 02 12:58:10 +0200 2013:
> > execfile(filename, {}, {})
> Would you pass a permanent individual global state dictionary like this?
>
> if not "foo.py" in module_globals:
> module_globals["foo.py"] = {}
On Jun 3, 2013 6:16 AM, "Charles" wrote:
>
> On Mon, Jun 3, 2013 at 8:57 AM, Charles wrote:
> > On Mon, Jun 3, 2013 at 12:54 AM, Bram Moolenaar
wrote:
> >>
> >> I have included patch 7.3.1099, which handles os.chdir() and
> >> os.fchdir().
> >
> > os.fchdir is not available for python in windows
On Jun 3, 2013 1:09 AM, "Bram Moolenaar" wrote:
>
>
> Glts wrote:
>
> > On Sunday, June 2, 2013 9:30:20 PM UTC+2, Bram Moolenaar wrote:
> > > Christian Brabandt wrote:
> > >
> > > > Note, that latest patch I sent, does not require an extra option, is
> > > > rather small, makes the code much more
On Jun 3, 2013 1:09 AM, "Bram Moolenaar" wrote:
>
>
> ZyX wrote:
>
> > The last proposal was using '_vim_runtimepath_' special item in sys.path
> > alongside with import hooks. I can hardly call this a consensus because
> > last my argument about why vim should use this magic was not replied to
by
On Jun 2, 2013 10:06 PM, "Bram Moolenaar" wrote:
>
>
> This item has been in the todo list for a very long time:
>
> Python: ":py raw_input('prompt')" doesn't work. (Manu Hack)
>
> It's nasty, I have to kill -9 Vim to get out.
>
> It appears Python tries reading from a file descriptor in a
On Jun 2, 2013 9:57 PM, "Bram Moolenaar" wrote:
>
>
> Almost three years ago Mark Mahnic sent a patch to access the screen
> from inside Python. It was sent on 2010 July 19.
>
> These are the docs:
>
>
> 6. Screen object*python-screen*
>
> The screen object
On Jun 2, 2013 9:54 PM, "Bram Moolenaar" wrote:
>
>
> I have included patch 7.3.1099, which handles os.chdir() and
> os.fchdir().
>
> There was an earlier patch from Xavier de Gaye on May 17.
> Is there anything in that patch not covered by 7.3.1099?
>
> At least here was discussion about adding s
On Jun 2, 2013 10:45 AM, "Yegappan Lakshmanan" wrote:
>
> Hi,
>
> On Sat, Jun 1, 2013 at 10:58 PM, tooth pik wrote:
> > On Sat, Jun 01, 2013 at 10:49:37PM -0700, Ben Fritz wrote:
> >> On Sunday, June 2, 2013 12:24:11 AM UTC-5, MarcWeber wrote:
> >> > ZyX told me that I should try to write the way
On Jun 2, 2013 10:06 AM, "Marc Weber" wrote:
>
> The simple test case (bottom) is interruptable, while catching sigint
using a
> signal handler
>
> This patch tries to catch all common cases by replacing
> got_int = TRUE with my own function. I didn't catch all, only those who
seemed
> related to
On Jun 1, 2013 7:43 AM, "Marc Weber" wrote:
>
> 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-w
Sorry, missed this part of the discussion when writing my previous reply.
On May 31, 2013 7:25 AM, "Shougo" wrote:
> > From your description, I think I'd rather see this as an additional
> value or values supported in 'completeopt'. Currently the only control over
> what gets inserted is "longest
On May 29, 2013 2:47 PM, "Ingo Karkat" wrote:
>
> On 29-May-2013 09:20 +0200, Gary Johnson wrote:
>
> > On 2013-05-29, Marc Weber wrote:
> >
> >> I wrote something similar initially, because
> >>
> >> if exists('g:is_loaded')
> >> finish
> >> endif
> >> let g:is_loaded = 1
> >>
> >> is j
On May 29, 2013 11:57 AM, "Marc Weber" wrote:
>
> I'd like to try providing patches for the following features:
>
> - nox patch
> https://code.google.com/r/yukihironakadaira-vim-cmdsrv-nox/
> What is it? Allows client-server communication via sockets.
>
> pro: only you can access your vim in
On May 27, 2013 11:54 PM, "ZyX" wrote:
>
> > The patch is not correct:
> >
> > 'bytes' is declared in OptionsAssItem(), in the block (line 1689):
> >
> > 'else if (PyUnicode_Check(valObject))'
> >
> > This declaration shadows the declaration of 'bytes' made by
DICTKEY_DECL at
> > the s
void *)&TheWindowList);
-Py_INCREF((PyObject *)(void *)&TheTabPageList);
-PyModule_AddObject(mod, "tabpages", (PyObject *)(void *)&TheTabPageList);
-
-PyModule_AddObject(mod, "vars", DictionaryNew(&globvardict));
-PyModule_AddObject(mod, "vvars", D
13 +0400
+++ b/src/if_python3.c Sat May 18 17:58:15 2013 +0400
@@ -666,7 +666,7 @@
return PyType_GenericAlloc(type,nitems);
}
-static PyObject *BufferDir(PyObject *, PyObject *);
+static PyObject *BufferDir(PyObject *);
static PyObject *OutputGetattro(PyObject *, PyObject *);
static int OutputSetattro(PyObject *, PyObject *, PyObject *);
static Py
ettv->v_type)
{
case VAR_DICT: ++rettv->vval.v_dict->dv_refcount; break;
diff -r e2f76dc2df31 -r a682902e547d src/testdir/test87.ok
--- a/src/testdir/test87.ok Fri May 17 21:20:17 2013 +0200
+++ b/src/testdir/test87.ok Sat May 18 01:47:01 2013 +0400
@@ -59,10 +59,10 @@
Subj. Patches are replies to this message.
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to t
On May 19, 2013 1:00 AM, "meh." wrote:
>
> I'm writing a fairly complex statusline and using %!Func() as
> statusline, everything was good until I started using my new shiny
> statusline and I realized the context it's run in is the current
> window and not the context %{} would use, so the one th
2012/9/1 Luis Carvalho :
>> Wondering whether you have repository with all these changes.
>
> No, since the patches are few and far between.
Pulling patches from the repository and saving them there is
convenient. When I was adding third argument to sort() patch was also
not big but I still cloned
Vim bindevalled scope dictionary has the same problem I reported for
extend(). This patch fixes it, though with it case “masks existing
function” is indistinguishable with “funcref variable must start with
a capital”. I can make them distinguishable with few more lines if
needed (due to the existen
It is a patch to a problem I reported earlier:
call extend(g:, {'input': function('tr')})
can be used to override built-in input() function (and to also add
invalid keys to g: dictionary).
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
33 matches
Mail list logo
