Martin Stubenschrott wrote:
I am using vim7 final, and have this problem:
Let's assume this buffer (between the quotes):
this
that
Now i start inserting 'th' and press ctrl-n and get a popup menu with
two choices 'this' and 'that', while the inserted text still remains
'th' (I am using
Gautam Iyer wrote:
On Wed, May 17, 2006 at 10:31:55AM -0400, James Vega wrote:
On Tue, May 16, 2006 at 11:19:57PM -0500, Gautam Iyer wrote:
Now when you type vim /tmp/bar it reports that a .swp file is found
and asks you about recovery. However when you press R for recovering
the
[EMAIL PROTECTED] wrote:
All,
In the options.txt file of Vim documentation...
Options 'cursorcolumn' and 'cursorline' are said to be local to
window. Given their behavior, it should say local to buffer rather
than local to window.
However, when thinking some more about this, maybe the
Hi Vimmers,
I got the attached mail privately but I believe it belongs on the list.
Best regards,
Tony.
---BeginMessage---
On 5/21/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Alexandru Iancu wrote: Hi, I posted the wrong files. I realised later after I posted while testing. Sorry!
Regards
steven bensky wrote:
Short file name (Filename) is not being retained in
Windows (XP).
VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7
2006 16:18:30)
Don't know if this is a bug per say, but, ...
---
Create a new file with a long filename.
vim this_is_a_test
Save the file.
List the
Zdenek Sekera wrote:
I have this:
if (char =~ '\m[;|?:[EMAIL PROTECTED]*(){}\\_+-[\]/\]')
do something
endif
Basically it is checking for all non-alphanumeric chars
(expect '=').
1. how do I include the ' char?.
I can't seem to find a proper way.
(I'd like to keep the patter in
Charles E Campbell Jr wrote:
Hello, Tony!
I've had several folks having a problem with WinXP and netrw. The
problems seem to involve temporary files during attempts to use ftp;
since temporary filenames are produced by tempname(), they're o/s
dependent. Admittedly without having searched
Bug: Cannot redir to @+
- Symptom: Trying to :redir to register + (seen by other apps as the
clipboard) gives
E475: Invalid argument: @+
- Vim version: 7.0.017 for GTK2 GUI
- Workaround: :redir to register * then (after :redir END) do manually
:let @+ = @*
Just redirecting to @* is not
Ron Blaschke wrote:
George Reilly wrote:
Ron Blaschke [EMAIL PROTECTED] wrote:
I recently managed to compile Vim on Windows XP x64, including the
Explorer integration. I don't know if everything is working, but I'm
using it for my daily work and at least everything I use seems fine.
Mathias Michaelis wrote:
Hi developers
If I compile vim on Windows XP with Microsoft Visual Studio 2005
Express Edition on the command line with
nmake -f Make_mvc.mak DEBUG=yes FEATURES=TINY GUI=yes OLE=yes
I get the errors:
ex_cmds2.obj : error LNK2019:
unresolved external symbol
Hello Vim gurus (and newbies) !
My Vim site http://users.skynet.be/antoine.mechelynck/vim/ has just been
updated. The updates include:
- Instead of mentioning Vim 6.4 and Vim 7.0 alpha, the site now only
refers to the release version of Vim 7.0. Sorry, no more patched
distributions of Vim
Mathias Michaelis wrote:
Hi Tony
Thanks for your reply!
If I compile vim on Windows XP with Microsoft Visual Studio
2005 Express Edition on the command line with
nmake -f Make_mvc.mak DEBUG=yes FEATURES=TINY GUI=yes OLE=yes
I get the [some] errors:
I guess it's a bug; but Tiny
Hari Krishna Dara wrote:
I read your previous emails about your windows laptop being out and that
you prefer Linux etc., so I have a suggestion. Why don't you install
VMWare virtual server on your Linux box and have windows run just for
the builds? If you don't want to purchase a license, it is
[EMAIL PROTECTED] wrote:
dear
sir
Thank you very much for your support.
I am panasonic corporate information systens company (china).I want to know
whether vim is free to use.If not i want to bay vim in china.
please tell me where to bay and how much .
Thanks Regards
James Vega wrote:
On Mon, Jun 05, 2006 at 11:10:21PM -0700, Hari Krishna Dara wrote:
Isn't there a cross-compiler for producing cygwin executables from
Linux?
There is a cross-compiler for producing Windows native executables.
It's mingw and that was what I used to produce binaries of
James Vega wrote:
On Tue, Jun 06, 2006 at 03:30:32PM +0200, A.J.Mechelynck wrote:
James Vega wrote:
On Mon, Jun 05, 2006 at 11:10:21PM -0700, Hari Krishna Dara wrote:
Isn't there a cross-compiler for producing cygwin executables from
Linux?
There is a cross
Steve Hall wrote:
From: A.J.Mechelynck, Jun 6, 2006 9:30 AM
Until or unlessI think I'll take a back seat to the development
of Vim executables for Windows.
Tony, for what it's worth, I've improved the Cream build routines so
that we can stay on top of patches more easily. Our
Mathias Michaelis wrote:
[...]
But: You don't see no of my mails written yesterday, and also not
all from this morning. The testmail written at 09:03:28 +0200 is not
from me, but from my Email-Provider. I found that emails that are
written on my Thunderbird Email Client AND where addressed to
Mathias Michaelis wrote:
Dear developers
I observe the following strange behaviour of gvim 7.0 on Windows XP
built with HUGE features by my own:
I open gvim.exe, work with it or leave it without touching it for
half an hour. Then, within gvim.exe, I type :q or :wq. gvim
saves the text, remove
William S Fulton wrote:
[...]
Just need spare time mate, but the SUSE guys have beat me to it already!
There is a buffer overrun, all the gory details here:
https://bugzilla.novell.com/show_bug.cgi?id=182212
It was reported as affecting vim 7 too.
William
Interesting... Notice the SuSE
Jochen Baier wrote:
hi,
i have weird behavior here (latest svn gvim, linux, Gnome or Wmii)
if i save with :w the window change the size to larger
size (5 pixel) for moment then it size back to the orginal size.
The left scrollbar is visible during this. no problems with
normal konsole vim.
is
Hi Steve, I got the attached email privately. I believe it is meant for you.
Best regards,
Tony.
---BeginMessage---
A.J.Mechelynck wrote:
And even if someday you do understand RPM (used by RedHat and SuSE),
you'll still have to figure out dpkg (for Debian) and what-not... I have
compiled gvim
Charles E Campbell Jr wrote:
[...]
The problem here is :so % doesn't source the buffer, it sources the
underlying file. Thus the
file must needs be gunzip'ed first.
Vimball could be set up not to gunzip the file, but then sourcing it
would fail.
Regards,
Chip Campbell
Looking at the
*pi_paren.txt* For Vim version 7.0. Last change: 2006 Apr 24
line 46 (i.e. 5th from bottom)
there is 'synmaxcolumn'
there should be 'synmaxcol'
Best regards,
Tony.
Bram Moolenaar wrote:
Mathias Michaelis wrote:
Patch
Problem:Make_mvc.mak creates an empty gvim.exe.mnf file
(or stops with an error message).
Solution: Don't use 'echo' to create files. Use inline files
instead.
Files: src/Make_mvc.mak
This has always
Bram Moolenaar wrote:
Mathias Michaelis wrote:
Patch
Problem:IMHO .pdb files should reside in the same directory as the
corresponding .exe files so they can be distributet along
with them.
Solution: Change one line within src/Make_mvc.mak
Files:
Bram Moolenaar wrote:
Tony Mechelynck wrote:
echo string1 file
echo string2 file
echo string3 file
etc.
ought to work, _except_ when the string is (ignoring case) ON OFF or
empty (in which case you will set, clear or display the echo on/off
setting instead of
Yakov Lerner wrote:
On 6/18/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 5/23/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
create a file ~/.vimtest as follows:
cat .vimtest
set nocompatible
set readonly
C-D
and execute (g)vim:
vim .vimtest
Mathias Michaelis wrote:
Bram
The source archive
ftp://ftp.vim.org/pub/vim/pc/vim70src.zip
contains the file if_sniff.h but not the corresponding source file
if_sniff.c. Has this a specific reason or has if_sniff.c simply been
forgotten?
The Sniff interface is something extra, you need to
Steve Hall wrote:
I just noticed four broken runtime files in ftp.vim.org:
runtime/filetype.vim
runtime/autoload/paste.vim
runtime/plugin/netrwPlugin.vim
runtime/plugin/vimballPlugin.vim
Each has a few stray partial duplicate lines at the end.
I don't notice any stray duplicate
[EMAIL PROTECTED] wrote:
All,
Can someone please try this out and confirm:
On Tue, Jun 20, 2006 at 09:18:40PM -0400, [EMAIL PROTECTED] wrote:
All,
I mentioned this problem once on the list before; however, the issue
wasn't reproducible. Now I found a way to consistently reproduce it.
1.
A.J.Mechelynck wrote:
[EMAIL PROTECTED] wrote:
All,
Can someone please try this out and confirm:
On Tue, Jun 20, 2006 at 09:18:40PM -0400, [EMAIL PROTECTED] wrote:
All,
I mentioned this problem once on the list before; however, the issue
wasn't reproducible. Now I found a way
Nicolas Weber wrote:
Hi,
You probably already know, but when I patched my source and compiled
it, I got these warnings:
gui.c: In function ‘gui_init_which_components’:
gui.c:3229: warning: implicit declaration of function
‘gui_mch_showing_tabline’
gui.c: In function ‘gui_update_tabline’:
Ilya wrote:
gvim –u NONE –U NONE
Create file with 100 empty lines, line with {, 20 empty lines and line
with }:
:exe normal i{\CR}\Esc20O\Escj%100O\Escj%
Turn on matchparen plugin:
:set nocp
:source $VIMRUNTIME/plugin/matchparen.vim
Now cursor should be on the }, this line is
Eric Van Dewoestine wrote:
Should prepending :silent to a command be suppressing an autocommand?
Neither the docs for autocommands nor the docs for :silent indicate
this is the intended behavior.
For example:
using the following the autocommand is executed as expected with the
desired output
Eric Van Dewoestine wrote:
Any thoughts on this?
Bram?
For the most part I've gotten use to the behavior, but I still
occassionaly find my self hitting enter when I see the first entry
highlighted, and receive an ambiguous use error because the
highlighted entry isn't actually in the command
George V. Reilly wrote:
[CCing the Vim and Vim-Dev lists. Not that it did any good the last time
I raised this subject.]
It is NOT me, dammit! Someone on the Vim list is infected with a virus
that trawls through his address book and forges the From address. I too
get dozens of virus-laden
mwoehlke wrote:
I found a really annoying problem trying to build VIM 7 on HP-UX. I have
an automated script that builds VIM as part of a toolchain. It ran
through, and to my surprise and annoyance, installed VIM in /usr/local
instead of where I wanted it.
Long story short, the script called
Stefan Karlsson wrote:
These two sections in the documentation seems contradictory:
*gui-kde* *kde* *KDE* *KVim*
There is no KDE version of Vim. There has been some work on a port using
the Qt toolkit, but it never worked properly and it has
Dear Bram,
I think there ought to be a help tag for c_CTRL-] (either synonymous
with i_CTRL-] , resending to it, or with a similar text). What do you
think? Abbreviations are terminated the same way in Insert and
Command-line modes aren't they?
Best regards,
Tony.
Matt Sicker wrote:
On Monday 17 July 2006 03:40, Mikolaj Machowski wrote:
Dnia poniedziałek, 17 lipca 2006 17:09, Charles E Campbell Jr napisał:
As I recall, the vim7 kde port was dropped because there was no
maintainer for the port. I'm not a KDE
user myself, so I'm not a candidate, but
mwoehlke wrote:
A.J.Mechelynck wrote:
mwoehlke wrote:
Well, that was exciting... I recently tried to build vim 7 on OSS
(Tandem / HP Nonstop S-Series). I finally got it to work by diff'ing
the ITUG Floss sources (link below) against vim-6.1 and applying the
diffs to vim-7.0 (and by first
Nikolai Weibull wrote:
Here's a patch for :pwd that echoes the pwd with the attributes
specified by the Directory highlighting group.
What do you people think about this? Is it necessary, nice, silly,
stupid, unnecessary? I think that it makes sense, seeing as how it
prints a /directory/.
Ilya wrote:
A.J.Mechelynck wrote:
I prefer answers given on the command-line (with more if necessary)
to appear in the default colors with the following exceptions:
- It's OK for titles (as in the listing of autocommands) to appear in
another colour;
- It's OK for the xxx of :highlight
Nikolai Weibull wrote:
On 7/22/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
But wouldn't the default be aligned with the direcories of the netrw
buffer (which I want in a different colour), rather than with the Normal
group?
hi def link PwdDirectory Directory
but seeing as how you both don't
*tips.txt* For Vim version 7.0. Last change: 2006 Apr 30
at line 152, there is:
terminfo entry (retrieved with /usr/5bin/infocmp -C xterm). Both should
5bin is obviously a typo. One might think that sbin would be right.
However, on my system (SuSE 9.3) infocmp resides in /usr/bin, not
Marvin Renich wrote:
I am enhancing my cyclecolor script and would like to use another
buffer, but would like to do it as transparently as possible.
I use bufnr(filename, 1) to create a new buffer, then save the current
buffer number, switch to the new buffer, do some things, and switch
back.
Mikolaj Machowski wrote:
Hello,
Results of findfile() are inconsistent:
/home/mikolaj/a
/home/mikolaj/1/b
/home/mikolaj/2/c
/home/mikolaj/3/d
/home/mikolaj/3/4/e
1. We are in /home/mikolaj::
echo findifile(b, 1;)
1/b
2. We are in /home/mikolaj/2::
echo findifile(b,
Bill McCarthy wrote:
Hello Vim Developers,
I was timing the startup process by stepping though what I
think Gvim does (on Win XP Pro with 7.0.42).
gvim -u NONE -N
That starts up without _vimrc or _gvimrc or plugins and sets
nocp.
:so $vim\_vimrc
worked fine.
:so $vim\_gvimrc
Benji Fisher wrote:
On Wed, Jul 26, 2006 at 07:45:12AM +0200, A.J.Mechelynck wrote:
Bill McCarthy wrote:
Hello Vim Developers,
I was timing the startup process by stepping though what I
think Gvim does (on Win XP Pro with 7.0.42).
gvim -u NONE -N
That starts up without _vimrc or _gvimrc
Bill McCarthy wrote:
On Wed 26-Jul-06 12:45am -0600, A.J.Mechelynck wrote:
IIUC, it's a feature: \* means a literal asterisk. Not a very good
feature since IIUC, asterisks are not allowed in filenames on Windows.
Or can they happen in long file names?
I know \* means a literal asterisk
Bill McCarthy wrote:
On Wed 26-Jul-06 5:03pm -0600, A.J.Mechelynck wrote:
$HOME/vimfiles and $HOME/vimfiles/after should be in your 'rtp' (on
Windows); the first place where Vim looks for your _vimrc is $HOME even
though it is not in 'rtp'. (And BTW, $VIM should not be in your 'rtp'
either
Can't select bottom window by mouse-clicking
Happens every time. How to reproduce:
1. :set ch=2 wmh=0 wh= don't know if relevant
2. Open at least two horizontally split windows
3. Make some window current, other than the bottom one
4. Click the bottom status line.
Actual result:
Nothing
Cc to vim-dev list.
Robin Becker wrote:
A.J.Mechelynck wrote:
Robin Becker wrote:
A.J.Mechelynck wrote:
Robin Becker wrote:
..
'guifontset' being empty is usually not a problem; and 'guifont' can
be empty (giving some default font); but in any case you need
fonts installed
Charles E Campbell Jr wrote:
A.J.Mechelynck wrote:
Can't select bottom window by mouse-clicking
Happens every time. How to reproduce:
1. :set ch=2 wmh=0 wh= don't know if relevant
2. Open at least two horizontally split windows
3. Make some window current, other than the bottom one
4
Denis Perelyubskiy wrote:
hello,
I am trying to emulate textpad. In textpad, when cursor is over some
word and you press ctrl-f5 the search box pops up, and a word is in the
input area.
So, an equivalent behavior (at least for now :-)) in vim is to press
ctrl-f5 and have a word show up in the
Ulrich Lauther wrote:
Hi,
the automated mechanism for unsubsrcibing from this list still doesn't
work.
Could please someone remove me from the list?
Thanks,
The list is operated only by non-humans (computers and programs, I
mean). The people at fu-berlin math department will let the
Ulrich Lauther wrote:
Ulrich Lauther wrote:
Hi,
the automated mechanism for unsubsrcibing from this list still doesn't
work.
Could please someone remove me from the list?
Thanks,
The list is operated only by non-humans (computers and programs, I
mean). The people at fu-berlin math department
Ulrich Lauther wrote:
On Wed, Aug 02, 2006 at 09:47:05AM +0200, Ulrich Lauther wrote:
the automated mechanism for unsubsrcibing from this list still doesn't
work.
Actually it does! I just unsubscribed from my old address, and
subscribed using my new email address. Just follow the instructions
Mohsin wrote:
I want to use a highlighter mode on my text file, example:
:color_region bold line1 col1 line2 col2
:color_region bold 5 5 6 6
:color_region underline 5 5 6 6
I couldn't do this in vim. Vim only has syntax coloring with regexps.
Emacs has functions to apply properties to
Mohsin wrote:
I already tried your solution, it only works for a single region at a time
On applying the same higlighting to second region and the first one is
un-highlighted.
Try this (the third command will unhilight the first region):
:highlight User1 term=bold cterm=5 guibg=red
match
François Pinard wrote:
[Mikolaj Machowski]
[Mohsin]:
Vim only has syntax coloring with regexps. Emacs has functions to
apply properties to text blocks, and I was hoping vim has something
comparable.
Of course it is possible:
:help /\%l
:help /\%c
Humph, not really!
Text
Mohsin wrote:
The problem is I want to apply the highlighting to
multiple blocks of text simultaneously, so regexp doesn't help.
mohsin.
:help /\|
Best regards,
Tony.
Suresh Govindachar wrote:
[...]
[snip entire para Tony wrote.]
Tony,
Your comments aren’t applicable to Francois.
--Suresh
Oops, sorry, the entire email sounded like a pro-Emacs rant to me,
coming from that Mohsin guy who kept repeating I came from Emacs, and
your Vim regexps can't do it
Bug or feature? When running GUI-enabled Vim in a console (not possible
on W32, but on Unix it is), the has() and exists() functions do not
always reflect the _current_ reality. Examples:
:echo has(gui_gtk2)
1
In the above case it may be regarded as a feature: I can still check
Martin Krischik wrote:
[...]
I was hoping there is a way without unduly stuffing Brams E-Mail inbox...
Bram has the final say on what makes it into the official distribution
anyway. Just be sure the Subject: line of your email clearly indicates
what you're writing about.
Martin
PS: Take
François Pinard wrote:
[...]
I did not really take position about if Vim or Emacs are better than one
another, or wrong altogether :-). But I do have an opinion: both are
great editors, each with their own many virtues and few weaknesses, each
being a good source of inspiration and ideas for
Nikolai Weibull wrote:
[...]
However, it can sort of be simulated by having marks that stick to the
text position that they mark, instead of line + fixed column. (We
don't have this kind of mark at the moment.)
nikolai
IIUC, Vim's marks _are_ normally anchored to the text they mark, not
Nikolai Weibull wrote:
On 8/5/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
However, it can sort of be simulated by having marks that stick to the
text position that they mark, instead of line + fixed column. (We
don't have this kind of mark at the moment.)
IIUC
Yakov Lerner wrote:
On 8/6/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
On 8/5/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
However, it can sort of be simulated by having marks that stick
to the
text position that they mark, instead of line
Weiguang Shi wrote:
Hi,
I was wondering if there is a plan to add the feature of Normal-mode
editing within a visual block. This would be very useful when drawing
ASCII figures in Vim, when you want to focus on and make changes in
a region. I haven't seen so far scripts smart enough to
Nikolai Weibull wrote:
On 8/5/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
When breaking a line before a mark, the mark stays with the part-line
before the line break:
And I repeat: Bug?
No. That's just the way marks work. And it's a misfeature in my opinion.
It's always possible to add
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Bug or feature? When running GUI-enabled Vim in a console (not possible
on W32, but on Unix it is), the has() and exists() functions do not
always reflect the _current_ reality. Examples:
:echo has(gui_gtk2)
1
In the above case it may be
Yakov Lerner wrote:
After certain 3-step manipulation with tabs,
can't quit vim with :q!. (vim 7.0.42). Tabline is
not updated properly.
% vim -u NONE -U NONE
ixescmake 1st buffer modified
:tabnewcr create 2nd tab
ixescmake 2nd
Yakov Lerner wrote:
On 8/6/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
% vim -u NONE -U NONE
ixescmake 1st buffer modified
:tabnewcr create 2nd tab
ixescmake 2nd buffer modified
:tabclose! 1
Charles E Campbell Jr wrote:
Hello!
What is the message about (given on the subject line and here: modified
1.2.6.55 Tv1).
I get it when I'm using tags:
vi -t sometag
Regards,
Chip Campbell
P.S. I use vim 7.0, patches 1-42, huge debug-build.
Regards,
Chip Campbell
I don't get that
Ali Akcaagac wrote:
Hello Bram,
On my home Linux system I can easily compile and install every patch you
release for Vim, same applies for the MorphOS versions that I from time
to time create and release for our users but for Windows - which I need
to use at work - I am stuck with the *.exe
Mark S. Williams wrote:
Thanks, Tony.
I did some digging. The change in question was in svn revision 57. It
appears to have introduced some sort of order-of-declaration problem
between BCC and the rest of the world. ;-)
Below is an svn patch that works for me, and the svn diff for
Bram Moolenaar wrote:
Ali Akcaagac wrote:
On my home Linux system I can easily compile and install every patch you
release for Vim, same applies for the MorphOS versions that I from time
to time create and release for our users but for Windows - which I need
to use at work - I am stuck with
Gary Johnson wrote:
[...]
I've also come up with a solution for part of the problem, that of
Vim's insistence on converting a name like
/project/xyz/system/src/bar.c@@/main/42
(through chdir() and getcwd()) to a name like
Bill McCarthy wrote:
On Sun 13-Aug-06 7:41pm -0600, Steve Hall wrote:
A normal full install should have all or nearly all these (at least my
install here on Fedora Core 5 does):
vim70/autoload/
colors/
compiler/
doc/
ftplugin/
icons/
indent/
Gabriel Farrell wrote:
Hi,
Regarding a thread [1] back in February on this list about local
additions, I'm not seeing some of the errors remarked upon at that
time, but I do see 'matchit.txt' under the LOCAL ADDITIONS heading
even when it's not installed. If I do copy it into the doc directory
Bram Moolenaar wrote:
Alexey I. Froloff wrote:
* Bram Moolenaar Bram@ [060808 22:52]:
! call system(a:cmd . ' . nmt . ')
This patch is evil (:-E~~~). Better add shellescape() function
to Vim and properly escape argument.
Well, at least it's a lot better than what it was. I know it
Philipp M. Frank wrote:
Hi,
I've been looking for a 7.0-compatible version of the conceal-patch [1],
but so far I have been unsuccessful.
Does anyone know if this patch is still maintained or should I try to
adapt it to 7.0 myself?
(To those not familiar with the conceal-functionality: it
After applying the latest 10 patches (54-63) to Vim, I get a number of
warnings (below). Since the compile proceeds to completion, I shall
install the resulting executable; but you may (or may not) want to
investigate this more deeply. I don't feel competent to determine which
of these
Mark S. Williams wrote:
I think I've uncovered an odd bug involving Netrw and the cindent local
buffer option for Java files, where cindent is unset under certain
conditions.
To track down the bug I removed all my Java file type plugins and
created a new Java file type plugin called java.vim
Christian MICHON wrote:
Hi vim-devers,
I'm currently trying out git (linux scm) and I have not found yet
how to perform a gvimdiff on a file locally modified with the latest
commit.
Is there a simple/easy way out for this issue ? Any git
specialist amond vim-dev who could give me a hint ?
Gaspar Chilingarov wrote:
Hello!
Are there any common method to return values from
ex_func_T type functions which are defined in
CMD_index in ex_cmds.h (external command handlers - say perl/ruby and etc)?
I would like to return function execution result to calling script - say
string, or list.
Gaspar Chilingarov wrote:
Hi all!
IIUC, ex_func_t means void *, i.e., a pointer to anything. You would
still need to know what type of object (a pointer to what) the function
you're calling is actually returning.
well, I'm going to write if_* script to integrate vim with erlang -- so
I
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Under :help starstar-wildcard it is said that the ** wildcard goes up
to 100 levels deep.
Under :help starstar it is said that it goes up to 30 levels deep by
default, but that any integer value in the range [0,255] can be
explicitly specified.
Bram Moolenaar wrote:
Yasuhiro Matsumoto wrote:
vim can't treat ff and fenc, bin option on modelines. We can specify
'fencs' for judging some encodings. But vim often mis-judge when opening a
text file. If we can set 'fenc' on modeline, vim won't fail.
I wrote a patch for this support.
Brad Beveridge wrote:
[...]
Potential issues :
[...]
- I am not familiar with autoconf stuff, so this patch does not
integrate with the make system of Vim, somebody probably needs to add
it to config.in. There were too many diffs in the various files that
I thought to check, and I didn't
Pierre Habouzit wrote:
Le ven 25 août 2006 17:38, Christian MICHON a écrit :
nice madcoding :)
work in bash, but not tcsh.
I said *decent* shell :P
Thanks anyway: I learned something new from it
you're welcome.
Oh, so tcsh is an indecent shell then... :-Þ
Best regards,
Tony.
Zdenek Sekera wrote:
Perhaps a strange question so maybe a small explanation
of why is in order:
When I :source or :runtime a *.vim file, commands in that
file build a buffer. To know when the buffer is complete,
I have to know what follows, and if complete (because
the following has an
Hello,
Changing a file's 'fileencoding' or 'fileformat' (or 'eol' when 'binary'
is set) sets the 'modified' flag, but setting or clearing 'bomb'
doesn't, even for Unicode files (e.g. enc == utf-8, fenc == or
fenc == utf-8). Now with, for example, 'bomb' set, if the disk file
is Unicode
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Changing a file's 'fileencoding' or 'fileformat' (or 'eol' when 'binary'
is set) sets the 'modified' flag, but setting or clearing 'bomb'
doesn't, even for Unicode files (e.g. enc == utf-8, fenc == or
fenc == utf-8). Now with, for example, 'bomb'
Gautam Iyer wrote:
On Wed, Aug 30, 2006 at 07:17:16PM +0200, Stefano Zacchiroli wrote:
I agree with the comment that plain TeX users may also define such
sectioning commands. Maybe it would be safe if you check for such
definitions, using an include-file search ... but of course, that is
more
Alexey I. Froloff wrote:
filetype.vim looks like:
augroup filetypedetect
...
Generic configuration file (check this last, it's just guessing!)
au BufNewFile,BufRead,StdinReadPost *
\ ... some files are being setf'ed to conf
Use the plugin-filetype checks last, they may overrule any
Yakov Lerner wrote:
When 'acd' is set, 'vim -S' open files in wrong directory.
To reproduce:
1. make your ~/.vimrc 1-liner 'set acd'
(Alternatively, use use vim -u NONE -c 'set acd' instead of vim
in commands below).
2. vim ~/xxx# or
:he options.txt
now you have two
Alexey I. Froloff wrote:
* Bram Moolenaar Bram@ [060831 00:14]:
The current method is correct. In the ftdetect scripts you can check
for 'filetype' being equal to conf and then do :set ft=anything to
overrule it. Use :setf only when you don't want to overrule the
default filetype.
I want
1 - 100 of 331 matches
Mail list logo
