uninstal.c RegDeleteKeyEx unresolved

A recent change to uninstal.c breaks building Vim on 32-bit Windows. These changes: hg diff -r 573da4dac306:b204ac54bea4 src/uninstal.c involve replacing RegDeleteKey with RegDeleteKeyEx Problem occurs with Windows XP 32-bit, using MS Visual C 6.0, command: nmake -f Make_mvc.mak Build stops at:

RE: syntax/r.vim

Jakson A. Aquino wrote: > I tried to contact the maintainer of syntax/r.vim I can't help you with that, but by the way... We have a page on the wiki intended to list scripts relating to R (because they are impossible to search for): http://vim.wikia.com/wiki/Script:List_of_R_Project_scripts John

RE: [Patch] Open new tab at the end of tab stack

Bram Moolenaar wrote: >> Gvim opens a new tab just next to the current tab by default. >> Is it acceptable to open the new tab at the end of the >> tabline by default? > > You can already do this: > > :99tab split file > > It's not default, but typing 99 isn't much effort. Bram - Did you see

tarPlugin.vim needs to be updated to handle xz files

In runtime file plugin/tarPlugin.vim, there are no lines for *.txz *.tar.xz which are needed to edit xz compressed tar archives. File plugin/gzip.vim handles *.xz, but tarPlugin.vim needs to be updated. The above is from Richard David Sherman who asked me to send it to vim_dev. Richard has

RE: new trends in vim development (SPAM?)

Tony Mechelynck wrote: > This looks like spam to me; I don't click links when I have > no idea what the link will do. As Marc said, it is spam and probably MALWARE. Please do not click links like this! I noticed a similar attempt at vim_use a day or two ago and flagged it as spam (thus banning th

RE: On extending motions and matches

Adrien "Pied" Piérard wrote: > it looks like motions like i" or a' that work with quotations > are hard-coded. As I happen to write a lot of math in latex, > I have many $ signs everywhere that I would like to treat as > quotations so that I can do da$ or yi$. > I guess this could be implemented wi

RE: Improved integration between Vim and its environment (full-screen, open URL, background execute())

Peter Odding wrote: > I've asked myself why Vim's system() function on Windows uses > vimrun.exe and shows a command prompt window. The only reason > I can think of is so that the user has a chance to quit the > external command using Ctrl-C. Sorry if the following is not relevant (I have not foll

Claimed memory leak in :match

A recent edit to a tip includes a claim that having :match in autocmd events leads to severe slow downs due to a memory leak. The tip has a variety of methods to highlight unwanted spaces, including the following extreme version which attempts to highlight dubious spaces as you type, but NOT highl

RE: Fix for wrong indentation of JavaScript code by cindent

Hari Kumar G wrote: > Vim uses cindent for JS files which works in general nicely. > There are a few cases where this does not work correctly. F.e. > > var a = { >     b: 1, >     c: "hello" > } > > cindent would align b: 1 to col 0 and indent c: "hello" by > shiftwidth. This is because of how it t

RE: mail from new wiki pages

Tom Link wrote: >> In your watchlist, click the link: Edit raw watchlist >> >> I believe you could just add lines like the following: >> Script:123 >> Script:4321 > > Is this trick still possible? I remember having edited the > raw watchlist before but now I cannot find the right link. I > cannot s

Possible bug when side scrolling

In the following, these Unicode characters are used: "\u200e" = 'LEFT-TO-RIGHT MARK' (U+200E) "\u2013" = 'EN DASH' (U+2013) On my 7.2.411 system, the following commands show a bug: gvim -u NONE :set columns=96 nowrap encoding=utf-8 :$put =repeat('a',50) . nr2char(0x200e) . repeat('b',40) . 'A

RE: Unsubscrible vim_dev

Simson Liu wrote: > I can still receive mail from the list. I have tried again, and have responded directly to Simson. I'm just replying here to let others know that I have acted. John -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you

RE: Unsubscrible vim_dev

Simson Liu wrote: > I have subscrible the list with new gmail box. But I can't > unsubscrible the list with my current work mail box. I have > sent the vim-dev-unsubscr...@vim.org the empty mail message > many times, but have no any effect. So other managers don't have to look, I have done the uns

RE: mail from new wiki pages

John Beckett wrote: > You can actually watch pages before they are created, > however, that's a bit exotic, so I would recommend creating > each relevant Script:xxx page then watching it. On second thoughts, it should be pretty easy to watch the pages that are NOT yet created, if

RE: mail from new wiki pages

Charles Campbell wrote: > I'd like it if new entries on the plugin-associated wiki > pages would be automatically email'd to the plugin author. > The vim pages do have the author's email addresses, so this > shouldn't be too hard to do, I think. That's easy. You can "watch" any pages of interest,

RE: REMOVE ME Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

Thomas Ibbotson wrote: > To be fair to the original poster it does say: > > reply to this email with the words "REMOVE ME" as the subject. > > at the bottom of the email, which is what they did. I have been wondering where the "REMOVE ME" text comes from. I'm a manager of the group, and the text d

RE: vim sf page ratings and feedback feature

Ben Fritz wrote: > For a while now, we've been resisting having a wiki page for > every plugin out there, as such information could easly become > overwhelming or get out of date. We want searches on the wiki > to show mostly tips about how to use Vim, how to write > scripts, etc. We didn't want it

RE: Patch 7.2.330

Dominique Pellé wrote: > We can download latest Vim from: ftp, cvs, svn, Mercurial and git. > > Hmm, I'd say we need to simplify. Can't we all use Mercurial > since it seems to be the preferred system from the > discussions here lately. An excellent idea. Time spent keeping all these systems synch

RE: exclusive vs. inclusive actions and selection

Ben Fritz wrote: > I'm a little puzzled over "exclusive" vs. "inclusive" actions > and how they interact with the 'selection' option. > > Specifically, the 'e' and 'g_' commands seem inconsistent to me. I used gvim 7.2.323 and "gvim -N -u NONE" to verify Ben's finding. Enter a line consisting of f

RE: vim homepage: Obsolete reference to http://vi-improved.com/wiki

Tom Link wrote: >> It should be > > This isn't the wiki though it once referred to. It seems to > be rather related to the #vim IRC channel, isn't it? Thanks for alerting me because there were two usages of .com on the wiki (vim.wikia.com) which I have just fixed. Robert

RE: [patch] Initialise history before adding elements

Steven Sajous wrote: > does anyone know why the unsubscribe does not work on this > list? I have done it 4 times and got a confirmation every > time. Still getting emails. Please say exactly what you did. You emailed what address approximately how many hours ago? John -- You received this messa

RE: Problem with "without Cream" vim-7.2.303 _vimrc

Steve Hall wrote: > Hmm, so then the original MyDiff() might have been ok for you? No. People have complained on the wiki that the "Vim without Cream" distribution does NOT work with diff. There were several misguided suggestions for how to make it work. Last March, I did some quick investigations

RE: Problem with "without Cream" vim-7.2.303 _vimrc

Steve Hall wrote: > I'm concerned about relying on things outside the default Vim > distro since it is too complicated for me to package. Between > the various versions of Windows and 32- and 64-bit > complexities, building binaries in addition to the Vim ones is > too risky. > > Same goes for putt

RE: Problem with "without Cream" vim-7.2.303 _vimrc

Steve Hall wrote: >> The version of _vimrc installed by the Cream vim "without >> Cream" installer appears to be an obsolete version and >> contains a MyDiff() that doesn't work. > > Thanks for your helpful bugfix, I will change this for the > next build. Sorry, I should have reported this to Stev

RE: Problem with 'hidden' and :bufdo

Craig Barkhouse wrote: > vim -c "bufdo normal gg" *.c > > The problem I see is that the first and last buffers have > syntax highlighting, but all the intermediate buffers do not. At ':help :bufdo' we see that bufdo disables the Syntax automcommand event (for speed). That means the buffers you ha

RE: Where to put experimental indent file (JavaFX)

black panda wrote: > I have a first attempt at an indent plugin for the JavaFX > language. I don't think it is completely ready for prime > time, but I want someplace to post it for others to use and > give feedback so I can learn and improve the code. I think > the Scripts section of www.vim.org

RE: 'l' breaks macro when run at the end of line

Milan Vancura wrote: > Consider a two-line file: > > AA > 2lp I am going to take a wild guess and hope that someone will find support in the documentation. A command like 99l may be interpreted to mean "move right N times, where N is the smaller of 99 and the maximum possible". However, a comma

RE: Memory is used up when I replace "\t0\n" to "\n"

Aleafs wrote: > :1,$ s/\t0\n/\n/g In a substitute, \n means two different things: - In the pattern, it refers to a newline. - In the replacement, it refers to a null byte (8 zero bits). You can see this at ':help :s' by following the first two links. In a replacement, '\r' inserts a newline. Y

RE: VisualBasic 'elseif' indent error

Maxim Kim wrote: > I am not sure of the way fixes of that kind are included into > vim runtime. I believe the procedure is to email the maintainer shown in indent/vb.vim. Wait a week or more. If no response, post here. The maintainer is supposed to manage updates and forward them to Bram. John

RE: Request: suppression of plugins

Please bottom post on this list. Quote a small (relevant) part of the message you are replying to, and put your text underneath. See the list guidelines: http://groups.google.com/group/vim_use/web/vim-information --~--~-~--~~~---~--~~ You received this message f

RE: Patch for Vim with Ruby 1.9

Please bottom post on this list. Quote a small (relevant) part of the message you are replying to, and put your text underneath. See the list guidelines: http://groups.google.com/group/vim_use/web/vim-information --~--~-~--~~~---~--~~ You received this message fr

RE: [patch] charsets of vim

Please bottom post on this list. Quote a small (relevant) part of the message you are replying to, and put your text underneath. See the list guidelines: http://groups.google.com/group/vim_use/web/vim-information --~--~-~--~~~---~--~~ You received this message fr

RE: storing files without a name

NEW USERS ON THIS MAILING LIST: Please bottom post on this list. Quote a small (relevant) part of the message you are replying to, and put your text underneath. Do NOT quote large amounts of irrelevant stuff. See http://groups.google.com/group/vim_use/web/vim-information --~--~-~--~--

RE: shell quote shouldn't depend on shellslash on windows.

REMINDER TO ALL: Please bottom post on this list. Quote a small (relevant) part of the message you are replying to, and put your text underneath. See http://groups.google.com/group/vim_use/web/vim-information John --~--~-~--~~~---~--~~ You received this message

RE: getting dropped from the mailing list

Charles E. Campbell, Jr. wrote: > This is the second time I've stopped receiving emails from > vim_dev (its happened to me once on vim_use) this past week, > unless there's actually been no activity on this group for > two days. I have directly emailed Chip with a report from Google Groups that s

RE: Feature request: Add a Diff option upon open when "Found a swap file..."

James Vega wrote: > Vim creates swapfiles expressly to ease the process of > recovering from problems. Whether they be the power going > out while they were editing, or their system crashing > (BSOD?), or even forgetting to close their Vim session and > needing to do more work from a remote conne

RE: Feature request: Add a Diff option upon open when "Found a swap file..."

David C. wrote: > When you attempt to open a text file that was closed > abnormally before, leaving a hidden .swp file, your open is > interrupted by something like: > Swap file "filename.txt.swp" already exists! Sorry, but I'm going to deliver some advice from a previous occasion when this was d

RE: Wrong behavior in startup : vimrc vs runtime

Please bottom post on this list. Quote a small (relevant) part of the message you are replying to, and put your text underneath. See http://groups.google.com/group/vim_use/web/vim-information John --~--~-~--~~~---~--~~ You received this message from the "vim_dev

Junk from 'vim_dev group' and 'vim_use group'

I do not understand what went wrong when 35 junk messages were recently sent to vim_use, and 15 similar junk messages to vim_dev (seem to be three-month old digests). I suppose they could be a bug within Google Groups, or craziness in a member's software. The user name shecenon (joined Jan 200

RE: Concel and Ownsyntax patch FINALLY updated...

Vince Negri wrote: > I think you should say > > Status: works, patch based on Vim 7.2.141 (patch also > available for Vim 6.4.10) Done -- I have updated following: http://groups.google.com/group/vim_dev/web/vim-patches John --~--~-~--~~~---~--~~ You received

RE: Concel and Ownsyntax patch FINALLY updated...

Charles E. Campbell, Jr. wrote: >> I'm hoping Yakov will update the wiki tip in due course: >> http://vim.wikia.com/wiki/Patch_to_conceal_parts_of_lines > > Yakov said something in that tip about AnsiEsc that needs > correcting -- AnsiEsc handles ansi escape sequences with > conceal if your vim su

RE: Concel and Ownsyntax patch FINALLY updated...

Vince Negri wrote: > The page on google groups needs a small update to fix the > reference to 7.0.35. Good point, but please tell me exactly what text would be appropriate. It currently reads: Status: works, but only in Vim 6.4.10 and 7.0.35 Will we just mention the most recent patch? How about

RE: Concel and Ownsyntax patch FINALLY updated...

> patch updated to 7.2.141 here: > http://vince.negri.googlepages.com/conceal-ownsyntax.diff Thanks Vince. I haven't used the Conceal patch, but I have noticed that it has some very interesting features, including 'cursorbind' which I think I want. Someone (I think Yakov Lerner) put a lot of car

RE: VisVim patch to try out

David Fishburn wrote: > I have never used it before, but I should be able to test it out. > I have VS 2003 and VS 2005 installed on my machine. I've never seen VisVim, but I recently merged some info about related issues to this tip: http://vim.wikia.com/wiki/Integrate_gvim_with_Visual_Studio As

RE: [PATCH] support for the bang in :diffthis (was Re: [PATCH] :diffoff should not change settings for non-diff windows)

Bram Moolenaar wrote: > It's perhaps a bit strange to use ":diffthis!" to start diff > mode in other windows. ":diffall" would be more obvious. > It's not symmetric with ":diffoff" vs ":diffoff!", but that > one doesn't say "this". > > What do you all think about using ":diffall" instead? There

RE: Vista - Gvim 7.2 - gvim forcing read only _vimrc and not picking changes made in external editor

Edmon wrote: > I am running Gvim 7.2 on Vista. > > I want to modify startup settings and fonts and for some > reason _vimrc is being opened in read only mode, and I cannot > get to open it other way. I do not want to understand Vista, but on XP a user does not have write permission to files unde

RE: mysterious unc path issue on windows

Hugo Ahlenius wrote: > My simple test case is to try to load a file on the share > //localhost/ share/file.txt I assume you replace 'localhost' with the name of the computer? And the space in the above is just a typo. There is no space in the UNC? > * The other Vista win64 machine I have should

RE: List Questions - Groups

Larson, DavidX S wrote: > As Garrett mentioned, there are many scripts that do the same > thing. It should would be nice if they could be grouped > together or categorized in some way. How hard would it be to > add script categories to www.vim.org? And/or perhaps add a > "related scripts" sect

RE: List Questions

Garrett Whelan wrote: > 1) Is this list primarily for those working on the actual C > code or those expanding C with scripts? > 2) Should it be for one group, the other or both? It's main purpose is for bug reports, enhancement discussion, and questions on the C source. However, any issues conce

RE: gvim crashes handling WM_OLE message with Ultramon's buttons turned on

Anycase Mike wrote: > What i want is to let the gVim supports all system fonts.For example: > :set guifont=Dungeon:h9 Any monospaced font supported by the operating system should work in gvim. Some ideas are at: http://vim.wikia.com/wiki/The_perfect_programming_font I just noticed the subject o

RE: Status of breakindent patch

Tom Link wrote: > Display "soft-wrapped" lines flushed left at the proper > indentation level if 'linebreak' is set > Author: Václav Šmilauer I put that info, with slight changes, at: http://groups.google.com/group/vim_dev/web/vim-patches Please check. John --~--~-~--~~--

VIRUS with Bram as sender

I should take a little longer checking, but in view of the potential for damage I'm sending a preliminary opinion: A message has just been sent to the vim_multibyte list. Header includes: From: b...@moolenaar.net To: vim-multib...@vim.org Subject: Mail Transaction Failed Date: Thu, 18 De

RE: Bug? xterm-function-keys broken

Matt Wozniski wrote: > For the life of me, I can't seem to get vim to recognize, > eg, and as separate keycodes. Perhaps the following is an explanation: :help version7 /xHome "Previously and could be mapped separately. This had the disadvantage that all mappings (with modifiers) had to

RE: Can we still edit the patches list on google groups?

Richard Hartmann wrote: > Can't hurt, all for it. Do you want to include the git howto > I sent to the user's list, as well? I can do it myself, just > need to know :) Despite the fact that this thread is about the unofficial patches, I was responding to Ben's script that relates to the offici

RE: Can we still edit the patches list on google groups?

Ben Schmidt wrote: > I gave up on SVN ages ago--I would have loved to use it, but > it's just too messy. Now I apply patches. Below is the script Eventually I'd like to have a tip (http://vim.wikia.com/) on building Vim, with probably one overview article, and separate articles for downloading,

RE: mac-osx and open

Nico Weber wrote: > If I remember correctly, you added that about a year ago > after I sent you a patch. So I guess the wiki is just outdated. Any chance you could update the tip? I recommend deleting any info that applies only to older Vim (before, say, Vim 7.0, but even 7.1 if it simplifies a

RE: Oldfiles?

Bill McCarthy wrote: > After updating my runtime today, I noted the command > `:ol[dfiles]'. That was for an experimental patch that Bram posted: http://groups.google.com/group/vim_dev/browse_thread/thread/20e72354ed4b2f42 I guess it will be a bit longer before the docs and the released code ar

RE: Can we still edit the patches list on google groups?

Following Richard's suggestion, I added a (shortened) description of Matt Wozniski's patch to: http://groups.google.com/group/vim_dev/web/vim-patches Matt: Please reply (to me or the list) if any wording needs to be changed. John --~--~-~--~~~---~--~~ You recei

RE: Can we still edit the patches list on google groups?

Richard Hartmann wrote: > Can you add the patch to the list, please? :) Sure but I don't have time to work out what text to put. We need something like the following from http://groups.google.com/group/vim_dev/web/vim-patches 10. Variable tabstops Author: Matthew Winn Status: alpha

RE: Can we still edit the patches list on google groups?

Richard Hartmann wrote: > I tried adding it to the vim google groups site [2], but > failed to locate any edit button. Can we still edit on this > site? On October 11 we had a discussion regarding a spammer who changed all the links on the 'Vim patches' page to a porn site (according to Google

RE: Patch: ECL if for 7.2

Mikael Jansson wrote: >> Good - that's published now at: >> http://groups.google.com/group/vim_dev/web/vim-patches > > You got the HREF wrong! :-) I'm having a bit of trouble decoding your message. To easily get the desired formatting I did a copy/paste of the previous item, then edited the ne

RE: Patch: ECL if for 7.2

Mikael Jansson wrote: > === > #. ECL (Embeddable Common Lisp) Interface > Author: Mikael Jansson et al > Status: Mostly complete, needs testing > Site: http://common-lisp.net/project/limp > > Implements many, but not all, of the VimScript functions. See > the project page for documen

RE: Patch: ECL if for 7.2

Mikael Jansson wrote: > I couldn't find an edit link on the Patch page. > How do I go about adding it? The Vim Patches page is: http://groups.google.com/group/vim_dev/web/vim-patches As discussed in the following thread, a spammer started changing the page so it LOOKED unchanged, but clicking a

RE: vim 7 ex-mode behavior

d tbsky wrote: > after some checking, i found command like below didn't work > under vim 7: > > a > 1 \\ > 2 \\ > . It works here on Vim 7.2 as well, although I had to use help to see how. Use ':help :a' and see what it says about "Watch out for lines starting with a backslash". The above line

RE: !py import weakref breaks vim

Greg Warner wrote: > thanks for the feedback. I've confirmed that it's only > breaking on one of my builds, and on another it works, so I'm > sure it's just a problem with how I'm compiling it. In the bad build, use ':version' to see what it says about Python (near the bottom). Perhaps that d

RE: List of Vim patches

Bram Moolenaar wrote: > So I created a page that can be edited: > http://groups.google.com/group/vim_dev/web/vim-patches > > I have added the 2008 Google Summer of Code entries as an example. > If you want people to know your Vim patch, please add it here! > > This should be an overview, with li

RE: Patch to try out: v:oldfiles

Bram Moolenaar wrote: > Now and then I start editing a file and want to go back to a > file I edited in a previous edit session. But the name > doesn't appear in the marks or buffer list. Still, I know > the file name is in the viminfo file. There are plugins for > this, but I thought it wo

RE: Problem with CursorMoved AutoCommand when Editing Files on a Remote WIndows Share

David Kotchan wrote: > I've discovered a problem with Vim 7.2 when using the > CursorMoved autocommand under Windows. The problem is only > evident when editing files on a Windows share Perhaps this recent thread is relevant? http://groups.google.com/group/vim_use/browse_thread/thread/a1bb61d03

RE: Opening files with Unicode names under Windows?

Vadim Zeitlin wrote: > So, for example, opening a file "Аня.vcf" opens the file > "???.vcf" on my English Windows system. Tony's advice about encoding might fix the situation. I have the following in my vimrc: set encoding=utf-8 and can open a file with the name you mentioned on Windows. The f

RE: (patch) Lua interface : Borland C++ 5.5.1 test

Mondal, Shishir wrote: > I have tried earlier, but could not do that: any one knows > definite steps how to unsubscribe from the list? Please report any problem you have when you try the following (report = reply to this mail): Click the link in the footer of the mail: > You received this messa

RE: adding a new feature

Ranjeeth P T wrote: > Usually when we open an object file( in C i.e.out file ) we > get unseen characters So adding the property of objdump will be nice?? Vim is distributed with xxd. The following tip mentions the basics, then presents a more elablorate procedure if you need to use xxd often:

RE: reverse recursive .vimrc

fnegroni wrote: > It is a feature that I would absolutely love to have: I > develop for several projects following different indentation > styles and visualisation rules. Some code in your vimrc to detect the current directory at startup, then implement the wanted settings, might be easier. O

RE: sort()'s function reference arg

Robert Webb wrote: > I believe it's the same on all systems. qsort() just > compares the sign. Of course it would be impossible to check every qsort() on all systems(), but the fact that strcmp() uses that logic is a pretty good sign (!) that qsort() will as well. However, as others have poi

RE: Bug with v_K and potentially K command

Tony Mechelynck wrote: > Maybe you should set a config-time option (or create one) to > avoid any interaction with the shell? > > Even better: If you don't want ever to become the victim of > any exploit, turn your computer off at the wall switch and > leave it off. > > :-b I haven't studied this

RE: Right-align vs right-justify documentation?

Ben Schmidt wrote: >> "Justify" means to insert variable-width spacing throughOUt >> the entire line so the left and right margins are aligned. >> That's how most books and newspaper articles appear. > > And 'right justify' sometimes means this too, as it seems it > does in the Vim docs, even thou

RE: Right-align vs right-justify documentation?

Peter Prohaska wrote: > :help right-justify > """There is no command in Vim to right justify text. [...]""" "Justify" means to insert variable-width spacing throught the entire line so the left and right margins are aligned. That's how most books and newspaper articles appear. "Right-align" mean

RE: Opening a file as the OS would

> Ingo Karkat wrote: > Use ":silent ! start %"; the 'silent' will close the DOS > window immediately. I use this > map x :silent ! start "1" "%:p" to execute > the current file. ':p' makes this independent from the CWD, > the surrounding "" make it handle spaces. The "1" is the > optional "ti

RE: CR-used-for-NL

Andy Wokula wrote: > Minor issue, but somehow confusing: > > Unix (and DOS (Win)) users know that Vim converts some > characters when reading and writing a file: > > File <-> Memory <-> Display > NL (NUL) (line break) > NUL NL NUL (^@) > > With ff=mac, Vim does another

RE: Vim: Improper Implementation of shellescape()/Arbitrary Code Execution

Jan Minár >> I'm glad to see you persist in finding more problems. > > I'm sure everybody is... In case there is any doubt, YES we are glad you are finding problems. Thanks very much! I hope Bram won't mind holding back the release of 7.2 to provide a couple more weeks for testing by you (and

RE: Five (5) new features request

smu johnson wrote: > 3. Perl's =cut pod comments work half the time in Vim's > syntax highlighting. It's a compromise between performance and quality. Read: :help :syn-sync > 4. Somehow a toggle option so that when you exit out of > insert mode, it doesn't automatically move the cursor to th

RE: Vim Patches Project. [Was: updated 'relativenumber' patch]

Ben Schmidt wrote: >> As a host I would suggest code google [6], as it has svn access, >> an issue tracker and a wiki. A link to this project from the >> official vim site, will be appropriate (with the usual warnings), >> although not strictly necessary. > > I too have been thinking for some ti

RE: Vim 7.2a in CVS

Christian MICHON wrote: > I also track vim-dev by usually doing this: downloading the > patches, and seldom use CVS/SVN. > > The biggest trouble I see is I need to format > patches/suggestions in the same way, if I do not have write > commit access. OK but surely that comment is for another p

RE: [patch] fixed typos in help files

Dominique Pelle wrote: > Thanks for Vim-7.2a-beta, so far it looks good. I ran the > spelling checker on the help files vim7/runtime/doc/*txt of > Vim-7.2a-beta, and found a few minor typos. I attach the patch. I just did a similar check and found a couple more (I missed several of yours!). P

RE: Vim 7.2a in CVS

Gautam Iyer wrote: > You can wget individual patches from git. > > For example: > > http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel. > git;a=commitdiff_plain;h=0deedbcc98a831284f6e9db2510e88e90e01c > 286;hp=5dd06d08015cf9c0721f34f7005ecd670025c334 I use the FTP server to get p

RE: Vim version 7.2a ready for BETA testing

Bram Moolenaar wrote: > Announcing: Vim (Vi IMproved) version 7.2a BETA I have done a successful compile, build, run and 'make test' on: - Windows XP - Fedora 8 Linux test11.in has: Note: This test will fail if "gzip" is not available. test30.in perhaps should say: Note: This test will fai

RE: Newly updated floating point patch

Bill McCarthy wrote: > For rounding you suggested: > > f >= 0 ? floor(f + 0.5) : -floor(-f + 0.5) > > Slightly simpler is: > > f < 0 ? ceil(f - 0.5) : floor(f + 0.5) > > For truncation you suggested: > > f >= 0 ? floor(f) : -floor(-f) > > Slightly simpler is: > > f < 0 ? cei

RE: Newly updated floating point patch

Bram Moolenaar wrote: > - Added a test. Please try this, I don't know if roundoff > errors might break it. It's a trivial issue, but test65 (floating point) disagrees with Microsoft Visual C MSVC 6.0. Line 11 of test65.in is: :$put =printf('%e', 123.456) Corresponding result expected in tes

RE: Newly updated floating point patch

Bram Moolenaar wrote: > OK, so Borland doesn't have round() and trunc(). I rather > not have a Vim version with only part of the floating point > support. The easy solution is to disable it for Borland in > src/feature.h: > > #ifdef FEAT_NORMAL > # define FEAT_EVAL > # if d

RE: Newly updated floating point patch

Bram Moolenaar wrote: > OK, so Borland doesn't have round() and trunc(). I rather > not have a Vim version with only part of the floating point > support. The easy solution is to disable it for Borland in > src/feature.h: > > #ifdef FEAT_NORMAL > # define FEAT_EVAL > # if d

RE: opening huge files, a little slow

misi wrote: > would like to use vim to edit large files (600mb). The best way to tune Vim for large files is Dr Chip's script: http://www.vim.org/scripts/script.php?script_id=1506 Due to a limitation in how Vim uses 32-bit integers (on a 32-bit system), files over 2GB may not be detected as la

RE: Updated floating point patch

Bram Moolenaar wrote: >> g and G omit superfluos zeroes, as well as the decimal point: >> >> double n = 12; >> printf("%g\n", n); // prints 12 >> printf("%#g\n", n); // prints 12. > > Vim is already using %g. For me the results are different. In Vim, the code in vim_snprintf() (in

RE: Updated floating point patch

Bram Moolenaar wrote: > I mean: Vim is using the library printf() to do the > conversion, but I don't see a way to tell printf() to omit > superfluous zeroes. g and G omit superfluos zeroes, as well as the decimal point: double n = 12; printf("%g\n", n); // prints 12 printf("%#g\n", n)

RE: Updated floating point patch

Ben Schmidt wrote: > math('sqrt',argument) > math('exp',exponent[,base=e]) > math('log',argument[,base=e]) > math('sin',argument[,degrees (bool)=0]) > math('cos',argument[,degrees (bool)=0]) > math('tan',argument[,degrees (bool)=0]) > math('atan',argument[,degrees (bool)=0]) Considering the funct

RE: Updated floating point patch

Mikolaj Machowski wrote: > echo printf("%.0f", "0.4") > E807: expected Float argument for printf() You mean (argument not a string): :echo printf("%.0f", 0.4) > echo printf("%d", "4-2") Same glitch. It's 4-2 not "4-2". > user friendly (eg. store and display 0.5 instead of 0.50) Here is

RE: Updated floating point patch

Bram Moolenaar wrote: > Attached you will find the latest floating point patch. Thanks Bram. I have patched and compiled without incident. A few tests, and a superficial look at the code changes, make me believe that the new float patch is good. As discussed, using strtod() is much more robust.

RE: Updated floating point patch

Bill McCarthy wrote: > does this LC_NUMERIC actually work on Windows - I recall > having problems with LC_ALL using the unix sort of GNU > coreutils - is this an environment variable we need to set? Just to spell out the situation: In a country where ',' is used for the decimal point, a user mi

RE: Floating point syntax

Bill McCarthy wrote: > My eval.c is the current release patched by both your latest > and John Beckett's fix. You new patch fails with: > > vim\vimfp> patch -b -p 0 -i Brams-may_not_work_with_jb.diff > patching file src/eval.c Hunk #1 FAILED at 4799. > 1 out of 1 hunk FAILED -- saving rejects to

RE: vimdiff with one non-existent and one existent file does not show contents ?

Yakov Lerner wrote: > cd /tmp > rm -f nosuchfile # make sure there is no such file > man 1 ls >ls.txt # get some text > vimdiff -U NONE -u NONE ls.txt nosuchfile # as expected > vimdiff -U NONE -u NONE nosuchfile ls.txt # where is contents of right pane > ??? On my system, the text is present i

RE: UTF-8 bomb showing up after :%!sort

Adri Verhoef wrote: > I think there is a problem here, namely that the BOM (Byte > Order Mark, see :help 'bomb') is transferred to the shell > command, when it shouldn't. In my opinion Vim should be able > to temporarily remove the BOM, then execute the shell > command, and finally place the

RE: omnicpp very slow under windows XP

epanda wrote: > I have done two tests and I have two bugreports.txt but I > don't know how to search the difference which make that > omnicpp is very slow under windows and fast under virtual > Linux CentOS. I believe the idea was that you would compare the two files to try and find any differ

<    1   2   3   >