Hi,
[...]
3. Embedded shell support like screen.vim.
ConqTerm or such come close. However it only works in insert mode, and
you cannot use vi keys.
It seems that Conque is dead at the moment, so I started a fork which
tries to improve usability. So I'm curious, what exactly does bother you
I updated detectindent plugin, but the original author seems to be
unreachable
http://www.vim.org/scripts/script.php?script_id=1171
Can you re-assingn the plugin to me (theNeuron) so that I can continue
to work on it? Of course I'll be happy to return it to original
:echo expand(/a/b/c 'd)
:echo glob(a 'b/*)
Both seem to work fine for me. Maybe you'd have to tell more about
your environment check if this also occurs when running vanilla vim
(no plugins, no (g)vimrc).
You are using Windows, right ?
I checked the source and what is happening for Unix
I have been using
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
./configure
make
...
Is it wrong ?
Thanks
--
Vlad
pgpI5x59VYROG.pgp
Description: PGP signature
Hi,
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two commas in a row or a
backslash seem to generate a comma.
glob behaves depending on your shell settings. Out of my experience,
best is csh or tcsh, where glob works reliably.
:set shell=/bin/tcsh
:echo glob(a 'b/*)
- a 'b/file
:set shell=/bin/bash
:echo glob(a 'b/*)
- a
[...]
Uh. That's horrible. It's a pain that whenever you do any kind of
VimScripting you always have to cover all your bases. It's getting to
become unmanageable.
Personally I would
[...]
Vim treats backtick-ed string honestly, so you can match some kinda
weird looking patterns via shell directly. e.g:
:echo glob('`for i in ~/{bin,tmp,\,}; do echo $i; done`')
A note, this might be incorrect if the name got matched contains special
chars like '\n'.
Would there be a
Would there be a way to read in string containing \000 character ?
That way you could use
...; do printf $i\000; done
However that does not seem to be possible:
:echo system(printf 'aaa\000bbb')
E484: Can't open file /tmp/v984274/8
:echo system(sh -c ' . 'printf aaa\000bbb' . ')
Hi,
Googling a bit brought me to this thread http://tinyurl.com/3cgns7
which provides 'workaround', i.e. putting something like:
Snip from the thread:
= cut ==
i still think that the best way would be to teach app developers that
Maybe I misunderstood here. If you want to tell vim to use /bin/sh all
the time, just put set shell= unconditionally into your vimrc.
That's clear, but I'd like to use fish and not /bin/sh as shell.
You can always run
:!fish
That's the problem - it does not work - and you can try
Hi,
I'm using diff mode to do 3way merging.
3way merging is for example situation, where two people make change to
single file at the same time, so you have base version, your version
and other version. You could commit your version and then merge the
other version, but this does not work very
I'm using diff mode to do 3way merging.
I'm using git and recently hit the same issue.
I suggest using this script: CVSconflict.vim
http://vim.sourceforge.net/scripts/script.php?script_id=1370
Excellent work from Charles E. Campbell, as usual ;-)
Ah, I didn't know that script. It
Do you have syntax highlighting enabled? If so, try turning it off
and see if that helps. It can take vim a long time to highlight
files with long lines.
Did not notice differences with syntax on/off. Both were equally slow.
I guess that cat-ing file, or viewing it in less is faster
Is it possible to receive your updated copy of this plug-in? I'm very
interested in it. It would be nice if you could publish it!
You may also have a look at my IndentConsistencyCop plugin
(http://vim.sourceforge.net/scripts/script.php?script_id=1690), which also
detects the indent
One more time, for the sake of the braindead (such as me):
How about:
ifeq ($(LINK_TO_VI),y)
LINKIT=ln -s -f
else
LINKIT=:
endif
...
-$(LINKIT) $(BINDIR)/$(VIMTARGET) $(DESTDIR)/usr/bin/vim
instead?
What make understands ifeq? This looks restricted to
Hi,
hi,I use OpenSolaris (solaris express community edition,snv_73).I download
vim-7.1.tar.zip2,vim-7.1-extra.tar.zip2,vim-7.1-lang.tar.zip2,bunziped
them into a directory .configureed options as bellow:
./configure --enable-gui --enable-pythoninterp --enable-cscope
On Thu, Mar 06, 2008 at 10:13:16AM +0200, Yakov Lerner wrote:
I see problem with shell highlighting with the following piece,
apparently caused by the command named 'locale'.
I am using latest runtime files. from rsync.
Does anybody see incorrect highlighting, too ?
Hi,
I'm new in this list, and new to vim sources. I have several questions. Can
you please explain me or give me some link with explanation about
1. Is there any documentation which explains .vim files and theirs context?
If you ask about vim scripting language, try ':help
$ vim -o a a #this doesn't open file a in two horizontal splits
$ vim -p a a #this doesn't open file a in two tabpages
Given that this behavior is consistant across three command-line
options, and without having searched for the code, I'd say that
Vim does this on purpose.
Hi,
[...]
The D-Bus connection is an Unix socket. When vim fires a signal from the
plug-in, some data is sent through the socket to the dbus-daemon
process. But to receive D-Bus signal, the socket file descriptor must
be added somehow in the vim main loop in order to call a function to
read
Hi Alban,
As suggested, you need to look into :help netbeans and at the various
projects that are using the netbeans interface. Don't be mislead by the
name, netbeans interface no longer has anything to do with netbeans.
Is it still bound to graphical vim (no textmode) ?
Thanks
--
.\eval.c:
Warning W8065 .\eval.c 14642: Call to function 'round' with no prototype
in function f_round
Warning W8065 .\eval.c 17027: Call to function 'trunc' with no prototype
in function f_trunc
As a workaround in eval.c you can simply replace
rettv-vval.v_float = round(f);
Hi,
Solaris 9 + SunStudio 12 seems to work fine. Just single nit:
./configure says
checking sys/ptem.h presence... yes
configure: WARNING: sys/ptem.h: present but cannot be compiled
configure: WARNING: sys/ptem.h: check
I have done a successful compile, build, run and 'make test' on:
[...]
Oh, didn't know that there's make test :)
When I run it, I can see
== make test ===
make[2]: Leaving directory `/share/chroot/on81/tmp/vim72a/src'
if test -n
== make test
===
make[2]: Leaving directory `/share/chroot/on81/tmp/vim72a/src'
if test -n -a -f po/Makefile; then \
cd po; make -f Makefile check VIM=../vim; \
fi
if test vim != vim -a ! -e
There is something wrong with what CVS did to the files. Especially in
runtime/tutor. Might take a day to sort out.
Sigh. Why can't I just tell CVS that this is the tree of files I want
to have in the repository?
The .tar.bz2 / .tar.gz on the Vim FTP site aren't afflicted
I've messed this up. I *do* get the test statement to fail, but
it carries on anyway, because of the leading - sign. I've done this:
Ah, I never said that the test fails, but looking at my previous message
I have to admit that it sounds so.
[...]
I can't find a GNU autoconf macro to test
Good point. I suggest you submit a patch to Bram. I'd do this for you,
especially as it's small, but you should get the credit for the fix.
Well, I thought that single letter change would not require diff, but
I'm happy to attach one :)
Thanks
--
Vlad
--- Makefile.orig st črn
[...]
Looks almost OK. This should be slightly better:
dnl sys/ptem.h depends on sys/stream.h on Solaris 9
AC_CHECK_HEADERS(sys/ptem.h, [], [],
[#if defined HAVE_SYS_STREAM_H
# include sys/stream.h
#endif])
Just a nitpick, it's for sure Solaris 8 till latest development build,
so plain
Hi,
Recently we discovered problem with editing dtrace files. To reproduce
it is simple:
A=fsinfo:::a*
A=$A,$A,$A,$A,$A,$A
printf $A,$A,$A\nEND {\n test.d
vim test.d
It takes very long time to open the file if you have syntax highlighting
enabled. We fixed the problem by the attached patch. I
Hi,
I would like to report a bug found by Keiichi Oono on Japan encoding and
vim.
After investigation of vim source files, it's clear that the vim does not
support ja_JP.PCK environment to edit SJIS (PCK) characters without manual
configuration.
.
Configuration
-
Create
> > So I noticed that vim has :terminal. I have compiled myself 8.1.0026 and
> > started to experiment. There are two major drawbacks for me and so this
> > email - a plea for considering updating them. I would like to have the
> > ability to modify the terminal contents and I would like the
Hi,
So I noticed that vim has :terminal. I have compiled myself 8.1.0026 and
started to experiment. There are two major drawbacks for me and so this
email - a plea for considering updating them. I would like to have the
ability to modify the terminal contents and I would like the terminal to
Hi,
I'm not sure how useful this will be. For Solaris we are using SIGSTKSZ
increased from 8000 to 16384. But recently we have seen few core dumps
like
000ccfc42860 vim`mch_write+0x22()
000ccfc42890 vim`ui_write+0x5b()
000ccfc428b0 vim`stoptermcap+0xc6()
000ccfc428c0
> > I'm not sure how useful this will be. For Solaris we are using SIGSTKSZ
> > increased from 8000 to 16384. But recently we have seen few core dumps
> > like
> >
> >
> > 000ccfc42860 vim`mch_write+0x22()
> > 000ccfc42890 vim`ui_write+0x5b()
> > 000ccfc428b0 vim`stoptermcap+0xc6()
>
Hi,
When compiling on Solaris using gcc 10, I am getting this error:
/usr/gcc/10/bin/gcc ... -o gvim ...
ld: fatal: symbol 'longVersion' is multiply-defined:
(file objects/version.o type=OBJT; file objects/main.o type=OBJT);
collect2: error: ld returned 1 exit status
link.sh: Linking
[...]
> The best solution seems to be to always declare longVersion in
> version.c, and always declare it extern in globals.h. Otherwise the
> #ifdef gets complicated.
Your patch works for me, thank you
--
Vlad
--
--
You received this message from the "vim_dev" maillist.
Do not
Hi,
When compiling on Solaris using gcc 10, I am getting this error:
/usr/gcc/10/bin/gcc ... -o gvim ...
ld: fatal: symbol 'longVersion' is multiply-defined:
(file objects/version.o type=OBJT; file objects/main.o type=OBJT);
collect2: error: ld returned 1 exit status
link.sh: Linking
Hi,
While trying to integrate latest vim into Solaris I found out that
the tests no longer finish. After some bisecting I found it it's caused
by patch 394
https://github.com/vim/vim/commit/5903aaf7eb4586cf7e4fa5a219092334b05c89de
Last output on the screen is
Test_map_cmdkey
Executed process
39 matches
Mail list logo