Re: [bug report] C syntax broken with anonymous arrays
Marc Chantreux wrote:
> After reading
> http://www.run.montefiore.ulg.ac.be/~martin/resources/kung-f00.html
> I now use anonymous arrays in C. This is an exemple of use:
>
> result = ldap_search_s( ld
> , "dc=u-strasbg,dc=fr"
> , LDAP_SCOPE_ONELEVEL
> , NULL
> , (char *[]){ "objectClass","dc", NULL }
> , 0
> , &msg
> );
>
> Unfortunatly, the { of the array and all the following { and } are
> marked as cErrInParen and i'm not skilled enougth to fix the problem. So
> i'm sorry to just report it.
The normal C syntax uses highlighting of { and } inside () to indicate a
missing ). There is no other way to show this common mistake.
If you really use { and } inside () you can disable the highlighting
with this line in your vimrc file:
let c_no_curly_error = 1
--
hundred-and-one symptoms of being an internet addict:
142. You dream about creating the world's greatest web site.
/// 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: VimWiki - released finally
Sebastian Menge wrote: > [cross-posted to vim, vim-dev, vim-announce, wikia-l] > > Hi all > > Finally I have imported all the vim tips from http://vim.org/tips to > > http://vim.wikia.com > > and set up a minimal infrastructure to keep things going. Not everything > is perfect, but I think it is usable now. > > Thanks to all the support from vim@vim.org and especially to the very > kind wikia community (#wikia on freenode and the mailing list, > Greetings!). > > Some words on contribution: A good wiki depends on two main factors: > Excellent content and a lively community. We have a lot of good content > now, but to make it excellent we need You! > > If you ever posted a tip or a comment to the old tips database, please > have a look at it on the wiki, and review the page. Every little bit > helps! > > See you on the wiki, Sebastian. Great! Let's await comments for a few days, then I'll add a few links on www.vim.org to the tips wiki. That should give the wiki quite a bit more traffic. How about redirecting http://www.vim.org/tips/tip.php?tip_id=805 to http://vim.wikia.com/wiki/VimTip805 (where 805 is an arbitrary number)? The Tips pages appear to load a bit slow, but otherwise it looks like all the info from the old pages is there. -- I wish there was a knob on the TV to turn up the intelligence. There's a knob called "brightness", but it doesn't seem to work. /// 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: Stable Vim version 7.1 has been released
Yongwei Wu wrote: > > > On 13/05/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > > > > > Announcing: Vim (Vi IMproved) version 7.1 > > > > > > I guess you already know about them. Just in case: > > > > > > * The home page still says "Vim 7.0.243 is the current version" > > > > That should be fixed automatically when the first patch goes out, > > which will be soon... > > I see it now :-) > > > > * Sources and Patches pages are not updated. > > > > Please give me the URL of where something wrong appears. That saves > > me a lot of time (which I don't have much of...). > > OK. Checking more thoroughly now. > > http://www.vim.org/download.php > The left side still has (wow, should be a long time ago, and I did > not notice it all the time): "Vim 6.4 has been released. Many people > have helped...". > > http://www.vim.org/sources.php > The information is about Vim 7.0 and 6.4, but no 7.1. > > http://www.vim.org/patches.php > Only 7.0 README. > > http://www.vim.org/subversion.php > 7.1 is marked unstable there. Thanks, I've updated them. - Bram -- hundred-and-one symptoms of being an internet addict: 133. You communicate with people on other continents more than you do with your own neighbors. /// 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: Stable Vim version 7.1 has been released
Davic Necas wrote: > On Mon, May 14, 2007 at 02:24:09PM +0200, Bram Moolenaar wrote: > > > > This is not a bug, an empty src/auto/config.h is included, because > > otherwise "make depend" doesn't work. > > I would rather say this means an additional problem in the > Makefiles. If a rule requires src/auto/config.h, it should > create it (directly or indirectly by dependences) when it > does not exist. That's what make is for. This is a chicken-egg problem: You can't generate src/auto/config.h without figuring out dependencies first. I ran into this problem once and having to create an empty config.h file manually is bad. > If `make distclean' can remove src/auto/config.h and create > it empty, why it cannot be created [empty] by the thing that > actually needs it? Hmm, perhaps that would work. Perhaps someone can try it out. The trick is to make it so that you don't rebuild too often. > This indeed works strangely; for instance `make -jN' with > N > 1 works with freshly unpacked sources, but it breaks > completely after `make distclean' -- which one would expect > to get the source tree to the same state. Well, figure out why it breaks and fix it... -- hundred-and-one symptoms of being an internet addict: 126. You brag to all of your friends about your date Saturday night...but you don't tell them it was only in a chat room. /// 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: Stable Vim version 7.1 has been released
Yongwei Wu wrote: > On 13/05/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > Announcing: Vim (Vi IMproved) version 7.1 > > I guess you already know about them. Just in case: > > * The home page still says "Vim 7.0.243 is the current version" That should be fixed automatically when the first patch goes out, which will be soon... > * Sources and Patches pages are not updated. Please give me the URL of where something wrong appears. That saves me a lot of time (which I don't have much of...). -- The difference between theory and practice, is that in theory, there is no difference between theory and practice. /// 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: Stable Vim version 7.1 has been released
Edward L. Fox wrote: > On 5/14/07, David Neèas (Yeti) <[EMAIL PROTECTED]> wrote: > > On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: > > > > Umm, I suspect there's still an issue for us pesky OSX users with our > > > > case-insensitive filesystems: > > > > > > > > [long list of successful updates snipped] > > > > svn: Failed to add file 'src/auto/config.h': object of the same name > > > > already exists > > > > > > Gah. Scrub that. Manually removing the file in question and updating > > > again has sorted it (that's the first time I've had Subversion complain > > > over several updates). > > > > > > Sorry for the noise... > > > > Actually, this is a repository bug. src/auto/config.h is > > fully generated therefore it should not be versioned. > > Yes, it's a bug. I can fix the problem, but not yet. Because I shall > also need to delete the corresponding files in the CVS repository to > keep the two repositories' consistency. If Bram would grant me such > permission to delete these unnecessary files in the CVS and SVN > repository, I'll do it right away. I already have the CVS writing > privilege, so the only thing I need is just a permission. :-) This is not a bug, an empty src/auto/config.h is included, because otherwise "make depend" doesn't work. The problem is that when running configure the file is overwritten by a non-empty one. When you update from CVS later it fails. But that is OK, just ignore the error. It would be nicer if we have some way to avoid the error message, but I don't know how. -- hundred-and-one symptoms of being an internet addict: 125. You begin to wonder how often it REALLY is necessary to get up and shower or bathe. /// 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: Stable Vim version 7.1 has been released
Edward L. Fox wrote:
> I finally committed the two missing files from the sf.net's shell
> server. Let's blame the Great Fire Wall built by the P.R.C.
> government.
Thanks for taking care of the SVN repository! I verified that checking
out "vim7" gives the same result as the CVS server and the tar archives.
--
hundred-and-one symptoms of being an internet addict:
119. You are reading a book and look for the scroll bar to get to
the next page.
/// 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///
Stable Vim version 7.1 has been released
Announcing: Vim (Vi IMproved) version 7.1 This is a stable release of Vim, version 7.1. Since version 7.0 lots of problems were fixed and runtime files were updated. It has been one year and five days since 7.0! Most of Vim 7.1 was already available as patches for quite a while. A couple of test versions were made to spot problems in the distribution. Therefore Vim 7.1 can be considered very stable. If you are using an older version, it is highly recommended you install Vim 7.1. Several crashing bugs and a security issue were fixed. Once you have installed Vim 7.1 you can find details about the changes since Vim 7.0 with ":help version-7.1". I will not make an Amiga or OS/2 binary for Vim 7.1. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/ Information about which files to download for what system: http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1 is also available from CVS and Subversion: http://www.vim.org/cvs.php http://www.vim.org/subversion.php An overview of the files: UNIX: unix/vim-7.1.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1-extra.tar.gz extra files extra/vim-7.1-lang.tar.gz multi-language files doc/vim71html.zip help files converted to HTML MS-WINDOWS: pc/gvim71.exe self-installing, includes all runtime files pc/vim71rt.zip runtime files for binaries below pc/vim71lang.zip files for translated messages and menus pc/gvim71.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71ole.zip GUI binary with OLE support pc/gvim71_s.zipGUI binary for Windows 3.1 pc/vim71d16.zip16 bit console version for MS-DOS pc/vim71d32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71w32.zipconsole version for Windows NT/2000/XP pc/vim71src.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1.diff.gzsources + runtime files extra/vim-7.0-7.1-extra.diff.gz extra files extra/vim-7.0-7.1-lang.diff.gz multi-language files unstable/unix/vim-7.1b-7.1.diff.gz sources + runtime files unstable/extra/vim-7.1b-7.1-extra.diff.gz extra files unstable/extra/vim-7.1b-7.1-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to <[EMAIL PROTECTED]>. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: "vim -u NONE". Try different machines if possible. See ":help bugs" in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 114. You are counting items, you go "0,1,2,3,4,5,6,7,8,9,A,B,C,D...". /// 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: WARNING! Don't update your local svn repository now!
Edward L. Fox wrote: > On 5/12/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > Nicolas Weber wrote: > > > > > > The directories structure of the Subversion repository has been > > > > changed. Please use this command to checkout the latest sources: > > > > > > > > svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7 > > > > > > > > If you had checked out a copy of the sources before, please run this > > > > command in your source root directory to switch into the current > > > > branch: > > > > > > > > svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 > > > > > > Can someone update http://www.vim.org/subversion.php to reflect these > > > changes? > > > > I was still discussing what should actually be there, and making sure > > that SVN contains that. > > > > In my opinion "vim7" should get you the latest stable version. So far > > that is 7.0.243, thus 7.0 with patches. As soon as Vim 7.1 is out of > > beta then "vim7" should get you Vim 7.1. > > > > "vim7.1" should get you the latest version of Vim 7.1. So far that is > > the beta version. After the release it will be the stable version, thus > > the same as "vim7". > > > > Still need to check that it actually works this way. > > It's already this way. > > > There might also be other ways to get one of these, but that is less > > relevant. > > > > In my opinion we should keep it easy for the downloader to select one of > > the available versions. The download page would only need one or two > > alternatives. > > > > I have never maintained a SVN repository, thus have no idea how > > difficult or easy these things are! > > I've found an easy way to solve that problem. So now can we can announce? Great. Note that Vim 7.1 should go out today (fingers crossed), so be ready to update it again. I'll update the subversion page on www.vim.org now. -- hundred-and-one symptoms of being an internet addict: 112. You are amazed that anyone uses a phone without a modem on it...let alone hear actual voices. /// 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: WARNING! Don't update your local svn repository now!
Nicolas Weber wrote: > > The directories structure of the Subversion repository has been > > changed. Please use this command to checkout the latest sources: > > > > svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7 > > > > If you had checked out a copy of the sources before, please run this > > command in your source root directory to switch into the current > > branch: > > > > svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 > > Can someone update http://www.vim.org/subversion.php to reflect these > changes? I was still discussing what should actually be there, and making sure that SVN contains that. In my opinion "vim7" should get you the latest stable version. So far that is 7.0.243, thus 7.0 with patches. As soon as Vim 7.1 is out of beta then "vim7" should get you Vim 7.1. "vim7.1" should get you the latest version of Vim 7.1. So far that is the beta version. After the release it will be the stable version, thus the same as "vim7". Still need to check that it actually works this way. There might also be other ways to get one of these, but that is less relevant. In my opinion we should keep it easy for the downloader to select one of the available versions. The download page would only need one or two alternatives. I have never maintained a SVN repository, thus have no idea how difficult or easy these things are! -- In a world without walls and borders, who needs windows and gates? /// 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///
Vim version 7.1b BETA has been released
Announcing: Vim (Vi IMproved) version 7.1b BETA
This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all
patches, updated runtime files and a few fixes.
If you were using 7.1a please upgrade to 7.1b and verify it works well.
Please report every problem you find! It will only be a couple of days
until the 7.1 release, so hurry.
Once you have installed Vim 7.1b BETA you can find details about the
changes since Vim 7.0 with ":help version-7.1".
Changes since 7.1a:
- Lots of spelling mistakes fixed.
- Several runtime files updated. Somehow people tend to send me updates
_after_ doing a release...
- Bug in downloading a missing spell file fixed. Could wipe out a
buffer with your text when downloading failed.
- Building with MingW fixed (and now Win32s version also builds).
- Editing compressed files didn't work when folding enabled.
Testing
---
This is a BETA test version. Please give it a good test and report
anything that isn't right. That includes a crash but also a typo in the
documentation.
I will not make an Amiga or OS/2 binary for Vim 7.1b. A Mac version is
hopefully available soon on http://macvim.org/
Where to get it
---
All files can be found below this directory:
ftp://ftp.vim.org/pub/vim/unstable/
Information about which files to download for what system (don't use the
links, they are still for Vim 7.0):
http://www.vim.org/download.php
A list of mirror sites can be found here:
http://www.vim.org/mirrors.php
Vim 7.1b is also available from CVS (soon, still checking in):
http://www.vim.org/develop.php
An overview of the files:
UNIX:
unix/vim-7.1b.tar.bz2 sources + runtime files, bzip2 compressed
VARIOUS:
extra/vim-7.1b-extra.tar.gz extra files
extra/vim-7.1b-lang.tar.gz multi-language files
doc/vim71bhtml.zip help files converted to HTML
MS-WINDOWS:
pc/gvim71b.exe self-installing, includes all runtime files
pc/vim71brt.zip runtime files
pc/vim71blang.zip files for translated messages and menus
pc/gvim71b.zip GUI binary for Windows 95/98/NT/2000/XP
pc/gvim71bole.zip GUI binary with OLE support
pc/gvim71b_s.zipGUI binary for Windows 3.1 (untested)
pc/vim71bd16.zip16 bit console version for MS-DOS
pc/vim71bd32.zipconsole version for MS-DOS/Windows 95/98
pc/vim71bw32.zipconsole version for Windows NT/2000/XP
pc/vim71bsrc.zipsources for PC (with CR-LF)
DIFFS TO PREVIOUS RELEASE:
unix/vim-7.1a-7.1b.diff.gz sources + runtime files
extra/vim-7.1a-7.1b-extra.diff.gz extra files
extra/vim-7.1a-7.1b-lang.diff.gzmulti-language files
Mailing lists
-
For user questions you can turn to the Vim mailing list. There are a
lot of tips, scripts and solutions. You can ask your Vim questions, but
only if you subscribe. See http://www.vim.org/maillist.php#vim
If you want to help Vim development or get the latest patches, subscribe
to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev
Subject specific lists:
Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte
Macintosh issues: http://www.vim.org/maillist.php#vim-mac
Before you ask a question you should search the archives, someone may
already have given the answer.
Reporting bugs
--
Send them to <[EMAIL PROTECTED]>. Please describe the problem precisely.
All the time spent on answering mail is subtracted from the time that is
spent on improving Vim! Always give a reproducible example and try to
find out which settings or other things influence the appearance of the
bug. Try starting without your own vimrc file: "vim -u NONE". Try
different machines if possible. See ":help bugs" in Vim. Send me a
patch if you can!
If something needs discussing with other developers, send a message to the
vim-dev mailing list. You need to subscribe first.
Happy Vimming!
--
>From "know your smileys":
C=}>;*{)) Drunk, devilish chef with a toupee in an updraft,
a mustache, and a double chin
/// 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: what "feature" is required to return to last editing position?
Micah Cowan wrote: > Copying the dev list. The missing context is that running vim via sudo > before having run it as regular user, causes permission problems with > the created .viminfo file (and others?). > > Vincent BEFFARA wrote: > >>> Wonderful, the problem really is about permission of .viminfo! > >>> > >>> I noticed that you considered this to be a bug, but is this bug belon> gs > >>> to > >>> "sudo" or "vim"? > >>> > >>> i.e. for non-interactive "su" of "root", vim will save at user $HOME > > >>> with > >>> root permission. > >> FYI, this same issue was discussed at > >> https://bugs.launchpad.net/ubuntu/+bug/58002 > > > > From that discussion it would appear that it is a bug of neither, but > > rather of Ubuntu itself : sudo (as configured there) preserves $HOME, > > vim sees it and uses it to create .viminfo if it is not there. The > > natural fix is to put the right option in the sudo config file > > (always_set_home or something sounding like that). > > Except that this isn't always what is desired. And, if it's a bug of > Ubuntu, it's also a bug of every other distribution I've ever known > (thought there probably are some of which I'm aware, that set this). > > The biggest beef I would have with setting that option is that there > doesn't appear to be a way to /disable/ it for individual cases :p > ...still, I can't envision a reasonable case where the user couldn't > simply type out his own home directory (~user instead of ~?), or if > necessary set the environment himself within the sudo command, so it may > be a reasonable solution. > > > However, it would be nice of vim to always test that it owns the $HOME > > directory before creating files there. Would it break anything ? > > I think this would be a good idea as well. One could argue that if we > reason this way for vim, we should reason this way about everything that > ever creates config files in the user's home directory; however, not > every such thing can be expected to be run as root, and editors--and > most particularly vim--are extremely likely to be run as root, so I > think it's not unreasonable to ask them to take on this responsibility. And what if root always uses $HOME/.viminfo, where $HOME is the only person who can be root? It might be that there is no root home directory. Let's keep it simple: $HOME/.viminfo is the default viminfo file. If you want to use another file you have to tell Vim. > Perhaps rather than simply avoiding file creation, in the case of root > we could set the file's owner to the real id/gid, instead of the > effective one. This option is unavailable when the user is sudoing as > non-root, but this seems much less likely to happen before having run it > normally, than running under sudo is. Giving away a file is a big no-no for security reasons. Root may yank text in a register that a normal user is not supposed to see and this ends up in the viminfo file. > Another issue, which was touched on in that Ubuntu bug report, is that > vim doesn't warn or anything when it can't open .viminfo. Perhaps it > should distinguish between ENOENT and EPERM, and warn in the latter > case? It should possibly also warn in the event that it decides to > change ownership as above (if this is decided to be a good idea), or > when it is not created because of non-root, non-HOME-owner effective > user id. :set verbose=1 When ACLs are used there are many ways reading a file can fail. Just mentioning that it failed should be sufficient, the user will have to figure out why. That's better than a wrong message. -- >From "know your smileys": :-| :-| Deja' vu! /// 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: VimWiki - again - but with a brand new option
Ian Tegebo wrote: > > > On 5/6/07, Sebastian Menge <[EMAIL PROTECTED]> wrote: > > > > Hi all > > > > > > > > Independent of the implementation used, I suggest to develop good > > > > guidelines. The Wiki should be really valuable and not redundant to > > > > vim-tips or mailing-lists. > > > > > > I would like to make another implementation independent suggestion; > > > one could make a VimWiki more valuable by importing the _extremely_ > > > valuable vim helpfiles into it. > > > > Please don't do this. It might sound like a nice idea, but it means > > making a branch that will be very hard to merge back into the help files > > of the distribution. > I feel misunderstood but it serves me right for not saying what I mean... > > Synchronizing data is no fun, I agree. While I was up in the clouds I > was imaging that the wiki would be the authoritative source for the > helpfiles after doing an initial _import_. Then the text version > would be exported as needed, e.g. end user runtime update or for a new > release. That's the problem: It's very easy to change the text in the wiki in such a way it won't be possible to put back in the distribution. Also, I need to check every change, at least briefly (depend on where the change comes from). That is the only way to maintain the quality. Thus I would need a list of changes, preferably in the form of a patch. When people change the wiki in various ways this will quickly become a nightmare. Taking the existing help files and _adding_ to them is good. Especially if corrections and additions are marked somehow, so that they eventually end up in the distribution. Otherwise links to tips can be added. I'm currently working on the 7.1 release and then will go travelling, thus I won't have much time to discuss the tips wiki. I certainly encourage everybody to make it work. After all, a wiki is a collaborative work! -- >From "know your smileys": 2B|^2B Message from Shakespeare /// 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: Could you please give me the most bleeding-edge sources?
Edward L Fox wrote: > I noticed that you also maintained another CVS repository besides the > sf.net's CVS repository. And many changes to that internal CVS won't > be applied to the sf.net's CVS repository unless a large release is to > be made. > > In my opinion, as the SVN repository is now standardized, could you > please give me the most bleeding-edge sources so that I can commit > them into the trunk/ directory of the SVN repository, and some users > who wish to use the unstable experimental version then can help you to > test the code. I don't know what you are talking about. The most recent version is the distributed archives plus the patches plus updated runtime files. In CVS is that minus runtime file updates. There are a few changes on my local harddisk, but they are not in a patch yet for good reasons. -- >From "know your smileys": =):-) Uncle Sam /// 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: VimWiki - again - but with a brand new option
Ian Tegebo wrote: > On 5/6/07, Sebastian Menge <[EMAIL PROTECTED]> wrote: > > Hi all > > > > Independent of the implementation used, I suggest to develop good > > guidelines. The Wiki should be really valuable and not redundant to > > vim-tips or mailing-lists. > > I would like to make another implementation independent suggestion; > one could make a VimWiki more valuable by importing the _extremely_ > valuable vim helpfiles into it. Please don't do this. It might sound like a nice idea, but it means making a branch that will be very hard to merge back into the help files of the distribution. Please use the wiki for tips. That is an addition to the help files. > For example, I would love to be able to quickly correct spelling > mistakes or contribute to plugin helpfiles a la a Wiki interface. I > could then imagine updating my local helpfiles through the Wiki > interface via a sync-plugin. If you see spelling mistakes in the help files please send them to me. I just fixed 250 of them, because someone send me a list. That's useful for everyone. The main goal now is to get the Vim tips collection back to live. It has been dead for three months now! Perhaps we can figure out some clever way to also make the help files available with links between the tips and the help files. Thus in the help file you would see some link that takes you to a tip associated with the text at that position. But without that the tips are still very useful. -- >From "know your smileys": O:-) Saint /// 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: Resp.: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote: > 2007/4/16, Bram Moolenaar <[EMAIL PROTECTED]>: > > Thanks. I updated the Aap script according to your shell script. > Thank you! > > > I also changed the .aff files to include the FOL/LOW/UPP lines. That > > works better when switching languages. > > > > I also added the MIDWORD line to make clear a quote can appear halfway a > > word. > I didn't find the time to learn much spellchecking yet. If you say so, > I must agree :) Do check this in the real world. I don't use this spell file, thus I won't notice mistakes. > > I don't understand why you need to remove words that contain a dot. > > English words with an embedded dot works just fine. > Yes, you are right. Please include the "." and "-" too in the midword > list. I'd like to have "ª", "º" and "°" included when they are > trailing characters, too. > > BTW, there is a problem with µ. If you start a sentence with "µg", it > will be highlighted as miscapitalized and Vim will suggest "Mg" > instead. Perhaps you need to change the 'spellcapcheck' option. > > I can't do much with the .pdf file that replaces the README file. > > Please ask the maintainers to provide a plain text file with the > > Copyright notice. > It should be fixed in a short time. > > > Please verify the .spl files I produced are the same (or better :-) than > > yours. > The spelldump output is the same. That is good to hear. We're sure the same words appear then. However, things like handling of midword characters still need to be checked. > The newest pt_BR dictionary is: > BR_DIR = > http://www.deso-se.com.br/downloads/download.php?arquivo=pt_BR-2007-04-11 > BR_FNAME = pt_BR-2007-04-11.zip > > There should be a new release soon. I'll rebuild the spell file with the new dictionary. Hopefully I can upload them later today. -- hundred-and-one symptoms of being an internet addict: 58. You turn on your computer and turn off your wife. /// 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///
Vim version 7.1a BETA has been released
Announcing: Vim (Vi IMproved) version 7.1a BETA This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all patches and updated runtime files. I expect this to be stable, since the patches have been used by many people already. This BETA is mainly to check that the files has been setup properly. It's been almost a year since the last one! Please report every problem you find! It will only be a few days until the 7.1 release, so please take a little time right now to check it out. Once you have installed Vim 7.1a BETA you can find details about the changes since Vim 7.0 with ":help version-7.1". Testing --- This is a BETA test version. Please give it a good test and report anything that isn't right. That includes a crash but also a typo in the documentation. I will not make an Amiga or OS/2 binary for Vim 7.1a. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/unstable/ Information about which files to download for what system (don't use the links, they are still for Vim 7.0): http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1a is also available from CVS (when it works again) and with Aap: http://www.vim.org/develop.php An overview of the files: UNIX: unix/vim-7.1a.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1a-extra.tar.gz extra files extra/vim-7.1a-lang.tar.gz multi-language files doc/vim71ahtml.zip help files converted to HTML MS-WINDOWS: pc/gvim71a.exe self-installing, includes all runtime files pc/vim71art.zip runtime files pc/vim71alang.zip files for translated messages and menus pc/gvim71a.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71aole.zip GUI binary with OLE support pc/gvim71a_s.zipGUI binary for Windows 3.1 (untested) pc/vim71ad16.zip16 bit console version for MS-DOS pc/vim71ad32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71aw32.zipconsole version for Windows NT/2000/XP pc/vim71asrc.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1a.diff.gz sources + runtime files extra/vim-7.0-7.1a-extra.diff.gz extra files extra/vim-7.0-7.1a-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to <[EMAIL PROTECTED]>. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: "vim -u NONE". Try different machines if possible. See ":help bugs" in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 53. To find out what time it is, you send yourself an e-mail and check the "Date:" field. /// 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: mail plugin and hexdump file cause endless loop in vim 7
Andrei Voropaev wrote: > I've hit one interesting problem. When I've tried to send in an email > large hexdump (around 50K) the vim entered endless loop with 100% CPU > usage. I could terminate this loop by hitting Ctrl-C, but as soon as > I've tried to move to the long line the same thing happened again. > > Since I could manipulated this file with vim without mail ftplugin, I > came to conclusion that the problem has something to do with that > plugin. The file in question is located at > http://vandal.sdf-eu.org/hexdump.txt > > To reproduce the problem I did the following steps > > bash$ vim mutt-vandal-1001-25710-908 > > :new hexdump.txt > 2yy > :q > p > > At this point vim freezes and top reports that it uses 100% CPU. > > Just in case. I use ~/.vim/ftplugin/mail.vim with > set fo-=l > > Can anyone else try and see if the same thing happens? It's the syntax highlighting. Do ":syn clear" and the problem goes away. There must be some item in the mail syntax highlighting that can't handle long lines. Perhaps you can have a look at $VIMRUNTIME/syntax/mail.vim. Delete some lines to check which one causes trouble. The planned improvements to the regexp code (part of the Google summer of code) should also help. But it will takes several months before we get something. -- hundred-and-one symptoms of being an internet addict: 49. You never have to deal with busy signals when calling your ISP...because you never log off. /// 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: Vim Logo Use
Taylor Venable wrote: > I can't find anything about it on the Vim website, so I was wondering > what the status of the Vim logo is. Does someone own the copyright to > it? Is it in the public domain? Would it be alright to create, say, a > wallpaper with the Vim logo in it and release the wallpaper under a > CC-BY-SA license? Thanks for clarification! The Vim logo was made by a few people, at least including Vince Negri and me. It's hard to say who owns the copyright officially, but I can claim to make decisions about it, since I decided to use it. In general you are free to use the Vim logo for promotion of Vim. No need to get written permission. However, if I notice misuse of the Vim logo I might get furious and poke someone with soft cushions. Have at you! I don't think you need a license for a wallpaper, especially since it will be hard to match the "license" of the Vim logo. -- hundred-and-one symptoms of being an internet addict: 47. You are so familiar with the WWW that you find the search engines useless. /// 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: help needed with completion in version 7
Andrei Voropaev wrote: [...] > > It's difficult to decide when to leave this editing mode. > > Also because you can make a typo, and expect Backspace to correct that. > > If the key exits completion mode you can't go back to what you were doing. > > It's strange that you are saying "it's difficult to decide when to leave > the editing mode". As soon as there are no matches after my editing, the > completion shall stop, just like it stops when I don't hit the BackSpace > key. Or do I miss something? I mean, why appending to what I've typed is > different from modifying it? Essentially it's just different way to > modify the input for the completion function. From my naive point of > view, the logic should be something like following. When you have 500 matches you can type some more characters to reduce the number of matches. But you may make a typo and end up with zero matches. Then it's nice you can press backspace and type the right character. Otherwise you would have to start completion again (e.g., with CTRL-X CTRL-O when you were doing omni completion). -- hundred-and-one symptoms of being an internet addict: 34. You laugh at people with 14400 baud modems. /// 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: spam in subject
The subject of this message was: Subject: Re: ***SPAM*** Re: Re: ***SPAM***_Vim70's hignlighting You are very lucky it got through. You have to remove ***SPAM*** from the subject line, otherwise it has a high probability to be marked as spam. I'm getting so much spam lately that my spam-filtering rules are quite agressive. So don't write a message that looks more or less like spam. -- A fool must search for a greater fool to find admiration. /// 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: wish: show search progress on slow searches
Yakov Lerner wrote: > Wish: when search is slow, show the progress line number > every second on the bottom line (like, 12345 of 9). What is slow? Checking if the second passed will make the search even slower. Checking time is quite slow on some systems (the check for CTRL-C suffers from this). > Maybe this can be done with plugin, I'm not sure. Probably not without a big performance hit. > Maybe simply status line can be refreshed once in a second, > temporarily setting line number to the current search position. That would be confusing. Need to show it somewhere else (but where?). > Some regexes take half minute to several minutes time on multimegabyte > file. It would be nice to see the progress numbers onscreen. True. Some of my functions also echo the current line number now and then. -- "You know, it's at times like this when I'm trapped in a Vogon airlock with a man from Betelgeuse and about to die of asphyxiation in deep space that I really wish I'd listened to what my mother told me when I was young!" "Why, what did she tell you?" "I don't know, I didn't listen!" -- Arthur Dent and Ford Prefect in Douglas Adams' "The Hitchhiker's Guide to the Galaxy" /// 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: wish: collaboration of N vim instances editing same file
Yakov Lerner wrote: > Is it possible to add this item to the vim voting list ?: > > "collaboration of N vim instances editing same file" > -- Ability of N instances of vim to absorb, merge and show changes > to the same file made by other running vim instances [ either by reading > other vim's swapfiles, or somehow else ] ? It's an interesting idea. Won't be easy to implement in such a way that it works on most platforms. It will probably require a server to make it possible for various Vim instances to find each other. And to take care of authentication. Perhaps such a server already exists? > Can this be added to SOC ? Too late. -- What a wonderfully exciting cough! Do you mind if I join you? -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" /// 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: let loaded_matchparen = 1
Andre Majorel wrote: > Are there any plans to make the highlight-the-matching-thing > "feature" disabled by default in a future release of Vim ? It defaults to off when 'compatible' is set. Otherwise, incompatible changes are only made when there is a very good reason. Since hardly anyone complains about highlighting matching parens, there doesn't appear to be a reason. -- The startling truth finally became apparent, and it was this: Numbers written on restaurant checks within the confines of restaurants do not follow the same mathematical laws as numbers written on any other pieces of paper in any other parts of the Universe. This single statement took the scientific world by storm. So many mathematical conferences got held in such good restaurants that many of the finest minds of a generation died of obesity and heart failure, and the science of mathematics was put back by years. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" /// 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: make issues on OSX
Robert Hicks wrote: > I downloaded revision 252 from the svn repo and it gave make errors > (which I piped to a text file). > > Do I need to report that somewhere? Use the vim-mac maillist. -- How To Keep A Healthy Level Of Insanity: 17. When the money comes out the ATM, scream "I won!, I won! 3rd time this week!" /// 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: help file imprecision
Tony wrote: > In > > *insert.txt*For Vim version 7.0. Last change: 2006 Dec 06 > > under :help i_CTRL-_ at lines 222-223, there is: > > Only if compiled with the |+rightleft| feature (which is not > the default). > > there should be: > > Only if compiled with the |+rightleft| feature (which means > a Big or Huge version of Vim). I'll just remove the text between parenthesis, it's confusing. -- How To Keep A Healthy Level Of Insanity: 13. Go to a poetry recital and ask why the poems don't rhyme. /// 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: help needed with completion in version 7
Andrei Voropaev wrote: > On Fri, Apr 27, 2007 at 01:17:39PM +0200, A.J.Mechelynck wrote: > [...] > > >Aha, I think, that here we talk about a bug! If I hit Ctrl-N, get the > > >needed completion, and then start typing further, then the completion > > >stops as soon as there are no more matches. BUT. If after Ctrl-N I hit > > >Backspace first, and then continue typing, then completion does not stop > > >even when there are no more matches. In this case only Esc or Ctrl-Y > > >aborts the completion. > > > > > > > Ah, finally, I can reproduce that. I think it's only a missing screen > > redraw. If I backspace, then type a few letters, then (let's say) a period, > > the message "match m of n" is still there. Hitting makes it > > disappear (replaced by "-- INSERT --"), after which brings the > > cursor back where it belongs. > > Unfortunately it's not just a missing screen. If you try to do > completion again it won't work. So again, type the beginning of word, > hit Ctrl-N, hit Backspace, type ( and beginning of another word, hit > Ctrl-N to complete it. It won't work saying that there are no matches. > That's because old completion is still active and it tries to complete > the whole thing. This happens very often when one has to write C > functions :) So, I would say this is a more serious bug than just > missing update of the screen. When you press Backspace you go into a mode where you edit the text, so that you can change the list of matches. Just about any character can appear in the matches (e.g., for line completion or when using omni completion). It's difficult to decide when to leave this editing mode. Also because you can make a typo, and expect Backspace to correct that. If the key exits completion mode you can't go back to what you were doing. > Actually, I've hit another bug few times already, unfortunately I can't > reproduce it. When I type quickly and miss a key, then I try to undo my > changes and instead get back the message "Can't undo, the line numbers > are incorrect" or something like that. Usually it happens after I hit > 2-3 keys wrong, so I still can't reproduce it. Well, when I type > japanese text in "over the spot" mode this is "normal". But everyone > decided that this is a bug in the japanese input. Looks like it can be > triggered also in non-japanes input. If you find a way to reproduce this "undo line numbers wrong error" then I would very much like to see it. It's hard to fix something that I can't reproduce. -- How To Keep A Healthy Level Of Insanity: 5. Put decaf in the coffee maker for 3 weeks. Once everyone has gotten over their caffeine addictions, switch to expresso. /// 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: VimCrypt - a cry for help
Gordon Bazeley wrote: > Hi guys, > A bit of a cry for help I'm afraid. I've been using Vim to keep a > diary for the last few years and somehow the file I use for this > purpose has become corrupted through a system crash. I have a rather > old backup but don't really want to go that route unless I need to. > > The file in question was encyrpted with VimCrypt and the file now > looks a bit strange to say the least. There is a section of readable > text at the top of the document (although notably NOT the text that > was actually at the top of the doc when I last used it) and after > about thirty lines or so the text becomes garbled for another 1600 > lines or so. > > I've tried copying the garbled text into a new file and prepending it > with "VimCrypt~" but Vim is not recognising it as a crypted file (I'm > not sure if this portion of the file is actually crypted or just > garbled). > > A section of the garbled text is given below: > > =07=D9a=AA=F7Fhl=B8=89V=C6w[=9DSZ=FFoz)M82=A6=08=FB>=F4=EE=8C=8B=8B=F9=07= > =89, > =16m=E4=D0=F6=FE-[=03=86=FD=04=1C=FFc=BC=1F=E4 Before you do anything that changes your harddisk, try an undelete program to find the swap file used during the last edit. The swapfile is not encrypted. The name is normally ".filename.swp". Careful: As soon as you start Vim on the same file it's likely that the old one gets overwritten and undelete won't work. There is also a small chance that you find a backup of the original file: "filename~". It should exist even when 'backup' is off. But if 'writebackup' is off you won't have it. If you're very lucky, the system crash caused a swap file to stay on your harddisk. Even when it's corrupted it contains the text (in reverse order). I'm afraid that otherwise there is hardly any chance to get the text back. The encryption goes from the start of the file to the end. If at some point the data is corrupted, the decryption for the rest will be corrupted too. -- Don't Panic! -- The Hitchhiker's Guide to the Galaxy /// 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: undo line numbers wrong
Rob Cussons wrote: > >>just wondering if anyone else had experienced an error message like > >>this. It seems that every so often, I've not managed to find any > >>systematics to this, when I try to perform an undo, I get "undo line > >>numbers wrong" or something similar, sorry I don't have the exact error > >>in front of me, it happened about 5 minutes ago and I was in the middle > >>of something, so I just dealt with it! It doesn't happen very often, but > >>when it does if I later try to undo something, it all goes a bit haywire > >> and seems to not undo the last change etc. Sorry this is so vague, if > >>it happens again, I'll see if I can pin it down better. Just wondered if > >>anyone else had experienced this and maybe knew the cause. > > > > What is your ":version" output? > > Hi Bram, below is the :version output. > > :version > VIM - Vi IMproved 7.0 (2006 May 7, compiled Jul 16 2006 12:51:49) > Included patches: 1-35 There were a few updates to the undo function, especially patch 182. You could try including all the patches that are available. If the problem persists please try to find out what triggers the problem. There might also be something in your environment that matters (esp. plugins). It works fine for everybody else, so what is different for you? -- The goal of science is to build better mousetraps. The goal of nature is to build better mice. /// 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: undo line numbers wrong
Rob Cussons wrote:
> just wondering if anyone else had experienced an error message like
> this. It seems that every so often, I've not managed to find any
> systematics to this, when I try to perform an undo, I get "undo line
> numbers wrong" or something similar, sorry I don't have the exact error
> in front of me, it happened about 5 minutes ago and I was in the middle
> of something, so I just dealt with it! It doesn't happen very often, but
> when it does if I later try to undo something, it all goes a bit haywire
> and seems to not undo the last change etc. Sorry this is so vague, if
> it happens again, I'll see if I can pin it down better. Just wondered if
> anyone else had experienced this and maybe knew the cause.
What is your ":version" output?
--
All good vision statements are created by groups of people with bloated
bladders who would rather be doing anything else.
(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: Vim freezes system ?!
Yakov Lerner wrote:
> On 4/6/07, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> > On 4/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I did th3 follwing: With a program, which generates random numbers in
> > > different formats, I created a file, which consists of _one_ line of
> > > 2097152 characters ("0"-"9","A"-"F").
> > >
> > > To split the line into lines of 72 characters each, I started vim and
> > > let it read the file.
> > >
> > > I postioned the cursor at position 0 and entered the following in
> > > normal mode:
> > >
> > > qq72i0q
> > >
> > > Then I did a
> > >
> > > [EMAIL PROTECTED]
> > >
> > > After only 10 or 15 (guessed) executions of the macro the system
> > > freezes while constantly swapping (?) and became unuseable and did no
> > > longer respond.
> > >
> > > Even the mouse pointer was nearly unmoveable...
> > >
> > > After heavily and constantly trying I managed to kill the X-session
> > > and to 'killall -9 vim' from the console to get back my computer.
> >
> > Hello Meino "the vim killer" Cramer,
> > I tried your scenario. You need to add 'set ul=-1' to disable undoes, and
> > 'set lz' to disable excess redraws. Even then, vim goes rather slow at
> > this task.
> >
> > Indeed, vim grows to >1000MB vm/rss size
> > size in matter of one minute without ul=-1 (, and growing very fast. )
>
> The thing I find strange here is that values of 'maxmem', 'maxmemtot' were:
>
> :set mm? mmt?
> maxmem=643272
> maxmemtot=643272
>
> , yet vim grew past x2.5 times that limits (with default 'ul')
> without messages.
> Is this expected behaviour ?
The 'maxmem' and 'maxmemtot' are for the text that is kept in memory.
Above these limits text is put in the swap file.
Text that is kept for undo is always in memory and there is no limit for
the amount, there is only 'undolevels'. See ":help limits".
I think the problem with the way lines are split here is that you go in
and out of Insert mode for every change. This causes the current line
to be saved for undo every time. With a function that gets the line and
inserts every 72 chararacters it's probably a lot faster.
--
It doesn't really matter what you are able to do if you don't do it.
(Bram Moolenaar)
/// 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
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: Problem with pastetoggle
Jeffery Small wrote:
> >Perhaps you can make your key send CSI instead of Esc to avoid the
> >confusion.
>
> Bram:
>
> This sounds interesting, however I'm not sure how to do this or even if I can.
> I am using an xterm with the standard C character set (LC_TYPE=C). Can I
> even define an 8-bit code with this character set? In my .Xdefaults file I
> added the lines:
>
> xterm*VT100*translations: #override \n\
> F11: string(0x9B) string("[192z")
>
> but the key still outputs ^[[192z - probably because the high bit is being
> stripped off. If you have any suggestions, I'm interested. And thanks for
> the reply.
It should be possible for xterm. I think you need to enable the
"8-bit-control" or "eightBitControl" somewhere.
--
If the Universe is constantly expanding, why can't I ever find a parking space?
/// 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
Cyril Slobin wrote: > Who maintains Esperanto spell files for Vim? File eo.utf-8.spl is > completely broken! In fact it was broken long ago when I've download > Vim 7.0. Now I've upgrade to 7.0.219 and have checked if something > became better. No hope -- it is the same broken file. I use Win32 > version of Vim. There is no maintainer. I simply took the spell files from myspell (OpenOffice.org). They are still dated 27-Oct-2005, thus it appears nobody is working on them. > I have complied my own eo.utf-8.spl from ispell sources by Sergio > Pokrovskij found in Debian 3.1 distribution. It understands both real > Unicode and surrogate "Cxirkaux"-style (if you don't speak Esperanto, > you don't need to understand this). Archive contains .spl file itself, > two .dic files, two .aff files and short readme file (it is in > Esperanto, not English, and named "legumin", not "readme"). You can > download it from: > > http://www.45.free.net/~slobin/vim/eo.utf-8.zip > > Maybe it is a good idea to replace broken file with my one on Vim ftp site. > > I've newer use aap and don't know vim maintaining technology, I've > just manually converted ispell files to myspell ones and than compiled > them to Vim format. > > I have not checked eo.iso-8859-3.spl file, I newer use iso-8859-3. To be able to allow others to reproduce building the .spl file, it's required that a script is used to fetch the input files, do any conversions/patching and use Vim to build the .spl file. 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. What is strange is that myspell uses eo_l3 and you have eo_EO and eo_UX. Why two regions? -- I once paid $12 to peer at the box that held King Tutankhamen's little bandage-covered midget corpse at the De Young Museum in San Francisco. I remember thinking how pleased he'd be about the way things turned out in his afterlife. (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: Netrw under Windows 98 doesn't go to upper directory
Cyril Slobin wrote:
> I've just upgraded to Vim 7.0.219 and netrw version 107, and under
> WIndows 98 it doesn't go to upper directory (neither by pressing "-"
> nor by pressing on "../" line). I've guessed that reason is in
> this lines:
>
>elseif !g:netrw_cygwin && (has("win32") || has("win95") ||
> has("win64") || has("win16"))
> " windows
> if a:islocal
> let dirname=
> substitute(dirname,'^\(\a:\\\)\=\(.*\)\\\([^\]\+$\)','\2','')
> else
> let dirname=
> substitute(dirname,'^\(\a:\\\)\=\(.*\\\)\([^\]\+\\$\)','\2','')
> endif
>
> First, this code supposes that directory separator is "\" while a few
> lines before it was replaced with "/". Second, this code cuts off
> drive letter and backslash after them making directory relative
> instead of absolute. My workaround follows:
>
>elseif !g:netrw_cygwin && (has("win32") || has("win95") ||
> has("win64") || has("win16"))
> " windows
> if a:islocal
> let dirname=
> substitute(dirname,'^\(\a:[\\/]\)\=\(.*\)[\\/]\([^\\/]\+$\)','\1\2','')
> else
> let dirname=
> substitute(dirname,'^\(\a:[\\/]\)\=\(.*[\\/]\)\([^\\/]\+[\\/]$\)','\1\2','')
> endif
>
> This works for me.
I can't find these lines in the current version of netrw, 108. Please
try the most recent version and talk to Charles Campbell if it's still
wrong.
--
Managers are like cats in a litter box. They instinctively shuffle things
around to conceal what they've done.
(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: Problem with pastetoggle
Jeffery Small wrote: > I'm using vim 7.0 on a Solaris 9 system. > > If I put the following line in my .vimrc file: > > set pastetoggle=[192z > > Then when I am editing in insert mode, each time I hit ESC to return > to command mode the cursor sit there jumping to the right and back > continuously until another key is pressed. If I press ESC again it stops > or if I move the cursor it also stops. If I comment out the above line > then I do not see this problem. > > Any suggestions as to how to address this? Thanks. This is normal. When Vim gets an it doesn't know if you pressed the key or that some special key sequence is coming. Perhaps you can make your key send CSI instead of Esc to avoid the confusion. Oh, there is one change I can make that will help: *** ../../vim-7.0.224/src/getchar.c Sun Mar 4 21:25:44 2007 --- getchar.c Thu Apr 19 22:13:37 2007 *** *** 2183,2189 } /* Need more chars for partly match. */ if (mlen == typebuf.tb_len) ! keylen = KL_PART_MAP; else if (max_mlen < mlen) /* no match, may have to check for termcode at * next character */ --- 2187,2193 } /* Need more chars for partly match. */ if (mlen == typebuf.tb_len) ! keylen = KL_PART_KEY; else if (max_mlen < mlen) /* no match, may have to check for termcode at * next character */ -- "You're fired." (1980) "You're laid off." (1985) "You're downsized." (1990) "You're rightsized." (1992) (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: Python crash
Chuck Mason wrote:
> This crashes my vim:
>
> function! PyCrash()
> python << EOF
> import sys
> sys.path.append("c:\\python23\\lib")
> from threading import Thread
> import vim
>
> def f():
> vim.command("copen")
>
> t = Thread(target=f)
> t.start()
> EOF
> endfunc
>
> "" crash!
> call PyCrash()
>
> Does anyone know why? I mean, granted vim.command might not be
> thread-safe but it most certainly shouldn't crash.
There are a few calls in the Python interface to make sure everything
happens in one thread. However, how this works appears to change with
every version of Python, so it might not work with Python 2.4. It might
actually be this thread-protection code that causes the crash.
Perhaps someone who knows how these things work can have a look at
src/if_python.c. Search for "thread\c".
--
Our job was to build a computer information system for the branch banks. We
were the perfect people for the job: Dean had seen a computer once, and I had
heard Dean talk about it.
(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: A nice efm for javac
Michael Lamb wrote:
> >> I've put some spare time into an errorformat string and a filter
> >> script which makes plain-old javac compilation nicer than the
> >> examples from :help errorformat-javac
> >
> > Assuming this works well, it's only for Unix. Thus I would add it
> > to ":help errorformat-javac" instead of replacing the existing
> > example.
>
> I intended neither but I'd be happy for the former. It's not a
> significant change, so feel free to omit my name for brevity.
I like to keep the name in, so that when later changes are suggested we
know who wrote the original.
> If you're going to add this to the help files where lots of people will
> read it, let me be a bit more professional. I've made minor language
> changes to your modification of my text, below.
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Here is an alternative for Unix that filters the errors first: >
>:setl errorformat=%Z%f:%l:\ %m,%A%p^,%-G%*[^sl]%.%#
>:setl makeprg=javac\ %\ 2>&1\ \\\|\ vim-javac-filter
>
> You need to put the following in "vim-javac-filter" somewhere in your
> path (e.g., in ~/bin) and make it executable: >
> #!/bin/sed -f
> /\^$/s/\t/\ /g;/:[0-9]\+:/{h;d};/^[ \t]*\^/G;
>
> In English, that sed script:
> - Changes single tabs to single spaces and
> - Moves the line with the filename, line number, error message to just
>after the pointer line. That way, the unused error text between
>doesn't break vim's notion of a "multi-line message" and also
>doesn't force us to include it as a "continuation of a multi-line
>message."
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Thanks for the update. Only the last two items changed, right?
> I was concerned about this not being a cross-platform solution. I'd be
> delighted if there were a more elegant (pure-vim) method. Is there a way
> to have some vimscript modify the errorfile before parsing?
Currently not. Now that Vim script is powerful enough for this it would
be a good idea to add it. Don't know how it would work exactly.
--
BLACK KNIGHT: I'm invincible!
ARTHUR: You're a looney.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: A nice efm for javac
Michael F. Lamb wrote:
> I've put some spare time into an errorformat string and a filter script
> which I think makes plain-old javac compilation (read: not using JUnit,
> not using Ant) quite a bit nicer than the examples from :help
> errorformat-javac, without being too heavy or complicated. I've tested
> this with only Vim 7.0.122 on Linux, Sun Java 1.6.0, and only minimally
> at that.
>
> It correctly discovers the column number even if you use tabs in your
> source code, doesn't fill the "error message" variable with extra crud,
> shows the "symbol:" and "location:" lines in the quickfix window, but
> properly skips over them when doing :cnext and :cprevious. Note that
> "symbol:" and "location:" will appear above their related error message
> in the quickfix window.
>
> Here's the sed script to filter the output from javac. I named it
> 'vim-javac-filter' and placed it in my path.
>
> #!/bin/sed -f
> /\^$/s/\t/\ /g;/:[0-9]\+:/{h;d};/^[ \t]*\^/G;
>
> In English, that sed script:
> - Changes tabs to spaces and
> - Moves the line with the filename, line number, error message to just
>after the pointer line. That way, the extra gunk between doesn't
>break vim's notion of a "multi-line message" and also doesn't force
>us to include that gunk as a "continuation of a multi-line message."
>
> Here's the corresponding efm:
>
> :setlocal errorformat=%Z%f:%l:\ %m,%A%p^,%-G%*[^sl]%.%#
>
> To make it work using ":make":
>
> :setlocal makeprg=javac\ %\ 2>&1\ \\\|\ vim-javac-filter
Assuming this works well, it's only for Unix. Thus I would add it to
":help errorformat-javac" instead of replacing the existing example.
How about this:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Here is an alternative from Michael F. Lamb for Unix that filters the errors
first: >
:setl errorformat=%Z%f:%l:\ %m,%A%p^,%-G%*[^sl]%.%#
:setl makeprg=javac\ %\ 2>&1\ \\\|\ vim-javac-filter
You need to put the following in "vim-javac-filter" somewhere in your path
(e.g., in ~/bin) and make it executable: >
#!/bin/sed -f
/\^$/s/\t/\ /g;/:[0-9]\+:/{h;d};/^[ \t]*\^/G;
In English, that sed script:
- Changes tabs to spaces and
- Moves the line with the filename, line number, error message to just after
the pointer line. That way, the extra gunk between doesn't break vim's
notion of a "multi-line message" and also doesn't force us to include that
gunk as a "continuation of a multi-line message."
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
--
DENNIS: Look, strange women lying on their backs in ponds handing out
swords ... that's no basis for a system of government. Supreme
executive power derives from a mandate from the masses, not from some
farcical aquatic ceremony.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: :args -> buffer list mapping issue
Chuck Mason wrote:
> A coworker (who is not on VIM Mailing List) has asked me to forward this
> issue here. Is this already known about or what do we do to submit a
> bug?
>
> I have verified that it happens on my build of vim. His repro steps are
> below. My :version is
[...]
You don't mention the version of the netrw plugin that you are using.
That's important here.
> From: Boris Kazanskii=20
> Sent: Wednesday, April 04, 2007 2:43 PM
> To: Chuck Mason
> Subject: :args -> buffer list mapping issue
>
> :args allows to insert directory browser buffers into the buffer list,
> which cause :bn, :bufdo and friends to fail
After ":args" you should use ":next" to move to the next argument.
> To reproduce:
> - Open vim (win32)
> - :args D:\Program\ Files\Vim\**\co*.* (or whatever matches your
> configuration)
> - :bfirst
> - do a couple of :bn, this will never ever get over the first
> directory browser buffer (D:\Program\ Files\Vim\vim70\colors\ in this
> case)
> - :bufdo echo expand("%") will also stop after it encounters the
> first directory browser
> - :bd/:bw are unable to delete these "bad" directory buffers
> - the only way to get rid of these is to do :1,1000bd
Does this still happen when using a path without a space in it?
--
ARTHUR:Be quiet! I order you to shut up.
OLD WOMAN: Order, eh -- who does he think he is?
ARTHUR:I am your king!
OLD WOMAN: Well, I didn't vote for you.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: Resp.: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote:
> Finally, I have a working pt "dictionary" for vim.
>
> I attached a shell script, which means I gave up learning AAP. Not
> that it's hard, but it took me long enough to sit down and write the
> script, and I wouldn't like to stall any longer.
>
> I believe I wrote all the relevant comments in the script.
>
> The gzipped spl file is 1,3M large, so I didn't attach it yet. May I
> send it directly to you, Bram? I have no sug file because it seems
> that the MAP's are doing a better job than I could do with SOFO's.
Thanks. I updated the Aap script according to your shell script.
I also changed the .aff files to include the FOL/LOW/UPP lines. That
works better when switching languages.
I also added the MIDWORD line to make clear a quote can appear halfway a
word.
I don't understand why you need to remove words that contain a dot. In
English words with an embedded dot works just fine.
I can't do much with the .pdf file that replaces the README file.
Please ask the maintainers to provide a plain text file with the
Copyright notice.
I produced the .spl files this way. You can find them on the ftp
server: ftp://ftp.vim.org/pub/vim/runtime/spell
You can see the Aap recipe and diff files here:
ftp://ftp.vim.org/pub/vim/runtime/spell/pt
Please verify the .spl files I produced are the same (or better :-) than
yours.
--
FIRST SOLDIER: So they wouldn't be able to bring a coconut back anyway.
SECOND SOLDIER: Wait a minute! Suppose two swallows carried it together?
FIRST SOLDIER: No, they'd have to have it on a line.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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///
A new voting item
Upon request I have added one more item to vote on: Add an indication what text was changed since editing started (change bar or diff) If you are sponsoring Vim or are a registered Vim users you can adjust your votes at http://www.vim.org/sponsor/vote.php . -- It is illegal to take more than three sips of beer at a time while standing. [real standing law in Texas, United States of America] /// 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: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote: > Er... does it make a big difference if I send a regular shell script? > > I don't know how to write scripts in any other language. That said, if > it's important maybe I could learn AAP. Well, I can transform the commands to the Aap script, but we still need to verify that the result is the same. Or I can generate and upload the spell file and then you check if it's OK. You can use ":spelldump" with your and the uploaded dictionary. -- Close your shells, or I'll kill -9 you Tomorrow I'll quota you Remember the disks'll always be full And then while I'm away I'll write ~ everyday And I'll send-pr all my buggings to you. [ CVS log "Beatles style" for FreeBSD ports/INDEX, Satoshi Asami ] /// 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: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote: > 2007/3/25, Bram Moolenaar <[EMAIL PROTECTED]>: > > Try ":set spelllang=pt_br". Region in lower case. > > Duh! > > OK, I should be able to provide a vim-spell-pt package soon. While the > pt_PT part was updated recently, the pt_BR one should release a new > version soon. > > When I have a final vim-spell-pt package, what should I do to get it > uploaded to vim's FTP server? IIRC Vim can fetch from there; is that > correct, or will the dict be release only with the next version of > vim? Send me an updated runtime/spell/pt/main.aap and diffs for the .dic and .aff files. Then I'll generate the files and upload them. This also verifies the procedure is repeatable. You can send me your .spl file so I can compare the results. -- Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. (Calvin) /// 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: Error In Documentation?
Vigil wrote:
> On Sun, 25 Mar 2007, Bram Moolenaar wrote:
>
> > You apparently really want to pass ${*} to the shell command. The help
> > for makeprg explains replacing $* with the name of the file, but you use
> > "%" for that.
>
> My help says that $* is replaced with the arguments, which I take to
> mean -T in my example:
>
> The placeholder "$*" can be given (even multiple times) to specify
> where the arguments will be included
>
> It doesn't say anything about the filename. Maybe it needs to
> distinguish which arguments it is referring to.
Sorry, "$*" is indeed replaced by the ":make" arguments, not the file name.
> > This probably also works:
> >
> >setlocal makeprg=/usr/share/vim/vim70/tools/efm_perl.pl\ -c\ -w\ $*
>
> Nope. When I replace efm_perl.pl with efm_perl2.pl, a simple script that
> outputs the arguments it was called with, and I have
>
> set makeprg=~/.vim/tools/efm_perl2.pl\ -c\ -w\ ${*}\ %
>
> and I call ":make" on the file that I have open ('binary.pl'), efm_perl2.pl
> outputs
>
> Called with: -c -w binary.pl
>
> When I call it with ":make -T", it outputs
>
> Called with: -c -w binary.pl -T
What happens here is that ${*} is changed by the shell to an empty
string. Then % is changed to the file name, and the other arguments
follow, since you don't use $*. If you leave out ${*} you get the same
result.
> Now, if I change the makeprg thus:
>
> set makeprg=~/.vim/tools/efm_perl2.pl\ -c\ -w\ $*
>
> and call ":make":
>
> Called with: -c -w
>
> and ":make -T":
>
> Called with: -c -w -T
>
> As you can see, the filename of the current buffer is not passed to the
> makeprg.
No, but the argument is. Thus these two are equivalent:
set makeprg=~/.vim/tools/efm_perl2.pl\ -c\ -w\ % $*
set makeprg=~/.vim/tools/efm_perl2.pl\ -c\ -w\ %
Because when $* is not used you get the arguments anyway.
> Further experimentation reveals that the order of "%\ ${*}" or "${*}\
> %" makes no difference to the arguments that efm_perl2.pl is passed,
> nor their order. Indeed, ${*} is superfluous, but it does seem that I
> need % to substitute both the filename AND any arguments I give to
> :make.
>
> $* and all variations of braces in and around it, just doesn't work.
>
> This option may contain '%' and '#' characters, which are
> expanded like when used in a command-line.
>
> I think that needs explaining a bit more. To me, % is used when
> specifying the entire range of the file on the vim command line, and #
> prints lines with their respective line numbers :/
This refers to using them in an argument. That should be mentioned,
I'll adjust the text.
--
It is illegal for anyone to give lighted cigars to dogs, cats, and other
domesticated animal kept as pets.
[real standing law in Illinois, United States of America]
/// 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: GVim Crash
Andy Wokula wrote:
> GVim7 (Win32) crashes if I do the following:
>
> " clean startup
> :new
> :tabnew
> :call winnr("#")
>
> " happens with or without 219 patches included
I can reproduce it. Will be fixed soon.
--
If an elephant is left tied to a parking meter, the parking fee has to be paid
just as it would for a vehicle.
[real standing law in Florida, United States of America]
/// 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: Error In Documentation?
Vigil wrote:
> On Fri, 23 Mar 2007, Bram Moolenaar wrote:
>
> >> in :help makeprg, I think the {$*} in the example ought to be ${*}. At
> >> least, it wouldn't work for me unless I did that.
> >
> > No, it's really $*. This is replaced by Vim before passing the command
> > to the shell.
>
> $* and {$*} won't work in my ftplugin. This, however, does:
>
> setlocal makeprg=/usr/share/vim/vim70/tools/efm_perl.pl\ -c\ -w\ ${*}\ %
>
> Perhaps the braces are to get around ithe command being sourced from a file?
You apparently really want to pass ${*} to the shell command. The help
for makeprg explains replacing $* with the name of the file, but you use
"%" for that.
This probably also works:
setlocal makeprg=/usr/share/vim/vim70/tools/efm_perl.pl\ -c\ -w\ $*
No idea why you wanted to include the {}. In the example it's for the
latex command.
--
SIGFUN -- signature too funny (core dumped)
/// 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: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote:
> Good and bad news from the pt "dictionary".
>
> The good news is that I finally decided to distribute the spell
> checking file with the pt_PT dictionary from the Linguateca [1]. The
> bad news is that I still get "region XX not supported". Please tell me
> what am I doing wrong:
>
> 1. Place pt_(PT|BR).(aff|dic) at ~/tmp
> 2. Rum gVim
> 3. :mkspell ~/.vim/spell/pt ~/tmp/pt_PT ~/tmp/pt_BR
> 4. :set spell spelllang=pt_BR (or _PT)
> 5. "Warning: region BR not supported" (same for PT).
Try ":set spelllang=pt_br". Region in lower case.
--
BRIDGEKEEPER: What is your favorite colour?
LAUNCELOT:Blue.
BRIDGEKEEPER: Right. Off you go.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: hosting wiki tips
Martin Krischik wrote: > Doesn't Vim have a SourceForge page? Because SF is currently beta > testing Wikis [1]. Advantage here: We don't need to install anything. > We just have to wait for the beta to end. The problem with SourceForge is that their uptime is not good. Last month the shell server was down for more than a week. That means I could not change the web pages. When using the SF wiki the tips still need to be converted, thus I don't see an advantage in doing this on SF. -- User: I'm having problems with my text editor. Help desk: Which editor are you using? User: I don't know, but it's version VI (pronounced: 6). Help desk: Oh, then you should upgrade to version VIM (pronounced: 994). /// 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: Error In Documentation?
Vigil wrote:
> In vim's:
>
> VIM - Vi IMproved 7.0 (2006 May 7, compiled May 30 2006 13:06:19)
> VIM - Vi IMproved 6.4 (2005 Oct 15, compiled May 23 2006 12:03:57)
>
> in :help makeprg, I think the {$*} in the example ought to be ${*}. At
> least, it wouldn't work for me unless I did that.
No, it's really $*. This is replaced by Vim before passing the command
to the shell.
--
MONK: ... and the Lord spake, saying, "First shalt thou take out the Holy Pin,
then shalt thou count to three, no more, no less. Three shalt be the
number thou shalt count, and the number of the counting shalt be three.
Four shalt thou not count, neither count thou two, excepting that thou
then proceed to three. Five is right out. Once the number three, being
the third number, be reached, then lobbest thou thy Holy Hand Grenade of
Antioch towards thou foe, who being naughty in my sight, shall snuff it.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: Feature proposal: Change bars
Christoph Kögl wrote: > I want to propose a feature I have come to appreciate in some editors > (e.g. Codewright and most recently in the Delphi 2006 editor) that > (g)vim currently lacks: change bars. By this I mean a colored bar to the left > of the first text column (some other vim scripts use that area already, > e.g. ShowMarks http://www.vim.org/scripts/script.php?script_id=152), namely > a green bar in front of each line that has been changed (and > subsequently saved) since editing this file has started, and a yellow > bar in front of each line that has been changed (but not yet saved). > (The colors should be configurable.) > > Or is there a possibility to emulate change bars using the "signs" feature? This has been asked for a few times. Currently you could use diff mode, but that looks quite different from a change bar. I'll add a voting item for this. -- ARTHUR: Go on, Bors, chop its head off. BORS: Right. Silly little bleeder. One rabbit stew coming up. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// 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: google summer of code: gdb - vim
Erik Bergman wrote: > I've tried clewn, and while it works (somewhat) it's far from perfect. > I had also hoped for such a summer of code project. Solid debugger > support is about the only thing left that I really miss in vim. Is it > too late to add new project suggestions by now? You can submit applications until March 24. -- TIM: But follow only if you are men of valour. For the entrance to this cave is guarded by a monster, a creature so foul and cruel that no man yet has fought with it and lived. Bones of full fifty men lie strewn about its lair ... "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// 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: Consistently exit "message display" with 'q'?
Jean-Rene David wrote: > * Bram Moolenaar [2007.03.20 11:45]: > > > How many times did I repeat a command just because > > > I had pressed one time too many... > > > > You can type "g<" to go back to the messages. > > Thanks! Didn't know about that. > > Reading the help, this only brings back the last > viewed page of messages though. Not quite the same > thing as bringing up the complete output of the > last command. After "g<" you are back at the hit-enter prompt and scroll further back. -- Q: What do you call a fish without an eye? A: fsh! Q: What do you call a deer with no eyes? A: no eye deer. Q: What do you call a deer with no eyes and no legs? A: still no eye deer. /// 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: Consistently exit "message display" with 'q'?
Jean-Rene David wrote: > * [EMAIL PROTECTED] [2007.03.19 22:30]: > > The more frustrating thing is: if I continuously > > scroll down in the 'more-prompt' mode, the > > 'more-prompt' will eventually quits the display > > and the message are disappeared forever, so I > > must be careful NOT to press any key when the > > last line of message are shown. > > I'm fairly sympathetic to this concern. > > How many times did I repeat a command just because > I had pressed one time too many... You can type "g<" to go back to the messages. -- Life is a gift, living is an art. (Bram Moolenaar) /// 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///
Vim joins Google Summer of Code
Instead of doing a boring holiday job, students can work on Vim this summer. Google sponsors the work. Ideas for what could be worked on can be found on the ideas page: http://www.vim.org/soc/ideas.php But you can also come up with your own task. Keep in mind that the number of students that will be accepted is limited, thus write a good application! For more information about the Google Summer of Code program, you can visit this page: http://code.google.com/soc/ Students should plan to submit their applications by March 24, 2007. -- ARTHUR:I command you as King of the Britons to stand aside! BLACK KNIGHT: I move for no man. The Quest for the Holy Grail (Monty Python) /// 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: OT: Apparently I work for Bram...
Tim Chase wrote: > Found this amusing: a while back, for some open web survey of > "cast your vote for your favorite software", I submitted Vim. > There was a mandatory field for the "company" that produced it, > so I put in Bram's name. > > Well, a year or so later, somehow that combination of my name and > Bram as a business found their way together and I just got a > magazine addressed to me at my company, "Bram Moolenaar". [rolls > eyes] Well, there are far worse folks to be associated with, so > it's no great crime given that Bram (or what I know of him and > have seen on google-video) is quite an affable fellow. But > that's technology for you. It will certainly be a notable marker > if they sell my name to advertisers. > > So, according to Sys-Con media's computers, I now work for Bram. I will send you your work plan for the coming week. Don't expect a paycheck though! :-) > Maybe someday I'll set their crazy computers straight. Or maybe > it's not-so-subtle commentary that I spend too much time on the > vim-list. :) > > -tim > PS: and I never even heard back whether Vim got any accolades > from the survey. :( Accolades? I prever chocolades. -- I'm sure that I asked CBuilder to do a "full" install. Looks like I got a "fool" install, instead. Charles E Campbell, Jr, PhD /// 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: How to display a omni-comletion menu from a vim script function?
Thomas wrote: > Let me rephrase my question: > > Is it possible to display the omni-completion menu in normal mode, eg > from a function called in normal mode? > > I don't want to set omnifunc or completefunc for this. No, the omni-completion menu only works in Insert mode. Using the popup menu in other modes is currently not supported. There is the GUI popup menu, like it's used for spell checking. -- ARTHUR: Then who is your lord? WOMAN: We don't have a lord. ARTHUR: What? DENNIS: I told you. We're an anarcho-syndicalist commune. We take it in turns to act as a sort of executive officer for the week. The Quest for the Holy Grail (Monty Python) /// 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///
Adjusted list of features to vote on
Greetings, Vim users! Vim sponsors and registered Vim users can vote for features. The result can be seen here: http://www.vim.org/sponsor/vote_results.php Vim 7.0 has added a number of features that still appeared in the voting list. I have now updated the list to reflect the Vim 7.0 features. Removed features: - add tabbed windows - add undo tree (be able to go back to any previous situation) - add a ":grep" command that does not use an external command - add option to highlight the screen line (and column) of the cursor Changed features: - "add intelligent completion" -> "add more and better omni completion plugins" - "add more features to Vim scripting (arrays, lists, sorting, etc.)" -> "add more features to Vim scripting" - "add more autocommand events (for ":cd", start Insert mode, etc.)" -> "add more autocommand events (for ":cd", jump to tag, etc.)" - "add on-the-fly spell checking" -> "improve on-the-fly spell checking" If you voted for one of these, please go to the voting pages and adjust your votes: http://www.vim.org/sponsor/vote.php You need to login. Happy Vimming! -- Have you heard about the new Barbie doll? It's called Divorce Barbie. It comes with all of Ken's stuff. /// 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: clone a vim session into a new tab
Andy Wokula wrote: > >> Ok tabpages are included in the session per default. Try > >> :set sessionoptions-=tabpages > >> first. > >> > > > > Awesome! Thanks a lot! > > > >> :help 'sessionoptions' > >> > > > > The help is a bit confusing. It says > > > > There is no option to include tab pages yet, only the current tab > > page > > is stored in the session. |tab-page| > > > > But in reality, it stores all the tab pages. Is this a bug in the > > documentation? or am I misreading something? > > > > raju > > Confuses me too. Looks like some forgotten beta version note. Right, I'll remove it. -- MORTICIAN:Bring out your dead! [clang] Bring out your dead! [clang] Bring out your dead! CUSTOMER: Here's one -- nine pence. DEAD PERSON: I'm not dead! The Quest for the Holy Grail (Monty Python) /// 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: complete=custom for path including spaces
Raphael Bauduin wrote: > I'm writing a command with a custom completion, and it works fine, > except when there's a space in the "path" to complete. > > For example, without spaces everything works: >:Radiant edit pages/ho > will complete to >:Radiant edit pages/home/ > which I can further complete: >:Radiant edit pages/home/fi > to >:Radiant edit pages/home/first-post/ > > If there's a space, it doesn't work: >:Radiant edit pages/Ho > is completed to >:Radiant edit pages/Home\ Page/ > But now, this >:Radiant edit pages/Home\ Page/A > doesn't complete it, although my completion function returns what is > expected as completion: >pages/Home\ Page/About >pages/Home\ Page/Articles > > What am I missing here? Did you try returning the matches without the backslash? You can also try using "customlist", then Vim will not filter the results. The backslash may confuse the filtering. -- "A mouse can be just as dangerous as a bullet or a bomb." (US Representative Lamar Smith, R-Texas) /// 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///
Financial report ICCF available
Greetings, Vim users! The ICCF Holland foundation is Vim's charity. Vim users are asked to consider helping needy children in Kibaale, Uganda. Since April 2006 the Vim sponsorship and registration is also destined for this project. The financial report for 2006 is now available. You can find it here: http://iccf-holland.org/jaar2006.pdf There is also a Dutch version: http://iccf-holland.org/jaar2006n.pdf I'm glad to report that the total revenue has increased by 25%. Mainly because of Vim sponsorship. Thanks to all the people who donated! More information about ICCF Holland on the website: http://iccf-holland.org I hope to visit the project before the summer and report how the money is being used. -- Proverb: A nightingale that forgets the lyrics is a hummingbird. /// 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: [PATCH] minor doc update
Michael Wookey wrote: > > OTOH, the svn repository is known to "lag behind" the other > > repositories, sometimes by a week or more: diffing against it runs > > the risk of forking the code. IIUC, the "latest on nluug.nl" is also > > the "latest official version" at any point in time. You can compare > > the first line of the version you have with the one I showed above. > > I think it is wise to always diff against the latest known version, > > whichever it be: IOW, if your version is earlier than mine, it > > will "imminently" be obsoleted, even if your patch is not accepted. > > Excellent point. Bram - what is your preference for documentation > patches? Mostly it doesn't matter much, especially for small changes like this one. For larger changes it's better to diff against the runtime files on the ftp site. These are more recent, since I don't send out patches for runtime files (except when it's related to source code changes). See http://www.vim.org/runtime.php -- [clop clop] GUARD #1: Halt! Who goes there? ARTHUR:It is I, Arthur, son of Uther Pendragon, from the castle of Camelot. King of the Britons, defeator of the Saxons, sovereign of all England! GUARD #1: Pull the other one! The Quest for the Holy Grail (Monty Python) /// 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: Why does VimResized get triggered 4 times per resize
Tony Mechelynck wrote: > Marius Roets wrote: > > Hi everybody, > > Can somebody explain the following behaviour to me. In my .vimrc I put > > the following: > > " --START -- > > function ResizeEvent() > > let &lines = &lines - 1 > > execute '!echo "resizing "'.&lines . ' >> test.txt' > > endfunction > > > > autocmd VimResized * call ResizeEvent() > > " END --- > > Now for every resize event, I get 4 lines in test.txt. The result is > > that I end up with 'lines' being decreased 4 times, instead of just > > once. > > > > Thanks > > Marius > > > > Strange: normally autocommands don't nest, which would mean that using ":let > &lines = &lines - 1" (or ":set lines-=1") inside an autocommand (for > VimResized) shouldn't trigger VimResized again. > > I confirm this strange behaviour: after sourcing a script containing > > function ResizeEvent() > set lines-=1 > redir >> ~/resize.log > silent echo "lines:" &lines > redir END > endfunction > au! VimResized * call ResizeEvent() > > then invoking (once) ":call ResizeEvent()" at the gvim command-line, I get > the > following in ~/resize.log (which previously didn't exist): > > > > lines: 35 > lines: 34 > lines: 33 > lines: 33 > lines: 32 > What probably happens is that the resizing, or the event triggered by it, is noticed after the function returns. Thus the first resize triggers the function, 'lines' is decreased, the function returns and then the event is triggered again. -- The psychic said, "God bless you." I said, "I didn't sneeze." She looked deep into my eyes and said, "You will, eventually." And, damn if she wasn't right. Two days later, I sneezed. --Ellen Degeneres /// 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: new tabs and ultraMon
Afton Lewis wrote: > I"m using gVim 7.0 on windows XP, with dual monitors and ultraMon installed. > > When I go from no-tabs to one (or is that one tab to two?) gvim jumps > to my primary monitor. Further tab creations don't cause this. I > created tabs with > :tabe > :tabnew > > If the instance is already on my primary monitor, no such jump occurs. > > Any thoughts? > > I have ultraMon installed, but turning ultraMon off doesn't change the > behaviour. Sounds like an old resizing problem. Does the problem go away if you do: :set guioptions-=e -- "Intelligence has much less practical application than you'd think." -- Scott Adams, Dilbert. /// 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: accounts and wikis
Charles Campbell wrote:
> In order to prevent spam, some sort of verification procedure seems to
> be necessary.
>
> Vim's website already supports "accounts"; would requiring one to log
> into a vim account before making tips or add-ons to tips help?
> A verification step for account privilege (apply for account -> mail to
> user with magic cookie -> user mails magic cookie back) should serve to
> ameliorate spam, I'd think, although it'd still be possible.
Most servers don't support sending e-mail. It's disabled at
SourceForge, for example. The reason is that they want to prevent
becoming a spam source.
--
GALAHAD: Camelot ...
LAUNCELOT: Camelot ...
GAWAIN:It's only a model.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: VimTips Wiki: New Direction
Tom Purl summarized: > Here's my view of "where we are" regarding the Vim Tips wiki conversion > project: > > 1. The Google wiki seems to be a poor option due to the difficulty >involved in registering. > 2. Multiple other wiki engines have been discussed, and the clear >favorite seems to be a site built on top of the Mediawiki >application. > 3. Of all of the sites that offer free wiki hosting using Mediawiki, >Wikibooks seems to be the most favored. > > Note: These are all my opinions based on what I've read. I hope to hear > from everyone that has a different perspective :) > > Ok, so based on my version of reality, I think that we should proceed with > the following actions: > > 0. I'll create the following page on the Vim Tips chapter of the Vim book > on Wikibooks (whew!): > * http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox > 1. All of the people who wrote tip conversion scripts before should >update them so that the output format is "Wikipedia markup", not > "Google markup" > * I apologize to the script writers for making them do more work. > Hopefully, the necessary changes to your scripts will be small. > * Also, please note that I _don't_ think that anyone should > contribute a new script to this effort. We already have three very > capable scripts that can probably get the job done very well, so I don't > think that the effort would be worthwhile for anyone else. > 2. Convert one tip and post the output on the TipsSandbox page listed >above. > 3. The vim community will come to a consensus on the best format for the >tips, and we will use the best script for the job. > 4. Consensus achieved!!! > 5. We will automate the task of converting all of the tips. > 6. A group of wiki superusers will inspect 50 random tips and make sure >that they look good. > 7. The invisible hand of The Wiki will then gradually make our wonderful >collection of Vim tips even more awesome than they've ever been before! ;D > > So, what do you guys think? Sounds great to me. I'm still a bit worried about spammers, since that is what broke down the current tip collection. Perhaps someone can look into this, so that the scripts we use for conversion do the right thing? -- hundred-and-one symptoms of being an internet addict: 258. When you want to see your girlfriend, you surf to her homepage. /// 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: BufWritePre and :wqa
Cyril Slobin wrote: > Hello vim people! > > Does anybody noted that the BufWritePre triggers on :w and :wq > commands, but doesn't on :wqa command? At least with Vim 7.0 Win32 > version. And if nobody reported this yet, where and how should I > report? Is this message enough? > > P.S. In fact I've made use of this error, so when it will be fixed, > I'll find a way to emulate it! ;-) It will help a lot to understand what you are talking about if you include an example script. Details might matter. -- hundred-and-one symptoms of being an internet addict: 257. Your "hundred-and-one" lists include well over 101 items, since you automatically interpret all numbers in hexadecimal notation. (hex 101 = decimal 257) /// 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: Problem with C/C++ syntax folding
Jay Atkinson wrote: > I seem to be having a problem with the default syntax folding in Vim 7.0. > The syntax folding seems to get confused whenever there is a statement like > this: > > a = (b == 0) ? 1 : 2; > > After a statement like that, the folding just collapses everything after > that statement into one fold. It normally highlights all the following > curly braces in red as well. Has anyone stumbled across this problem and > come up with a fix? It appears to work fine for me. Try this: vim -u NONE yourfile.c source $VIMRUNTIME/syntax/c.vim set foldmethod=syntax Does it still happen then? If not then you have something added to the C syntax that causes the problem. -- hundred-and-one symptoms of being an internet addict: 241. You try to look for Net Search even when you're in File Manager. /// 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: GB18030 != CP936
Yongwei Wu wrote:
> > It would be possible to make a special case for GB18030 in set_init_1().
> > This would set 'encoding' to "utf-8" and 'termencoding' to "GB18030".
> > Perhaps you can try these settings and check if everything works:
> > translated menus, input methods, using Vim in a terminal (if a GB18030
> > terminal exists), etc.
>
> It is a viable solution, but it is complicated. I have no access to a
> GB18030 terminal currently, but I can speculate that in order to
> achieve the "no surprise" principle, you will have to change
> fileencoding and fileencodings too so that people can open a
> GB18030/GBK file without setting any Vim options.
'fileencodings' should also be set, but perhaps it's already OK because
of other rules in the option initialization. Needs to be checked.
> My main point is that if our purpose is to make Vim novices edit
> Simplified Chinese files (almost always encoded in GBK) without
> troubles in the zh_CN.GB18030 environment, a hack to set encoding to
> CP936 will be enough for all practical purposes. Vim veterans will
> know how to have their way around. My objection to Patch 58 is only
> that it *disabled* Vim veteran's possibility to edit GB18030 files.
So basically you want to set 'encoding' to "cp936", but not use the
alias. So that most files can be edited without trouble, and conversion
still works for people who need the extra characters. Thus instead of
falling back to "utf-8" in set_init_1() you would fall back to "cp936".
Then no other options need to be set (hopefully).
Try this patch:
*** ../../vim-7.0.205/src/option.c Tue Oct 17 18:36:03 2006
--- option.cWed Feb 28 21:52:39 2007
***
*** 3290,3295
--- 3290,3303
* If not, go back to the default "latin1". */
save_enc = p_enc;
p_enc = p;
+ if (STRCMP(p_enc, "gb18030") == 0)
+ {
+ /* We don't support "gb18030", but "cp936" is 99% the same, thus
+* use that. It's not an alias to still support conversion
+* between gb18030 and utf-8. */
+ p_enc = vim_strsave((char_u *)"cp936");
+ vim_free(p);
+ }
if (mb_init() == NULL)
{
opt_idx = findoption((char_u *)"encoding");
*** ../../vim-7.0.205/src/mbyte.c Tue Dec 5 22:09:02 2006
--- mbyte.c Tue Feb 27 16:27:44 2007
***
*** 364,370
{"949", IDX_CP949},
{"936", IDX_CP936},
{"gbk", IDX_CP936},
- {"gb18030", IDX_CP936}, /* only 99% the same */
{"950", IDX_CP950},
{"eucjp", IDX_EUC_JP},
{"unix-jis", IDX_EUC_JP},
--- 364,369
--
If evolution theories are correct, humans will soon grow a third
hand for operating the mouse.
/// 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: How do I make the current working directory follow the active document in Gvim?
Tony Mechelynck wrote: > Bram Moolenaar wrote: > > Tony Mechelynck wrote: > > > >> here are a few examples; some of them use a fictional "subject": > > > > Nice overview. Let me add this to the user manual. > > > > In the paragraph about :help pattern with 'wildmenu' on, I let > myself be carried away: and don't apply to the wildmenu > for helptags. I wanted to keep it simple, thus I left out the whole part of the 'wildmenu'. -- hundred-and-one symptoms of being an internet addict: 223. You set up a web-cam as your home's security system. /// 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: VimTips - Google Wiki Usefulness
Tom Purl wrote: > > Besides that, transferring all existing tips to the wiki needs to be > > tried out. > > I don't understand what you mean here. Are you saying that we should > move forward with a Google wiki conversion, irrespective of whether or > not we end up using the Google wiki? No, I meant that the conversion should be tried out for whatever wiki we may want to use. If we can't automatically add all the existing tips then that's a big disadvantage. A CAPTSCHA mechanism would cause trouble, for example, if there is no other way to add pages. -- hundred-and-one symptoms of being an internet addict: 216. Your pet rock leaves home. /// 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: GB18030 != CP936
Yongwei Wu wrote: > > > On 2/27/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > > > > > If I understand it correctly is GB18030 a multi-byte character set that > > > > is mostly the same as cp936, but adds a number of 4-byte characters. > > > > Vim does not support those 4-byte characters, thus setting 'encoding' to > > > > gb18030 won't work. > > > > > > > > But conversion between gb18030 and utf-8 should work, thus when > > > > 'encoding' is utf-8 it should be possible to use gb18030 in > > > > 'fileencodings' and 'fileencoding'. Perhaps you can check if that > > > > works. > > > > > > No, with Patch 58 Vim regards gb18030 as an alias for cp936, and > > > gb18030 does not work at all: this is the major problem. > > > > Please be specific: What do you mean with "does not work at all"? > > As I said, Vim regards gb18030 as cp936 after Patch 58. I.e., "e > ++enc=gb18030" is equivalent to "e ++enc=cp936" now. One cannot > correctly open in Vim a file encoded in GB18030, and the 4-byte > encoded characters will not be correct. Since Vim does not support gb18030 for 'encoding', and using "gbk" or "cp936" will not support the 4-byte characters either, the only way would be to set 'encoding' to "utf-8". The current solution to set 'encoding' to "cp936" works only for most characters, not all. It would be possible to make a special case for GB18030 in set_init_1(). This would set 'encoding' to "utf-8" and 'termencoding' to "GB18030". Perhaps you can try these settings and check if everything works: translated menus, input methods, using Vim in a terminal (if a GB18030 terminal exists), etc. -- hundred-and-one symptoms of being an internet addict: 213. Your kids start referring to you as "that guy in front of the monitor." /// 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: VimTips - Google Wiki Usefulness
Georg Dahn wrote: > --- Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Using wikibooks.org sounds attractive, but I don't see any protection > > against spamming. And that is exactly what happens to the Vim tips. > > It's just a matter of time before this happens on wikibooks.org too. > > WikiMedia, which is the software of WikiPedia and WikiBooks and one of > the most flexible and most feature-rich software for wikis, offers the > following protection against spamming: > > http://meta.wikimedia.org/wiki/Wiki_Spam > http://meta.wikimedia.org/wiki/Anti-spam_Features > http://meta.wikimedia.org/wiki/Spam_Filter > > Or just see the contents of the whole category: > > http://meta.wikimedia.org/wiki/Category:Anti_Spam > > Hope, that helps. This only mentions what would be possible, not what wikibooks.org is using. It doesn't sound like they are using some automatic mechanism. -- hundred-and-one symptoms of being an internet addict: 209. Your house stinks because you haven't cleaned it in a week. /// 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: VimTips - Google Wiki Usefulness
Samuel Wright wrote: > On 27/02/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Using wikibooks.org sounds attractive, but I don't see any protection > > against spamming. And that is exactly what happens to the Vim tips. > > It's just a matter of time before this happens on wikibooks.org too. > > The difference is that people can correct the spam on a public wiki, > whereas in the vim tips you can add spam, but not fix it unless you > are an admin. The problem with the spam was that it became so much that manually removing it no longer worked, even though there were many people willing to do this. There needs to be an automatic mechanism. Or require logging in. -- hundred-and-one symptoms of being an internet addict: 210. When you get a divorce, you don't care about who gets the children, but discuss endlessly who can use the email address. /// 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: VimTips - Google Wiki Usefulness
Denis Perelyubskiy wrote: > On Mon, 26 Feb 2007 09:29:32 -0600 (CST), "Tom Purl" <[EMAIL PROTECTED]> > said: > > Ok, so the majority of people seem to be saying that the Google wiki > > isn't very well-suited for our needs. Most notably, it's very likely > > that it will severely inhibit contributions. I agree with this > > whole-heartedly. > > http://freemind.sourceforge.net/wiki/index.php/Main_Page > > I don't know what freemind is, but the project is hosting a wiki on > sourceforge. Our vim.sf.net is on sourceforge. Can't we just stick a > wiki there and be done with it? SourceForge has become less reliable. For example, the shell server was offline for more than a week. Fortunately the website kept working, but I was unable to edit files there. I don't expect this to improve, I would rather move away from SourceForge. -- hundred-and-one symptoms of being an internet addict: 207. You're given one phone call in prison and you ask them for a laptop. /// 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: VimTips - Google Wiki Usefulness
Steve Hall wrote:
> From: "Yakov Lerner", Mon, February 26, 2007 5:38 am
> > On 2/26/07, A.J.Mechelynck wrote:
> > >
> > > If we gan get hosting space somewhere for a mediawiki server, I'm
> > > all in favour.
> >
> > From: http://en.wikibooks.org/wiki/Wiki_Science:How_to_start_a_Wiki
>
> I started one here ages ago here:
>
> http://en.wikibooks.org/wiki/Vim_Tipbook
>
> Someone else started adding syntax coloring and the overly complicated
> {{Vi/Ex|set}} stuff, but I have no problem stripping this off to get
> back to the simpler format I proposed:
>
> http://en.wikibooks.org/w/index.php?title=Learning_the_vi_editor/Vim/Tips_and_Tricks&oldid=561585
Of the free wiki's available wikibooks looks quite attractive. No
people adding advertisements or one-man efforts.
I do wonder how they avoid spamming. It seems anyone can edit a page.
--
hundred-and-one symptoms of being an internet addict:
205. You're constantly yelling at your spouse, family, roommate, whatever,
for using the phone for stupid things...like talking.
/// 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: VimTips - Google Wiki Usefulness
Tom Purl wrote: > Ok, so the majority of people seem to be saying that the Google wiki > isn't very well-suited for our needs. Most notably, it's very likely > that it will severely inhibit contributions. I agree with this > whole-heartedly. > > Also, a lot of people are discussing third-party wiki hosting sites and > the possibility of running our wiki on donated server space. I think > this is a useful exercise in case we do end up not using the Google > wiki. > > However, there are still people, including Bram, who seem to feel pretty > strongly about using the Google wiki. Bram, are we going down the wrong > track by planning for a non-Google wiki? For this site, I think it's > very important that we get as close to a consensus as possible regarding > who will do the hosting. No, I don't feel strongly about using the Google wiki. It was just an idea that came up. Being able to use the large server base and cleverness of Google would be an advanage. But there are also disadvantages, mainly that it's not simple to let everybody edit the wiki. Using wikibooks.org sounds attractive, but I don't see any protection against spamming. And that is exactly what happens to the Vim tips. It's just a matter of time before this happens on wikibooks.org too. Besides that, transferring all existing tips to the wiki needs to be tried out. -- hundred-and-one symptoms of being an internet addict: 206. You religiously respond immediately to e-mail, while ignoring your growing pile of snail mail. /// 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: VimTips - Google Wiki Usefulness
Paul Irofti write: > I don't understand why Google Wiki is being discussed here as the main > solution. As I see it there are a few _major_ disadvantages of using it: I can understand that you may have something against using Google, but there is no reason to be paranoid about it. > - it has software limitations that a large community, such as ours, > can't cope with What limitations? Google code has only just started and it's quickly expanding the features offered. Not only is it for free, it's also way more reliable than SourceForge (the shell server was recently out for more than a week :-(). > - it's managed and offered by a third party organization I'm not going to own a Vim webserver and pay for it, thus this will always be so. > - we don't have controls of what features we want in and/or out or the > way the layout/code/roadmap goes There are a few limitations, yes. Reasonable limitations though. > - it's a commercial product and Vim will be asociated with it in the long > run It's not commercial, it's free. > - Google is as corporate as you can get, corporations and OpenSource > don't mix well together (there are tons of examples) There are lots of open source people working for Google, probably more than in any other company. We feel quite happy about that. > - from what I've read in this thread it doesn't even have all the > features needed for a working Vim-tips wiki That might indeed be the bottleneck. And that's why we were trying it out, to see if it would work well enough. > On the other hand mediawiki seems the best solution for something like > this: > > - it's *OpenSource* > - it offers an easy management environment > - it can support high loads of traffic (see wikipedia) > - it has multi-language support > - it's easy to customize and improve > - it's not chown()-ed by any corporation And requires your own webserver, maintenance, etc. Main problem here is to avoid spamming, this has destroyed many wikis already and will only get worse. It's so much easier to join a service that is well maintained than to run your own. > I know I'm not a regular here, but I read most of the mail I get from > vim@ and don't quite get why you people are seriously considering this. > So I thought I'd drop my two cents and hope that someone can shed some > light. Main reason is that all self-made solutions fail eventually. The tips on SourceForge are now closed because of the spamming problems. We need something else. Keep in mind that both Scott Johnston and myself are working for Google, that helps for getting things done. SourceForge is a dead end, it takes them forever to fix problems. -- hundred-and-one symptoms of being an internet addict: 204. You're being audited because you mailed your tax return to the IRC. /// 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: GB18030 != CP936 (Alternative project?)
Tony Mechelynck wrote: > Here is an alternative way to handle it, which may be "the right way" > from a conceptual point of view, and in the long term, though it may > be much more difficult from the coding point of view. It may or may > not be "the right thing to do" pragmatically: > > Treat GB18030 as what it is, namely, a Unicode Transformation Format. > In other words, whenever 'encoding' is set to GB18030, use UTF-8 > internally and convert when reading and writing, just like we already > do for UTF-16le, UTF-16be, UTF-32le and UTF-32be. > > This, of course, also suffers from the performance problems related to > conversion GB18030 <=> UTF-8. Converting various Unicode encodings to and from UTF-8 is trivial. Conversion between GB18030 and UTF-8 requires iconv. This is a huge difference. Also because the conversion may fail. If we go this way it's probably better not to use tricks and explicitly set 'encoding' to utf-8. One would need to try this out to discover any problems, e.g. with menus. Try Motif: GTK is utf-8 based thus Motif is more of a challange. -- Spam seems to be something useful to novices. Later you realize that it's a bunch of indigestable junk that only clogs your system. Applies to both the food and the e-mail! /// 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: How do I make the current working directory follow the active document in Gvim?
Tony Mechelynck wrote:
> here are a few examples; some of them use a fictional "subject":
Nice overview. Let me add this to the user manual.
--
panic("Fod fight!");
-- In the kernel source aha1542.c, after detecting a bad segment list
/// 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: GB18030 != CP936
Yongwei Wu wrote: > On 2/27/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > If I understand it correctly is GB18030 a multi-byte character set that > > is mostly the same as cp936, but adds a number of 4-byte characters. > > Vim does not support those 4-byte characters, thus setting 'encoding' to > > gb18030 won't work. > > > > But conversion between gb18030 and utf-8 should work, thus when > > 'encoding' is utf-8 it should be possible to use gb18030 in > > 'fileencodings' and 'fileencoding'. Perhaps you can check if that > > works. > > No, with Patch 58 Vim regards gb18030 as an alias for cp936, and > gb18030 does not work at all: this is the major problem. Please be specific: What do you mean with "does not work at all"? Since Vim doesn't support gb18030 internally and only Unicode has all the characters, I guess it would only work to edit these files when 'encoding' is "utf-8". However, if gb18030 is used in the environment that means that console output needs to be converted, thus 'termencoding' also needs to be set. -- hundred-and-one symptoms of being an internet addict: 202. You're amazed to find out Spam is a food. /// 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: GB18030 != CP936
Zhaojun Wu wrote: > Hi, Yongwei, > > I am also realizing this issue during my recent research on Chinese encodings. > > As shown in the wikipedia, CP936 is just the encoding derived from > Microsoft's Windows 95. Due to the popularity of Windows OS in > mainland China, the Chinese government build the GBK (GB-2312 > extension) on the top of CP936 to cover more characters which are out > of the old GB2312 standard. > GB18030 actually is a Unicode-compatible standard and a superset of > GB2312 and back-compatible with GBK. > > Thus, in this case, GB18030 could not be treated as CP936. > > If you can read Chinese, here is a brief and good introduction of > various Chinese encoding systems. > [http://www.eygle.com/digest/2007/01/zhs16gbk_char.html] > > For the encoding detection, I find another powerful tool "enca" > (Extremely Naive Charset Analyser) > [http://trific.ath.cx/software/enca/] to do the same job. > > It seems working better than your "tellenc". For example, your > "tellenc" cannot identify the encoding of one Chinese utf-8 test file > distributed in the "enca" package. > > So far, I haven't dig into the details of both of your > implementations, but just enclosed that test file for you reference. If I understand it correctly is GB18030 a multi-byte character set that is mostly the same as cp936, but adds a number of 4-byte characters. Vim does not support those 4-byte characters, thus setting 'encoding' to gb18030 won't work. But conversion between gb18030 and utf-8 should work, thus when 'encoding' is utf-8 it should be possible to use gb18030 in 'fileencodings' and 'fileencoding'. Perhaps you can check if that works. -- hundred-and-one symptoms of being an internet addict: 199. You read this entire list of symptoms, looking for something that doesn't describe you. /// 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: 2html.vim 256 color support
; + let s:cterm_color130 = "#af5f00" + let s:cterm_color131 = "#af5f5f" + let s:cterm_color132 = "#af5f87" + let s:cterm_color133 = "#af5faf" + let s:cterm_color134 = "#af5fd7" + let s:cterm_color135 = "#af5fff" + let s:cterm_color136 = "#af8700" + let s:cterm_color137 = "#af875f" + let s:cterm_color138 = "#af8787" + let s:cterm_color139 = "#af87af" + let s:cterm_color140 = "#af87d7" + let s:cterm_color141 = "#af87ff" + let s:cterm_color142 = "#afaf00" + let s:cterm_color143 = "#afaf5f" + let s:cterm_color144 = "#afaf87" + let s:cterm_color145 = "#afafaf" + let s:cterm_color146 = "#afafd7" + let s:cterm_color147 = "#afafff" + let s:cterm_color148 = "#afd700" + let s:cterm_color149 = "#afd75f" + let s:cterm_color150 = "#afd787" + let s:cterm_color151 = "#afd7af" + let s:cterm_color152 = "#afd7d7" + let s:cterm_color153 = "#afd7ff" + let s:cterm_color154 = "#afff00" + let s:cterm_color155 = "#afff5f" + let s:cterm_color156 = "#afff87" + let s:cterm_color157 = "#afffaf" + let s:cterm_color158 = "#afffd7" + let s:cterm_color159 = "#af" + let s:cterm_color160 = "#d7" + let s:cterm_color161 = "#d7005f" + let s:cterm_color162 = "#d70087" + let s:cterm_color163 = "#d700af" + let s:cterm_color164 = "#d700d7" + let s:cterm_color165 = "#d700ff" + let s:cterm_color166 = "#d75f00" + let s:cterm_color167 = "#d75f5f" + let s:cterm_color168 = "#d75f87" + let s:cterm_color169 = "#d75faf" + let s:cterm_color170 = "#d75fd7" + let s:cterm_color171 = "#d75fff" + let s:cterm_color172 = "#d78700" + let s:cterm_color173 = "#d7875f" + let s:cterm_color174 = "#d78787" + let s:cterm_color175 = "#d787af" + let s:cterm_color176 = "#d787d7" + let s:cterm_color177 = "#d787ff" + let s:cterm_color178 = "#d7af00" + let s:cterm_color179 = "#d7af5f" + let s:cterm_color180 = "#d7af87" + let s:cterm_color181 = "#d7afaf" + let s:cterm_color182 = "#d7afd7" + let s:cterm_color183 = "#d7afff" + let s:cterm_color184 = "#d7d700" + let s:cterm_color185 = "#d7d75f" + let s:cterm_color186 = "#d7d787" + let s:cterm_color187 = "#d7d7af" + let s:cterm_color188 = "#d7d7d7" + let s:cterm_color189 = "#d7d7ff" + let s:cterm_color190 = "#d7ff00" + let s:cterm_color191 = "#d7ff5f" + let s:cterm_color192 = "#d7ff87" + let s:cterm_color193 = "#d7ffaf" + let s:cterm_color194 = "#d7ffd7" + let s:cterm_color195 = "#d7" + let s:cterm_color196 = "#ff" + let s:cterm_color197 = "#ff005f" + let s:cterm_color198 = "#ff0087" + let s:cterm_color199 = "#ff00af" + let s:cterm_color200 = "#ff00d7" + let s:cterm_color201 = "#ff00ff" + let s:cterm_color202 = "#ff5f00" + let s:cterm_color203 = "#ff5f5f" + let s:cterm_color204 = "#ff5f87" + let s:cterm_color205 = "#ff5faf" + let s:cterm_color206 = "#ff5fd7" + let s:cterm_color207 = "#ff5fff" + let s:cterm_color208 = "#ff8700" + let s:cterm_color209 = "#ff875f" + let s:cterm_color210 = "#ff8787" + let s:cterm_color211 = "#ff87af" + let s:cterm_color212 = "#ff87d7" + let s:cterm_color213 = "#ff87ff" + let s:cterm_color214 = "#ffaf00" + let s:cterm_color215 = "#ffaf5f" + let s:cterm_color216 = "#ffaf87" + let s:cterm_color217 = "#ffafaf" + let s:cterm_color218 = "#ffafd7" + let s:cterm_color219 = "#ffafff" + let s:cterm_color220 = "#ffd700" + let s:cterm_color221 = "#ffd75f" + let s:cterm_color222 = "#ffd787" + let s:cterm_color223 = "#ffd7af" + let s:cterm_color224 = "#ffd7d7" + let s:cterm_color225 = "#ffd7ff" + let s:cterm_color226 = "#00" + let s:cterm_color227 = "#5f" + let s:cterm_color228 = "#87" + let s:cterm_color229 = "#af" + let s:cterm_color230 = "#d7" + let s:cterm_color231 = "#ff" + let s:cterm_color232 = "#080808" + let s:cterm_color233 = "#121212" + let s:cterm_color234 = "#1c1c1c" + let s:cterm_color235 = "#262626" + let s:cterm_color236 = "#303030" + let s:cterm_color237 = "#3a3a3a" + let s:cterm_color238 = "#44" + let s:cterm_color239 = "#4e4e4e" + let s:cterm_color240 = "#585858" + let s:cterm_color241 = "#626262" + let s:cterm_color242 = "#6c6c6c" + let s:cterm_color243 = "#767676" + let s:cterm_color244 = "#808080" + let s:cterm_color245 = "#8a8a8a" + let s:cterm_color246 = "#949494" + let s:cterm_color247 = "#9e9e9e" + let s:cterm_color248 = "#a8a8a8" + let s:cterm_color249 = "#b2b2b2" + let s:cterm_color250 = "#bcbcbc" + let s:cterm_color251 = "#c6c6c6" + let s:cterm_color252 = "#d0d0d0" + let s:cterm_color253 = "#dadada" + let s:cterm_color254 = "#e4e4e4" + let s:cterm_color255 = "#ee" +endif endif endif -- hundred-and-one symptoms of being an internet addict: 196. Your computer costs more than your car. /// 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: Vim presentation in Mountain View
Tom Flynn wrote: > I watched and enjoyed it as well. Though I had a quick question. Towards > the end, during the question and answer session, you mentioned that you had > worked on integration with gdb at some point. You went so far as to > type-out the web-address of the project. However, the video seems too > low-res to make out what you typed. Could you reply with that link? That's http://www.agide.org . -- I'm in shape. Round IS a shape. /// 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: VimTips - Google Wiki Usefulness
John Beckett wrote: > I like the concept of using the Google wiki. In addition to the "Google > is Good" factor, there is the likelihood of very high reliability and zero > cost. Also, it seems appropriate due to Bram's work. > > As has been pointed out, spam is a really big threat, and will get > worse (more automated) every year. I don't see why we should ask > anyone here to take on the job of manually removing junk. The > problems of using the Google wiki may be a benefit in the future. > > How about this concept: Use the Google wiki with a dozen admins. > Those admins are likely to be here, and either have a Google ID or > would be willing to get one. > > Create a new mailing list ([EMAIL PROTECTED]), or use an existing list > with a convention that the subject should start with "vimtip". > > On the wiki, explain how to post a tip by emailing the tip to the > agreed mail account. That would require the user to join the list. > Alternative: Have an automated account that forwards any mail > including "vimtip" to the agreed mailing list. > > A discussion here would then massage the tip and decide its fate. > Perhaps it is too similar to an existing tip, or perhaps it should be > incorporated into an existing tip. After a week, a kind wiki admin > would post the final tip to the wiki. > > ---Benefits--- > No spam on wiki. > Each posted tip will be massaged and worthwhile. > Tips on similar topics could be arranged together. > > Someone with a tip doesn't have to worry if it's "good" > (it will only be posted if the community likes it). > That might encourage tippers. > > ---Problems--- > No WYSIWYG editing (might be a benefit - uniform style). > Burden on community to edit tip within a few days > (and likelihood of unresolved arguments). > Burden on admins to post tip. > > Some tippers will be offended when their work is edited > or rejected. That might discourage tippers. I think this puts too much burdon the volunteers that become an admin. And it defeats the easy of use of a wiki. I do think that we can do the addition of new people who want to be able to edit the wiki manually. That should also filter out the spammers. There is only a delay between wanting to edit the wiki and being able to do it the first time. Not perfect, but it's something that we can setup right now and try out. -- A bad peace is better than a good war. - Yiddish Proverb /// 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: tips project
Tom Purl wrote: > >> Ok everyone, the project's created: > >> > >> * http://code.google.com/p/vimtips/ > > > > I think there's a major disadvantage in using the code.google.com wiki > > - it only allows people who have been added to the project to edit the > > wiki via the web interface (please correct me if I'm wrong). At least > > if it allows editing by anyone with a google id, that would be > > reasonable enough for anyone to contribute and it'll avoid spam, but > > if only people added to the project can edit the wiki, it'll become a > > bottleneck and will discourage anyone who wants to contribute, I don't > > think many people will go through that much trouble (at least going by > > the number of 'anonymous' tip notes). > > I agree that this could be a problem. It could be lessened somewhat if > Google allowed people to join the project using a web interface, but > they don't. On the help site > (http://code.google.com/support/bin/answer.py?answer=56534&topic=10382), > they recommend that you email one of the project members to gain access, > which they would allow you to create and edit wiki pages. But this is > awkward and slow at best. > > To make things a little easier, I'll create a mailing list on the > project that people can use to request access and make miscellaneous > comments. Hopefully this will be a decent workaround until Google gives > us finer-tuned control over the project's security. How many administrators can there be? If we assume that the current tips moderators are willing to be administrators, watch the list of people who want to join the project, perhaps this can work. It's not ideal though. -- If Microsoft would build a car... ... Occasionally your car would die on the freeway for no reason. You would have to pull over to the side of the road, close all of the car windows, shut it off, restart it, and reopen the windows before you could continue. For some reason you would simply accept this. /// 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: tips project
Tom Purl wrote: > Ok everyone, the project's created: > > * http://code.google.com/p/vimtips/ > > Hooray! > > The next step is to see some conversion script ideas. If you're the type > of person who can write a script like this in 15 minutes, then by all > means do so and send it to me. Otherwise, we can discuss it on the > mailing list unless people think its too OT. > > So if you're interested in helping, start scraping vim.org/tips and let us > know what works for you. Thanks to Tom for getting this started! All the others: please give constructive suggestions. -- An error has occurred. Hit any user to continue. /// 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: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote: > Not much news, but I'd like you to know I didn't give up on the pt > dictionary. There are two pt_PT dictionaries, and I'm negotiating with > them which will be included. Is anyone from Portugal reading this? > > I still don't get how are the sug files created. If I run the mkspell > command myself I end up with only a spl file... ":help spell-NOSUGFILE" explains how you get one (and how to avoid that if you don't want it). You need to define soundfolding. Without that Vim doesn't need a .sug file. -- "Hit any key to continue" is very confusing when you have two keyboards. /// 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///
[correction] Recording of Vim presentation available
I wrote: > It's a lot quicker to get the PDF with the presentation and notes: > http://www.moolenaar.net/habits.pdf > This is about 640 Kbyte. But that's the old one! Use this link instead: http://www.moolenaar.net/habits_2007.pdf Oh, and in case you are interested in the books mentioned, use this link: http://iccf-holland.org/click2.html Sorry for the confusion. -- hundred-and-one symptoms of being an internet addict: 168. You have your own domain name. /// 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///
Recording of Vim presentation available
Dear Vim users, A week ago I did a presentation on Vim, called "Seven habits of effective text editing 2.0". I was happy to see a lot of people come to listen to me. Many more than expected, we ran out of food and had to get extra chairs. Thanks to all who were there, it was nice to have a big audience. And I was excited to greet some of the people who I previously only knew through e-mail. The video of the presentation is now available on Google video: http://video.google.com/videoplay?docid=2538831956647446078 The presentation itself is about 45 minutes. With the Q&A included it is 80 minutes. If you can't use Google video, you may get the video file from the ftp server: ftp://ftp.vim.org/pub/vim/stuff/7Habits20.avi This is 507 Mbyte of divx. You may want to use a mirror site: ftp://ftp.vim.org/pub/vim/MIRRORS It's a lot quicker to get the PDF with the presentation and notes: http://www.moolenaar.net/habits.pdf This is about 640 Kbyte. -- hundred-and-one symptoms of being an internet addict: 163. You go outside for the fresh air (at -30 degrees) but open the window first to hear new mail arrive. /// 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: The Seven Habits Of Effective Text Editing 2
cRaig - > On 2/19/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > ... > > I'll ask if I can get the video in a portable format and put it on the > > Vim ftp server. > > If you choose "Download" from a Linux workstation, you can save the > video as an AVI file. The presentation is approx. 500 MB (and well > worth it, I might add). Yeah, I noticed this is actually a divx file, so it probably plays on most systems. I'm uploading it to the ftp server (hopefully I don't hit quota!). - Bram -- hundred-and-one symptoms of being an internet addict: 153. You find yourself staring at your "inbox" waiting for new e-mail to arrive. /// 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///
Dos runtime files adjusted
I have changed the script that uploads the runtime files to the ftp
server. It now better matches the list of files in the archives.
The "runtime/dos/spell" directory now exists and contains the
English spell files, just like the distribution. This means you can use
"rsync --delete" without deleting distributed files.
Keep in mind that when you downloaded other spell files and put them in
the runtime directory, "rsync --delete" will delete them.
For Unix: the "runtime/spell" directory contains all the languages,
rsync gets them all. You may want to exclude the "spell" directory.
Or use Aap, that should work better anyway. See:
http://www.vim.org/runtime.php
Let me know if you spot a mistake in the runtime files on the ftp server.
I can't adjust the web pages right now, the SourceForge shell server is
broken. They expect it to be fixed by the 21st. That's more than a
week downtime :-(.
--
Although the scythe isn't pre-eminent among the weapons of war, anyone who
has been on the wrong end of, say, a peasants' revolt will know that in
skilled hands it is fearsome.
-- (Terry Pratchett, Mort)
/// 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: The Seven Habits Of Effective Text Editing 2
Yongwei Wu wrote: > > Bin Chen wrote: > > > > > Thanks. I am also looking forward to this talk. But unfortunately the > > > google video is blocked in some countries, could some one put the video > > > to the vim official site? and this can make this video seems more > > > official ^&^. > > > > From what countries is the video blocked? Or is it that all of Google > > video is blocked? > > The message I got was: > > Thanks for your interest in Google Video. > > Currently, the playback feature of Google Video isn't available in > your country. > > We hope to make this feature available more widely in the future, and > we really appreciate your patience. > > I am in China. I am not sure which countries have similar problems. > Maybe you can get this kind of information, Bram? I'll ask if I can get the video in a portable format and put it on the Vim ftp server. -- hundred-and-one symptoms of being an internet addict: 1 49. You find your computer sexier than your girlfriend /// 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: tips project
Tom Purl wrote: > I just checked the Google Code site (http://code.google.com/hosting/), > and couldn't find a Vim or VimTips project. I'd try creating it, but I > feel like someone more "official" to the project should do so. I think > someone should do it before someone else takes the name (like some > malicious Emacs user :), even if the tips conversion script isn't done > yet. > > Otherwise, I'd be happy to do it and brag to my dorky friends about how > integral my efforts are to the Vim project ;) > > What do you guys think? I think the person who wants to have a go at moving the tips to the wiki should register the project. So, you can do it, but then you also need to get started on the work. Or find people to do it (and add them to the project). -- hundred-and-one symptoms of being an internet addict: 142. You dream about creating the world's greatest web site. /// 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: Omni Confusion
Bill McCarthy wrote:
> Writing in C, I have a function that looks like this:
>
> void myfunc( A *a, B *b, C *c )
> {
> /* stuff */
> }
>
> A, B and C are structures in a header file which is
> included.
>
> The included header file contains the structures like this:
>
> typedef struct A
> {
> /* members */
> } A;
>
> If I start a line in myfunc() like:
>
> b->
>
> and, in insert mode after the '>' type ctrl-x ctrl-o, I am
> given only choices from the A structure. I see the same
> thing replacing the 'b' with either a 'a' or 'c'.
>
> Note, I am of course using ctags and I can jump around with
> tags - so the tagfile is fine.
>
> Bug?
I guess the script doesn't understand multiple declarations in one line.
Try changing the function header to:
void myfunc( A *a,
B *b,
C *c)
You could also try the cpp omni completion script. This is script 1520
on www.vim.org.
--
hundred-and-one symptoms of being an internet addict:
141. You'd rather go to http://www.weather.com/ than look out your window.
/// 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: The Seven Habits Of Effective Text Editing 2
Bin Chen wrote: > Thanks. I am also looking forward to this talk. But unfortunately the > google video is blocked in some countries, could some one put the video > to the vim official site? and this can make this video seems more > official ^&^. >From what countries is the video blocked? Or is it that all of Google video is blocked? -- hundred-and-one symptoms of being an internet addict: 137. You decide to stay in college for an additional year or two, just so you can have the free Internet access. /// 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: tips project
John Beckett wrote: > Bram Moolenaar wrote: > > Using the project name VimTips would be good. > > Everyone here is used to the name "Vim Tips" so VimTips sounds good, but on > a wiki I suggest that the name should be just "Vim". I'm sure we will use the wiki for other things than tips some day. Therefore just using "Vim" would be confusing. > It seems logical to me that a Vim Tips wiki would start with a (brief) page > outlining what Vim is, then have links to other information. Links would > include www.vim.org for core information, and a contents page for the wiki > tips. > > To be useful, the existing Vim Tips should be structured into some logical > order (tips on navigation, search, status line, fonts, tags, etc). Perhaps > the existing structure of Vim Help could be used. > > OTOH the perfect is the enemy of the good, so perhaps you just want to move > all tips as is, then have people slowly massage them into a coherent set of > useful tips. We can do both. But we need to start somewhere. Moving all tips over is the first step. We can simply keep the tip number at first. Making some kind of index is something that anyone can do once the wiki exists. > The wiki tips project would only be helpful after some severe editing IMHO. > Some tips should simply be omitted (or held under a section with a name > suggesting deprecation, like "Old Tips"). Other tips should be combined. > Unfortunately these steps would involve author angst. It will be useful right away: There are plenty of ways to search. Just like what is done now. Only the scoring mechanism will be lost. Hopefully we can think of a good way to find the best tips. > One good feature of the current Tips web site is that each tip is clearly > written by a specific person who is prominently credited. That gives the > author a good reason to correct errors and make updates. Traditionaly that > would not be done in a wiki, and there may be some loss. As far as I know it's not possible to edit a tip after it has been submitted. And many authors don't come back later. As with all wiki's the users must refrain from messing up someone else's work. It's a social effort. I think we can setup some "basic rules" for the Vim tips wiki, which as that the original text is separate from remarks and additions. But corrections can be made in-place. -- hundred-and-one symptoms of being an internet addict: 136. You decide to stay in a low-paying job teaching just for the free Internet access. /// 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: The Seven Habits Of Effective Text Editing 2
Jimmy - > I just heard about your recent talk at google, entitled > "The Seven Habits Of Effective Text Editing 2". > ( > http://google-code-updates.blogspot.com/2007/02/open-source-developers-google-speaker.html > ) > > The original "seven habits of effective text editing" was fascinating > and useful. I am sure that I'm not the only vimmer who would > be interested in hearing more about this updated version. However, I > can't find any links to either a video or a transcript of this talk. > Are you planning to make this available on your website? Is it > available elsewhere? The video has just become available here: http://video.google.com/videoplay?docid=2538831956647446078 The slides are available here: http://www.moolenaar.net/habits_2007.pdf I'll do an announcement soon. If you spot something wrong in the notes let me know, I can still fix those. Enjoy! - Bram -- There are three kinds of persons: Those who can count and those who can't. /// 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: Help needed on pt_BR spell checking
Leonardo Fontenelle wrote: > Hello, Bram, thanks for the reply! > > I'm sorry, but I can't find the famous $RUNTIMEPATH/spell/*.diff > files. They are don't seem to be part of the vim or the vim-spell-xx > packages in gentoo, and I can't find them in vim's ftp server. I can't > find the a-a-p recipes either... I'm sorry if this should be more > obvious, but I'm stuck. > > When I can make a good pt_BR vimspell file I'll contact the pt_PT > people to see how are we going to maintain vim dictionaries. You can find the spell *.diff files in the Unix archive and the PC runtime archive. -- hundred-and-one symptoms of being an internet addict: 131. You challenge authority and society by portnuking people /// 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///
tips project
Hi all, Google code has now added support for a wiki. This means open source projects can have a wiki that's free, fast and reliable (hopefully :-). http://code.google.com/hosting/ During my presentation last Tuesday the idea came up (again) to move the Vim tips to a wiki. The big advantage is that instead of having to read the notes below the tip to find out about improvements, the notes can be added in the right place, or even correct mistakes in the tip. I would like to ask for volunteers who want to take the current tips and notes, write some kind of script to move them to the wiki and set it up for use. If this works well we can delete the tips from the Vim website. They are currently closed for updates anyway, thus this is a good time to try it. Using the project name VimTips would be good. Please don't create it unless you are going to set up the wiki! -- hundred-and-one symptoms of being an internet addict: 127. You bring your laptop and cellular phone to church. /// 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///
