Hi,
gg=G does not work in vim 7.4
I just tried with Vim 7.4.77 ('big' build) on a C file and it worked
fine for me. Could you please elaborate a bit more?
--
--
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
Hi all,
I don't know whether this is caused by Vim or Netrw, but here's a way
to crash both:
1. cd /tmp mkdir foo
2. vim
3. :e foo/
4. rmdir foo touch foo
5. In Netrw choose .. to go up to /tmp
6. Open foo
Vim crashes at this point with a segmentation fault. Sometimes it will
not crash
On 26 December 2013 13:43, Tony Mechelynck wrote:
Hm, you're removing the directory you're working on and replacing it by a
file of the same name, then asking to follow the hardlink ./.. in it, which
you implicitly just removed? Sounds to me like you were asking for trouble,
but well…
Of
Hi Dominique,
On 27 December 2013 09:07, Dominique Pellé wrote:
Can you try the attached patch? Since I can't reproduce
the bug, I'm not sure it will fix it. So please verify that it
fixes the crash and the valgrind error.
Yes it does! The inability to edit the current buffer is still
On Thu, Feb 14, 2013 at 12:54 PM, Christian Brabandt wrote:
Question is, if you run into a problem, how do you know you have to turn
off that option? If syntax highlighting is off it might be obvious, but
when some plugins behave badly you might not have a clue.
Anybody that uses such an
It seems that Vim does not have the same behavior depending on whether
longest is used as a complete option.
When using set completeopt=menu, if I use c-n and there's only one
possible completion, the current word is completed without showing the
menu and I'm immediately out of the
No idea. You could check the log files to check if you see a hint.
Is the file patches/7.1.246 corrupted in some way?
I just tried and both with CVS and with patches Vim builds fine.
The patch is not corrupted. I've the checked the files
src/auto/configure and src/configure.in, and it
This is with Vim 7.1.251
1) vim -u NONE
2) :set lines=25
3) :set columns=80
4) 150i computer chairEsc
5) gg
6) icc-n
The popup menu is displayed below the current real line instead of the
current visible line. Since the real line does not fit on the screen,
it is invisible. Even when it fits on
On Tue, Mar 4, 2008 at 4:58 PM, Charles E Campbell Jr
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
I seem to have a problem where I want to upgrade my version of gvim
for linux but am somewhat confused by the site
there seems to be a vim-7.1.tar.bz2 but I have no idea
On Fri, Mar 28, 2008 at 5:09 PM, François Ingelrest [EMAIL PROTECTED] wrote:
On Wed, Mar 26, 2008 at 10:15 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
François Ingelrest wrote:
I've taken a look at the code and the fix consists in one small change
(see attached patch): setting
On Sat, Mar 29, 2008 at 3:17 PM, François Ingelrest [EMAIL PROTECTED] wrote:
Here are two patches I've written. The first one leaves a maximum of
two lines of context between the cursor and the popup menu. The second
one introduces an option (pumshift) to set that value (default is
two
On Sat, Mar 29, 2008 at 9:22 PM, Dominique Pelle
[EMAIL PROTECTED] wrote:
Hi François:
I have tested your patch #1. For long lines that wrap multiple times,
completion popup
does not behave in a symetric way whether popup appears:
1/ below the cursor (i.e. when cursor is near the top
An easy one.
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
--- Vim_orig/vim/runtime/doc/eval.txt 2008-03-29
On Sat, Apr 12, 2008 at 8:11 PM, Birgi Tamersoy [EMAIL PROTECTED] wrote:
I really think that by the end of this August we can have an on-the-
fly code checker which will be used by a majority of the community.
I'm not sure how many people are interested in on-the-fly compilation.
I know I'm
On Sun, Apr 20, 2008 at 1:25 AM, Joe Keen [EMAIL PROTECTED] wrote:
Are you two having the same problem?
There is a difference in the size_t and int type of the second argument.
But the idea is that these lines are removed when the function prototype
is in the header. Question is
On Tue, Apr 29, 2008 at 11:18 AM, gnani [EMAIL PROTECTED] wrote:
But from the compiled source code, I don't know how to create package.
Can you help me
As Tony said, it's related to how to package something for netBSD, not
to Vim specifically.
Hi,
Here is a patch that improves a bit notebook tabs with GTK2. It:
- Groups the creation of tab labels into one function (the code was
duplicated at two places before)
- Adds a file icon in front of the label
Here are some screenshots:
2008/5/1 Christian J. Robinson [EMAIL PROTECTED]:
Are icons tied with MIME system? So it will be different icon for
HTML file, different for C++ .h header?
Actually, Vim already has the filetype detection system, so an icon
for each filetype could be defined.
I like this idea, but
Hi!
On Fri, May 2, 2008 at 10:23 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Here is a patch that improves a bit notebook tabs with GTK2. It:
- Groups the creation of tab labels into one function (the code was
duplicated at two places before)
- Adds a file icon in front of the
On Tue, May 6, 2008 at 5:43 PM, Antony Scriven [EMAIL PROTECTED] wrote:
Nico Weber [EMAIL PROTECTED] wrote:
the GUI version and that's the way GUIs generally look
like. The same goes for icons in notebook tabs: Almost
all the GUI applications I can think of display such an
On Tue, Jun 24, 2008 at 22:38, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.2a BETA
Compiled and installed fine on Ubuntu 8.04 with GTK2.
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more
On Thu, Jun 26, 2008 at 22:18, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.2a.001
Problem:On some systems X11/Xlib.h exists (from X11-dev package) but
X11/Intrinsic.h does not (in Xt-dev package). This breaks the
build. Also, on Solaris 9 sys/ptem.h isn't
On Fri, Jun 27, 2008 at 15:42, Bram Moolenaar [EMAIL PROTECTED] wrote:
Francois Ingelrest wrote:
On Thu, Jun 26, 2008 at 22:18, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.2a.001
Problem:On some systems X11/Xlib.h exists (from X11-dev package) but
X11/Intrinsic.h does
Hi,
On Sat, Jun 28, 2008 at 10:30, momodi [EMAIL PROTECTED] wrote:
I download the src files of vim7.2a and run make install
now my vim's version is 7.2a
but my gvim's version is also 7.1
why?
my OS: ubuntu 8.04
A possible explanation would be that you have compiled v7.2 without
GUI
On Wed, Jul 2, 2008 at 22:57, Amy Williams [EMAIL PROTECTED] wrote:
Gvim appears to have very slow scrolling for output from external commands.
This is an issue for me, particularly with :make and with spell checking.
To see the issue, run gvim, type a word, and then with the cursor over that
Hi,
On Tue, Jul 8, 2008 at 05:05, Charles E. Campbell, Jr.
[EMAIL PROTECTED] wrote:
I'm just beginning a semi-automated test suite -- I expect that that
will help enormously sometime in the misty future. I'll be going
through the commands and trying to build the tests, checking netrw as I
On Wed, Jul 16, 2008 at 01:10, Ian Kelling [EMAIL PROTECTED] wrote:
For 4, you can do something similar, like :inoremap ESC ESCl
I've been using something like that for some time:
inoremap Esc RightEsc
This works in GVim but breaks extended keys in Vim (they send Esc as
the first keycode).
On Wed, Jul 16, 2008 at 16:57, Tony Mechelynck
[EMAIL PROTECTED] wrote:
I've been using something like that for some time:
inoremapEsc RightEsc
This works in GVim but breaks extended keys in Vim (they sendEsc as
the first keycode).
It seems that Vim doesn't wait a bit to see if another
Hi,
On Fri, Aug 29, 2008 at 06:35, Martti Kuparinen [EMAIL PROTECTED] wrote:
I don't know if this is valid or not but if this is, is someone working on
this?
http://www.rdancer.org/vulnerablevim-K.html
See this thread:
Hi all,
If I put this in a foo.vim file:
highlight Comment guifg=White guibg=Black
function! Foo()
highlight Comment guifg=White guibg=Black
endfunction
The first highlight line is highlighted, but not the second one. It
seems that's because it's inside a function. Is it
On Thu, Nov 6, 2008 at 22:41, Roberto Miura Honji [EMAIL PROTECTED] wrote:
I'm using highlight inside a function and It's working.
You get the same color highlighting inside and outside the function?
For me the highlighting works inside functions for most statements,
but not for the 'highlight'
On Fri, Nov 7, 2008 at 08:08, François Ingelrest
[EMAIL PROTECTED] wrote:
On Thu, Nov 6, 2008 at 22:41, Roberto Miura Honji [EMAIL PROTECTED] wrote:
I'm using highlight inside a function and It's working.
You get the same color highlighting inside and outside the function?
For me
On Thu, Nov 6, 2008 at 23:36, Roberto Miura Honji [EMAIL PROTECTED] wrote:
- Auto-complete using a tab key (like ctrl-p).
- When the word have a '/' (linux separator of directories) auto-complete
like a file (ctrl-x ctrl-f).
- When the list search is returned, the tab can be used to scroll
Hi all,
The only highlight concerning the wildmenu I'm aware of is 'WildMenu'.
This lets me choose how the current match should be highlighted, but I
can't set the style of other entries in that menu. AFAICT, Vim
automatically uses the highlight style of the status bar.
This is annoying,
Thanks for the trick!
On Sun, Nov 9, 2008 at 07:01, Tony Mechelynck
[EMAIL PROTECTED] wrote:
On 08/11/08 14:12, François Ingelrest wrote:
Hi all,
The only highlight concerning the wildmenu I'm aware of is 'WildMenu'.
This lets me choose how the current match should be highlighted, but I
On Sun, Nov 9, 2008 at 11:14, Anton Sharonov [EMAIL PROTECTED] wrote:
Unfortunately, it is not true. At least for SVN, (and I suspect
that for CVS it is as well the case) there are recent versions of
the runtime files (don't ask me why, for me it is also _very_
confusing). Anyway, to get
On Mon, Nov 17, 2008 at 22:18, Dominique Pelle
[EMAIL PROTECTED] wrote:
Does anybody else see that bug too?
Works fine for me.
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Nov 17 2008 08:42:16)
Included patches: 1-42
Normal version with GTK2 GUI
Hi,
On Fri, Nov 28, 2008 at 10:08, Bram Moolenaar wrote:
Patch 7.2.050
Problem:Warnings for not checking return value of fwrite(). (Chip
Campbell)
Solution: Use the return value.
Files: src/spell.c
I still get such warnings, for instance:
diff.c:702: warning: ignoring return
On Fri, Nov 28, 2008 at 13:51, Tony Mechelynck wrote:
Hm, François, is this a console-only version with no multibyte
capabilities? I have additional warnings in mbyte.c, gui.c,
gui_gtk_x11.c (and netbeans.c).
Yes, it's a fresh CVS checkout with just normal features and nothing else.
On Fri, Nov 28, 2008 at 17:12, Bram Moolenaar wrote:
Can you check if adding (void) before a function gets rid of the warning
for an unused return value?
No, adding (void) makes no difference as I get the same warning in both cases.
--~--~-~--~~~---~--~~
You
On Fri, Nov 28, 2008 at 21:27, Bram Moolenaar wrote:
Patch 7.2.055
Problem:Various compiler warnings with strict checking.
Solution: Avoid the warnings by using return values and renaming.
Files: src/diff.c, src/eval.c, src/ex_cmds.c, src/ex_docmd.c,
src/fileio.c,
Hi,
On Wed, Nov 12, 2008 at 13:08, Bram Moolenaar wrote:
Francois Ingelrest wrote:
Hi all,
When I do the following:
1. vim -u NONE -U NONE foo.c
2. :tabnew
3. :tabprev
4. :saveas bar.c
The tabline is not refreshed, and the current tab is still named
foo.c. Switching to the other
On Mon, Mar 5, 2012 at 12:24, Birger J. Nordølum wrote:
I can only once again petition that the DNS part of the Vim project get
fixed, as this is to considered as being a flawed configuration, and can't
be acknowledged as a good design decision.
I personally don't care whether vim.org works
Hi all,
I've updated Vim to 7.3.744 (features=big) and now netrw fails the
second time I try to open a file using :Explore
1. Start vim
2. :E and open a file
3. :E fails
At step 3 I get a blank screen with no listing. This seems to be
caused by this line in my .vimrc:
let g:netrw_liststyle=3
On Wed, Jan 30, 2013 at 12:31 PM, Bram Moolenaar wrote:
This looks like a good solution. I'll include it. With Christian's
addition.
I think I found a case where the 'relativenumber' option is reset. I'm
sending this report in this thread, although I don't know if it's
caused by the recent
Hi,
2010/7/28 Dominique Pellé:
I'm sorry, I messed up again and forgot one file in the patch :-(
Here it is again.
This new feature is great! It's easier and a bit faster to have
completion at hand when setting the file type.
One (maybe silly) question though: Isn't it possible to use
Hi all,
The following code is highlighted incorrectly when using the cpp filetype:
#if defined FOO
#elif defined BAR
#endif
The part defined BAR is not highlighted, while defined FOO is.
AFAICT, my runtime files are up to date.
I don't know much about Vim syntax files, so I can't tell where
On Tue, Nov 3, 2009 at 12:10, Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.2.269
Problem: Many people struggle to find out why Vim startup is slow.
Solution: Add the --startuptime command line flag.
Files: runtime/doc/starting.txt, src/globals.h, src/feature.h,
Hi all,
I've started to use the command DiffOrig proposed in the help (see :h
:DiffOrig). When I use it and then return to normal mode, the left
margin is not correctly restored, some empty space being left in front
of the text (or in front of line numbers if displayed).
Here are some steps:
1.
On Tue, Nov 24, 2009 at 11:04, Christian Brabandt wrote:
I believe, that is the foldcolumn. You should issue :diffoff when closing
your diff. See :h foldcolumn
Indeed, thanks!
Is there a way to go back to normal mode (i.e., closing the diff
window and issuing :diffoff) or should I just create
2010/5/25 Dominique Pellé dominique.pe...@gmail.com:
Does anybody use all Vim features? :-)
Does anybody actually know all Vim features? :-)
Sometimes I accidentally quit Vim while editing a file (hitting w and
q at the same time when saving for instance), losing the undo history
at the same
Hi,
On 9 May 2015 at 16:31, Daniel Kosiński wrote:
This does happens for both / and ? searches. I tried searching for it with
vim/gvim -u NONE and it couldn't match it either. If I search only for
'Makijaż' it matches the word correctly but as soon as I add space character
it skips h2 tag.
On 23 November 2016 at 15:17, Matlink wrote:
> Doesn't work on my 2:7.4.488-7 on debian.
Have you upgraded the package? I got an upgrade this morning, I guess
it fixed the issue.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
Hi all,
The new :term command is great! But I get a white background in my
terminal instead of a black one. Foreground colors look right I think.
I made a few tests and found that the 'set t_RB=' line in my .vimrc
causes this issue. If I remove it I get a proper black background.
However if I
Hi all,
When I do this:
1. vim -u NONE
2. :term
3. c-w w
4. c-w w
At step 4, the :term buffer gets the focus but a few bytes seem to be
sent to the buffer as well. They're displayed right over my prompt on
the first line, first column, and there doesn't seem to be a way to
get rid of them.
Hi Bram,
On 16 August 2017 at 22:46, Bram Moolenaar wrote:
> If I use a dark color them: ":colors darkblue", and open a terminal with
> :term, then the terminal window has a dark background.
>
> libvterm does not recognize t_RB, I don't see how it matters. Perhaps
> your 'background' value in
Hi Bram,
On 16 August 2017 at 21:09, Bram Moolenaar wrote:
> I don't see this. Most likely related to using Gnome. Have you tried
> using an xterm?
I don't see this with an xterm or even in a console outside of X, so
it may indeed have something to do with gnome-terminal. Anything I
could do
Hi,
On 17 August 2017 at 16:55, Bram Moolenaar wrote:
> OK, then try this:
> :set t_SH=
Thanks, this fixes the issue. I guess it is related to this discussion:
https://groups.google.com/d/topic/vim_dev/TFYu5FtOA30/discussion
--
--
You received this message from the "vim_dev"
Hi,
On 17 August 2017 at 14:24, James McCoy wrote:
> What exactly are the extra characters you're seeing? At a guess, it's
> something like "[2 q". If so, that's because libvte (until relatively
> recently) passed through control codes that it didn't understand, which
> meant they were printed
Hi,
On 18 April 2017 at 18:53, Bram Moolenaar wrote:
> Patch 8.0.0567
> Problem:Call for requesting color and ambiwidth is too early. (Hirohito
> Higashi)
> Solution: Move the call down to below resetting "starting".
> Files: src/main.c
This patch
Hi Bram,
On 1 May 2017 at 15:35, Bram Moolenaar wrote:
> Strange. Do you have t_RB set? If so, does it help to make it empty?
Yes it seems to be automatically set (at least not set in my .vimrc)
to <1b>]11;?<07>. If I make it empty in my .vimrc, termguicolors works
as
Hi,
On 1 May 2017 at 17:37, Bram Moolenaar wrote:
> OK, well then maybe we should implement this comment:
> {/* TODO: don't set option when already the right value */
>
> Try this patch:
>
> ...
Sorry but that doesn't work.
Patch applies cleanly and compilation
On 2 May 2017 at 11:15, Bram Moolenaar wrote:
> Hmm, and when you set 'background' to the right value in your .vimrc,
> does that make any difference?
Yes this works. I added 'set t_RB=<1b>]11;?<07>' and I get the proper
colors. Actually setting it to any value seems to work
Hi,
On 3 May 2017 at 11:11, Christian Brabandt wrote:
> So gdefault seems to be popular to a certain degree. I wouldn't have
> thought that, it is just such an obscure option.
I've always used it, it's quite handy to always replace all
occurrences and not just the first one.
Hi,
On 29 August 2017 at 20:18, Bram Moolenaar wrote:
> Gnome terminal can't handle a standard xterm escape sequence?
> The escape sequence is correct, it works fine on any xterm.
> I verified it correctly gets us the right cursor blink mode.
>
> I don't see this problem in a gnome-terminal on my
Hi,
On 30 August 2017 at 13:48, Bram Moolenaar wrote:
> I'm getting tired of those terminals that say they are xterm while they
> are not...
>
> My gnome-terminal reports this version: [>1;4402;0c
> What does yours say?
> Since a real xterm only has a version in the 300 range now, we could
>
Hi,
On 30 August 2017 at 18:59, Bram Moolenaar wrote:
> I made the check > 4000, thus 3801 would indeed not match.
> Let's make it > 3000 then.
Works fine now, thanks for taking care of this.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below
On 22 February 2018 at 03:55, Christian J. Robinson wrote:
> _Please_ make it possible to use http://vim.org, even if it just
> automatically redirects to http://www.vim.org. Your own reply here shows
> why it's needed.
It's been asked again and again for years, e.g.,
Hello,
:h varsofttabstop reads :
For example, when editing assembly language files where statements
start in the 8th column and comments in the 40th, it may be useful
to use the following:
:set varsofttabstop=8,32,8
To me, this will move the cursor to the 9th (inserting 8 spaces) and
41th
BTW, I'm sorry if this has been asked before as I didn't have time to
catch all my emails recently, but if the vartab feature is to be used
for column editing (and it's great at that), wouldn't it be more
logical to provide the columns where to stop at rather than the length
of tabs?
For
Hi all,
I recently updated my vim to v8.1.1824, including netrw which is now v165.
When sorting by name, directories and files are now mixed up among
other things. I'm not sure whether this is a bug or if I didn't get
how to use g:netrw_sort_sequence, but this variable seems to be
ignored which
Hi,
On Sat, 27 Aug 2022 at 06:56, Charles Campbell wrote:
> So, I thought what I'd like to do is to get vim 9.0 back (with no
> patches) and see if that worked. Then, if the plugin continues to
> misbehave, then I'd like to get vim 8.0. Once I have a version of vim
> where the plugin works I'd
Hello,
On Tue, 13 Dec 2022 at 02:31, Alex von Gluck IV
wrote:
> Shift makes no difference for me. Can you provide documentation on what
> shift is supposed to do?
>
> I can reference the FreeDesktop clipboard specification which doesn't
> mention anything about required modifiers:
>
>
73 matches
Mail list logo