I am switching back to console Vim because it solved the No.1 problem of Gvim: it doesn't allow another thread to start a X based graphical UI, as it will clash with the one of its own. Also it now supports true color and is much faster in responding user ops.
Unfortunately I bumped into the old Alt key mapping problem. After examining all possibilities I think setting the key codes in Vim is the most practical:
function! s:ConsoleMapAltKey()
let char= 'a'
while char <= 'z'
exec "set <A-".char.">=\<Esc>".char
let char= nr2char(1+char2nr(char))
endwhile
set ttimeout
set ttimeoutlen=30
endfunction
This supposedly should tell Vim that the <Alt-...> key will generate <Esc> leading key sequences, and enable Vim to tell them apart from user input of <Esc> followed by other keys by the different time lapse.
This works perfectly under Normal and Command mode, no ambiguity when <Esc> was pressed, but not in Insert mode, where the <Alt-...> key combination will always be accepted as one <Esc> followed by another key from the user. I tried explicitly doing key mapping:
imap <A-s> xxx
and it didn't work. Can anyone enlighten me on this, thanks.
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, April 5, 2017
Re: Trouble building Huge Vim8 on CentOS 7
On Wed, Apr 5, 2017 at 4:18 AM, Mun <mjelists@gmail.com> wrote:
> Hi,
>
> On Tue, Mar 21, 2017 at 07:13 PM PDT, L A Walsh wrote:
> LAW> Mun wrote:
> LAW> >I tried to find a yum package that provides SMlib.h, but my system said:
> LAW> >"No matches found". Sigh.
> LAW> ----
> LAW> I found I had to create my own reverse index of packages in my
> LAW> distro to find files.
> LAW>
> LAW> basically a:
> LAW> "rpm -qpl path-to-pkg/pkg.rpm > path-to-rpmlist/pkg.rpm.lst"
> LAW> for each rpm in my distro (so each rpm file list ends up in a
> LAW> different file).
> LAW>
> LAW> It's the only way to find a file that I've found. It's 550Meg
> LAW> of just rpm-file lists. That said, how to find files in your
> LAW> distro, isn't really a 'vim question', but a question for
> LAW> people who know how to find things in your distro.
> LAW>
> LAW>
> LAW> Dunno if it is helpful, but in suse13.2, it's in libSM-devel.
>
> Thanks for the reply. I was able to finally get vim to compile, but it
> was a little painful to discover all of the dependencies.
>
> If there exists documentation which specifies the dependencies for a
> "huge gui" implementation on CentOS7, I missed it.
>
> Kind regards,
>
> --
> Mun
The output of rpm queries is often inwieldy, so it's useful to grep
them for what you're looking for. For instance, to see which of the
foobar packages are installed,
rpm -qa | grep ^foobar
(notice the initial ^ which has the same meaning as in a Vim pattern)
is much nicer than looking at the full rpm -qa output.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hi,
>
> On Tue, Mar 21, 2017 at 07:13 PM PDT, L A Walsh wrote:
> LAW> Mun wrote:
> LAW> >I tried to find a yum package that provides SMlib.h, but my system said:
> LAW> >"No matches found". Sigh.
> LAW> ----
> LAW> I found I had to create my own reverse index of packages in my
> LAW> distro to find files.
> LAW>
> LAW> basically a:
> LAW> "rpm -qpl path-to-pkg/pkg.rpm > path-to-rpmlist/pkg.rpm.lst"
> LAW> for each rpm in my distro (so each rpm file list ends up in a
> LAW> different file).
> LAW>
> LAW> It's the only way to find a file that I've found. It's 550Meg
> LAW> of just rpm-file lists. That said, how to find files in your
> LAW> distro, isn't really a 'vim question', but a question for
> LAW> people who know how to find things in your distro.
> LAW>
> LAW>
> LAW> Dunno if it is helpful, but in suse13.2, it's in libSM-devel.
>
> Thanks for the reply. I was able to finally get vim to compile, but it
> was a little painful to discover all of the dependencies.
>
> If there exists documentation which specifies the dependencies for a
> "huge gui" implementation on CentOS7, I missed it.
>
> Kind regards,
>
> --
> Mun
The output of rpm queries is often inwieldy, so it's useful to grep
them for what you're looking for. For instance, to see which of the
foobar packages are installed,
rpm -qa | grep ^foobar
(notice the initial ^ which has the same meaning as in a Vim pattern)
is much nicer than looking at the full rpm -qa output.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, April 4, 2017
single shot mapping insert mode backwards line move
Hi,
I'm trying to build a function for solving some completion hacking.
I mean, I would like to quickly move my cursor in insertmod backward in
the current line and cycle though the positions.
My idea is to define 2 key bindings:
imap <c-left> which will detect some char in the current line [=/]
imap <c-right> which will delete one space backward
hitting c-left would bring my cursor in insert mode just after the char
matched:
I represent the cursor with a pipe
var=pipo/molo|
var=pipo/|molo
var=|pipo/molo
and each c-left cycle through matchable character, and back where we
started the mapping
I would know if I can imap <esc> temporary so it will finish my cycle
and move the cursor back to the started position, saved in a mark (may
be some offset compute, because I inserted space).
That way I can come back to insert mode and hit <c-x><c-f> to have file
completion fore example, with the modified path and having filename
completed with current path.
Do I need to handle the imap <esc> myself or it there some instant
one-shot mapping?
Here is my function draft:
" supprime l'espace dans la completion "test_ nom_class<c-f>"
imap <c-left> <esc>miF x`ia
" insert l'espace sur in char
[=/]
imap <c-right> <esc>:call Lookup_back()<cr>a
" var=pipo/molo
func! Lookup_back()
let l = getline('.')
let s = 0
" save the line txt in g:last_l, will be our memory + g:last_match
if exists("g:last_l")
if l == g:last_l
let s = g:last_match + 1
else
let g:last_l = l
endif
else
" init
norm mi
let g:last_l = l
endif
" reverse it
let r = join(reverse(split(l, '\zs')), '')
let p = match(r, '[=/][^ ]', s)
let g:last_match = p
if p > -1
call cursor(line('.'), col("'i") - p)
else
let g:last_l = ""
" put back at 'i
"call cursor(line('.'), col("'i"))
endif
echo p
endf
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm trying to build a function for solving some completion hacking.
I mean, I would like to quickly move my cursor in insertmod backward in
the current line and cycle though the positions.
My idea is to define 2 key bindings:
imap <c-left> which will detect some char in the current line [=/]
imap <c-right> which will delete one space backward
hitting c-left would bring my cursor in insert mode just after the char
matched:
I represent the cursor with a pipe
var=pipo/molo|
var=pipo/|molo
var=|pipo/molo
and each c-left cycle through matchable character, and back where we
started the mapping
I would know if I can imap <esc> temporary so it will finish my cycle
and move the cursor back to the started position, saved in a mark (may
be some offset compute, because I inserted space).
That way I can come back to insert mode and hit <c-x><c-f> to have file
completion fore example, with the modified path and having filename
completed with current path.
Do I need to handle the imap <esc> myself or it there some instant
one-shot mapping?
Here is my function draft:
" supprime l'espace dans la completion "test_ nom_class<c-f>"
imap <c-left> <esc>miF x`ia
" insert l'espace sur in char
[=/]
imap <c-right> <esc>:call Lookup_back()<cr>a
" var=pipo/molo
func! Lookup_back()
let l = getline('.')
let s = 0
" save the line txt in g:last_l, will be our memory + g:last_match
if exists("g:last_l")
if l == g:last_l
let s = g:last_match + 1
else
let g:last_l = l
endif
else
" init
norm mi
let g:last_l = l
endif
" reverse it
let r = join(reverse(split(l, '\zs')), '')
let p = match(r, '[=/][^ ]', s)
let g:last_match = p
if p > -1
call cursor(line('.'), col("'i") - p)
else
let g:last_l = ""
" put back at 'i
"call cursor(line('.'), col("'i"))
endif
echo p
endf
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Trouble building Huge Vim8 on CentOS 7
Hi,
On Tue, Mar 21, 2017 at 07:13 PM PDT, L A Walsh wrote:
LAW> Mun wrote:
LAW> >I tried to find a yum package that provides SMlib.h, but my system said:
LAW> >"No matches found". Sigh.
LAW> ----
LAW> I found I had to create my own reverse index of packages in my
LAW> distro to find files.
LAW>
LAW> basically a:
LAW> "rpm -qpl path-to-pkg/pkg.rpm > path-to-rpmlist/pkg.rpm.lst"
LAW> for each rpm in my distro (so each rpm file list ends up in a
LAW> different file).
LAW>
LAW> It's the only way to find a file that I've found. It's 550Meg
LAW> of just rpm-file lists. That said, how to find files in your
LAW> distro, isn't really a 'vim question', but a question for
LAW> people who know how to find things in your distro.
LAW>
LAW>
LAW> Dunno if it is helpful, but in suse13.2, it's in libSM-devel.
Thanks for the reply. I was able to finally get vim to compile, but it
was a little painful to discover all of the dependencies.
If there exists documentation which specifies the dependencies for a
"huge gui" implementation on CentOS7, I missed it.
Kind regards,
--
Mun
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Tue, Mar 21, 2017 at 07:13 PM PDT, L A Walsh wrote:
LAW> Mun wrote:
LAW> >I tried to find a yum package that provides SMlib.h, but my system said:
LAW> >"No matches found". Sigh.
LAW> ----
LAW> I found I had to create my own reverse index of packages in my
LAW> distro to find files.
LAW>
LAW> basically a:
LAW> "rpm -qpl path-to-pkg/pkg.rpm > path-to-rpmlist/pkg.rpm.lst"
LAW> for each rpm in my distro (so each rpm file list ends up in a
LAW> different file).
LAW>
LAW> It's the only way to find a file that I've found. It's 550Meg
LAW> of just rpm-file lists. That said, how to find files in your
LAW> distro, isn't really a 'vim question', but a question for
LAW> people who know how to find things in your distro.
LAW>
LAW>
LAW> Dunno if it is helpful, but in suse13.2, it's in libSM-devel.
Thanks for the reply. I was able to finally get vim to compile, but it
was a little painful to discover all of the dependencies.
If there exists documentation which specifies the dependencies for a
"huge gui" implementation on CentOS7, I missed it.
Kind regards,
--
Mun
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Monday, April 3, 2017
Re: How to make vim embed my own custom version of python ?
> If there is a command-line configure argument for the Python path
> (--with-python3-config-dir maybe? On my system, python3-config is a
> Python script which, just like the Python3 interpreter, lives in
> /usr/bin) you could have added it space-separated inside the value for
> CONF_OPT_PYTHON3, something like
>
> export CONF_OPT_PYTHON3='--enable-python3interp
> --with-python3-config-dir=/home/jackyliu/.local/dir'
>
> If you haven't changed python-config, and haven't copied it or linked
> it in your patched Python interpreter's directory, then I suppose your
> hack of setting $vi_cv_path_python3 is the least bad solution.
>
> Best regards,
> Tony.
Nope, just setting --with-python3-config-dir is not sufficient, configure yielded result like this:
checking --enable-python3interp argument... yes
checking for python3... /usr/bin/python3
checking Python version... 3.5
checking Python is 3.0 or better... yep
checking Python's abiflags... m
checking Python's install prefix... /usr
checking Python's execution prefix... /usr
checking Python's configuration directory... (cached) /home/jacky/Build/PythonX/python3_pyx/Python-3.6.1
checking Python3's dll name... libpython3.6m.so.1.0
Note configure still looks into /usr to try to find python, and it found 3.5。I suppose setting the variable $vi_cv_path_python3 can't be avoided, maybe my need is too rare?
Also I learned these:
*. Python has to be configured with the --enable-shared option on.
*. Vim has to be configured with this variable set properly:
export LD_LIBRARY_PATH=/home/jacky/.local/lib
and the same with the later invoking of Vim, I added it into my .bashrc。
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> (--with-python3-config-dir maybe? On my system, python3-config is a
> Python script which, just like the Python3 interpreter, lives in
> /usr/bin) you could have added it space-separated inside the value for
> CONF_OPT_PYTHON3, something like
>
> export CONF_OPT_PYTHON3='--enable-python3interp
> --with-python3-config-dir=/home/jackyliu/.local/dir'
>
> If you haven't changed python-config, and haven't copied it or linked
> it in your patched Python interpreter's directory, then I suppose your
> hack of setting $vi_cv_path_python3 is the least bad solution.
>
> Best regards,
> Tony.
Nope, just setting --with-python3-config-dir is not sufficient, configure yielded result like this:
checking --enable-python3interp argument... yes
checking for python3... /usr/bin/python3
checking Python version... 3.5
checking Python is 3.0 or better... yep
checking Python's abiflags... m
checking Python's install prefix... /usr
checking Python's execution prefix... /usr
checking Python's configuration directory... (cached) /home/jacky/Build/PythonX/python3_pyx/Python-3.6.1
checking Python3's dll name... libpython3.6m.so.1.0
Note configure still looks into /usr to try to find python, and it found 3.5。I suppose setting the variable $vi_cv_path_python3 can't be avoided, maybe my need is too rare?
Also I learned these:
*. Python has to be configured with the --enable-shared option on.
*. Vim has to be configured with this variable set properly:
export LD_LIBRARY_PATH=/home/jacky/.local/lib
and the same with the later invoking of Vim, I added it into my .bashrc。
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to make vim embed my own custom version of python ?
On Mon, Apr 3, 2017 at 2:13 PM, Jacky Liu <bluegene8210@gmail.com> wrote:
> On Monday, April 3, 2017 at 11:11:27 AM UTC+8, Tony Mechelynck wrote:
>> Configure has a lot, but really a lot, of possible arguments. To see
>> them all, use
>>
>> src/auto/configure --help |less
>>
>> For your usecase, I think the following might perhaps be relevant (but
>> you might want to read it all):
>>
>> --enable-pythoninterp=OPTS Include Python interpreter. default=no
>> OPTS=no/yes/dynamic
>> --enable-python3interp=OPTS Include Python3 interpreter.
>> default=no OPTS=no/yes/dynamic
>>
>> --with-plthome=PLTHOME Use PLTHOME.
>> --with-python-config-dir=PATH Python's config directory
>> --with-python3-config-dir=PATH Python's config directory
>>
>> Also, --disable-blablabla is equivalent to --enable-blablabla=no and
>> --without-blablabla is equivalent to --with-blablabla=no for any value
>> of blablabla.
>>
>> In any case, I recommend not to edit the makefile, and not to invoke
>> configure directly yourself with arguments on the command-line, but
>> instead to set the configure arguments by means of environments
>> variables set by sourcing a script, so you can be sure to use the
>> right arguments every time.
>>
>> For details, see the last two links above the bottom line of
>> http://users.skynet.be/antoine.mechelynck/vim/
>>
>> Best regards,
>> Tony.
>>
>
>
> You were right about using environment variables instead of arguments. After carefully checking /src/auto/configure I added this line to my script:
>
> export vi_cv_path_python3=/home/mydir/.local/bin/python3.6
>
> and it worked, vim found the specified version of Python.
>
> Thank you !
>
>
I meant setting configure arguments as environment variables to make,
but since it works for you, so much the better.
This is the script I source (running it isn't enough) when opening the
terminal where I'll be compiling Vim (and I may then compile it
repeatedly as new patches arrive, without sourcing the script again:
#!/bin/bash
export CONF_OPT_GUI='--enable-gui=gtk3 --enable-gnome-check'
export CONF_OPT_PERL='--enable-perlinterp'
export CONF_OPT_PYTHON='--enable-pythoninterp'
export CONF_OPT_PYTHON3='--disable-python3interp'
export CONF_OPT_TCL='--enable-tclinterp'
# /usr/bin/tclsh (softlink) is correctly set
export CONF_OPT_RUBY='--enable-rubyinterp'
export CONF_OPT_LUA='--enable-luainterp'
export CONF_OPT_MZSCHEME='--disable-mzschemeinterp'
#export CONF_OPT_PLTHOME='--with-plthome=/usr/local/plt'
export CONF_OPT_CSCOPE='--enable-cscope'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
export CONF_OPT_FEAT='--with-features=huge'
export CONF_OPT_COMPBY='"--with-compiledby=antoine.mechelynck@gmail.com"'
The shebang line is probably unneeded, since this script must be
"sourced" by the instance of bash which will be running make, not
"run" as a program (which would get its own environment, forgotten on
return).
And I repeat, I never invoke configure on the command-line but only
through make: "make config" or "make reconfig", and sometimes just
plain "make" decides that it needs to run configure anyway. In all
these cases, especially the latter one, the correct configure
arguments are set.
If there is a command-line configure argument for the Python path
(--with-python3-config-dir maybe? On my system, python3-config is a
Python script which, just like the Python3 interpreter, lives in
/usr/bin) you could have added it space-separated inside the value for
CONF_OPT_PYTHON3, something like
export CONF_OPT_PYTHON3='--enable-python3interp
--with-python3-config-dir=/home/jackyliu/.local/dir'
If you haven't changed python-config, and haven't copied it or linked
it in your patched Python interpreter's directory, then I suppose your
hack of setting $vi_cv_path_python3 is the least bad solution.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Monday, April 3, 2017 at 11:11:27 AM UTC+8, Tony Mechelynck wrote:
>> Configure has a lot, but really a lot, of possible arguments. To see
>> them all, use
>>
>> src/auto/configure --help |less
>>
>> For your usecase, I think the following might perhaps be relevant (but
>> you might want to read it all):
>>
>> --enable-pythoninterp=OPTS Include Python interpreter. default=no
>> OPTS=no/yes/dynamic
>> --enable-python3interp=OPTS Include Python3 interpreter.
>> default=no OPTS=no/yes/dynamic
>>
>> --with-plthome=PLTHOME Use PLTHOME.
>> --with-python-config-dir=PATH Python's config directory
>> --with-python3-config-dir=PATH Python's config directory
>>
>> Also, --disable-blablabla is equivalent to --enable-blablabla=no and
>> --without-blablabla is equivalent to --with-blablabla=no for any value
>> of blablabla.
>>
>> In any case, I recommend not to edit the makefile, and not to invoke
>> configure directly yourself with arguments on the command-line, but
>> instead to set the configure arguments by means of environments
>> variables set by sourcing a script, so you can be sure to use the
>> right arguments every time.
>>
>> For details, see the last two links above the bottom line of
>> http://users.skynet.be/antoine.mechelynck/vim/
>>
>> Best regards,
>> Tony.
>>
>
>
> You were right about using environment variables instead of arguments. After carefully checking /src/auto/configure I added this line to my script:
>
> export vi_cv_path_python3=/home/mydir/.local/bin/python3.6
>
> and it worked, vim found the specified version of Python.
>
> Thank you !
>
>
I meant setting configure arguments as environment variables to make,
but since it works for you, so much the better.
This is the script I source (running it isn't enough) when opening the
terminal where I'll be compiling Vim (and I may then compile it
repeatedly as new patches arrive, without sourcing the script again:
#!/bin/bash
export CONF_OPT_GUI='--enable-gui=gtk3 --enable-gnome-check'
export CONF_OPT_PERL='--enable-perlinterp'
export CONF_OPT_PYTHON='--enable-pythoninterp'
export CONF_OPT_PYTHON3='--disable-python3interp'
export CONF_OPT_TCL='--enable-tclinterp'
# /usr/bin/tclsh (softlink) is correctly set
export CONF_OPT_RUBY='--enable-rubyinterp'
export CONF_OPT_LUA='--enable-luainterp'
export CONF_OPT_MZSCHEME='--disable-mzschemeinterp'
#export CONF_OPT_PLTHOME='--with-plthome=/usr/local/plt'
export CONF_OPT_CSCOPE='--enable-cscope'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
export CONF_OPT_FEAT='--with-features=huge'
export CONF_OPT_COMPBY='"--with-compiledby=antoine.mechelynck@gmail.com"'
The shebang line is probably unneeded, since this script must be
"sourced" by the instance of bash which will be running make, not
"run" as a program (which would get its own environment, forgotten on
return).
And I repeat, I never invoke configure on the command-line but only
through make: "make config" or "make reconfig", and sometimes just
plain "make" decides that it needs to run configure anyway. In all
these cases, especially the latter one, the correct configure
arguments are set.
If there is a command-line configure argument for the Python path
(--with-python3-config-dir maybe? On my system, python3-config is a
Python script which, just like the Python3 interpreter, lives in
/usr/bin) you could have added it space-separated inside the value for
CONF_OPT_PYTHON3, something like
export CONF_OPT_PYTHON3='--enable-python3interp
--with-python3-config-dir=/home/jackyliu/.local/dir'
If you haven't changed python-config, and haven't copied it or linked
it in your patched Python interpreter's directory, then I suppose your
hack of setting $vi_cv_path_python3 is the least bad solution.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to make vim embed my own custom version of python ?
On Monday, April 3, 2017 at 11:11:27 AM UTC+8, Tony Mechelynck wrote:
> Configure has a lot, but really a lot, of possible arguments. To see
> them all, use
>
> src/auto/configure --help |less
>
> For your usecase, I think the following might perhaps be relevant (but
> you might want to read it all):
>
> --enable-pythoninterp=OPTS Include Python interpreter. default=no
> OPTS=no/yes/dynamic
> --enable-python3interp=OPTS Include Python3 interpreter.
> default=no OPTS=no/yes/dynamic
>
> --with-plthome=PLTHOME Use PLTHOME.
> --with-python-config-dir=PATH Python's config directory
> --with-python3-config-dir=PATH Python's config directory
>
> Also, --disable-blablabla is equivalent to --enable-blablabla=no and
> --without-blablabla is equivalent to --with-blablabla=no for any value
> of blablabla.
>
> In any case, I recommend not to edit the makefile, and not to invoke
> configure directly yourself with arguments on the command-line, but
> instead to set the configure arguments by means of environments
> variables set by sourcing a script, so you can be sure to use the
> right arguments every time.
>
> For details, see the last two links above the bottom line of
> http://users.skynet.be/antoine.mechelynck/vim/
>
> Best regards,
> Tony.
>
You were right about using environment variables instead of arguments. After carefully checking /src/auto/configure I added this line to my script:
export vi_cv_path_python3=/home/mydir/.local/bin/python3.6
and it worked, vim found the specified version of Python.
Thank you !
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Configure has a lot, but really a lot, of possible arguments. To see
> them all, use
>
> src/auto/configure --help |less
>
> For your usecase, I think the following might perhaps be relevant (but
> you might want to read it all):
>
> --enable-pythoninterp=OPTS Include Python interpreter. default=no
> OPTS=no/yes/dynamic
> --enable-python3interp=OPTS Include Python3 interpreter.
> default=no OPTS=no/yes/dynamic
>
> --with-plthome=PLTHOME Use PLTHOME.
> --with-python-config-dir=PATH Python's config directory
> --with-python3-config-dir=PATH Python's config directory
>
> Also, --disable-blablabla is equivalent to --enable-blablabla=no and
> --without-blablabla is equivalent to --with-blablabla=no for any value
> of blablabla.
>
> In any case, I recommend not to edit the makefile, and not to invoke
> configure directly yourself with arguments on the command-line, but
> instead to set the configure arguments by means of environments
> variables set by sourcing a script, so you can be sure to use the
> right arguments every time.
>
> For details, see the last two links above the bottom line of
> http://users.skynet.be/antoine.mechelynck/vim/
>
> Best regards,
> Tony.
>
You were right about using environment variables instead of arguments. After carefully checking /src/auto/configure I added this line to my script:
export vi_cv_path_python3=/home/mydir/.local/bin/python3.6
and it worked, vim found the specified version of Python.
Thank you !
--
--
You received this message from the "vim_use" 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 the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)