On 5/29/07, Nico Weber [EMAIL PROTECTED] wrote:
What do you think? I prefer (c) from implementation, efficiency and
intuitivity perspective.
I agree. Strongly.
Yes, I agree with (c) , too. I suggested once new type of options to vim that
behaved both like boolean, and numeric. But Bram
On 5/29/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/29/07, Nico Weber [EMAIL PROTECTED] wrote:
What do you think? I prefer (c) from implementation, efficiency and
intuitivity perspective.
I agree. Strongly.
Yes, I agree with (c) , too. I suggested once new type of options to vim
On 5/14/07, Václav Šmilauer [EMAIL PROTECTED] wrote:
Hello,
I submit patch that implements the 'breakindent' feature. It is on vim todo
list, since the moment I tried a few years ago (see e.g.
http://marc.info/?l=vim-devm=109921292009721w=1). Picture says what it's
about (showbreak is aligned
On 5/14/07, Václav Šmilauer [EMAIL PROTECTED] wrote:
Hello,
I submit patch that implements the 'breakindent' feature. It is on vim todo
list, since the moment I tried a few years ago (see e.g.
http://marc.info/?l=vim-devm=109921292009721w=1). Picture says what it's
about (showbreak is aligned
On 5/28/07, Iain Murray [EMAIL PROTECTED] wrote:
On 26/05/07, Iain Murray [EMAIL PROTECTED] wrote:
On 26/05/07, Yakov Lerner [EMAIL PROTECTED] wrote:
I believe you can achieve what you want using 'cmap expr' cleverly.
...
I might still attempt a patch. Having the space replacement actually
On 5/25/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
John Beckett wrote:
A.J.Mechelynck wrote:
What about a different function to return, say, the number of
1K blocks (or the number of times 2^n bytes, with a parameter
passed to the function) that a file uses?
Yes, that's a much
On 5/26/07, Iain Murray [EMAIL PROTECTED] wrote:
Hi,
Searching for hello world in vim doesn't match hello\nworld.
This is annoying when editing documents. The solution is to
search for hello\_sworld. But it is frustrating to type \_s
instead of a space in every search.
I have been getting
On 5/9/07, Edward L. Fox [EMAIL PROTECTED] wrote:
If you had checked out a copy of the sources before, please run this
command in your source root directory to switch into the current
branch:
svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
This switch command gives me
On 5/5/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
I compared runtime files form ftp [1] and from svn [2].
Both vims are labeled vim71a. But many runtimes are different.
In svn, many files are labeled 2007. In ftp, they are 2006 versions.
Why
On 5/8/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 5/5/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
I compared runtime files form ftp [1] and from svn [2].
Both vims are labeled vim71a. But many runtimes are different
On 5/8/07, Yakov Lerner [EMAIL PROTECTED] wrote:
Full diffs are attached. Diffs are produced by the script diff-vim-ftp-svn.sh,
also attached.
Re-sending attachments which came out zero-length in previous email.
Yakov
diffs
Description: Binary data
diff-vim-ftp-svn.sh
Description: Bourne
On 5/6/07, Martin Krischik [EMAIL PROTECTED] wrote:
Am Sonntag 06 Mai 2007 schrieb Yakov Lerner:
On 2007-05-05, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
I tried to build vim7.1 from svn. But all I get from usual
svn location (https
The patch adds flag to search() flag to not use smartcase.
'*' and '#' do not use smartcase, but search() always uses smartcase
(cannot be turned off).
When we use search() with @/ pattern that comes from * or #,
search() fails because of discrepancy in smartcase handling.
Yakov
---
On 5/3/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
The patch adds flag to search() flag to not use smartcase.
'*' and '#' do not use smartcase, but search() always uses smartcase
(cannot be turned off).
When we use search() with @/ pattern that comes from
On 5/1/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 4/30/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[This is development, removed the Vim maillist]
Yakov Lerner wrote:
On 4/29/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 4/29/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov
On 4/30/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[This is development, removed the Vim maillist]
Yakov Lerner wrote:
On 4/29/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 4/29/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
Wish: when search is slow, show
On 4/29/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 4/29/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
Wish: when search is slow, show the progress line number
every second on the bottom line (like, 12345 of 9).
What is slow?
To my taste, when something takes
On 4/29/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
Wish: when search is slow, show the progress line number
every second on the bottom line (like, 12345 of 9).
What is slow?
To my taste, when something takes longer than 1-2 sec,
I'd prefer some visual feedback
The svn tree has all patches already inside, it does not matter
how many patches are there. You just checkout and build.
It's not that you need to download baseline and then 222 patches, no.
Yakov
On 4/27/07, Jonathan Smith [EMAIL PROTECTED] wrote:
With the insane number of patches collecting
On 4/24/07, Ilya Sher [EMAIL PROTECTED] wrote:
Robert Lee wrote:
[snip]
Counterwish #2: Dump VimScript and replace it with EMCAScript (maybe
using SpiderMonkey) so that people don't need to learn a new language
As a sarcastic joke, this sounds average. But seriously, vim
having supprt for
On 4/24/07, Gregory Seidman [EMAIL PROTECTED] wrote:
On Tue, Apr 24, 2007 at 05:49:19PM +0200, Nikolai Weibull wrote:
On 4/24/07, Gregory Seidman [EMAIL PROTECTED] wrote:
On Tue, Apr 24, 2007 at 10:49:49AM +0300, Ilya Sher wrote:
Robert Lee wrote:
[snip]
Counterwish #2: Dump VimScript
On 4/24/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Multi-line matches are not always displayed correctly. A match is
searched for in the line where redrawing starts, which can be anywhere.
Your pattern only matches when redrawing starts at or before line 4078.
Maybe we need a pattern that
Hello Bram,
Is it possible to add this item to the vim voting list ?:
collaboration of N vim instances editing same file
-- Ability of N instances of vim to absorb, merge and show changes
to the same file made by other running vim instances [ either by reading
other vim's swapfiles, or
Hello Bram,
Maybe vim would better set eol/noel after ':r !cmd' also,
no only after reading the file into buffer ? (that is, the condition
whether input had final \n or not).
As I can see currently, this piece of info is lost after ': !cmd' ?
Yakov
On 2/24/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
-char_u di_key[1]; /* key (actually longer!) */
+char_u di_key[]; /* key (actually longer!) */
I think this is c99 vs c89 difference. C99 allows x[] as last member
of the struct, but c89 does not. As Bram mentioned,
On 2/4/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Alexei Alexandrov wrote:
I'm doing some performance investigations of Vim code trying to
understand whether there are any possibilities to improve it.
Currently I've made the following observations (all investigations are
done on Windows):
In the script below, where # and n are remapped,
n goes the wrong direction after #. To see:
vim -u NONE bad.bim
:so %
gg/bacrnnn#n
-- the last n goes forward. we expect it to move backward.
But when script is rewritten to the form #2, then n after # works
correcty. Plain moving the
On 11/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
It bothers me how when switching between tabs (gt) or switching between
buffers (:bn, :bp), sometimes a buffer will end up being
shifted/scrolled up/down within its window.
For the occasions that I want to shift the buffer I have keys like
On 11/2/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hello,
I'm pretty new to this mailing list and I hope I'm posting at the
right place. I just want to report a simple bug, easy to reproduce.
I have only tested it on Windows.
Open vim, write a single 1 characters line (filled with
On 11/2/06, Steve Hall [EMAIL PROTECTED] wrote:
From: dotpanic dotpanic homelinux.org, Thu, November 02, 2006 6:11 am
I'm pretty new to this mailing list and I hope I'm posting at the
right place. I just want to report a simple bug, easy to reproduce.
I have only tested it on Windows.
On 10/31/06, Виктор Кожухаров [EMAIL PROTECTED] wrote:
Hello,
I'm working on a syntax file for .edc files. The problem before me is
that I want to use a different syntax file for a script part. I've
created the syntax file for the script syntax, and I've read how yto use
syn include.
The real
On 10/23/06, Nikolai Weibull [EMAIL PROTECTED] wrote:
On 10/23/06, Mikolaj Machowski [EMAIL PROTECTED] wrote:
Hello,
I understand that escape() was primarily designed to escape strings when
passing to system functions, but personally I never used that and in
didn't noticed such use in
Almost every plugin begins with this check:
if exists(g:plugin_name) | finish | endif
let g:plugin_name = 1
I understand this tries to save time if vim tries to load plugins 2nd time.
But aren't plugins loaded only at vim startup ? Does vim *ever*
ever try to load plugins 2nd time ? In
On 10/20/06, Peter Hodge [EMAIL PROTECTED] wrote:
--- Yakov Lerner [EMAIL PROTECTED] wrote:
Almost every plugin begins with this check:
if exists(g:plugin_name) | finish | endif
let g:plugin_name = 1
I understand this tries to save time if vim tries to load plugins 2nd time
Of different current methods to access vim sources (svn, ftp, rsync, etc)
which one is fastest to be updated when new patch is issued, and
also has most reliable/fast server ?
Yakov
On 10/13/06, David Schweikert [EMAIL PROTECTED] wrote:
Would it be possible to make Vim overwrite a backup file only if
the buffer was actually modified? Look at the following scenario:
1. I edit file foobar.txt, make some change and save it.
- the backup file foobar.txt~ is created
2. I
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
While replying to a post on the vim users' list, I noticed a slight
problem. The diff commands set some options, but this is not reported
with verbose set. For example
:e foo.txt
:set fdm=marker
:diffsplit
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
While replying to a post on the vim users' list, I noticed a
slight
problem. The diff commands set some options, but this is not reported
On 10/13/06, Corinna Vinschen [EMAIL PROTECTED] wrote:
Hi,
I got a report on the Cygwin mailing list that the following message
appears when trying to open /etc/hosts in vim:
E303: Unable to open swap file for /etc/hosts, recovery impossible
What happens is this:
/etc/hosts is by default a
I observe strange behaviour related to 'set shortmess+=T' . Sometimes
this 'T' flag shortens long messages, sometimes it does not.
To see:
1.
vim -u NONE
2.
:set nocp shortmess=aT
:nmap ZB :echomsg repeat('a',co+10)cr
3.
Press ZB. You get long message and 'Press Enter' prompt.
4.
Type
:norm ZBcr
I suggest new flag for 'viminfo'; flag to turn on the *last-position-jump*
functionality (say, letter j). Such it will be much easier method to
turn on the last-position-jump functionality. With new flag, it will be mere:
:set viminfo='20,50,s10,j
or
:set viminfo+=j
-- as easy as
On 10/7/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
I suggest new flag for 'viminfo'; flag to turn on the *last-position-jump*
functionality (say, letter j). Such it will be much easier method to
turn on the last-position-jump functionality. With new flag
On 10/6/06, Bill McCarthy [EMAIL PROTECTED] wrote:
On Thu 5-Oct-06 8:54pm -0600, Gary Johnson wrote:
gvim -u NONE -i NONE -N
Setting -u NONE -i NONE -N is all that's needed. See :help -u.
I never noticed that 'vim -u NONE' ever read the .viminfo ?
For example, if I set 'set nocp' in
On 10/6/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Peter Hodge wrote:
[...]
I wouldn't think the -i option is necessary, because 'viminfo' is empty by
default anyway. [...]
The 'viminfo' option is not empty by default, except in 'compatible' mode (see
-u option forces 'compatible' on.
On 10/5/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
CursorHold is suppsed to be triggered in normal mode
after updatetime, correct ? But in the scenario below,
when vim gets into normal mode after insert mode,
CursorHold is not triggered:
1. vim -u NONE -U NONE
2
CursorHold is suppsed to be triggered in normal mode
after updatetime, correct ? But in the scenario below,
when vim gets into normal mode after insert mode,
CursorHold is not triggered:
1. vim -u NONE -U NONE
2. :let x=0
3. :let ut=200 just some low value
3. :au CursorHold * let
On 10/3/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
On 10/1/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
One thing that really annoys me with Vim is the limits it emposes on
what names are legal for user-defined functions and commands. I know
On 10/3/06, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Bram Moolenaar wrote:
Suresh Govindachar wrote:
Is it possible to add an autocommand-event for Clipboard Changed?
Not really. This is not something that happens inside Vim. Polling for
changes in the system is not really
I observe that CursorHold is not triggered when cursor
in spending long time in commandline, correct ?
Is it possible to trigger CursorHold also when cursor is
in command line ? (Maybe by some :au CursorHold
commandline syntax ?)
BTW does all this mean that if I enter commandline (:) within
On 9/30/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Sometimes people ask me for a command to search for the text that is
currently visually selected. You could add a mapping for the '/' key,
but then you lose the possibility to extend the visual area by
searching for a pattern.
Since we might
On 9/30/06, Georg Dahn [EMAIL PROTECTED] scribbled:
Hi!
Bram Moolenaar wrote:
/ search for the Visually selected text forward
? same, backward
Is there a good alternative?
I think, this is ok. For the moment I have the following lines
...
vnoremap expr *
On 9/30/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Sometimes people ask me for a command to search for the text that is
currently visually selected. You could add a mapping for the '/' key,
but then you lose the possibility to extend the visual area by
searching for a pattern.
Since we might
On 9/25/06, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Just a suggestion -- I'd appreciate a WinClose event. BufWinLeave would
almost do, but if two or more windows are open on the same buffer, then
no event. WinLeave fires whenever one changes windows, which isn't
what I want, either.
On 9/13/06, Ian Kilgore [EMAIL PROTECTED] wrote:
On Wed, Sep 13, 2006 at 11:27:43AM +0300, Yakov Lerner wrote:
Nice. So simple. I have couple of comments.
Thank you :)
1. Don't you need to reset 'paste' back to 'nopaste' when
high cps stops ?
There is a hastily coded version of the patch
I noticed that :redraw works differently from Ctrl-L in certain situations:
1) vim -u NONE
:set laststatus=2 statusline ruler
:help help get some text
2) Let's cause some screen mispaininting, so we can test :redraw:
:silent! !echo aaa cause mispainted screen (this
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote:
After recompiling Vim with -D_FILE_OFFSET_BITS=64, everything
involving tags break, including the help system. Typing :h,
or pressing ^] to jump to a tag, causes Vim to get caught in an
infinite loop.
Is there another way to get large file
On 9/14/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote:
After recompiling Vim with -D_FILE_OFFSET_BITS=64, everything
involving tags break, including the help system. Typing :h,
or pressing ^] to jump to a tag, causes
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote:
After recompiling Vim with -D_FILE_OFFSET_BITS=64, everything
involving tags break, including the help
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote:
After recompiling Vim with -D_FILE_OFFSET_BITS=64
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/14/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/14/06, Haakon Riiser [EMAIL PROTECTED] wrote
Vim patches submitted by external submitters are either
'incorporated' or 'outsude of vim sources'. That's black-and-white.
I thought it's possible to add some intermediate state, where
'experimental-patch' is neither outside of vim nor inside-vim. This
is useful because people can try
I see a case in which winrestview() work incorrectly after PageDown
near end-of-file. (This is in the context of scrollfix plugin.)
To reproduce:
% vim -u NONE -c 'so x.vim'# x.vim is below
:help help have some text
:set nu see line numbers
press seevral
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
It is fairly easy to check for inconsistencies in Binary, Octal, and Hex
I'm afraid C does not notion of binary numbers.
Yakov
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
It is fairly easy to check for inconsistencies in Binary, Octal, and Hex
I'm afraid C does not notion of binary numbers.
Yakov
On some systems that answer is correct
On 9/11/06, Nikolai Weibull [EMAIL PROTECTED] wrote:
On 9/11/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
[a way to create a list of what patches has been applied]
Here's a simpler version of that script that doesn't allow for patches
to be skipped. I don't know if the Vim build scripts
On 9/12/06, Mark Manning [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
It is fairly easy to check for inconsistencies in Binary, Octal,
and Hex
I'm afraid C does
This patch adds 'extrahuge' build size, which is
huge+interpreters (spelled as --with-features=extrahuge
or --with-features=allinterp).
Yakov
P.S. Maybe --with-features=max is better name.
patch-extrahuge
Description: Binary data
On 9/10/06, Mark Manning [EMAIL PROTECTED] wrote:
In the syntax stuff, the c.vim file should be changed to have the following:
Old:
syn regioncStringstart=++ skip=+\|\\+ end=++
contains=cSpecial
New
syn regioncStringstart=++ skip=+\||'+ end=++
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
(If I
put in echo version it comes back as 700. Even the 7.0.17 version
comes back as 700
Output of ':echo version' does not reflect patchlevel. (the .17 in
7.0.17 is patchlevel).
You can see the patchlevel on the initial splashscreen, or
in
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
Hey, I hate to keep barging in here asking questions and such but here
is a new one. :-)
In the new basic.vim file I am having a problem. In FreeBasic you can
use both single as well as double quotes to enclose a string.
Unfortunately, you can
-- Forwarded message --
From: Mark Manning [EMAIL PROTECTED]
Date: Sep 11, 2006 1:43 AM
Subject: Re: New question
To: Yakov Lerner [EMAIL PROTECTED]
Ok, tried it and it works! :-)
Thanks! :-)
Mark
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
I saw in the c.vim that there was an error statement for octal numbers.
There isn't one for hex numbers so I made one really quickly. If you
want, just put it into the c.vim file. :-)
The test:
syn regioncHexErrorstart=0x\x*[g-zG-Z]
Hello,
The biggest build size that exists now (the --with-features) is 'huge'.
This 'huge' still does not include interpreters.
What does public and Bram think about adding another build size
('extra-huge') that includes [all] interpreters ?
What is your feeback ?
Yakov
Possible namings:
On 9/8/06, Mark Manning [EMAIL PROTECTED] wrote:
I believe I may have found an obscure bug. It is not a harmful bug. It
does not make VIM crash or do weird things. (Well, sort-of.) :-)
Here is how to reproduce it:
First you have to have a lot of open and close braces (}). They
do
On 9/7/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
I see several problems (that I can't explain) in the vim refresh-loop
watching the growing file (a-la 'tail -f'). Vim commands are below.
Problem #1: There is unexpected output on the bottom line
On 9/7/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/7/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
I see several problems (that I can't explain) in the vim refresh-loop
watching the growing file (a-la 'tail -f'). Vim commands are below.
Problem #1
Giving buffer new name in different directory does not change
to new directory, when 'acd' is set. This does not sound right,
taking into account that switching buffers to and back makes
current directory right.
To reproduce:
% vim -u NONE ~/xxx
:set acd
:he acdto have 2nd buffer
I see erratic screen redraw (namely, curshor shown
past last line of file, or on wrong line (which is not line('.'))).
This vim 7.0.86 taken from svn today, including recent
fix to winrestcmd().
It happens after certain winrestview() when 'showcmd' is set.
This code works ok with 'noshowcmd'.
On 9/3/06, Ilya [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
When I removed both 'keepend' and 'extend', it
started to work as expected.
No, it would not work as I want it to. Block would not end unclosed
String. Like this:
{ Some string with a quote ( ) inside }
Ah, I have a guess what
On 9/2/06, Ilya [EMAIL PROTECTED] wrote:
Hello.
I have a question regarding syntax matching. I have some kind of syntax
and I have some solution to highlight it, but it does not work the way I
expect it to.
What I want: match syntax that consists of blocks (enclosed in {}),
strings (enclosed
On 9/3/06, Ilya [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
When I removed both 'keepend' and 'extend', it
started to work as expected.
No, it would not work as I want it to. Block would not end unclosed
String. Like this:
{ Some string with a quote ( ) inside }
What about the following
On 9/3/06, Ilya [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/2/06, Ilya [EMAIL PROTECTED] wrote:
Hello.
I have a question regarding syntax matching. I have some kind of syntax
and I have some solution to highlight it, but it does not work the way I
expect it to.
What I want: match
On 9/2/06, Ilya [EMAIL PROTECTED] wrote:
Hello.
I have a question regarding syntax matching. I have some kind of syntax
and I have some solution to highlight it, but it does not work the way I
expect it to.
What I want: match syntax that consists of blocks (enclosed in {}),
strings (enclosed
On 9/1/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
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
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 files open: (1) ~/xxx
On 8/30/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
On Sun, Aug 27, 2006 at 02:40:24PM +0200, Bram Moolenaar wrote:
Apparently the sorbs blacklist mechanism is still being used, causing
trouble for some people. I have asked the mail server maintainer to
remove
The following does not work as expected. I wonder
whether it is a bug or a feature:
cabbr XXX c-R=xyz.Left()cr
function! Left()
return \Left
endfun
Instead of repositioning cursor left, I get
:[EMAIL PROTECTED]
I know It is possible to make it work via feedkeys(), but this
[EMAIL
This is filetype.vim patch and syntax for initng config files.
Initng is bold new replacement for sysv-init, http://initng.thinktux.net
Those config files sit under /etc/initng/** and have extension *.i
Distinguishing them from other *.i files is easy, they have
#!/bin/itype in the 1st line.
On 8/17/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Vince Negri wrote:
I'm still alive, just very busy :-)
New home for conceal patches is:
http://vince.negri.googlepages.com/
[...]
OK. I've updated my W32 and Unix HowTo (compile Vim) pages to mention
this, and while I was at it, I've
I want to suggest different format of features listing in output of :version.
Namely, I suggest that all included features go first in one list, and
after them, all excluded go in another list. I think this is more readable
than existing format, in which both (+) and (-) features are mixed in a
On 8/12/06, Gary Johnson [EMAIL PROTECTED] wrote:
I just finished troubleshooting a problem that had several
contributing factors, one of which was the way Vim's mch_FullName()
function behaves with ClearCase versioned file names.
If you open a file under ClearCase using the full path name and
On 8/12/06, mwoehlke [EMAIL PROTECTED] wrote:
Bram Moolenaar wrote:
hundred-and-one symptoms of being an internet addict:
256. You are able to write down over 250 symptoms of being an internet
addict, even though they only asked for 101.
So where is the complete list? ;-)
I believe
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 buffer modified
On 8/4/06, Martin Krischik [EMAIL PROTECTED] wrote:
How are updates to the runtime files submitted?
You email them to Bram.
Yakov
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 + fixed column. (We
On 7/28/06, Nikolai Weibull [EMAIL PROTECTED] wrote:
On 7/27/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Vim uses the X server for communication. Only users with write access
to the X server can send a message to Vim. And if you have write
access, you are also able to send keystrokes to
On 7/26/06, Marc Weber [EMAIL PROTECTED] wrote:
I did notice that you can do
su
gvim
:echo SERVERNAME
and then using another user
gvim --servername=GVIMxx --remote-send='!/dowhatyouwant ;-)'
Marc,
In case you are talking X11:
D you have x11 authorization enabled or disabled ?
Command 'xhost'
On 7/26/06, Marc Weber [EMAIL PROTECTED] wrote:
Marc,
In case you are talking X11:
D you have x11 authorization enabled or disabled ?
I've been taking x11.
I did modify xhost because I wanted a php script be able to launch vim.
But I've restarted X now and xhost - shows the same as xhost. It
1 - 100 of 130 matches
Mail list logo
