> ... neither of the following work:
> :echo expand("$PATH")
This works for me now as it has in the past, using a gvim compiled with MSVC.
Could there be a difference if compiled with gcc?
> :echo expand("%PATH%")
Agree this does not work.
Charlie
--
--
You received this message from the
> Since a couple of days, the vim-win32-installer repository fails to
> provide updated binaries and my guess is, that this patch is the reason.
> It basically started after 8.0.1071.
Win64 msvc: in script test_terminal the function Test_terminal_no_cmd() does
not seem to work. It hangs after
ed but not deleted by command ExecAsScript T1_G.
This is testing try/catch; not sure how to fix.
----
Charles Cooper
--
--
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 inf
On Thursday, March 26, 2015 at 3:24:43 AM UTC-4, Christian Brabandt wrote:
> Hm, I have never used the new renderoption. So I just tried it
> :set encoding=utf8
> :set guifont=Envy_Code_R:h11:cANSI
> :set rop=type:directx
>
> And suddenly, no text is rendered at all. I can make this go away typing
On Tuesday, August 12, 2014 5:39:05 PM UTC-4, Bram Moolenaar wrote:
> Dominique wrote:
> > Bram Moolenaar wrote:
> > > Patch 7.4.402
> > > Problem:Test 72 crashes under certain conditions. (Kazunobu Kuriyama)
> > > Solution: Clear the whole bufinfo_T early.
> > > Files: src/undo.c
> >
>
Compiling Vim 7.4.282 on windows produces a warning due to some of the changes
in patch 276.
ex_cmds.c(1554) : warning C4101: 'is_fish_shell' : unreferenced local variable
The warning can be eliminated by moving the declaration of is_fish_shell to be
immediately after the #if, or enclosing the
On Saturday, February 1, 2014 9:11:51 AM UTC-5, Christian Brabandt wrote:
> Can you see, if this patch fixes it for you?
>
Yes, in patched vim the cursor does not jump with :sleep.
I am trying to come up with a script that would better show the original
problem of having the cursor be restored
> the :sleep command mispositions cursor when there are splits. From vim -u
> NONE,
>
> :vsp|vsp|vsp|vsp|wincmd w|wincmd w
> :sleep 2 "cursor will shift to the first split
Just to clarify, when trying it looked to me like the cursor jumped to the
first split during the sleep and then jumped bac
On Thursday, September 19, 2013 3:45:24 PM UTC-4, Bram Moolenaar wrote:
> I would say the current behavior is intended. If you reset 'diff', but
> then realize it doesn't look right, you can use :diffoff to reset the
> other side effects of :diffthis.
I never thought of that!
> If you don't wan
The diffoff! and diffoff commands both reset options in the window they are
called from without checking the value of &diff. The options which the commands
reset are: diff, scrollbind, cursorbind, scrollopt, wrap, foldmethod,
foldcolumn. Here are 2 examples using the wrap option, after starting
Hello.
> > > >> :call expand('a', 'p', 0700)
> > > (gdb) set args -u NONE -U NONE +'call mkdir(expand("abc", "p", 0700))'
The example reads --> call mkdir(expand("abc", "p", 0700))
but should it be --> call mkdir(expand("abc"), "p", 0700)
expand("abc","p", 0700) is not a correct use of expan
Building 7.3.1157 on an older system
uname -s -r -v -m --> HP-UX B.11.23 U ia64
cc --version --> cc: HP C/aC++ B3910B A.06.14 [Feb 22 2007]
./configure \
--with-features=big \
--with-x\
--enable-gui=auto \
--enable-multibyte
cc -c -I. -
Confirming problem tied to setting liststyle in vimrc; problem disappears when
set line commented.
--
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
On Thursday, August 2, 2012 3:58:02 PM UTC-4, Bram Moolenaar wrote:
> I have a new PC with Windows 7 that I want to use to build Vim for
> distribution. It's a 64 bit system but I first want to build 32 bit
> binaries.
> I have installed MS C++ Express 2008, since the binaries from this
> compiler
This problem occurs in vim with +multi_byte.
:edit ++encoding=xyz always causes error E474, while ++enc=xyz succeeds.
"encoding" is the only ++option where the short form of the option is a
substring of the long form. The check for these options does not account
for this.
Here is one way to fi
On Thursday, August 18, 2011 9:33:25 PM UTC-4, mattn wrote:
>
> But please generate diff without including only for changes of blank/space.
> ;)
>
>
Thank you, I did not notice that tabs had been expanded. Here is the
corrected version.
--
You received this message from the "vim_dev" mailli
See https://groups.google.com/d/topic/vim_dev/p5qS9s8YgAc/discussion for a
description of the problem on windows.
On linux the current if_perl.xs will let you link with a dynamic perl 5.14,
but leads to an error at runtime when actually using perl from vim.
This is caused by changes to perlapi
17 matches
Mail list logo