Hi,
I sent this comment in a reply to another mail, seems it got lost. I'm
resending it in a "thread" on its own:
When I have a completion menu that's long, but still completely fits the
current window (say, 30 entries) and I hit hit or the whole
list is redrawn (ie, it flickers). Is there
On Sun, 16 Apr 2006 22:58:07 -0400
Benji Fisher <[EMAIL PROTECTED]> wrote:
> > When I start the Vim beta here[1] things work great. However, dropping
> > to the shell with :sh and then trying to start another copy of vim
> > results in a crash. Same thing happens when doing :!vim, that is:
>
Hi!
> Sorry, I meant to suggest trying
>
> :verbose hi Constant
>
> When I try this, it tells me that the Constant highlighting was set in
> $VIMRUNTIME/syntax/syncolor.vim .
> This file is :source'd after the :syn on command. In your gvimrc
> file, do you have the lines to override the de
Hi,
In the following cases:
:com -complete=custom,some#file#Something ...
:com -complete=customlist,Something
the -complete part is shown as an error. I guess the path#to#Something
way of specifying functions needs to be included.
Thanks,
Srinath
On Sun, Apr 16, 2006 at 05:56:19PM +0200, Nikolai Weibull wrote:
> On 4/16/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> >
> > Nikolai Weibull wrote:
>
> > > :x.
> > >
> > > and again position the cursor over/at the trailing space. Again execute
> > >
> > > :echo expand('')
> > >
> > > The expa
On Sun, Apr 16, 2006 at 10:49:35PM -0400, sean wrote:
> Hi,
> First off, thanks for a great editor! Sorry to be dropping in with a
> problem ;o)
>
> When I start the Vim beta here[1] things work great. However, dropping
> to the shell with :sh and then trying to start another copy of vim
> res
Hi,
First off, thanks for a great editor! Sorry to be dropping in with a
problem ;o)
When I start the Vim beta here[1] things work great. However, dropping
to the shell with :sh and then trying to start another copy of vim
results in a crash. Same thing happens when doing :!vim, that is:
Vi
On Sun, Apr 16, 2006 at 02:57:37PM +0200, Georg Dahn wrote:
> Hi!
>
> Since I dislike the highlights of 'Constant' and 'Title', which is
> Magenta as default, I have defined in my gvimrc:
>
> hi Constant guifg=Maroon
> hi Title guifg=Maroon
>
> I have no 'colo ...' or 'set background=...'. When
Hi Bram,
Thanks for implementing list[M:N] truncation when N > length(list)!
On 4/16/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> > function :Close()
> > ...
> >
> > What do you think?
>
> Much to complicated. In nearly all situations you can simply prepend
> an ID to the global name, such
> I used to build Vim from CVS usin a-a-p. After seeing the
> announcements for 7.0d and 7.0BETA, I tried updating from CVS but
> didn't get anything. Is anyone else seeing this problem?
The CVS for non-developers apparently still doesn't work.
http://sourceforge.net/docman/display_doc.php?docid
I used to build Vim from CVS usin a-a-p. After seeing the
announcements for 7.0d and 7.0BETA, I tried updating from CVS but
didn't get anything. Is anyone else seeing this problem?
TIA,
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net/blog
On Sun, Apr 16, 2006 at 05:47:37PM +0200, Bram Moolenaar wrote:
> > To try it out, put the following in an empty buffer:
> >
> > :x.
> >
> > And position the cursor over/at the trailing space. Then execute
> >
> > :echo expand('')
> >
> > The expansion will be empty.
> >
> > Now, change t
Hi!
If you didn't want a black foreground colr, then why did you specify a
black foreground color?
This is only an example to reproduce that behavior.
If you want to reset the colors you need to use ":hi clear".
It's not totally logical, but that's how it works.
If it's like that, then it
Georg Dahn wrote:
> I think, the following behavior is a bug:
>
> The highlight 'Title' is not reset by doing 'set bg=dark' which should
> set the highlights to the defaults of the black background or reload the
> color scheme. It should be reset to #ffa0a0 as far as I can remember
> (the sam
On 3/31/06, Aaron Griffin <[EMAIL PROTECTED]> wrote:
> The file: $VIMRUNTIME/syntax/terminfo.vim
> Line 77 needs to be changed from:
> syn match terminfoParameters
> '%\('[A-Z]'\|{[0-9]\{1,2}}\|p[1-9]\|P[a-z]\|g[A-Z]\)'
> to:
> syn match terminfoParameters
> '%\(\'[A-Z]\'\|{[0-9]\{1,2}}\|p[1-9]\|P[
On 4/16/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
> Nikolai Weibull wrote:
> > :x.
> >
> > and again position the cursor over/at the trailing space. Again execute
> >
> > :echo expand('')
> >
> > The expansion will be ':x.'.
>
> I don't see this, the result is empty both times. Are you sur
Nikolai Weibull wrote:
> I think that find_ident_at_pos contains a bug. The thing is that
> expand("") expands to a non-empty string if positioned over a
> whitespace character after a WORD at the start of a line, but to an
> empty string anywhere else. I doubt that this is intentional, but it
Hi!
I think, the following behavior is a bug:
The highlight 'Title' is not reset by doing 'set bg=dark' which should
set the highlights to the defaults of the black background or reload the
color scheme. It should be reset to #ffa0a0 as far as I can remember
(the same as 'Constant'):
1. sta
Hi!
In the meantime I found another one: Could you please set MatchParen
differently, because with a dark background a light foreground and Cyan
don't fit. I suggest setting guifg to bg or Black.
How about using guibg=DarkCyan?
Looks OK to me, it is much better!
Best wishes,
Georg
Send i
Hi!
What does
:verbose hi Constant guifg=Maroon
show?
Nothing. But the Constants are Maroon afterwards.
In addition to the above sort of debugging, you can add a line like
let g:foo = "2006 April 16 background=" . &background
to your color scheme file. The date stamp is to avo
Announcing: Vim (Vi IMproved) version 7.0e BETA
This is the fourth BETA release of Vim 7. It appears to be quite stable
and about ready for daily use, but I would like to do some more testing
to be sure.
We are getting closer to a release. Please report every problem you
find!
Since the thi
I think that find_ident_at_pos contains a bug. The thing is that
expand("") expands to a non-empty string if positioned over a
whitespace character after a WORD at the start of a line, but to an
empty string anywhere else. I doubt that this is intentional, but it
seems that at least the rubycompl
On Sun, Apr 16, 2006 at 02:57:37PM +0200, Georg Dahn wrote:
> Hi!
>
> Since I dislike the highlights of 'Constant' and 'Title', which is
> Magenta as default, I have defined in my gvimrc:
>
> hi Constant guifg=Maroon
> hi Title guifg=Maroon
>
> I have no 'colo ...' or 'set background=...'. When
Hi!
I suppose you wanted to send your answer to the list, so I have put the
email address of the list as CC.
Well, is already used for indentation or inserting spaces/tabs
till you are at the next tabstop. So your suggestion would produce much
more confusion.
However, you can map it, if y
Georg Dahn wrote:
> > Right, I forgot to change grey90 into something else. I never
> > work with a dark background and my monitor is set at a low brightness
> > that makes things with a dark background look bad. I'll assume that
> > the grey40 you suggest will work for most people.
>
> Th
Georg Dahn wrote:
> Ok, let's assume there are several completions, such that you get a menu
> with . Then if you move the selection with the cursor keys and
> press , the selected item is being chosen. If you do the same
> with (instead of using cursor keys), inserts a new line. I
> think,
Hi!
Ok, let's assume there are several completions, such that you get a menu
with . Then if you move the selection with the cursor keys and
press , the selected item is being chosen. If you do the same
with (instead of using cursor keys), inserts a new line. I
think, this is confusing.
Is
Hi!
Since I dislike the highlights of 'Constant' and 'Title', which is
Magenta as default, I have defined in my gvimrc:
hi Constant guifg=Maroon
hi Title guifg=Maroon
I have no 'colo ...' or 'set background=...'. When gVim is open, the
Title is Maroon, but the Constant still is Magenta. Sinc
Hi,
In the meantime I found another one: Could you please set MatchParen
differently, because with a dark background a light foreground and
Cyan don't fit. I suggest setting guifg to bg or Black.
That's bugging me too.
Something else: When I have a completion menu that's long, but still
compl
Hi!
> Right, I forgot to change grey90 into something else. I never
> work with a dark background and my monitor is set at a low brightness
> that makes things with a dark background look bad. I'll assume that
> the grey40 you suggest will work for most people.
Thanks!
In the meantime I found
Marc Weber wrote:
> I'm restructuring my vim scripts and I'm not sure in which namespace to
> put some functions/ commands/ maps.
>
> By now there are these namespaces (copied from vim
> help) as far as I know
> |buffer-variable|b: Local to the current buffer.
> |window-variable|
I'm restructuring my vim scripts and I'm not sure in which namespace to
put some functions/ commands/ maps.
By now there are these namespaces (copied from vim
help) as far as I know
|buffer-variable|b: Local to the current buffer.
|window-variable|w: Local to the current window.
|glob
Adam Monsen wrote:
> I was very pleased to see Taro Muraoka's functionality included for
> selecting quoted strings! Here's a small patch to correct the fact that
> these are visual mode commands as opposed to normal mode commands.
Well, you can use them in Normal mode after an operator: da"
I
Georg Dahn wrote:
> Vim choses the default colors of the syntax highlighting for gVim
> depending of the value of background. If I add the lines
>
> set background=dark
> hi Normal guifg=#e0e0e0 guibg=#202020
>
> I get the defaults for dark backgrounds. Unfortunately, the background
> colors
Steve Hall wrote:
> I'm seeing a gVim 7.0d (GTK2) bug in refreshing the GUI tab bar. When
> a guitablabel is set by autocmd (VimEnter, BufEnter, etc), the results
> aren't actually shown until the Vim window is refreshed, such as with
> :set nu or :set list.
I fixed this a couple of days ago. P
On Sat, 2006-04-15 at 13:54 +0200, Bram Moolenaar wrote:
> Closing a tab cannot be undone, thus I don't think it should be done
> too easily. It's easy to double click while you meant to click once
> two times.
I agree here. How often can it happen that during development (maybe
under time pressu
36 matches
Mail list logo
