Re: [PATCH] Determining whether a window used :lcd
On 4/11/07, Bob Hiestand [EMAIL PROTECTED] wrote: The attached patch very simply implements the following from the todo: 7 There is no way to change directory and go back without changing the local and/or global directory. Add a way to find out if the current window uses a local directory. Add cdcmd() that returns :cd or :lcd? I personally would prefer the function be called something like 'isdirlocal()'. I need this feature for my vcscommand.vim plugin, which changes directory a fair amount, and can screw up the user environment if the user makes use of :lcd. Does anyone have any feedback on this? Thank you, bob cdcmd.patch Description: Binary data
Re: [PATCH] Determining whether a window used :lcd
Bob Hiestand wrote: On 4/11/07, Bob Hiestand [EMAIL PROTECTED] wrote: The attached patch very simply implements the following from the todo: 7 There is no way to change directory and go back without changing the local and/or global directory. Add a way to find out if the current window uses a local directory. Add cdcmd() that returns :cd or :lcd? I personally would prefer the function be called something like 'isdirlocal()'. I need this feature for my vcscommand.vim plugin, which changes directory a fair amount, and can screw up the user environment if the user makes use of :lcd. Does anyone have any feedback on this? It was still in my pile of messages to read. I agree that a different function would be more useful. I prefer haslocaldir(). This would return zero when the current window uses the global directory, one when it has a local directory. Later we could add an argument for selecting the window. If you agree, and nobody has something to say on this, can you change your patch? -- The only way the average employee can speak to an executive is by taking a second job as a golf caddie. (Scott Adams - The Dilbert principle) /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: syntax highlighting addition
Jonathan Smith wrote: Conary [1] has a file format called a recipe [2] which is in many ways similar in function to a spec file or an ebuild. rPath has been maintaining a syntax highlighting file for this format, but it would be nice if vim would accept a patch to include this in the standard distribution. Attached is just such a patch. Thanks for looking into this. recipe is not a good filetype name. Is there anything against using conary? The syntax file must not start with syntax clear. Look into a few examples in the Vim 7 distribution how this is done properly. I would very much prefer that the author of the file directly sends the syntax file to me. At least for copyright issues. Well, the files are called recipes. In the same way that you wouldn't call a spec file rpm, you wouldn't call a recipe conary. Conary has other file types which it uses, which vim should not be able to edit (changesets, the equivalent of an RPM). Well, then we would need to call it conaryrecipe, but that's quite long. At least you need to be consistent: the name of the filetype is used for the file name, and all syntax items must start with that name. I now notice that you also have items starting with python. That's weird. Is this the result of copypaste or was this intentional? You'll notice that rPath Inc is listed as the author. I am a member of the rPath distro team, and an employee of the same, so copyright shouldn't be an issue. Ah, it's good to know this. Thanks for the tips about syntax clear. Taking an example from the spec.vim file, I have modified the recipe.vim file to hopefully be acceptable. It is once again attached to this email. Getting better. Nikola's comments also apply (thanks Nikola!). -- Sometimes you can protect millions of dollars in your budget simply by buying a bag of cookies, dropping it on the budget anylyst's desk, and saying something deeply personal such as How was your weekend, big guy? (Scott Adams - The Dilbert principle) /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
current file name to apped to an ex command
Hi: I am trying to send a command to shell that invoke cleartools to checkout/in files that I am currently working on. unfortunatly, I am pretty new to vim and I've tried searching throught the man pages, but I cant' seem to figure out how to do so. Any help would be appreciated. Thanks! I have this in my _vimrc file: function! CHANGE_CURR_DIR() let _dir = expand(%:p:h) let _filename = expand(%)//I added this line exec cd . _dir unlet _dir endfunction autocmd BufEnter * call CHANGE_CURR_DIR() I think the above code automatically sets the current working directory to the file that I am editing at the moment and also sets _dir and _filename. I would like to map F12 to execute the following code within the shell. This si what I have so far: map F12 :!cleartool co -c . filenameCR The filename is the current file name that I am editing. I can't seem to figure out how to expand the variable _filename into string to be put into the ex command. Can anyone help me? I've tried many things, but nothing will work -- View this message in context: http://www.nabble.com/current-file-name-to-apped-to-an-ex-command-tf3618091.html#a10102666 Sent from the Vim - General mailing list archive at Nabble.com.
Re: current file name to apped to an ex command
I would like to map F12 to execute the following code within the shell. This si what I have so far: map F12 :!cleartool co -c . filenameCR You might try nnoremap f12 :!cleartool co -c . %cr The percent is expanded to be the current file name. :help :_% has more details on some of these. You even use it in your previous mapping (the %:p:h). If needed, you can even use the same modifiers as in ... -c . %:pcr to specify the full filename-cum-path You might also use lcd (local-cd) instead of cd in your other mapping: :help :lcd in comparison to the help found above it at :help :cd -tim
Re: current file name to apped to an ex command (2)
I have this in my _vimrc file: function! CHANGE_CURR_DIR() let _dir = expand(%:p:h) let _filename = expand(%)//I added this line exec cd . _dir unlet _dir endfunction autocmd BufEnter * call CHANGE_CURR_DIR() You may also want to investigate the 'autochdir' option :help 'autochdir' which exploits Vim's builtin ability to do what you're describing above. -tim
Two different versions of Vim...
Hello, all. This is going to be painfully basic, I'm sure, but I can't find my way around it. I've just clean-installed Ubuntu 7.04 and am busily setting things up the way I want them. Naturally, Vim comes first. :) Ubuntu installed vim as a default package, without GUI enabled. I installed the GUI-related packages, but then decided that I'd rather have all patches up to date and installed Vim via AAP (which I really like, by the way). I ended up with Vim 7.0.224 in text-mode, but version 7.0.164 in GUI mode. Apparently, the Ubuntu-packaged versions install to one place, and the AAP version in another. I removed all Vim-related Ubuntu packages and re-ran the AAP install with --enable-gui=gtk2 in my config.arg file. That's evidently not the correct syntax, since I ended up with no GUI available. Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance.
Re: VimWin
Dear Zhichao, On 20/04/07, Zhichao Hong [EMAIL PROTECTED] wrote: Hi, all, I have been using Vim on the Win32 platform for a few years (since version 5.0). I enjoyed this program greatly. The Win32 build normally does not get patched frequently and the users on that platform cannot take the advantages of the bug fixes as frequently as UNIX user could have. So I normally maintains my own vim build with the latest patches for my personal use. Now I would like to share this with the users. The result from this effort is that I have created the the vimwin project at sourceforge ( http://sourceforge.net/projects/vimwin). Here is the project will help: * Compile Vim on Win32 with the latest VC++ compiler (VC8.0) * Compile Vim with the latest patches * Add misc enhancement that are not available from the original vim. And the source code for the changes/enhancement are always made open and available. The first release I created has the Vim compiled using VC8.0 with patches up to 224. It has the enhancement that can toggle the vim into/out of full screen mode. The F11 is the magic key. You can try this by downloading the software from http://sourceforge.net/projects/vimwin and please provide feedback. I have just installed your version of vim, but I can't figure out how to switch it into full screen mode. I currently have F11 mapped (and I don't wish to change this), so I guess that this is part of the problem, although I have tried removing that line from my _vimrc and I still can't get into full screen mode. If I run gvim -u NONE it works okay. I have tried 'grepping' first the doc/ dir and then the whole vim70 directory, but I can find no relevant mention of full ?screen, so I'm not sure how I can get this to work with my vimrc. Can you tell me the command that F11 is linked to in the default build so that I can test it and/or assign it to another key combination please? I've tried running gvim -u NONE and then typing map F11, but it says no mapping found, implying there is something more cunning going on that I don't understand! Many thanks in advance, Al
Re: Two different versions of Vim...
Please see the following archived message: * http://www.mail-archive.com/vim@vim.org/msg06747.html HTH! Tom Purl On Fri, April 20, 2007 10:09 am, Marv Boyes wrote: Hello, all. This is going to be painfully basic, I'm sure, but I can't find my way around it. I've just clean-installed Ubuntu 7.04 and am busily setting things up the way I want them. Naturally, Vim comes first. :) Ubuntu installed vim as a default package, without GUI enabled. I installed the GUI-related packages, but then decided that I'd rather have all patches up to date and installed Vim via AAP (which I really like, by the way). I ended up with Vim 7.0.224 in text-mode, but version 7.0.164 in GUI mode. Apparently, the Ubuntu-packaged versions install to one place, and the AAP version in another. I removed all Vim-related Ubuntu packages and re-ran the AAP install with --enable-gui=gtk2 in my config.arg file. That's evidently not the correct syntax, since I ended up with no GUI available. Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance.
gvim 7: german umlauts not found when :set ic (Windows)
I realized this by accident in gvim: Ignorecase works *correct*, except my Umlauts (äöüß). When I search for them in lowercase, these *are* found, when they are lowercase, but *not* when they are UPPERCASE. In my old gvim 6.2 they *are* found. Any Ideas? Probably a bug? Or a wrong codepage or something like that? Thank You Joachim Microsoft Windows XP VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7 2006 16:21:39) MS-Windows 32 bit GUI version ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/
Re: Two different versions of Vim...
Also, I forgot to mention that AAP is a perfectly fine way to have a cutting-edge version of Vim on your Ubuntu computer. On Fri, April 20, 2007 10:09 am, Marv Boyes wrote: Hello, all. This is going to be painfully basic, I'm sure, but I can't find my way around it. I've just clean-installed Ubuntu 7.04 and am busily setting things up the way I want them. Naturally, Vim comes first. :) Ubuntu installed vim as a default package, without GUI enabled. I installed the GUI-related packages, but then decided that I'd rather have all patches up to date and installed Vim via AAP (which I really like, by the way). I ended up with Vim 7.0.224 in text-mode, but version 7.0.164 in GUI mode. Apparently, the Ubuntu-packaged versions install to one place, and the AAP version in another. I removed all Vim-related Ubuntu packages and re-ran the AAP install with --enable-gui=gtk2 in my config.arg file. That's evidently not the correct syntax, since I ended up with no GUI available. Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance.
Re: current file name to apped to an ex command
On 2007-04-20, darkwalk [EMAIL PROTECTED] wrote: Hi: I am trying to send a command to shell that invoke cleartools to checkout/in files that I am currently working on. unfortunatly, I am pretty new to vim and I've tried searching throught the man pages, but I cant' seem to figure out how to do so. Any help would be appreciated. Thanks! If you're using ClearCase, I'd recommend Doug Potts's ccase.vim script, http://vim.sourceforge.net/scripts/script.php?script_id=15 HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
RE: Mapping M-CR doesn't work
I'm using GVIM on WinXP SP2: I'm trying to map ALT-ENTER. It doesn't work (I just get enter). Uhhh, ain't alt-enter trapped by the OS, ie, to switch between window/console modes?
Re: Two different versions of Vim...
On Fri, 20 Apr 2007 11:09:11 -0400 Marv Boyes [EMAIL PROTECTED] wrote: Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance. I think the problem with the GUI is that Ubuntu installs its X11 libraries and headers in non-standard locations; you have to pass these locations to the configure script. Unfortunately, if you fail to pass these, and configure can't find the X11 libs or includes in their default locations, but receives the --enable-gui option, it won't quit. Instead, it will quietly build a non-gui version, despite what you told it. I'd wager that's probably what you're experiencing. AAP is OK for patching and keeping up-to-date, as long as the recipe is updated as patches are released. Unfortunately, I have not always found these to be right in sync, and it has been my experience that a more time-accurate way to track patches is through the patch README file, located on the Vim website. I've also had issues with AAP builds generating segmentation faults when you run the :version command. (Ironically, manually building source from an AAP fetch works fine...) To get around these, I wrote a Perl script that automatically fetches source and patches, then configures Vim for a very full-featured installation. Downloads are conserved so that when a new patch comes out, you just re-run the script which will then fetch only the new patch and rebuild the source tree from the archives it has kept. It's not extremely user-friendly (yet) and may require some tweaking by hand, but by default offers these configuration options: * features = huge * gui = gtk2 * multibyte * perl / python / ruby / scheme If you're interested (and by now I certainly am tooting my own horn, sorry) you can fetch it from my website at: http://www.metasyntax.net/?section=codepage=devel#vim-builder You may also want to check out the Vi Improved page on my site for more information about installation on Ubuntu, including how to enable Scheme support. If you decide to use my script, please let me know that it works / what you think about it. I'd like to add some more user-friendly features (prompts or command-line switches to enable config options, etc) when I get some more time / motivation to work on it. Happy Vimming! -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: Esperanto dictionary
On 4/20/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Please take the existing $VIMRUNTIME/spell/eo/main.aap and modify it a bit to build the .spl file. This can't be very difficult, you would mostly use the command you type manually. OK, I'll try this. Probably tomorrow. What is strange is that myspell uses eo_l3 and you have eo_EO and eo_UX. Why two regions? Esperanto language uses some letters from Latin3 character set. Of course, they are in Unicode too. But during half-century in ASCII-based world there was established some conventions for transcribing these letters in pure ASCII. There are still some disagreements which one is most popular, or most standard, or most suitable, but I believe that Cxirkaux-convention is most widely used (no, I can't prove this with statistics). The convention is named Cxirkaux after transcription of the word Ĉirkaŭ (I hope you have an appropriate font installed to read this). It is handy to be able to check Esperanto text in both modes (or choose any one of two). Probably to make two files -- eo.ascii.spl and eo.utf-8.spl -- will be theoretically more pure, but my solution allows to switch between two modes fast. -- Cyril Slobin [EMAIL PROTECTED] `When I use a word,' Humpty Dumpty said, http://45.free.net/~slobin `it means just what I choose it to mean'
Re: Two different versions of Vim...
On Fri, April 20, 2007 11:29 am, Marv Boyes wrote: 1- After removing every trace of Ubuntu's default-installed vim, I installed the following from repositories: vim-common vim-full vim-gui-common That gave me vim with the GNOME2 interface. The command 'gvim' runs Vim 7.0.164 with a GUI. The command 'vim' returns the error /usr/local/bin/vim: No such file or directory. So, apparently, text-mode vim vanished for some reason, or my paths got screwed up. (Please pardon the undoubtedly inaccurate terminology.) Check your ~/.bashrc and ~/.bash_profile files to see if you have a vim alias pointing at that location. Also, your EDITOR system variable might be pointing at that explicit location. You can check that variable using the following command: $ echo $EDITOR If your editor is pointing at /usr/local/bin/vim, then you may want to just change it to vim. 2- After removing every trace of Vim as installed above, I ran AAP with --enable-gui=gnome2 in my config.arg. I got Vim 7.0.224 in text-mode, but the GUI is reported as having _not_ been enabled at compile time. Ok, first, did you run the build-dep commands that I referenced in my previous e-mail message? Please note that I didn't ask you to run apt-get install; you should be running apt-get build-dep in order to install all of the gui dependencies that Vim requires. Next, you don't have to uninstall the Ubuntu version of Vim in order to install the AAP version. It's my understanding that AAP installs the vim folder tree under /usr/local, not /usr (like the Ubuntu package). Not uninstalling the Ubuntu packages if they're already there will probably save you time and make troubleshooting easier. Now, if you installed the gui dependencies and are still having problems, then we need to find someone who's more familiar with AAP. If I were install vim from source the old fashioned-way, I would do the following: $ cd /arbitrary/vim/build/dir $ ./configure --enable-gui=gnome2 21 | tee ./config.custom (the previous command configures vim and sends STDOUT and STDERR to the config.custom file. Tee is used to also send all output to the terminal) (lots of output) $ grep -i error ./config.custom $ grep -i exception ./config.custom $ grep -i gui ./config.custom $ grep -i gnome ./config.custom (the previous three commands tell you if there were any problems with the config. The gui search is especially important) I'm assuming you can do some similar troubleshooting using AAP, but I'm not familiar with that process. Does anyone else know how you can do this with AAP? Again, I'm sorry if I'm missing something extremely basic; it's just that nothing I'm trying is working. No reason to apologize, a lot of people have had problems compiling vim with gui support in the past. Also, there aren't really any trolls on this list, so you don't have to walk on egg shells :) HTH! Tom Purl
Re: VimWin
* A. S. Budden [EMAIL PROTECTED] [070420 20:50]: Dear Zhichao, On 20/04/07, Zhichao Hong [EMAIL PROTECTED] wrote: Hi, all, I have been using Vim on the Win32 platform for a few years (since version 5.0). I enjoyed this program greatly. The Win32 build normally does not get patched frequently and the users on that platform cannot take the advantages of the bug fixes as frequently as UNIX user could have. So I normally maintains my own vim build with the latest patches for my personal use. Now I would like to share this with the users. The result from this effort is that I have created the the vimwin project at sourceforge ( http://sourceforge.net/projects/vimwin). The Cream project also provides binaries for windows: http://cream.sourceforge.net/ There are also some other binaries for windows out there. Here is the project will help: * Compile Vim on Win32 with the latest VC++ compiler (VC8.0) * Compile Vim with the latest patches * Add misc enhancement that are not available from the original vim. And the source code for the changes/enhancement are always made open and available. The first release I created has the Vim compiled using VC8.0 with patches up to 224. It has the enhancement that can toggle the vim into/out of full screen mode. The F11 is the magic key. You can try this by downloading the software from http://sourceforge.net/projects/vimwin and please provide feedback. I have just installed your version of vim, but I can't figure out how to switch it into full screen mode. I currently have F11 mapped (and I don't wish to change this), so I guess that this is part of the problem, although I have tried removing that line from my _vimrc and I still can't get into full screen mode. If I run gvim -u NONE it works okay. I have tried 'grepping' first the doc/ dir and then the whole vim70 directory, but I can find no relevant mention of full ?screen, so I'm not sure how I can get this to work with my vimrc. Can you tell me the command that F11 is linked to in the default build so that I can test it and/or assign it to another key combination please? I've tried running gvim -u NONE and then typing map F11, but it says no mapping found, implying there is something more cunning going on that I don't understand! I think on Windows :simalt ~x should do it. Many thanks in advance, Al
css indenting
Hello everyone, How do I get vim to stop adding an indent to a line when the previous line ends with a semicolon? This happens when I am editing a CSS file. What options should I be looking at? Thank you for your time, Michael Michael D. Phillips - A computer science enthusiast I do not hate Windows, I just like the alternatives better. Linux is my primary choice. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: wish: collaboration of N vim instances editing same file
On 4/20/07, cga2000 [EMAIL PROTECTED] wrote: collaboration of N vim instances editing same file [there was some text] See the screen(1) man page and search for multi. Are you (Is he) talking about several users concurrently modifying the same file(s) .. possibly from different geographic locations? I can't think of any valid reason why one lonely user - me for instance - would want to fire up several instances of vim to edit the same file. It can be. For example, in LNX user can edit file in text console, then switch to X11 and then start editor again to edit the same file, forgetting that other instance of VIM already launched. I in this case just do killall vim(or killall -9 vim, depending on mood).
Re: VimWin
I am aware of the the cream project. Unfortunately they are the gnu compilers. As I have a professional Visual C++ compiler, and Vim is such as great tool, I would like to compile it with the latest professional tool. I don't intent to stir flame war between gnu and microsoft compilers. Also, cream does not always update to the latest patch. There is a delay sometimes I could not wait. The simalt ~x trick is not what you can get. It only maximize the app not make it a full screen. In the full screen, I mean, the title bar is hidden. The app is taking the whole screen space that is availabel. Yes, it will also hide the taskbar behind it because it is the full screen. You can experiment this with Firefox, Acrobat reader, etc. The main benefit of full screen to allow you concentrate. And of course to show off the vim editor. Thanks for the simalt ~x trick anyway. Zhichao On 4/20/07, Dimitar [EMAIL PROTECTED] wrote: * A. S. Budden [EMAIL PROTECTED] [070420 20:50]: Dear Zhichao, On 20/04/07, Zhichao Hong [EMAIL PROTECTED] wrote: Hi, all, I have been using Vim on the Win32 platform for a few years (since version 5.0). I enjoyed this program greatly. The Win32 build normally does not get patched frequently and the users on that platform cannot take the advantages of the bug fixes as frequently as UNIX user could have. So I normally maintains my own vim build with the latest patches for my personal use. Now I would like to share this with the users. The result from this effort is that I have created the the vimwin project at sourceforge ( http://sourceforge.net/projects/vimwin). The Cream project also provides binaries for windows: http://cream.sourceforge.net/ There are also some other binaries for windows out there. Here is the project will help: * Compile Vim on Win32 with the latest VC++ compiler (VC8.0) * Compile Vim with the latest patches * Add misc enhancement that are not available from the original vim. And the source code for the changes/enhancement are always made open and available. The first release I created has the Vim compiled using VC8.0 with patches up to 224. It has the enhancement that can toggle the vim into/out of full screen mode. The F11 is the magic key. You can try this by downloading the software from http://sourceforge.net/projects/vimwin and please provide feedback. I have just installed your version of vim, but I can't figure out how to switch it into full screen mode. I currently have F11 mapped (and I don't wish to change this), so I guess that this is part of the problem, although I have tried removing that line from my _vimrc and I still can't get into full screen mode. If I run gvim -u NONE it works okay. I have tried 'grepping' first the doc/ dir and then the whole vim70 directory, but I can find no relevant mention of full ?screen, so I'm not sure how I can get this to work with my vimrc. Can you tell me the command that F11 is linked to in the default build so that I can test it and/or assign it to another key combination please? I've tried running gvim -u NONE and then typing map F11, but it says no mapping found, implying there is something more cunning going on that I don't understand! I think on Windows :simalt ~x should do it. Many thanks in advance, Al -- Zhichao Hong, CSDP [EMAIL PROTECTED]
Re: VimWin
Dimitar, Sorry, the only way to use this feature is to use F11 key. I agree it is kind of rude. I am looking into how to make it full screen with a normal vim command. Then you will be able to map to any arbitrary keys. I think some plugins might map F11 key for you. So you can do a find-grep in your vimfiles directory and see who is taking this key. Stay tuned, I will make the full screen not so intrusive in the near future. Thanks for trying out this tool. Zhichao On 4/20/07, Dimitar [EMAIL PROTECTED] wrote: * A. S. Budden [EMAIL PROTECTED] [070420 20:50]: Dear Zhichao, On 20/04/07, Zhichao Hong [EMAIL PROTECTED] wrote: Hi, all, I have been using Vim on the Win32 platform for a few years (since version 5.0). I enjoyed this program greatly. The Win32 build normally does not get patched frequently and the users on that platform cannot take the advantages of the bug fixes as frequently as UNIX user could have. So I normally maintains my own vim build with the latest patches for my personal use. Now I would like to share this with the users. The result from this effort is that I have created the the vimwin project at sourceforge ( http://sourceforge.net/projects/vimwin). The Cream project also provides binaries for windows: http://cream.sourceforge.net/ There are also some other binaries for windows out there. Here is the project will help: * Compile Vim on Win32 with the latest VC++ compiler (VC8.0) * Compile Vim with the latest patches * Add misc enhancement that are not available from the original vim. And the source code for the changes/enhancement are always made open and available. The first release I created has the Vim compiled using VC8.0 with patches up to 224. It has the enhancement that can toggle the vim into/out of full screen mode. The F11 is the magic key. You can try this by downloading the software from http://sourceforge.net/projects/vimwin and please provide feedback. I have just installed your version of vim, but I can't figure out how to switch it into full screen mode. I currently have F11 mapped (and I don't wish to change this), so I guess that this is part of the problem, although I have tried removing that line from my _vimrc and I still can't get into full screen mode. If I run gvim -u NONE it works okay. I have tried 'grepping' first the doc/ dir and then the whole vim70 directory, but I can find no relevant mention of full ?screen, so I'm not sure how I can get this to work with my vimrc. Can you tell me the command that F11 is linked to in the default build so that I can test it and/or assign it to another key combination please? I've tried running gvim -u NONE and then typing map F11, but it says no mapping found, implying there is something more cunning going on that I don't understand! I think on Windows :simalt ~x should do it. Many thanks in advance, Al -- Zhichao Hong, CSDP [EMAIL PROTECTED]
indenting
How does one start debugging indent? I am trying to figure out how to change the behavior. Any help would be greatly appreciated. Michael Michael D. Phillips - A computer science enthusiast I do not hate Windows, I just like the alternatives better. Linux is my primary choice. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Esperanto dictionary
Cyril Slobin wrote: On 4/20/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Please take the existing $VIMRUNTIME/spell/eo/main.aap and modify it a bit to build the .spl file. This can't be very difficult, you would mostly use the command you type manually. OK, I'll try this. Probably tomorrow. Good. What is strange is that myspell uses eo_l3 and you have eo_EO and eo_UX. Why two regions? Esperanto language uses some letters from Latin3 character set. Of course, they are in Unicode too. But during half-century in ASCII-based world there was established some conventions for transcribing these letters in pure ASCII. There are still some disagreements which one is most popular, or most standard, or most suitable, but I believe that Cxirkaux-convention is most widely used (no, I can't prove this with statistics). The convention is named Cxirkaux after transcription of the word ÄirkaÅ (I hope you have an appropriate font installed to read this). It is handy to be able to check Esperanto text in both modes (or choose any one of two). Probably to make two files -- eo.ascii.spl and eo.utf-8.spl -- will be theoretically more pure, but my solution allows to switch between two modes fast. OK. So when the user does :set spl=eo_eo he still gets the pure version? It's important that the user has a choice of what words he wants to accept. -- I recommend ordering large cargo containers of paper towels to make up whatever budget underruns you have. Paper products are always useful and they have the advantage of being completely flushable if you need to make room in the storage area later. (Scott Adams - The Dilbert principle) /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Esperanto dictionary
On 4/21/07, Bram Moolenaar [EMAIL PROTECTED] wrote: OK. So when the user does :set spl=eo_eo he still gets the pure version? It's important that the user has a choice of what words he wants to accept. Yes. Setting eo_eo accepts unicode Ĉirkaŭ only, setting eo_ux accepts ascii Cxirkaux only, setting eo accepts both. And again -- I have not tested latin3 version of spl file, I never use latin3. -- Cyril Slobin [EMAIL PROTECTED] `When I use a word,' Humpty Dumpty said, http://45.free.net/~slobin `it means just what I choose it to mean'
Re: wish: collaboration of N vim instances editing same file
On Fri, Apr 20, 2007 at 03:55:33PM EDT, Andrew Maykov wrote: On 4/20/07, cga2000 [EMAIL PROTECTED] wrote: collaboration of N vim instances editing same file [there was some text] See the screen(1) man page and search for multi. Are you (Is he) talking about several users concurrently modifying the same file(s) .. possibly from different geographic locations? I can't think of any valid reason why one lonely user - me for instance - would want to fire up several instances of vim to edit the same file. It can be. For example, in LNX user can edit file in text console, then switch to X11 and then start editor again to edit the same file, forgetting that other instance of VIM already launched. I in this case just do killall vim(or killall -9 vim, depending on mood). Yeah .. I know .. the recipe for a happy life is good health and a bad memory .. I have neither .. so accounting for folks who happen to be forgetful sounds a bit far-fetched to me .. :-) And should vim take into account the foibles of different categories of users in the first place? Thanks, cga
Re: vim doesn't sort numerical fields
I wanted to sort the first field numerically of a text applying the functions of Dr. Chip but all I can achieve is the following: - 977 ./gnuwin/coreutils-5.3.0-dep 9784 ./RESKIT 98./gnuwin/coreutils-5.3.0-9/usr/share/locale/af 987 ./Unison/Orchestral 9882 ./mac/PC Mac Lan_9_FULL/pmac2K/GSSetup/gs7.05 99./WinFIG15/WinFIG/doc - Is it possibile to sort the 1. first field numerically and how? The :sort command takes several options to tweak its behavior. It looks like you may want :%sort n to sort numerically rather than ASCII-wise. -tim
Re: Esperanto dictionary
Bram Moolenaar wrote: Cyril Slobin wrote: On 4/20/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Please take the existing $VIMRUNTIME/spell/eo/main.aap and modify it a bit to build the .spl file. This can't be very difficult, you would mostly use the command you type manually. OK, I'll try this. Probably tomorrow. Good. What is strange is that myspell uses eo_l3 and you have eo_EO and eo_UX. Why two regions? Esperanto language uses some letters from Latin3 character set. Of course, they are in Unicode too. But during half-century in ASCII-based world there was established some conventions for transcribing these letters in pure ASCII. There are still some disagreements which one is most popular, or most standard, or most suitable, but I believe that Cxirkaux-convention is most widely used (no, I can't prove this with statistics). The convention is named Cxirkaux after transcription of the word ĈirkaÅ (I hope you have an appropriate font installed to read this). It is handy to be able to check Esperanto text in both modes (or choose any one of two). Probably to make two files -- eo.ascii.spl and eo.utf-8.spl -- will be theoretically more pure, but my solution allows to switch between two modes fast. OK. So when the user does :set spl=eo_eo he still gets the pure version? It's important that the user has a choice of what words he wants to accept. I think you got it. For any people who'd want a better understanding of the matter, here's what I could think of as an explanation: The non-ASCII letters in the Esperanto variant of the Latin alphabet are the following (in upper and lower case): Ĉĉ, C-circumflex Ĝĝ, G-circumflex Ĥĥ, H-circumflex Ĵĵ, J-circumflex Ŝŝ, S-circumflex Ŭŭ, U-breve There are at several known ways to transliterate them to ASCII, and Esperantists have been arguing without end about which one was the better, with partisans of the first and last ones below flaming each other for weeks on end in the Usenet group soc.culture.esperanto and elsewhere: * h-method. In the original work which brought Esperanto to the public in 1887, the work The International Language in five languages (Russian, Polish, French, German, and English) by D-ro Esperanto, a nom-de-plume of Dr. Louis Lazarus Zamenhof, there was an additional sentence under the Alphabet (I'm quoting from the English edition): *Remark.* -- If it be found impracticable to print works with the diacritical signs (^,˘), the letter h may be substituted for the sign (^), and the sign (˘) may be omitted altogether. IOW: ch, gh, hh, jh, sh, u. One problem of this official or Fundamental notation is that it creates ambiguities between u and u-breve, and between letter+circumflex and letter+h. The latter can be found in e.g. chashundo (chas- +hundo, a hunting dog), danchalo (danc- + halo, a ballroom), etc. It is, however, most natural-looking in that the most-used of these, c-circumflex and s-circumflex, have exactly the sound of English ch and sh; and u-breve, which represents the semivowel [w], is used almost exclusively after a vowel, to form the second part of the closing diphongs [au] [eu] and, rarely, [ou]. (U-breve also occurs initially in a few imported words like uato (hydrophilic) cotton; cotton wool, from French ouate.) Examples: chasi to hunt, ghardeno a garden, ehho an echo, bovajho beef, shajni to seem, preskau almost. * Slavic method (for use on Latin typewriters for East-European countries): replace the circumflex or breve by a caron (a superscript similar in shape to the letter v). This method, though unofficial like all the ones below, is also somewhat natural-looking, at least for Slavic-language people. * pre-circumflex method: ^c, ^g, ^h, ^j, ^s, ^u * post-circumflex method: c^, g^, h^, j^, s^, u^ * x-method: cx, gx, hx, jx, sx, ux. This one has been widely used on computer systems (see at bottom) but it requires _three_ (not two) case variants for each letter: uppercase (for titles in all-caps), CX GX HX JX SX UX; titlecase (for the first letter of a sentence or of a proper noun etc.), Cx Gx Hx Jx Sx Ux; lowercase, cx gx hx jx sx ux. All the above except the first avoid ambiguities, because Esperanto doesn't use the letter X (or a freestanding circumflex); but they (especially the latter three) have been variously described as ugly and as contrary to the «Fundamento de Esperanto». Add to these, any of the above except the last, with u-breve replaced by u-grave (which, like the dead-key circumflex, can be found on any typewriter for the French language). IIUC, the eo_EO region would use the actual letters with superscripts (as found in Latin3 or Unicode), and the eo_UX region would use method 4, which is widely used on computer systems, including in e-mails emanating from the Universal Esperanto Association (i.e., the Esperantist headquarters) in Rotterdam. Best regards, Tony. -- Our country has plenty of good five-cent cigars,
Re: VimWin
Zhichao Hong wrote: [...] The Win32 build normally does not get patched frequently and the users on that platform cannot take the advantages of the bug fixes as frequently as UNIX user could have. [...] The Win32 binary build available on the ftp.vim.org site doesn't get patched, it only gets updated for new releases (the latest one was 7.0). But the distribution available at https://sourceforge.net/project/showfiles.php?group_id=43866package_id=39721 is usually updated within a few days of every new bugfix. Notwithstanding the fact that it is on one of the Cream for Vim project pages on SourceForge, this distribution does not contain any of the Cream additions and patches -- it is plain-vanilla vim and gvim as compiled from official sources, together with copies of the latest official runtime files. Best regards, Tony. -- F: When into a room I plunge, I Sometimes find some VIOLET FUNGI. Then I linger, darkly brooding On the poison they're exuding. -- The Roguelet's ABC
Re: VimWin
Zhichao Hong wrote:
Dimitar,
Sorry, the only way to use this feature is to use F11 key. I agree
it is kind of rude. I am looking into how to make it full screen with
a normal vim command. Then you will be able to map to any arbitrary
keys.
If it is properly patched into gvim C/C++ code, you ought to be able to use
it e.g. in the {rhs} of a :nnoremap to use a different key for it, even if
there is another mapping with F11 as the {lhs}.
I think some plugins might map F11 key for you. So you can do a
find-grep in your vimfiles directory and see who is taking this key.
Stay tuned, I will make the full screen not so intrusive in the near
future.
Thanks for trying out this tool.
Zhichao
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
181. You make up words that go with the happy tune your modem makes
while dialing your ISP.
Re: VimWin
Zhichao Hong wrote: I am aware of the the cream project. Unfortunately they are the gnu compilers. As I have a professional Visual C++ compiler, and Vim is such as great tool, I would like to compile it with the latest professional tool. I don't intent to stir flame war between gnu and microsoft compilers. Also, cream does not always update to the latest patch. There is a delay sometimes I could not wait. [...] It doesn't hurt to have more than one supplier for a single product, so your contribution is welcome. However, please understand that the higher price tag on the VC++ compiler, or the Professional label on its box, don't necessarily make it a higher-quality product than the open-source gcc compiler. Tagging a product Professional and upping its price are purely commercial (merchandising, marketing) methods to make the gullible customer _believe_ that the product is of a higher quality. In my experience, when it goes about the computer world, more often than not the product in question is of _lower_ quality than the open-source (almost-)free equivalent. Cases in point: - Microsoft Windows XP Professional (I haven't tested Vista, but from what I hear it could also serve here) vs. openSUSE Linux. - Internet Explorer vs. Firefox. - Notepad vs. gvim. - Etc... Best regards, Tony. -- Mollison's Bureaucracy Hypothesis: If an idea can survive a bureaucratic review and be implemented it wasn't worth doing.
Re: Mapping M-CR doesn't work
Matthew Gilbert wrote: Gene Kwiecinski wrote: I'm using GVIM on WinXP SP2: I'm trying to map ALT-ENTER. It doesn't work (I just get enter). Uhhh, ain't alt-enter trapped by the OS, ie, to switch between window/console modes? I'm using GVIM. Also, I can enter CTRL-V_ALT-ENTER and M-CR is inserted at the command line without issue. Thanks though. _matt This at least means that gvim is getting the alt-enter keystroke all right. Can you use at least one of :inoremap M-CR Meta-Carriage-Return or :inoremap A-Enter Alt-Enter after starting Vim with gvim -u NONE -N ? If you can, then there is something that overrides it when you use your usual vimrc and plugins. Best regards, Tony. -- Please take note:
Re: gvim 7: german umlauts not found when :set ic (Windows)
[EMAIL PROTECTED] wrote: I realized this by accident in gvim: Ignorecase works *correct*, except my Umlauts (äöüß). When I search for them in lowercase, these *are* found, when they are lowercase, but *not* when they are UPPERCASE. In my old gvim 6.2 they *are* found. Any Ideas? Probably a bug? Or a wrong codepage or something like that? Thank You Joachim Microsoft Windows XP VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7 2006 16:21:39) MS-Windows 32 bit GUI version ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ Changing the setting of the 'casemap' option (q.v.) might (or might not) help you. This option was added in 6.1.221 so it should work in both 6.2 and 7.0, but maybe your vimrc (or something) is setting it to different values? Possible settings: :set casemap= :set casemap=internal :set casemap=keepascii :set casemap=internal,keepascii (the latter one is the compiled-in default). Best regards, Tony. -- A pretty young lady named Vogel Once sat herself down on a molehill. A curious mole Nosed into her hole -- Ms. Vogel's ok, but the mole's ill.
How can I get rid of this popup?
I recently installed vim 7.x and I'm very impressed with all the new features, especially the new tab stuff .. On the other hand, I'm sorry to say that there is _ONE_ feature that's literally driving me _NUTS_. If I hit the CTRL-P combo by accident .. p is very close to [ .. and I use CTRL-[ a lot .. well, some popup menu materializes out of the blue .. presenting me with a list of completion choices .. Thanks, but I am not senile or otherwise mentally challenged .. I know what I want to type .. and most of the time vim does not .. and since I can type reasonably well .. I do _NOT_ need this completion feature. Is there any way I can turn of this completion popup .. ? Since unwanted popups is one of the absolute evils of the web .. I'm unsure why this should have become a default feature of the current version vim and I sincerely hope it will cease to be the default with the next release. Maybe this might make some sense for GUI users .. but could it be left our of the terminal version? Thanks, cga
Re: How can I get rid of this popup?
On Fri, 20 Apr 2007 22:34:35 -0400 cga2000 [EMAIL PROTECTED] wrote: Is there any way I can turn of this completion popup .. ? One way to turn it off completely is to compile Vim without the insert_expand feature. Or remap C-p in insert mode to do nothing. Since unwanted popups is one of the absolute evils of the web .. I'm unsure why this should have become a default feature of the current version vim and I sincerely hope it will cease to be the default with the next release. I don't really see how this relates to the Internet, but I for one find this feature highly useful, especially when typing some long function name that I've already used before. Plus it's very flexible in what it can do, and where it will look for completions. Maybe this might make some sense for GUI users .. but could it be left our of the terminal version? I think the prevailing thought is that this feature is pretty valuable -- and you can always turn it off if you don't like it (see above). REFERENCES - :help insert_expand :help 'complete' -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: How can I get rid of this popup?
cga2000 wrote: I recently installed vim 7.x and I'm very impressed with all the new features, especially the new tab stuff .. On the other hand, I'm sorry to say that there is _ONE_ feature that's literally driving me _NUTS_. If I hit the CTRL-P combo by accident .. p is very close to [ .. and I use CTRL-[ a lot .. well, some popup menu materializes out of the blue .. presenting me with a list of completion choices .. Thanks, but I am not senile or otherwise mentally challenged .. I know what I want to type .. and most of the time vim does not .. and since I can type reasonably well .. I do _NOT_ need this completion feature. Is there any way I can turn of this completion popup .. ? Since unwanted popups is one of the absolute evils of the web .. I'm unsure why this should have become a default feature of the current version vim and I sincerely hope it will cease to be the default with the next release. Maybe this might make some sense for GUI users .. but could it be left our of the terminal version? Thanks, cga :imap C-P Nop will make it do nothing. Another possibility (I think) is :set complete= which should (IIUC) disable both Ctrl-N and Ctrl-P except when the popup is _already_ up. A third possibility is to disable the +insert_expand feature at compile-time. BTW, me too I know what I want to type, but I found out recently that for _long_ words which have already been used in the current session (or in any file still listed in the buffer list) it is often more efficient (and less error-prone) to type the first letter(s) then Ctrl-N, then maybe a few additional Ctrl-N's to select the right entry, than to type the whole shebang by hand again. If there are too many completions, Ctrl-P to get back to what I typed then add letters one by one, will usually narrow the choices to just a few, including the one I want. And yes, I use mostly gvim, but I would use it the same way in Console vim. As for making it the default in console Vim only, I don't see why a feature which works identically in gvim and console Vim should have different defaults in both, especially when it is easy to disable it in the vimrc. As for disabling Insert-mode completion by default in both console Vim and gvim, don't count on it: Bram has a long history of preferring whatever doesn't break existing behaviour, and I can't fault him on that. ;-) Best regards, Tony. -- Hackers know all the right MOVs.
