Re: VimWiki - released finally
On 6/5/07, Sebastian Menge [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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. I am EXCITED! -- -fREW
Re: VimWiki - released finally
Hi, Finally I have imported all the vim tips from http://vim.org/tips to http://vim.wikia.com if you must have ads, would it be possible to go with text-only ads? Additionally, the Digg this story button at the bottom is stupid ;-) Just my destructive 2 cents, Nico
Re: [Cygwin] Configure Detects Incorrect Ruby Version
* Taylor Venable taylor@ [070605 06:48]: ruby: no such file to load -- ubygems (LoadError) This is pretty clearly supposed to be the rubygems module, You have -rubygems somewhere in your $RUBYOPTS environment variable. Either unset this variable before building vim, check your configuration files (shell profile?) or install rubygems in case you really need it;-) not the ubygems module, so probably there's a misspelling in the code somewhere. Nope, it's for use with '-r' option. -- Regards, Sir Raorn. signature.asc Description: Digital signature
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 [EMAIL PROTECTED] 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: VimWiki - released finally
Sebastian, Why not utilize the talk: pages for the comments (see discussion tab at top of each wiki page)? Just curious. -Robert 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 [EMAIL PROTECTED] 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.
why does :save not work with -stdin-
I usually do search like this: $ grep Word *.* | vim -u myvimrc - $ cat myvimrc :autocmd StdinReadPost * :sav! /tmp/x but when I quit :q, vim always asks me to save the file again, why is the file marked as modified? I tried all combinations of flags, but can't get vim to mark the file as saved, any insights appreciated, mosh.
Re: why does :save not work with -stdin-
Hi Mohsin,
On 6/6/07, Mohsin [EMAIL PROTECTED] wrote:
I usually do search like this:
$ grep Word *.* | vim -u myvimrc -
$ cat myvimrc
:autocmd StdinReadPost * :sav! /tmp/x
but when I quit :q, vim always asks me to save the file again,
why is the file marked as modified?
I tried all combinations of flags, but can't get vim to
mark the file as saved,
It's a bug. Here is the patch. Please test it carefully, thanks very
much for reporting this to me. I'll ask Bram to add it to the official
release soon.
Index: buffer.c
===
--- buffer.c(revision 296)
+++ buffer.c(working copy)
@@ -171,14 +171,6 @@
/* Put the cursor on the first line. */
curwin-w_cursor.lnum = 1;
curwin-w_cursor.col = 0;
-#ifdef FEAT_AUTOCMD
-# ifdef FEAT_EVAL
- apply_autocmds_retval(EVENT_STDINREADPOST, NULL, NULL, FALSE,
- curbuf, retval);
-# else
- apply_autocmds(EVENT_STDINREADPOST, NULL, NULL, FALSE, curbuf);
-# endif
-#endif
}
}
@@ -207,6 +199,18 @@
unchanged(curbuf, FALSE);
save_file_ff(curbuf); /* keep this fileformat */
+#ifdef FEAT_AUTOCMD
+if (read_stdin)
+{
+# ifdef FEAT_EVAL
+apply_autocmds_retval(EVENT_STDINREADPOST, NULL, NULL, FALSE,
+ curbuf, retval);
+# else
+apply_autocmds(EVENT_STDINREADPOST, NULL, NULL, FALSE, curbuf);
+# endif
+}
+#endif
+
/* require ! to overwrite the file, because it wasn't read completely */
#ifdef FEAT_EVAL
if (aborting())
any insights appreciated,
mosh.
Regards,
Edward L. Fox
[bug report] C syntax broken with anonymous arrays
Hi all,
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.
Regards,
mc
Re: Selecting font size
Tim Johnson wrote: when I choose the font size, the font that is loaded is very different from what was installed when i started and is far from appealing. Is it a bitmap font? You can recognize a bitmap font from the sharp edges and pixellated appearance. Bitmap fonts come in only one size, so if that's the case you don't have much choice but to change font. Fortunately there are usually a wealth of fixed bitmap fonts of varying size and shape to choose from and you can find a ton more on the web, both free and commercial. If it's not a bitmap font, then it's a strange behaviour. Can you post screenshots of both fonts you get, before and after changing size? Maybe some of us will recognize them. (Don't send picture files directly to the list, it's considered rude. Rather, upload them to your web space, to http://imageshack.us/ or to another such service and post the link to the picture.) Tobia
search/paste question
Excuse the dumb question, but I can't find the answer in the docs... I see you can /text to search, and do * to find the next occurrence of the word under the cursor, but how do you paste text that you've just yank'd, into the search line after you press / without using the mouse? Thanks C
Re: search/paste question
I see you can /text to search, and do * to find the next occurrence of the word under the cursor, but how do you paste text that you've just yank'd, into the search line after you press / without using the mouse? You can use control+R followed by / to insert the text of the last search. :help i_CTRL-R :help c_CTRL-R (both are pretty much the same, as it works in both insert mode and command-line mode). This allows you access to any of vim's registers from insert mode or command-line mode--not just the search, but the file-name, the a-z registers, etc. :help registers Note that when you shift from using /text to using *, you'll get a subtle shift in your search pattern, as * tacks on \ and \ around your word to ensure a whole-word pattern. These extra characters are part of the search pattern and will thus be included/pasted when you use the above control+R/ method. You may want to use n/N for searching for the next/previous instance of your pattern instead. -tim
VimWiki - released finally
[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.
ex editor
I guess that this email group may not be the group I need. Is there a useful specialised ex group, in particular is there a community of ex (or vi/vim +occasional ex) users on MAC OSX. What I consider to be highly undesirable new features make ex (and perhaps vi/vim) extremely awkward to use on MACs and I would dearly like to be able to replace ex by a more comfortable older version eg not wiping image of recent changes on screen on exit. undo to undo just the last change by default - not all changes since start of session. etc Any suggestions what to do or where to go for help would be gratefully received C. Moncrieff
Re: VimWiki - released finally
Am Dienstag, den 05.06.2007, 13:38 +0200 schrieb misi e: all what is missing now (as long as I know) an interface to access this wiki from vim itself .) Easy with http://wikipediafs.sf.net :-) Cool would be a vim-plugin that detects [[WikiPage]] and produces a link that opens WikiPage.mw from the wikipediafs. Seb.
buffer local autocmd
hello, i want to setup some things only for php-source files. But i don't get the autocmd local to buffer. The setup was also applied to opened c++ files after the first php file. currently i have this inside my .vimrc (php.vim sets some tabulator options) autocmd FileType php source ~/.vim/php.vim i've tried something like: autocmd FileType buffer php source ~/.vim/php.vim without luck. Any hints how i can achieve this? -- Markus Schulz
Re: ex editor
I would dearly like to be able to replace ex by a more comfortable older version eg not wiping image of recent changes on screen on exit. I'm not 100% sure how to do this one. This is likely a terminal thing. Perhaps you can monkey with the settings as described in :help xterm-save-screen where it sounds like the NOTE 2 at the bottom of that section describes what you want: :set t_ti= t_te= I'm ambivalent about this option, as sometimes I want it, and sometimes I don't, and I don't think about it until I quit and find that it's not what I wanted. Some machines I use preserve the original screen (using the alternate screen for vim), and some don't. I've just learned to shrug that one off :) undo to undo just the last change by default - not all changes since start of session. Vim7's undo is mind-blowingly more powerful than any other software I've used (except maybe VCS software such as RCS/Subversion/Mercurial/etc). It shouldn't undo all changes since the start of the session (assuming by session, you mean since opening the file). Vim certainly allows you to return to the old-school way of doing things, as described at :help undo-two-ways and following section for how Vim treats undo blocks as well. etc Without more details on this etc, it's hard to point you in the right direction. However, this mailing list is a friendly place, so if you encounter more questions, feel free to ask them here and the list will try and help you out. I get accused of being the list's resident Ex junkie, so hopefully I can help. :) I'm likely one of the scant few who still wants Vim to support true open mode (:help :open). Not urgently, but there are times it would have been handy. Fortunately, I've got some older versions of vi that do support it for those scarse occasions I want it. -tim
Re: ex editor
C.Moncrieff wrote: I guess that this email group may not be the group I need. I'm afraid you're stuck, at least as far as official vim groups go. There's this one and vim-development, primarily. See http://vim.sourceforge.net/community.php for the complete list. What I consider to be highly undesirable new features make ex (and perhaps vi/vim) extremely awkward to use on MACs and I would dearly like to be able to replace ex by a more comfortable older version eg not wiping image of recent changes on screen on exit. set nors If that doesn't do the trick, try set t_ti= t_te= (but this will only help with console vim, not gvim) undo to undo just the last change by default - not all changes since start of session. See :help 'undolevels' etc Not clear about this one! Any suggestions what to do or where to go for help would be gratefully received Seems to me that this mailing list is best for what you're inquiring about. Regards, Chip Campbell
vim not opening directories
currently running vim 7.1.2 svn. In the past when invoking vim on a directory, it would open the directory and list the contents, my current build is not doing this. It returns the message src is a directory instead. Can someone point me to what I've mis-configured? Thanks, reid
Re: vim not opening directories
Op dinsdag 5 juni 2007, schreef Reid Thompson: currently running vim 7.1.2 svn. In the past when invoking vim on a directory, it would open the directory and list the contents, my current build is not doing this. It returns the message src is a directory instead. Can someone point me to what I've mis-configured? You are probably running vim in 'compatible' mode. Try :set nocompatible to disable this behaviour, or create a ~/.vimrc file (if this file even exists, vim defaults to nocompatible) And maybe start vim as 'vim' instead of 'vi' helps too. Regards, Peter Palm
Re: vim not opening directories
On Tue, 2007-06-05 at 16:32 +0200, Peter Palm wrote: Op dinsdag 5 juni 2007, schreef Reid Thompson: currently running vim 7.1.2 svn. In the past when invoking vim on a directory, it would open the directory and list the contents, my current build is not doing this. It returns the message src is a directory instead. Can someone point me to what I've mis-configured? You are probably running vim in 'compatible' mode. Try :set nocompatible to disable this behaviour, or create a ~/.vimrc file (if this file even exists, vim defaults to nocompatible) And maybe start vim as 'vim' instead of 'vi' helps too. Regards, Peter Palm I have a .vimrc. it has Use Vim settings, rather then Vi settings (much better!). This must be first, because it changes other options as a side effect. set nocompatible I've already tried invoking via [EMAIL PROTECTED]:~$ /usr/bin/vim src [EMAIL PROTECTED]:~$ /usr/bin/gvim src
Re: vim not opening directories
Op dinsdag 5 juni 2007, schreef Reid Thompson: I have a .vimrc. it has Use Vim settings, rather then Vi settings (much better!). This must be first, because it changes other options as a side effect. set nocompatible I've already tried invoking via [EMAIL PROTECTED]:~$ /usr/bin/vim src [EMAIL PROTECTED]:~$ /usr/bin/gvim src Well, the problem is vim can't find the netrwPlugin.vim file. What is the output of :echo $VIMRUNTIME ? Peter
Problem installing Vim 7.1 - DiffOrig command in vimrc_example.vim
Hi, I've installed Vim 7.1 on a Linux machine. When I run gvim, the following error message appears on my terminal: Error detected while processing /raid2/guardino/resources/vim/vim7.1/share/vim/vim71/vimrc_example.vim: line 85: E174: Command already exists: add ! to replace it (However gvim does start up). I don't get this message when I run vim. If I comment-out the DiffOrig command in vimrc_example.vim, this error disappears. I temporarily removed my plugins and .gvimrc config files to check whether this could have been the cause of the problem, but it wasn't. Could anyone help to resolve this issue? Has anyone else seen it? Many thanks! Cesare --- This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
Re: search/paste question
Tim Chase wrote: I see you can /text to search, and do * to find the next occurrence of the word under the cursor, but how do you paste text that you've just yank'd, into the search line after you press / without using the mouse? You can use control+R followed by / to insert the text of the last search. :help i_CTRL-R :help c_CTRL-R (both are pretty much the same, as it works in both insert mode and command-line mode). This allows you access to any of vim's registers from insert mode or command-line mode--not just the search, but the file-name, the a-z registers, etc. :help registers Note that when you shift from using /text to using *, you'll get a subtle shift in your search pattern, as * tacks on \ and \ around your word to ensure a whole-word pattern. These extra characters are part of the search pattern and will thus be included/pasted when you use the above control+R/ method. You may want to use n/N for searching for the next/previous instance of your pattern instead. -tim Similarly, after a yank, you can use Ctrl-R on the command-line to put the yanked value there (Ctrl-R for the default register, or Ctrl-R followed by the register name if you yanked into a named register). Best regards, Tony. -- Q: Do you know what the death rate around here is? A: One per person.
Re: vim not opening directories
Reid Thompson wrote: I have a .vimrc. it has Use Vim settings, rather then Vi settings (much better!). This must be first, because it changes other options as a side effect. set nocompatible I've already tried invoking via [EMAIL PROTECTED]:~$ /usr/bin/vim src [EMAIL PROTECTED]:~$ /usr/bin/gvim src * make sure that your account has read-write access (if somehow its owned by root...) * In addition to set nocompatible, you should also have: (in your .vimrc) if version = 600 filetype plugin indent on endif * Check that you in fact have a .vimrc, not a .gvimrc, for this. If you use .gvimrc instead, well, it loads after the plugins would, and so the filetype plugin on won't be effecacious. * Fire up vim; check on $VIMRUNTIME -- make sure that plugin/netrw*.vim and autoload/netrw*.vim are both there and readable by you as a user. Regards, Chip Campbell
Re: buffer local autocmd
On 2007-06-05, Markus Schulz [EMAIL PROTECTED] wrote: hello, i want to setup some things only for php-source files. But i don't get the autocmd local to buffer. The setup was also applied to opened c++ files after the first php file. currently i have this inside my .vimrc (php.vim sets some tabulator options) autocmd FileType php source ~/.vim/php.vim i've tried something like: autocmd FileType buffer php source ~/.vim/php.vim without luck. Any hints how i can achieve this? The problem may be in your ~/.vim/php.vim file. Make sure any options are set there using setlocal, not just set. set applies most options globally while setlocal applies most options to only the current buffer. See :help setlocal To make mappings local to the current buffer, see :help map-buffer HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: VimWiki - released finally
On Tue, June 5, 2007 6:51 am, Sebastian Menge wrote: Am Dienstag, den 05.06.2007, 13:38 +0200 schrieb misi e: all what is missing now (as long as I know) an interface to access this wiki from vim itself .) Easy with http://wikipediafs.sf.net :-) Also, don't forget about the ItsAllText plugin for Firefox. Tom Purl
Re: VimWiki - released finally
On Tue, June 5, 2007 5:41 am, 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. Wow! This really looks excellent Sebastian. Also, it look very robust and complete. I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Thanks again! Tom Purl
Re: vim not opening directories
On Tue, 2007-06-05 at 16:50 +0200, Peter Palm wrote: Op dinsdag 5 juni 2007, schreef Reid Thompson: I have a .vimrc. it has Use Vim settings, rather then Vi settings (much better!). This must be first, because it changes other options as a side effect. set nocompatible I've already tried invoking via [EMAIL PROTECTED]:~$ /usr/bin/vim src [EMAIL PROTECTED]:~$ /usr/bin/gvim src Well, the problem is vim can't find the netrwPlugin.vim file. What is the output of :echo $VIMRUNTIME ? Peter /usr/share/vim/vim71
Re: VimWiki - released finally
How do you update the categories? I can't seem to find that text when I edit the full page. Thanks! Tom Purl On Tue, June 5, 2007 6:51 am, Sebastian Menge wrote: Am Dienstag, den 05.06.2007, 13:38 +0200 schrieb misi e: all what is missing now (as long as I know) an interface to access this wiki from vim itself .) Easy with http://wikipediafs.sf.net :-) Cool would be a vim-plugin that detects [[WikiPage]] and produces a link that opens WikiPage.mw from the wikipediafs. Seb.
Re: vim not opening directories
On Tue, 2007-06-05 at 11:14 -0400, Charles E Campbell Jr wrote: Reid Thompson wrote: I have a .vimrc. it has Use Vim settings, rather then Vi settings (much better!). This must be first, because it changes other options as a side effect. set nocompatible I've already tried invoking via [EMAIL PROTECTED]:~$ /usr/bin/vim src [EMAIL PROTECTED]:~$ /usr/bin/gvim src * make sure that your account has read-write access (if somehow its owned by root...) * In addition to set nocompatible, you should also have: (in your .vimrc) if version = 600 filetype plugin indent on endif I have Only do this part when compiled with support for autocommands. if has(autocmd) Enable file type detection. Use the default filetype settings, so that mail gets 'tw' set to 72, 'cindent' is on in C files, etc. Also load indent files, to automatically do language-dependent indenting. filetype plugin indent on * Check that you in fact have a .vimrc, not a .gvimrc, for this. If you use .gvimrc instead, I have a .vimrc and a .gvimrc well, it loads after the plugins would, and so the filetype plugin on won't be effecacious. * Fire up vim; check on $VIMRUNTIME -- make sure that plugin/netrw*.vim and autoload/netrw*.vim are both there and readable by you as a user. [EMAIL PROTECTED]:~$ ls -rlt /usr/share/vim/vim71/plugin/ total 52 -rw-r--r-- 1 root root 2095 2007-06-05 10:09 zipPlugin.vim -rw-r--r-- 1 root root 1664 2007-06-05 10:09 vimballPlugin.vim -rw-r--r-- 1 root root 705 2007-06-05 10:09 tohtml.vim -rw-r--r-- 1 root root 1878 2007-06-05 10:09 tarPlugin.vim -rw-r--r-- 1 root root 499 2007-06-05 10:09 spellfile.vim -rw-r--r-- 1 root root 1362 2007-06-05 10:09 rrhelper.vim -rw-r--r-- 1 root root 889 2007-06-05 10:09 README.txt -rw-r--r-- 1 root root 8934 2007-06-05 10:09 netrwPlugin.vim -rw-r--r-- 1 root root 3549 2007-06-05 10:09 matchparen.vim -rw-r--r-- 1 root root 1451 2007-06-05 10:09 gzip.vim -rw-r--r-- 1 root root 1346 2007-06-05 10:09 getscriptPlugin.vim [EMAIL PROTECTED]:~$ ls -rlt /usr/share/vim/vim71/autoload/ total 844 drwxr-xr-x 2 root root 4096 2007-05-30 14:46 xml -rw-r--r-- 1 root root 11450 2007-06-05 10:09 zip.vim -rw-r--r-- 1 root root 14857 2007-06-05 10:09 xmlcomplete.vim -rw-r--r-- 1 root root 18517 2007-06-05 10:09 vimball.vim -rw-r--r-- 1 root root 12964 2007-06-05 10:09 tar.vim -rw-r--r-- 1 root root 13849 2007-06-05 10:09 syntaxcomplete.vim -rw-r--r-- 1 root root 25495 2007-06-05 10:09 sqlcomplete.vim -rw-r--r-- 1 root root 4956 2007-06-05 10:09 spellfile.vim -rw-r--r-- 1 root root 23457 2007-06-05 10:09 rubycomplete.vim -rw-r--r-- 1 root root773 2007-06-05 10:09 README.txt -rw-r--r-- 1 root root 20981 2007-06-05 10:09 pythoncomplete.vim -rw-r--r-- 1 root root 293714 2007-06-05 10:09 phpcomplete.vim -rw-r--r-- 1 root root 1232 2007-06-05 10:09 paste.vim -rw-r--r-- 1 root root 203836 2007-06-05 10:09 netrw.vim -rw-r--r-- 1 root root 7561 2007-06-05 10:09 netrwSettings.vim -rw-r--r-- 1 root root 10226 2007-06-05 10:09 netrwFileHandlers.vim -rw-r--r-- 1 root root 27028 2007-06-05 10:09 javascriptcomplete.vim -rw-r--r-- 1 root root 24253 2007-06-05 10:09 htmlcomplete.vim -rw-r--r-- 1 root root 5740 2007-06-05 10:09 gzip.vim -rw-r--r-- 1 root root 4972 2007-06-05 10:09 gnat.vim -rw-r--r-- 1 root root 19107 2007-06-05 10:09 getscript.vim -rw-r--r-- 1 root root 2924 2007-06-05 10:09 decada.vim -rw-r--r-- 1 root root 15922 2007-06-05 10:09 csscomplete.vim -rw-r--r-- 1 root root 16307 2007-06-05 10:09 ccomplete.vim -rw-r--r-- 1 root root 21511 2007-06-05 10:09 ada.vim -rw-r--r-- 1 root root 3641 2007-06-05 10:09 adacomplete.vim Regards, Chip Campbell build options... [EMAIL PROTECTED]:~$ vim --version VIM - Vi IMproved 7.1 (2007 May 12, compiled Jun 5 2007 10:08:55) Included patches: 1-2 Compiled by [EMAIL PROTECTED] Normal version with GTK2-GNOME GUI. Features included (+) or not (-): -arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra -perl +postscript +printer -profile -python +quickfix +reltime -rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
Re: vim not opening directories
On Tue, 2007-06-05 at 11:14 -0400, Charles E Campbell Jr wrote: * make sure that your account has read-write access (if somehow its owned by root...) drwxr-xr-x 17 rthompso staff4096 2007-06-01 11:42 src
Re: VimWiki - released finally
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 12:00 PM, Tom Purl wrote: On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] 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. Wow! This really looks excellent Sebastian. Also, it look very robust and complete. I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Indeed - looks good! Can someone point out how I can get an RSS feed of the recent changes? The page is here http://vim.wikia.com/wiki/Special:Recentchanges Perhaps it's a feature we need to enable? I see some other wikia sites seem to append feed=rss to the url, but that doesn't work for the vim wiki... Brian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) Comment: Verify this email or encrypt your email for free - see gnupg.org iD8DBQFGZZB6GnOmb9xIQHQRAiKaAKDdpaAT2+ABJxXbqTUMNz+B4m6Q7ACfX8sj 2xm2SBX9KwsY+Zw0y8T+D1w= =5Eug -END PGP SIGNATURE-
Re: VimWiki - released finally
Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] BTW, nice work! -- Luc Hermitte http://hermitte.free.fr/vim/
vim apparently ignoring -c nomodeline cmdline option
When opening a file that ends with # vim:fdm=marker: vim keeps doing the folding, even if I call it with -c nomodeline (I also tried -c modelines=0). Is it vim fault's, or (more likely) mine? -- Rodolfo Borges
Re: ex editor
Tim Chase wrote: I'm likely one of the scant few who still wants Vim to support true open mode (:help :open). Not urgently, but there are times it would have been handy. Fortunately, I've got some older versions of vi that do support it for those scarse occasions I want it. Can you please expand on what :open does and what it's useful for? :help :open tells me nothing at all :-( Tobia
Re: VimWiki - released finally
On 6/5/07, Sebastian Menge [EMAIL PROTECTED] 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. I am EXCITED! -- -fREW
Re: vim apparently ignoring -c nomodeline cmdline option
On 2007-06-05, Rodolfo Borges [EMAIL PROTECTED] wrote:
When opening a file that ends with
# vim:fdm=marker:
vim keeps doing the folding, even if I call it with -c nomodeline (I
also tried -c modelines=0).
Is it vim fault's, or (more likely) mine?
Note that :help -c says:
-c {command}{command} will be executed after the first file
has been read (and after autocommands and
modelines for that file have been processed).
Try using --cmd instead of -c. See
:help --cmd
Regards,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Mobile Broadband Division
| Spokane, Washington, USA
history in new instance
Hi all- I use Vim 7 both on Windows and a Mac (in gui mode) and Linux (console mode) and I've noticed that all versions I have, except the Mac one, keeps a command history from previous instances. That is, if I type : and then up-arrow, I can see commands that I've previously entered even though I just started Vim. The Mac does keep a command line history of the current instance, but loses it when Vim is shut down. Is there a setting I can check to see how to set this? Thanks, Ron
Re: ex editor
On 6/5/07, Tim Chase [EMAIL PROTECTED] wrote: I would dearly like to be able to replace ex by a more comfortable older version eg not wiping image of recent changes on screen on exit. I'm not 100% sure how to do this one. This is likely a terminal thing. Perhaps you can monkey with the settings as described in :help xterm-save-screen where it sounds like the NOTE 2 at the bottom of that section describes what you want: :set t_ti= t_te= I'm ambivalent about this option, as sometimes I want it, and sometimes I don't, and I don't think about it until I quit and find that it's not what I wanted. Some machines I use preserve the original screen (using the alternate screen for vim), and some don't. I've just learned to shrug that one off :) undo to undo just the last change by default - not all changes since start of session. Vim7's undo is mind-blowingly more powerful than any other software I've used (except maybe VCS software such as RCS/Subversion/Mercurial/etc). It shouldn't undo all changes since the start of the session (assuming by session, you mean since opening the file). Vim certainly allows you to return to the old-school way of doing things, as described at :help undo-two-ways and following section for how Vim treats undo blocks as well. etc Without more details on this etc, it's hard to point you in the right direction. However, this mailing list is a friendly place, so if you encounter more questions, feel free to ask them here and the list will try and help you out. I get accused of being the list's resident Ex junkie, so hopefully I can help. :) I'm likely one of the scant few who still wants Vim to support true open mode (:help :open). Not urgently, but there are times it would have been handy. Fortunately, I've got some older versions of vi that do support it for those scarse occasions I want it. -tim Is :help undo where we can get information on Vim7's undo? I remember reading about how it was all awesome and stuff, but I haven't gotten a chance to actually try to use it yet. -- -fREW
Re: ex editor
Can you please expand on what :open does and what it's useful for? :help :open tells me nothing at all :-( Open-mode is a quasi-Ex and quasi-Vi mode, or could also be described as Vi mode on a glass/printing TTY. It doesn't redraw the screen. I found it useful when I had to use a printer as my output device: it offered the power of vi, but with the terminal-indifference of ed/ex. It's also helpful for doing what you describe, of having some of your shell session (prior to vi/ex invocation) available on the screen at the same time, yet still have the ability to navigate like in Vi. I believe both the nvi and stevie clones both implement open mode. -tim
Re: ex editor
Is :help undo where we can get information on Vim7's undo? I remember reading about how it was all awesome and stuff, but I haven't gotten a chance to actually try to use it yet. It's all contained in :help undo.txt The powerful additions to Vim7 are found at :help undo-branches I don't yet have g+ and g- hardwired into my fingers yet, but I do remember :earlier and :later for navigating forward and backwards in the undo tree. I don't use it often, but when I do, it's just what I need. And when I need this feature in other apps that don't provide it, I find myself wondering why can't $PROGRAM be more like Vim?! :) -tim
Re: VimWiki - released finally
On Tue, June 5, 2007 12:36 pm, [EMAIL PROTECTED] wrote: Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] But I am editing a tip, and I don't see any reference to a [[Category:Foo]] link. Thanks! Tom Purl
Re: VimWiki - released finally
On Tue, June 5, 2007 11:34 am, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 12:00 PM, Tom Purl wrote: On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] 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. Wow! This really looks excellent Sebastian. Also, it look very robust and complete. I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Indeed - looks good! Can someone point out how I can get an RSS feed of the recent changes? The page is here http://vim.wikia.com/wiki/Special:Recentchanges Perhaps it's a feature we need to enable? I see some other wikia sites seem to append feed=rss to the url, but that doesn't work for the vim wiki... Brian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) Comment: Verify this email or encrypt your email for free - see gnupg.org iD8DBQFGZZB6GnOmb9xIQHQRAiKaAKDdpaAT2+ABJxXbqTUMNz+B4m6Q7ACfX8sj 2xm2SBX9KwsY+Zw0y8T+D1w= =5Eug -END PGP SIGNATURE- The recent changes page has links for both rss and atom feeds. HTH! Tom Purl
Re: VimWiki - released finally
Hi, Finally I have imported all the vim tips from http://vim.org/tips to http://vim.wikia.com if you must have ads, would it be possible to go with text-only ads? Additionally, the Digg this story button at the bottom is stupid ;-) Just my destructive 2 cents, Nico
Re: VimWiki - released finally
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 1:59 PM, Tom Purl wrote: On Tue, June 5, 2007 11:34 am, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 12:00 PM, Tom Purl wrote: On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] Finally I have imported all the vim tips from http://vim.org/ tips to http://vim.wikia.com I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Can someone point out how I can get an RSS feed of the recent changes? The page is here http://vim.wikia.com/wiki/Special:Recentchanges The recent changes page has links for both rss and atom feeds. Oh - I guess it's in the headers only - I was looking for a clickable link rather than just the indicator in the url bar. If there's a clickable link supposed to be there - I'm not seeing it and a quick /atom/ of the source only shows the link in the headers. Thanks - Got what I needed. Brian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) Comment: Verify this email or encrypt your email for free - see gnupg.org iD8DBQFGZafzGnOmb9xIQHQRAnG8AJkBsmVDZebQ6Nt8i1+BS87h0KP0/wCgm39K o5hBYBes2edUet51OzftzA8= =Y0te -END PGP SIGNATURE-
Re: VimWiki - released finally
Selon Tom Purl [EMAIL PROTECTED]: On Tue, June 5, 2007 12:36 pm, [EMAIL PROTECTED] wrote: Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] But I am editing a tip, and I don't see any reference to a [[Category:Foo]] link. IIRC, the category won't appear in the general categories list until it has a page associated (edit the description of the category). However, if you have several pages for a given undocumented category (i.e. having [[Category:Foo]]) and then open the default page for the category (i.e. click on the red link) you will see all the related pages of that category. From my very little experience regarding the organisation of a wiki from scratch, I'll say that everytime we put a page into a new category, we have to define right away the page of that new category. Otherwise, another similar, but different) category may emerge. -- Luc Hermitte http://hermitte.free.fr/vim/
Re: VimWiki - released finally
On Tue, June 5, 2007 1:14 pm, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 1:59 PM, Tom Purl wrote: On Tue, June 5, 2007 11:34 am, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 12:00 PM, Tom Purl wrote: On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] Finally I have imported all the vim tips from http://vim.org/ tips to http://vim.wikia.com I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Can someone point out how I can get an RSS feed of the recent changes? The page is here http://vim.wikia.com/wiki/Special:Recentchanges The recent changes page has links for both rss and atom feeds. Oh - I guess it's in the headers only - I was looking for a clickable link rather than just the indicator in the url bar. If there's a clickable link supposed to be there - I'm not seeing it and a quick /atom/ of the source only shows the link in the headers. Here's what I'm seeing: URL: http://vim.wikia.com/wiki/Special:Recentchanges Using both IE and Firefox, I'm am seeing both RSS and Atom links in the toolbox box. This is true whether I am logged in or not. Here's exactly what I see in the toolbox box: Toolbox * RSS Atom * Upload file * Special pages What are you seeing? Thanks, Tom Purl
Re: buffer local autocmd
Markus Schulz wrote: hello, i want to setup some things only for php-source files. But i don't get the autocmd local to buffer. The setup was also applied to opened c++ files after the first php file. currently i have this inside my .vimrc (php.vim sets some tabulator options) autocmd FileType php source ~/.vim/php.vim i've tried something like: autocmd FileType buffer php source ~/.vim/php.vim without luck. Any hints how i can achieve this? Instead of ~/.vim/php.vim, name it ~/.vim/after/ftplugin/php.vim and you won't even need an autocommand. (Create the directories if they don't exist). Make sure the script contains only local commands such as :map buffer and :setlocal. Best regards, Tony. -- Lewis's Law of Travel: The first piece of luggage out of the chute doesn't belong to anyone, ever.
Multiple syntax behaviour inside a file
Hi all,
I would like to know if it's possible to do this crazy thing with vim :
I have a bunch of xml files wich contains template of many different
type of text : html, css, ruby, javascript, ...
Here's what it looks like :
?xml version=1.0?
templates
t name=test_css type=css
body {
background: white;
}
/t
t name=test_js type=javascript
function test(s) {
console.log(s);
}
/t
t name=test_html type=html
html
body
Test
/body
/html
/t
/templates
I guess the answer is no but I would like to know if it's possible
to make vim use different syntax highlighting and different folding
rules for each type of code ?
--
Fabien Meghazi
Website: http://www.amigrave.com
Email: [EMAIL PROTECTED]
IM: [EMAIL PROTECTED]
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: [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: vim apparently ignoring -c nomodeline cmdline option
Gary Johnson wrote:
On 2007-06-05, Rodolfo Borges [EMAIL PROTECTED] wrote:
When opening a file that ends with
# vim:fdm=marker:
vim keeps doing the folding, even if I call it with -c nomodeline (I
also tried -c modelines=0).
Is it vim fault's, or (more likely) mine?
Note that :help -c says:
-c {command}{command} will be executed after the first file
has been read (and after autocommands and
modelines for that file have been processed).
Try using --cmd instead of -c. See
:help --cmd
Regards,
Gary
Also, :nomodeline is not a valid Vim command. Use
vim --cmd set nomodeline
instead.
Best regards,
Tony.
--
You are old, father William, the young man said,
And your hair has become very white;
And yet you incessantly stand on your head --
Do you think, at your age, it is right?
In my youth, father William replied to his son,
I feared it might injure the brain;
But, now that I'm perfectly sure I have none,
Why, I do it again and again.
-- Lewis Carrol
Re: history in new instance
Ron Olson wrote: Hi all- I use Vim 7 both on Windows and a Mac (in gui mode) and Linux (console mode) and I've noticed that all versions I have, except the Mac one, keeps a command history from previous instances. That is, if I type : and then up-arrow, I can see commands that I've previously entered even though I just started Vim. The Mac does keep a command line history of the current instance, but loses it when Vim is shut down. Is there a setting I can check to see how to set this? Thanks, Ron :help 'history' :help 'viminfo' :help viminfo-file Best regards, Tony. -- FIRST HEAD: Oh! quick! get the sword out I want to cut his head off. THIRD HEAD: Oh, cut your own head off. SECOND HEAD: Yes - do us all a favour. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
Re: VimWiki - released finally
On Tue, June 5, 2007 2:29 pm, [EMAIL PROTECTED] wrote: Selon Tom Purl [EMAIL PROTECTED]: On Tue, June 5, 2007 12:36 pm, [EMAIL PROTECTED] wrote: Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] But I am editing a tip, and I don't see any reference to a [[Category:Foo]] link. IIRC, the category won't appear in the general categories list until it has a page associated (edit the description of the category). However, if you have several pages for a given undocumented category (i.e. having [[Category:Foo]]) and then open the default page for the category (i.e. click on the red link) you will see all the related pages of that category. From my very little experience regarding the organisation of a wiki from scratch, I'll say that everytime we put a page into a new category, we have to define right away the page of that new category. Otherwise, another similar, but different) category may emerge. I don't think that I'm describing my problem very clearly. I'm trying to edit the following page: * http://vim.wikia.com/wiki/Indenting_%22throws%22_in_java When I click on the edit link, I should see something similar to this: some text some more text [[Category:Foo]] Instead, all I see is this: some text some more text One would assume that if the raw version of the page didn't include a [[Category:Foo]] link, then the published version also wouldn't include any category information. The weird thing is that the published version of this particular page includes two categories; Review and VimTip. So what I don't understand is, why can't I change these categories? I've been editing Mediawiki pages for 4 years, and I've never seen anything like this. Thanks in advance for any help! Tom Purl
Re: VimWiki - released finally
Tom Purl wrote: On Tue, June 5, 2007 2:29 pm, [EMAIL PROTECTED] wrote: Selon Tom Purl [EMAIL PROTECTED]: On Tue, June 5, 2007 12:36 pm, [EMAIL PROTECTED] wrote: Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] But I am editing a tip, and I don't see any reference to a [[Category:Foo]] link. IIRC, the category won't appear in the general categories list until it has a page associated (edit the description of the category). However, if you have several pages for a given undocumented category (i.e. having [[Category:Foo]]) and then open the default page for the category (i.e. click on the red link) you will see all the related pages of that category. From my very little experience regarding the organisation of a wiki from scratch, I'll say that everytime we put a page into a new category, we have to define right away the page of that new category. Otherwise, another similar, but different) category may emerge. I don't think that I'm describing my problem very clearly. I'm trying to edit the following page: * http://vim.wikia.com/wiki/Indenting_%22throws%22_in_java When I click on the edit link, I should see something similar to this: some text some more text [[Category:Foo]] Instead, all I see is this: some text some more text One would assume that if the raw version of the page didn't include a [[Category:Foo]] link, then the published version also wouldn't include any category information. The weird thing is that the published version of this particular page includes two categories; Review and VimTip. So what I don't understand is, why can't I change these categories? I've been editing Mediawiki pages for 4 years, and I've never seen anything like this. Thanks in advance for any help! Tom Purl If you click [edit] somewhere in the page, you edit the corresponding section. To edit the whole page, click Edit this page at bottom. Best regards, Tony. -- Never commit yourself! Let someone else commit you.
Re: OT: Vi in a browser... Re: VimWiki
Just stumbled across this link: http://gpl.internetconnection.net/vi/ for a basic implementation of Vi, authored in JavaScript. With no desire to rekindle the debate, I just thought they might make a good match. In fact I could also use it for my wiki sites... if available. Just a quick thought. Regards, Ben K. Developer http://benix.tamu.edu
RE: VimWiki - released finally
Sebastian, Why not utilize the talk: pages for the comments (see discussion tab at top of each wiki page)? Just curious. -Robert Lets avoid using the vim-announce mailing list for a discussing of vim wiki and stick to vim-dev. David
RE: VimWiki - released finally
-Original Message- From: Tom Purl [mailto:[EMAIL PROTECTED] [...] So what I don't understand is, why can't I change these categories? I've been editing Mediawiki pages for 4 years, and I've never seen anything like this. This isn't a figment of Tom's mind. I just poked around the wiki. I'm not seeing a way to change the category of an existing article. When you create a new article, you can assign categories, but I'm not seeing a way to change the category on an existing article even if you edit the entire article by clicking on the edit link at the top of the article. If there is a way to change the category of an existing article, I'm missing it. Mike
Re: VimWiki - released finally
Sebastian, Why not utilize the talk: pages for the comments (see discussion tab at top of each wiki page)? Just curious. -Robert 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.
Re: VimWiki - released finally
* On Tue, Jun 05, 2007 at 02:54:21PM -0600, Mike Hansen [EMAIL PROTECTED]
wrote:
From: Tom Purl [mailto:[EMAIL PROTECTED]
[...]
So what I don't understand is, why can't I change these categories?
I've been editing Mediawiki pages for 4 years, and I've never seen
anything like this.
This isn't a figment of Tom's mind.
I just poked around the wiki. I'm not seeing a way to change the
category of an existing article. When you create a new article, you
can assign categories, but I'm not seeing a way to change the category
on an existing article even if you edit the entire article by clicking
on the edit link at the top of the article.
If there is a way to change the category of an existing article, I'm
missing it.
I did it twice.
- http://vim.wikia.com/wiki/Running_the_win32-version_of_Vim_from_cygwin
I've added the [Category:Cygwin], and removed Review.
[Category:Review] is a consequence on the template [1] {{Review}} [2]
The [category:VimTips] is likely a consequence of the template {{Tip}}
[3] used at the start of every vimtip.
BTW, it can be interresting to add a {{Vimscript}} template. In the
long term, it could check the existence of a wiki-page dedicated to the
script and point to that page if found, or to vim site otherwise.
(NB: I don't even know if this is possible, nor ergonomic)
In the short term, it is good way to provide links to the vimscripts of
vim.org.
[1] http://vim.wikia.com/index.php?title=Special%3AAllpagesfrom=namespace=10
[2] http://vim.wikia.com/wiki/Template:Review
[3] http://vim.wikia.com/wiki/Template:Tip
--
Luc Hermitte
http://hermitte.free.fr/vim/
Re: Multiple syntax behaviour inside a file
On 6/5/07, Fabien Meghazi [EMAIL PROTECTED] wrote:
Hi all,
I would like to know if it's possible to do this crazy thing with vim :
I have a bunch of xml files wich contains template of many different
type of text : html, css, ruby, javascript, ...
Here's what it looks like :
?xml version=1.0?
templates
t name=test_css type=css
body {
background: white;
}
/t
t name=test_js type=javascript
function test(s) {
console.log(s);
}
/t
t name=test_html type=html
html
body
Test
/body
/html
/t
/templates
I guess the answer is no but I would like to know if it's possible
to make vim use different syntax highlighting and different folding
rules for each type of code ?
I've written a vim-help syntax file that does this for code examples,
e.g. perl, vim script, sh. Look at the syn-include section of the
syntax.txt helpfile.
--
Ian Tegebo
Re: Selecting font size
On Monday 04 June 2007, Tim Johnson wrote: .. I appreciate some tips as how to resolve this. Just want to thank everybody for the help. all is good now. cheers tim
Re: vim not opening directories
I don't know if this is the same issue but I had the same behavior after I accidentally installed the latest version of the netrw plugin from Dr. Chip's site to my ~/.vimfies without removing the version in /usr/share/vim/vmi71 first. Once I removed the version in /usr/share it started displaying directory contents again. YMMV, SETH On 6/5/07, Reid Thompson [EMAIL PROTECTED] wrote: currently running vim 7.1.2 svn. In the past when invoking vim on a directory, it would open the directory and list the contents, my current build is not doing this. It returns the message src is a directory instead. Can someone point me to what I've mis-configured? Thanks, reid
Syntax Highlighting works for one file only
Hello: I'm using vim compiled as 'vim.full' for kubuntu 7.04 amd-64. I can load one file and one file only - it's a python file - where syntax highlighting comes on automatically. Any subsequent files with a .py extension are loaded with only strings highlighted. :setf python enables full highlighting I'm baffled. I've rebuilt .vimrc and .gvimrc one line at a time and I see nothing that could be causing this. Any and all help would be appreciated. Thanks Tim
Re: Syntax Highlighting works for one file only
Tim Johnson wrote: Hello: I'm using vim compiled as 'vim.full' for kubuntu 7.04 amd-64. I can load one file and one file only - it's a python file - where syntax highlighting comes on automatically. Any subsequent files with a .py extension are loaded with only strings highlighted. :setf python enables full highlighting I'm baffled. I've rebuilt .vimrc and .gvimrc one line at a time and I see nothing that could be causing this. Any and all help would be appreciated. Thanks Tim In your second (badly highlighted) *.py file, what does Vim answer to :verbose set filetype? ? Best regards, Tony. -- VIRGO (Aug 23 - Sept 22) You are the logical type and hate disorder. This nitpicking is sickening to your friends. You are cold and unemotional and sometimes fall asleep while making love. Virgos make good bus drivers.
Re: Syntax Highlighting works for one file only
On Tuesday 05 June 2007, A.J.Mechelynck wrote: In your second (badly highlighted) *.py file, what does Vim answer to :verbose set filetype? filetype=conf Last set from /usr/share/vim/vim70/filetype.vim Hmm! Thanks Tony Tim
Re: Syntax Highlighting works for one file only
Tim Johnson wrote: On Tuesday 05 June 2007, A.J.Mechelynck wrote: In your second (badly highlighted) *.py file, what does Vim answer to :verbose set filetype? filetype=conf Last set from /usr/share/vim/vim70/filetype.vim Hmm! Thanks Tony Tim Hm. In the Vim 7.1 filetype.vim, filetype conf is set for any file, one of the first 5 lines of which starts with #, but only if everything else fails (and *.py is detected as type python before that...) I wonder what causes your first *.py, but not the others, to be detected as python. Best regards, Tony. -- I have the world's largest collection of seashells. I keep it scattered around the beaches of the world ... Perhaps you've seen it. -- Steven Wright
'fileencodings': Why use ucs-2le for cp936 file?
Hello, Recently I want to do some research about 'fileencodings', what I want is to recognize utf-8, ucs-2le, euc-cn and cp936 encodings. So I set the 'fencs' in my .vimrc: set fencs=ucs-bom,utf-8,ucs-2le,euc-cn,cp936 However, cp936 files are always recognized as ucs-2le and I got everything in a mess... If I remove the ucs-2le: set fencs=ucs-bom,utf-8,euc-cn,cp936 That would work, but ucs-2le files cannot get recognized at all. It is said that unicode files all have BOM, and obviously cp936 files do not have BOM, so I wonder why cp936 files get recognized as ucs-2le file without any BOM. I tried to change my 'encoding' setting, but it doesn't affect anything. Any hints? -- Sincerely, Pan, Shi Zhu. ext: 2606
Re: 'fileencodings': Why use ucs-2le for cp936 file?
[EMAIL PROTECTED] wrote: Hello, Recently I want to do some research about 'fileencodings', what I want is to recognize utf-8, ucs-2le, euc-cn and cp936 encodings. So I set the 'fencs' in my .vimrc: set fencs=ucs-bom,utf-8,ucs-2le,euc-cn,cp936 However, cp936 files are always recognized as ucs-2le and I got everything in a mess... If I remove the ucs-2le: set fencs=ucs-bom,utf-8,euc-cn,cp936 That would work, but ucs-2le files cannot get recognized at all. It is said that unicode files all have BOM, and obviously cp936 files do not have BOM, so I wonder why cp936 files get recognized as ucs-2le file without any BOM. probably because the cp936 files you tested do not contain any sequence of bytes that would be illegal under UCS-2le. I tried to change my 'encoding' setting, but it doesn't affect anything. Any hints? -- Sincerely, Pan, Shi Zhu. ext: 2606 Unicode files may or may not have a BOM, depending on who (or which program) created them and where they come from. If you remove ucs-2le from your 'fileencodings', but leave ucs-bom at the start, any Unicode files having a BOM will still be recognised and the proper encoding set. Best regards, Tony. -- Cahn's Axiom: When all else fails, read the instructions.
Re: 'fileencodings': Why use ucs-2le for cp936 file?
A.J.Mechelynck [EMAIL PROTECTED] 写于 2007-06-06 09:51:51: Unicode files may or may not have a BOM, depending on who (or which program) created them and where they come from. If you remove ucs-2le from your 'fileencodings', but leave ucs-bom at the start, any Unicode fileshaving a BOM will still be recognised and the proper encoding set. Best regards, Tony. It seems that ucs-2le files with BOM will get recongized now. But I've got some other question: 1. will vim write BOM when writing to unicode files? or is there any options for that? 2. what is the correct way of converting a file encoding inside vim? I opened a file with cp936 encoding, then :set fenc=ucs-2le, then :w newfile.txt, close the vim and open the newfile.txt with a new vim, then I found everything in a mess. (gvim 7.1 winxp) -- Sincerely, Pan, Shi Zhu. ext: 2606
Re: Syntax Highlighting works for one file only
On Tuesday 05 June 2007, you wrote: Hm. In the Vim 7.1 filetype.vim, filetype conf is set for any file, one of the first 5 lines of which starts with #, but only if everything else fails (and *.py is detected as type python before that...) I wonder what causes your first *.py, but not the others, to be detected as python. The first file, the one that got good syntax highlighting, did not have a she-bang line, others did not. I'm having a similar problem: I also program with a language called rebol. filetype.vim does not properly understand how rebol works. Here is the original code: Rexx, Rebol or R au BufNewFile,BufRead *.r,*.R call s:FTr() fun! s:FTr() if getline(1) =~ '^REBOL' setf rebol else let n = 1 let max = line($) if max 50 let max = 50 endif while n max R has # comments if getline(n) =~ '^\s*#' setf r break endif Rexx has /* comments */ if getline(n) =~ '^\s*/\*' setf rexx break endif let n = n + 1 endwhile if n = max setf rexx endif endif endfun # it is incomplete because a rebol file may 1)begin with the regex REBOL in either lower or upper or mixed case 2)begin with a shebang line containing rebol 3)furthermore, in some cases neither condition would be present. Thus, I found that any rebol file *without* the shebang line highlighted properly, but with the shebang line, needed :setf rebol Now here is what is weird: I changed the code in filetype to the following simpler approach: au BufNewFile,BufRead *.r,*.R,*.reb setf rebol removing function FTr entirely but the same symptoms remain. I would suspect that there is a side effect from some other file that is sourced. When I get more time, I will remove files from ~/.vim/plugin , ... autoload etc and see what happens as I add them back in. In the meantime, this highly annoying but not a crisis, after all setf does the job. thanks for looking into this, I'd welcome other comments all the same. regards tim
Re: Syntax Highlighting works for one file only
On Tuesday 05 June 2007, A.J.Mechelynck wrote: Tim Johnson wrote: Hello: I'm using vim compiled as 'vim.full' for kubuntu 7.04 amd-64. I can load one file and one file only - it's a python file - where syntax highlighting comes on automatically. Any subsequent files with a .py extension are loaded with only strings highlighted. :setf python enables full highlighting I'm baffled. I've rebuilt .vimrc and .gvimrc one line at a time and I see nothing that could be causing this. Just for a quick test, I changed the name of the .vim directory. The symptoms that I described vanished. It would seem to be in the plugin or autoload directories. I've got some *old* vim scripts in there tim
Re: 'fileencodings': Why use ucs-2le for cp936 file?
[EMAIL PROTECTED] wrote: A.J.Mechelynck [EMAIL PROTECTED] 写于 2007-06-06 09:51:51: Unicode files may or may not have a BOM, depending on who (or which program) created them and where they come from. If you remove ucs-2le from your 'fileencodings', but leave ucs-bom at the start, any Unicode fileshaving a BOM will still be recognised and the proper encoding set. Best regards, Tony. It seems that ucs-2le files with BOM will get recongized now. But I've got some other question: 1. will vim write BOM when writing to unicode files? or is there any options for that? :setlocal bomb When opening a Unicode file, Vim will set or clear the buffer-local 'bomb' option according to the presence or absence of a BOM. That option is irrelevant for non-Unicode files. You can also set or clear it manually. When creating a new Unicode file from scratch, a BOM will be set, or not, depending on the corresponding global setting, so if you want your new Unicode files to be created with a BOM, you may add :setglobal bomb to your vimrc. 2. what is the correct way of converting a file encoding inside vim? I opened a file with cp936 encoding, then :set fenc=ucs-2le, then :w newfile.txt, close the vim and open the newfile.txt with a new vim, then I found everything in a mess. (gvim 7.1 winxp) -- Sincerely, Pan, Shi Zhu. ext: 2606 It should have worked; but if the file had no BOM, maybe its encoding was detected wrongly: so if it was in UCS-2le but Vim thought it was in GB2312 or in cp936... a mess would be the result. Try opening a file in cp936 then doing :setlocal fenc=ucs-2le bomb :w Your other Vim ought to display it correctly then. See also :help ++opt for another way to set the 'fileencoding' for one file only. Best regards, Tony. -- Life would be so much easier if we could just look at the source code.
How to jump to an existing tab page when jumping to an tag?
How to jump to an existing tab page when jumping to an tag? I use ctags for my c++ files. Normally, I opened many of such c++ files in different tag pages. But, when I using Ctrl-] to jump a tag under cursor, gvim will open the target file in current tab page, even when the target file is already opened in another tab page. How can I modify this behavior to make gvim jump to (focus on) the target file tab page instead of opening it in current tab page? Thanks Weihua
Pass vim variable to ruby function
Hi, This is my ruby script: VIM::command(function! OpenRequire(open) ruby open_require(open) endfunction) But open is not recognized by ruby. But I can do this: VIM::command(function! OpenRequire(open) echo a:open endfunction) This does not work too: VIM::command(function! OpenRequire(open) ruby open_require(a:open) endfunction) How do I pass vim function argument to ruby function. Thank you.
Re: Pass vim variable to ruby function
Akbar wrote:
Hi,
This is my ruby script:
VIM::command(function! OpenRequire(open)
ruby open_require(open)
endfunction)
But open is not recognized by ruby. But I can do this:
VIM::command(function! OpenRequire(open)
echo a:open
endfunction)
This does not work too:
VIM::command(function! OpenRequire(open)
ruby open_require(a:open)
endfunction)
How do I pass vim function argument to ruby function. Thank you.
What about
ruby open_require(VIM::evaluate('a:open'))
?
Best regards,
Tony.
--
NOBODY EXPECTS THE SPANISH INQUISITION
Re: 'fileencodings': Why use ucs-2le for cp936 file?
On 6/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, Recently I want to do some research about 'fileencodings', what I want is to recognize utf-8, ucs-2le, euc-cn and cp936 encodings. So I set the 'fencs' in my .vimrc: set fencs=ucs-bom,utf-8,ucs-2le,euc-cn,cp936 However, cp936 files are always recognized as ucs-2le and I got everything in a mess... If I remove the ucs-2le: set fencs=ucs-bom,utf-8,euc-cn,cp936 That would work, but ucs-2le files cannot get recognized at all. It is said that unicode files all have BOM, and obviously cp936 files do not have BOM, so I wonder why cp936 files get recognized as ucs-2le file without any BOM. It's not recommended using UCS-2 without BOM. It's not an easy thing to detect its file encoding automatically. Maybe you need a fenc detecting plugin, such as FencView. Although the current version of FencView cannot handle your problem, I think it will be able to do this after some modifications. Please contact Ming Bai [EMAIL PROTECTED] and tell him your problem. I tried to change my 'encoding' setting, but it doesn't affect anything. Any hints? -- Sincerely, Pan, Shi Zhu. ext: 2606 Regards, Edward L. Fox
Re: VimWiki - released finally
Am Dienstag, den 05.06.2007, 11:14 -0500 schrieb Tom Purl: How do you update the categories? I can't seem to find that text when I edit the full page. It's a tree (or a directed acyclic graph !?): Simply tag a category with its parent category/ies. For example snip [[Category:LanguageSpecific]] This category is for tips about the Python programming language. It is a subcategory of Category:LanguageSpecific. /snip
