A redrawing bug with linespace=0
I am on Windows 7 64-bit using Vim 7.4 official 32-bit build downloaded from Vim site a couple days ago. I was using 7.3 before that. I noticed a redrawing issue that might be a regression. Steps to reproduce: * First, do preparation: Launch gvim -u NONE -U NONE --noplugin set nocompatible syntax on set ft=markdown set linespace=0 set guifont=Courier_New * Then, go to Edit mode, type '_' (underscore) 10 times, then press Del 10 times to remove those. As a result of that you should get blank screen, but instead you get the lower horizontal line visible, see attachment. I guess it has to do with ClearType, but I believe there was no such issue in 7.3. -- Alexei Alexandrov -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. attachment: tmpimg03.png
Re: Bug report: typing misbehaves when changing a word with quot;ciwquot; for a numbered list
Bram Moolenaar Bram at Moolenaar.net writes: I think it's a bug. It's very annoying - I'm using the anw flags quite a bit. Maybe I hit some corner case here. This might very well be fixed by patch 7.3.020. If your Vim doesn't include it, try installing a newer version. I have updated to the most recent 7.3 source state and I confirm the bug does not reproduce there. Thanks a lot! -- 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 information, visit http://www.vim.org/maillist.php
Re: Remote command equivalent for -q command line option
Ben Schmidt wrote: Is it possible to get what I want? With a little jiggerypokery it should be! Perhaps something like gvim --remote-send C-\C-N:cfile build.logCR:call foreground()CR You'd obviously want to wrap that in a shell script or alias... And there are other possibilities if that doesn't work... If you're on Windows, running remote_foreground() in the client might be better than running foreground() in the server, for instance; then you'd have to run a remote_send in the client, too, via a :call not using the --remote-send argument. Err... I'll play with it, thanks! But I just realized that I don't like --remote-send since it doesn't create a new Vim instance in case when no server is running yet... Keeping thinking and trying... -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Remote command equivalent for -q command line option
Ben Schmidt wrote: Alexei Alexandrov wrote: Err... I'll play with it, thanks! But I just realized that I don't like --remote-send since it doesn't create a new Vim instance in case when no server is running yet... Keeping thinking and trying... If not on Windows, perhaps an autocommand to automatically raise Vim whenever it opens a file? In .vimrc: augroup AutoForeground au! au BufReadPost * :call foreground() augroup END I didn't mean raising, I meant creating a new Vim remote server if one doesn't exist yet. This is what silent means in the names of some of those command line arguments. Anyway, I think I end up with gvim --remote-tab-silent +cfile build.log build.log for now. It seems to do what I need with a nice side effect of opening the build log in a separate tab. Well, maybe it's actually nice since I do need to take a look at the log itself sometimes... We'll see. Thanks for your help, BTW! -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Remote command equivalent for -q command line option
Hi, I often use something like gvim -q build.log to browse through the build log compilation errors. I also use something like gvim --remote-tab-silent PATH quite a bit to open files in the already running instance of gvim. Ideally, I'd like to combine these 2 things and be able to load existing build log into running Vim instance. But I couldn't find a command line option which does that - all --remote commands require file to open argument, but I don't need to open the build.log file - I need to make it the errorfile. There is --remote-send command line option but it doesn't raise Vim window so it's not convenient either... Is it possible to get what I want? -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Format options in ftplugin/python.vim
Hi, Currently file type script for Python doesn't set any text format options. This is not convenient - if 'textwidth' is set, Vim starts to wrap lines for code as you write it. Also, 'o' command in normal mode doesn't insert the comment leader automatically. Please add the following code to ftplugin/python.vim: Set 'formatoptions' to break comment lines but not other lines, and insert the comment leader when hitting CR or using o. setlocal fo-=t fo+=croql -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: quickfix in foldopen doesn't work for keyboard mappings
Jürgen Krämer wrote: | Specifies for which type of commands folds will be opened, if the | command moves the cursor into a closed fold. It is a comma separated | list of items. [...] | When the command is part of a mapping this option is not used. Add | the |zv| command to the mapping to get the same effect. Regards, Jürgen Ah, thanks! -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: VIM and NTFS streams
krischik wrote: I fear you missed something - since NTFS v3.0 named forks are supported. They are called Alternate data streams. Oops, yep, I have a lot of stuff to catch up with. -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: VIM and NTFS streams
krischik wrote: Open a console and type man 5 attr? Or look here: http://linux.die.net/man/5/attr No it has nothing to do with Linux. FreeBSD, Solaris and Mac OS X support extended attributes as well. See: http://en.wikipedia.org/wiki/Extended_file_attributes Quote Wikipedia: In Linux, the ext2, ext3, ext4, JFS, ReiserFS and XFS filesystems support extended attributes (abbreviated xattr) if the libattr feature is enabled in the kernel configuration. Oh, thanks - this is a good learning for me. It's a shame I never heard of this before. On the other hand use of extended attributes could solve a problem with 5 lines of code where solving the same problem without could cost you 50. Determine file types, text file line endings and text file encoding come to my mind here. Ask Bram how many line of code he needed in Vim to determine these three informations. With consequent use of xattribs it would have been 6 lines: [...] And best of all: you know before you open the file. AFAIK Bram need to close and reopen files in unfortunate combinations. Such attributes would be useful, yes. But it's backward compatibility that is the root of all evil and you also mentioned this in a sibling post. So I'm not sure these things will become popular unless there is a brand new OS appears which doesn't have to be compatible with anything and it wins the market. Also, the named attributes story doesn't have to do much with numbered NTFS data streams, does it? It might be similar but numbers are too far from string identifier convenience. Which brings me back to my original thought - the design and implementation of data streams in NTFS are useless. -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch 7.1.235
Bram Moolenaar wrote: Patch 7.1.235 Problem:Pattern matching is slow when using a lot of simple patterns. Solution: Avoid allocating memory by not freeing it when it's not so much. (Alexei Alexandrov) Files:src/regexp.c Thanks a lot! You had to rework it somewhat as I can see, right? I'm also curious what happens with the DFA regexp engine rework? -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Re-assigning detectindent plugin
Vladimir Marek Vladimir.Marek at Sun.COM writes: I updated detectindent plugin, but the original author seems to be unreachable 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 received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Feature request: enable undo after reloading file
On 11/4/07, Bram Moolenaar [EMAIL PROTECTED] wrote: I'll put it in the todo list. However, don't expect it soon. I think the only right way to implement it is to do a diff between the buffer text and the file that is to be loaded. The difference would then be stored as a change in the undo buffer. Yes, this would be the most correct way. It is also not very easy to implement perhaps? P.S. Persistent undo would be great too. :) That's already in the todo list. I know actually - this is why the smile is there. Just making sure you know people need this feature :) -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Convert dot command into macro
Ben Schmidt wrote: ... I wonder what Bram thinks about including this functionality in standard Vim? I think it would be useful. What do others think? I would love to see this functionality in Vim. I miss it for very long time. It's very typical when you go through a number of files doing n. Sometimes you need to do it across the session and I wanted the . command be saved many times. I vote for it! --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch for VIM dosbatch syntax file
On Oct 18, 2:40 am, Tony Mechelynck [EMAIL PROTECTED] wrote: Alexei, why _four_ copies (to date) of this post? If you didn't get them yourself, check your gmail spam folder. Sorry, my Thunderbird screwed it up due to a wrong SMTP server setting. Every time it would say that it failed to send the message but as it turns out it lied :) --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Patch for VIM dosbatch syntax file
Hi Mike, In the VIM 7.1 distribution runtime files you're listed as the maintainer of dosbatch.vim file which is a syntax file for Windows/DOS batch files. Currently this syntax file doesn't list correctly @Spell/@NoSpell attributes of VIM 7.x which means it's very inconvenient to work with *.bat files when spell checking is on. The attached is a patch for the syntax file. Please consider reviewing it and directing to Bram for inclusion. P.S. It's intentionally that only echo ... strings are included into spell checking and not regular ... strings. During my local experience with it I found it more convenient since ordinary strings are usually file paths in *.bat files and full of wrong words. It's mostly comments and echo strings that should be spell-checked. Thanks! -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~--- Index: dosbatch.vim === --- dosbatch.vim(revision 607) +++ dosbatch.vim(working copy) @@ -44,7 +44,7 @@ String - using 's is a convenience rather than a requirement outside of FOR syn match dosbatchString \[^]*\ contains=dosbatchVariable,dosBatchArgument,@dosbatchNumber -syn match dosbatchString \echo[^)|]*lc=4 contains=dosbatchVariable,dosbatchArgument,@dosbatchNumber +syn match dosbatchString \echo[^)|]*lc=4 contains=dosbatchVariable,dosbatchArgument,@dosbatchNumber,@Spell syn match dosbatchEchoOperator \echo\s\+\(on\|off\)\s*$lc=4 For embedded commands @@ -91,9 +91,9 @@ syn match dosbatchLabel:\h\w*\ Comments - usual rem but also two colons as first non-space is an idiom -syn match dosbatchComment ^rem\($\|\s.*$\)lc=3 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument -syn match dosbatchComment \srem\($\|\s.*$\)lc=4 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument -syn match dosbatchComment \s*:\s*:.*$ contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument +syn match dosbatchComment ^rem\($\|\s.*$\)lc=3 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument,@Spell +syn match dosbatchComment \srem\($\|\s.*$\)lc=4 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument,@Spell +syn match dosbatchComment \s*:\s*:.*$ contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument,@Spell Comments in ()'s - still to handle spaces before rem syn match dosbatchComment (rem[^)]*lc=4 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument
Patch for VIM dosbatch syntax file
Hi Mike, In the VIM 7.1 distribution runtime files you're listed as the maintainer of dosbatch.vim file which is a syntax file for Windows/DOS batch files. Currently this syntax file doesn't list correctly @Spell/@NoSpell attributes of VIM 7.x which means it's very inconvenient to work with *.bat files when spell checking is on. The attached is a patch for the syntax file. Please consider reviewing it and directing to Bram for inclusion. P.S. It's intentionally that only echo ... strings are included into spell checking and not regular ... strings. During my local experience with it I found it more convenient since ordinary strings are usually file paths in *.bat files and full of wrong words. It's mostly comments and echo strings that should be spell-checked. Thanks! -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~--- Index: dosbatch.vim === --- dosbatch.vim(revision 607) +++ dosbatch.vim(working copy) @@ -44,7 +44,7 @@ String - using 's is a convenience rather than a requirement outside of FOR syn match dosbatchString \[^]*\ contains=dosbatchVariable,dosBatchArgument,@dosbatchNumber -syn match dosbatchString \echo[^)|]*lc=4 contains=dosbatchVariable,dosbatchArgument,@dosbatchNumber +syn match dosbatchString \echo[^)|]*lc=4 contains=dosbatchVariable,dosbatchArgument,@dosbatchNumber,@Spell syn match dosbatchEchoOperator \echo\s\+\(on\|off\)\s*$lc=4 For embedded commands @@ -91,9 +91,9 @@ syn match dosbatchLabel:\h\w*\ Comments - usual rem but also two colons as first non-space is an idiom -syn match dosbatchComment ^rem\($\|\s.*$\)lc=3 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument -syn match dosbatchComment \srem\($\|\s.*$\)lc=4 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument -syn match dosbatchComment \s*:\s*:.*$ contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument +syn match dosbatchComment ^rem\($\|\s.*$\)lc=3 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument,@Spell +syn match dosbatchComment \srem\($\|\s.*$\)lc=4 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument,@Spell +syn match dosbatchComment \s*:\s*:.*$ contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument,@Spell Comments in ()'s - still to handle spaces before rem syn match dosbatchComment (rem[^)]*lc=4 contains=dosbatchTodo,@dosbatchNumber,dosbatchVariable,dosbatchArgument
Re: Getting runtime files with AAP
Bram Moolenaar wrote: Hmm, perhaps another Python 2.5 incompatibility? At least it works fine for me with Python 2.4.2. Can you please locate the Process.py file in the aap Exec directory, and uncomment the msg_note() call below DEBUG? Then we can see what code is actually executed. Aap generates Python code and executes it, unfortunately Python then doesn't give good error messages. OK, I screwed it up myself... Attempt to locate the Process.py file quickly showed that AAP was executed not from the location I expected. In fact, some older version of APP was picked up - consequence of my recent computer re-installation. It now seems to work - it's downloading things at the moment. Sorry for the spam annoying spam with spam. P.S. In fact, when aap didn't work for me I came up with 2 rsync commands which sync up the contents of my Windows VIM runtime files pretty well. It leaves my Vim executables untouched and cleans up as much as possible at the same time. It also gets only english and russian spell files for me: rsync --verbose -avzcP --delete --exclude=spell --exclude=*.exe --exclude=*.pdb --exclude=*.dll --exclude=*.bat ftp.nluug.nl::Vim/runtime/dos/ ./ rsync --verbose -avzcP --delete --include=ru.* --include=en.* --exclude=*.spl --exclude=*.sug ftp.nluug.nl::Vim/runtime/spell/ ./spell/ FWIW... --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Usage of GetUserName in os_win32.c
Hi Vimmers, In file os_win32.c there is a function mch_get_user_name() which uses GetUserName() function to get the logon name on Windows. The constant used to declare a buffer to get the name is MAX_COMPUTERNAME_LENGTH which is not correct. The correct constant (as mentioned in the documentation) is UNLEN. I don't know the severity of this problem, but note that UNLEN is 256 characters, while MAX_COMPUTERNAME_LENGTH is only 15 characters. In fact, I discovered this problem while looking into BoundsChecker results for Vim - my logon name is longer than 15 chars and GetUserName were failing. Still, I can work in Vim perfectly - so this bug doesn't affect most of us. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Getting runtime files with AAP
Hi vimmers, I try to update my Vim runtime files with AAP. I have AAP 1.090 installed, plus Python 2.5. I execute command aap -f ftp://ftp.vim.org/pub/vim/runtime/main.aap fetch which is a copy-paste from Vim site and get the following error: fetch Aap: c:\cygwin\bin\gcc.EXE --version Aap: Attempting download of ftp://ftp.vim.org/pub/vim/runtime/main.aap; Aap: Downloaded ftp://ftp.vim.org/pub/vim/runtime/main.aap; to main.aap Aap: Updating recipe main.aap Aap: Attempting download of ftp://ftp.vim.org/pub/vim/runtime/main.aap; Aap: Downloaded ftp://ftp.vim.org/pub/vim/runtime/main.aap; to D:\programs\vim\111\main.aap Cannot read filetype.vim, guessing fileformat is dos. Aap: Attempting download of ftp://ftp.vim.org/pub/vim/runtime/getdos.aap; Aap: Downloaded ftp://ftp.vim.org/pub/vim/runtime/getdos.aap; to D:\programs\vim\111\getdos.aap Aap: Internal Error Aap: Traceback (most recent call last): File D:\programs\aap\Process.py, line 1163, in Process exec script_string in recdict, recdict File string, line 7, in module File D:\programs\aap\Error.py, line 50, in __init__ self.args = args TypeError: 'NoneType' object is not iterable Aap: Aborted Aap: More info in the logfile: D:\programs\vim\111\AAPDIR\log What might be the reason of the failure? -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
