Re: Gvim for KDE
Stefan Karlsson wrote: By the way, is there anyone out there that is working on a KDE version? I have tried Kyzis a bit, but didn't really like it ... As I recall, the vim7 kde port was dropped because there was no maintainer for the port. I'm not a KDE user myself, so I'm not a candidate, but perhaps if you volunteered to do KDE port+maintenance, you might be able to get it back in. Regards, Chip Campbell
Re: BUG: indirect 'configure' invocation hides exit status
A.J.Mechelynck wrote: mwoehlke wrote: I found a really annoying problem trying to build VIM 7 on HP-UX. I have an automated script that builds VIM as part of a toolchain. It ran through, and to my surprise and annoyance, installed VIM in /usr/local instead of where I wanted it. Long story short, the script called 'configure', which failed because it isn't (for some reason I have not yet figured out) finding the ncurses I built (--with-tlib=ncurses). Now, 'root/configure' calls 'src/configure' which calls 'src/auto/configure'... but the exit status is not preserved AT EITHER STEP. As a result, my script thinks 'configure' succeeded and moves on to 'make', which RE-runs 'configure' with default parameters, succeeds, and ultimately allows the script to move on to 'make install'! THIS IS BAD! The indirect 'configure' scripts need to preserve the exit status. The fix, which is trivial, I leave as an exercise. Answer to the exercise: set the appropriate environment variables so that when make runs configure, it will use whatever configure options you want to apply. Then you can do without a separate configure step (or use make config if you absolutely want one). ...Or... fix the indirect-invocation 'configure' scripts to not mask the exit status? IMO these are broken as-is (and the fix is trivial; Bram was looking at it last I heard). -- Matthew Interix, Sphinterix. Cygwin apps don't crash. :-)
Re: Gvim for KDE
Dnia poniedziałek, 17 lipca 2006 17:09, Charles E Campbell Jr napisał: As I recall, the vim7 kde port was dropped because there was no maintainer for the port. I'm not a KDE user myself, so I'm not a candidate, but perhaps if you volunteered to do KDE port+maintenance, you might be able to get it back in. I am not programmer but use KDE. IMO come back to KDE should wait until release of Qt4.2 . It should support glib event loop. Conflicts between glib and Qt event loops were major reasons for unresponsiveness of kvim. m.
Is anyone has the syntax file for omnet++ ned filetype?
hello, everyone I am working on omnet++, and I found that no syntax file for omnet++ ned filetype, is anyone has it? thanks.
Re: Website Sign-up
Aha, upload scripts and vote. Should not need to search around for reasons to sign up. If someone wants people to sign up to their web site, they should tell them why on the register/info/about page(s), IMHO. Ta :) On Mon, 17 Jul 2006, A.J.Mechelynck wrote: - getting an account at vim-online ( http://www.vim.org/ or http://vim.sourceforge.net/ ) : it allows you to upload useful scripts (if you write any) for use by others. - sponsoring Vim / registering your Vim copy: this allows you to help Bram dedicate more of his time to Vim development. It also allows you to vote for new features you'd want to see included. IIUC the answers to your question can be found by intelligently browsing the vim-online site. -- .
Re: Shell commands and the more-prompt
On 7/17/06, justin constantino [EMAIL PROTECTED] wrote:
I'm trying to write a plugin that runs a few shell commands. I want
the user to be able to see the output of the commands, but if it takes
up more than a screenful, there doesn't seem to be any way to see the
part that goes off screen. I looked for a way to make Vim use the
more-prompt for the output of shell commands but found none. Is there
a way?
Failing that, I tried to hack up a solution where I could grab the
output myself and then :echo it so that the more-prompt would be used,
but it only displayed the output after the command had completely
finished, which isn't very good because the commands take some time to
run.
Anyone know of a solution for this seemingly simple thing?
: let result = system('command')
echo result
If you want to capture error mesages, too, you can try
: let result = system('command 21')
:help system
Yakov
Re: Website Sign-up
On 7/17/06, Vigil [EMAIL PROTECTED] wrote: Aha, upload scripts and vote. Should not need to search around for reasons to sign up. Vim.org demands you you to login in order to search for script ? That's very strange. For me, it doesn't, Can't you open this page without being logged in :? http://www.vim.org/search.php Yakov
Re: ftplugin not detected
When adding the filetype plugin on to my .vimrc file, my ftplugin file is
indeed loaded when I edit *.adb files (Ada).
But it seems other stuff does not work in that case. I use vim 6.3.82.
So I made the following test: with no local filetype.vim file and no file
in .vim/ftplugin directory, I added the line filetype plugin on to my
..vimrc file.
Then the Ctrl+] shortcut which usually search my tagfile does not work
any more. Instead, it echos in the command-line :call JumpToTad_ada(''),
whereas without the new line in .vimrc it would return a list of choices
for the keyword under the cursor.
In the end, adding that simple line to my .vimrc file seems to break the
default configuration from $VIMRUNTIME directory, even though no particular
file lies in my local $RUNTIMEPATH.
Any idea explaining that strange behaviour?
Regards,
Julien
Internet
[EMAIL PROTECTED] - 07/16/2006 02:22 AM
To:drchip
cc:Julien 3 NGUYEN, vim
Subject:Re: ftplugin not detected
Charles E Campbell Jr wrote:
[EMAIL PROTECTED] wrote:
Hi everybody,
ViM does not detect my ada ftplugin file in $HOME/.vim/ftplugin/ada.vim,
though my runtimepath variable contains ~/.vim .
If I source the file manually, my stuff does work.
Has anyone an idea of what's wrong?
Your .vimrc needs
filetype plugin indent on
Regards,
Chip Campbell
N.B. indent in the above is optional for filetype plugin activation;
and if you source the vimrc_example vim (for instance by
source $VIMRUNTIME/vimrc_example.vim
near the top of your vimrc), the above :filetype command is included.
Best regards,
Tony.
This message and any attachments (the message) is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
-
Ce message et toutes les pieces jointes (ci-apres le
message) sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
Re: Website Sign-up
Yakov Lerner wrote: On 7/17/06, Vigil [EMAIL PROTECTED] wrote: Aha, upload scripts and vote. Should not need to search around for reasons to sign up. Vim.org demands you you to login in order to search for script ? That's very strange. For me, it doesn't, Can't you open this page without being logged in :? http://www.vim.org/search.php Yakov You may search for scripts without logging in. But if you *write* a script, you must log in before you can upload it. Best regards, Tony.
Color Question
Hello all, I'm on vim7 with 'syntax on' and 'colorscheme morning'. The colors used by syntax highlighting for c / c++ and java are great but on php or perl I've got a lot of Cyan in it. I don't know why but reading Cyan Text is horror for me and vim highlights a lot in php and perl with that color. I've turned all Cyan to Black in colors/morning.vim but that didn't help. please let me know how I can get rid of that cyan in this colorscheme. regards Ralf
Re: Color Question
On 7/17/06, Ralf Schmitt [EMAIL PROTECTED] wrote: Hello all, I'm on vim7 with 'syntax on' and 'colorscheme morning'. The colors used by syntax highlighting for c / c++ and java are great but on php or perl I've got a lot of Cyan in it. I don't know why but reading Cyan Text is horror for me and vim highlights a lot in php and perl with that color. I've turned all Cyan to Black in colors/morning.vim but that didn't help. please let me know how I can get rid of that cyan in this colorscheme. This colorscheme pack : http://www.vim.org/scripts/script.php?script_id=1498 contains 223 colorschemes in one pack This script: http://www.vim.org/scripts/script.php?script_id=1488 allows you to scroll through many colorschemes quickly. Of course you can also copy the colorscheme file ($VIMRUNTIME/colors/morning.vim) into your personal dir (~/.vim/colors) nuder your own name and edit it. Yakov
:e behaviour
Hi all, I would like to change the :edit command behaviour in order to make it open a file in the current tab if the current buffer is empty or in a new tab otherwise. I've made a :E command like this : command! -nargs=* -complete=file E :tabnew args But I always forget to use :E instead of :e because I'm too used to type :e file So I wonder if it's possible to change :edit command behaviour. -- Fabien Meghazi Website: http://www.amigrave.com Email: [EMAIL PROTECTED] IM: [EMAIL PROTECTED]
Re: CTRL-S under WXP and Linux
On Mon, Jul 17, 2006 at 01:09:58PM +, Eric Leenman wrote: Hi, I'm using VIM under WXP and under Linux. When I type :map it's both mapped as: v C-S * C-C:updateCR noC-S * :updateCR Why does my screen lock when I press CTRL-S under Linux? And is the only way to unlock it CTRL-Q under linux? That's because of the flow control capabilities terminals have. If you google for xoff xon, you'll find sites explaining what the flow control does. It's just something that you have to get used to when using *nixes. You may be able to disable it through the stty command. HTH, James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
How to distinguish [L]esen (Readonl y) from (L)öschen (Delete) ?
Original Message From: - Sun Jul 16 18:41:05 2006 X-Mozilla-Status: 0001 X-Mozilla-Status2: 0080 Message-ID: [EMAIL PROTECTED] Date: Sun, 16 Jul 2006 18:40:54 +0200 From: Andre Massing [EMAIL PROTECTED] User-Agent: Thunderbird 1.5.0.4 (X11/20060713) MIME-Version: 1.0 To: vim@vim.org Subject: How to distinguish [L]esen (Readonly) from (L)öschen (Delete) ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Dear Vimmers, probably a rather stupid question, but using german language makes it impossible for me to choose (L)öschen (Delete) instead of [L]esen (Readonly) by typing just l if there exists a swap-file from a chrashed session. So how can I tell vim to delete this file (in a console vim session)? Thanks in advance for any hints. Regards, Andre
Re: :e behaviour
Fabien Meghazi wrote: Hi all, I would like to change the :edit command behaviour in order to make it open a file in the current tab if the current buffer is empty or in a new tab otherwise. I've made a :E command like this : command! -nargs=* -complete=file E :tabnew args But I always forget to use :E instead of :e because I'm too used to type :e file So I wonder if it's possible to change :edit command behaviour. Keep your :E command, and add :cabbrev e E Now :e will change itself to :E when not followed by a letter, but :edit will get you the old behaviour of the :e command. HTH, Tony.
Re: :e behaviour
On 7/17/06, Fabien Meghazi [EMAIL PROTECTED] wrote: Hi all, I would like to change the :edit command behaviour in order to make it open a file in the current tab if the current buffer is empty or in a new tab otherwise. I've made a :E command like this : command! -nargs=* -complete=file E :tabnew args But I always forget to use :E instead of :e because I'm too used to type :e file Does the following work for you: cabbrev e c-R=(getcmdtype()==':' getcmdpos()==1 ? 'E' : 'e')cr It remaps ':e' to ':E' when e is typed at the beginning of command line, followed by space or other delimtier char. Yakov
Re: How to distinguish [L]esen (Readonly) f rom (L)öschen (Delete) ?
Hi! --- Andre Massing [EMAIL PROTECTED] wrote: probably a rather stupid question, but using german language makes it impossible for me to choose (L)öschen (Delete) instead of [L]esen (Readonly) by typing just l if there exists a swap-file from a chrashed session. This is an error of the german translation, which unfortunately has been noticed only after the release of Vim 7.0. Since I am the maintainer of the German translation for some months now, I am very sorry for this inconvenience. There is a newer file on the FTP server of Vim: http://ftp.vim.org/editors/vim/messages/de.po Just compile this and replace the distributed version with the compiled version of the latest messages. If you cannot compile it yourself, be free to ask me for my compiled version (I have compiled it under MS Windows, thus I am not sure, if it will work on Linux, too). Best wishes, Georg ___ Try the all-new Yahoo! Mail. The New Version is radically easier to use The Wall Street Journal http://uk.docs.yahoo.com/nowyoucan.html
Re: :e behaviour
:cabbrev e E Now :e will change itself to :E when not followed by a letter, but :edit will get you the old behaviour of the :e command. However, beware the funky behaviors that can ensue from this: Trying to type something like :echo the letter e is nice will expand to :echo the letter E is nice There are other oddball places this has manifested itself for me in the past (when trying similar things). Yakov's solution (that came in while typing this) has some checks in place to solve that. However, I think Yakov's solution just works in Vim7 and isn't backwards compat. with 6.x and earlier (for those of us with hosted servers that are a little sluggish in upgrading). -tim
Re: netrw with hiding
Bill McCarthy wrote: (concerning updating to netrw v102i) After some struggling to get the .vba file, it installed nicely in my vimfiles/ directory. It didn't work at all until I removed the v98 distribution files: [c:\vim\vim70]zip -rm netrw98 . -i *netrw* Yes, that's why I said to be sure to remove all vestiges of older netrw. Netrw has the common to plugins feature to prevent itself from being loaded more than once. The vimball installs itself into the first accessible directories along your runtimepath; typically, this location is the user's personal plugins location. However, the system copy of plugins loads first; thus, the older copy of netrw ends up taking precedence if its not removed first. then it worked fine - but once Bram updates the official plugin directory, I like to have modified versions in my vimfiles so I can still apply patches to the release and have my modifications take precedence. Well, Bram typically doesn't release patches to plugins, syntax files, indent files, etc. Whenever vim 7.1 is released, it will install itself into the vim70 directory, and will include a version of netrw. Due to the logic mentioned above, it will take precedence over your personal copy of netrw anyway. I noticed that some files are always missing from the list. For example, .exe .jpg .gif Why is this and how do we override? Netrw doesn't normally suppress these; I don't know why these files are missing from your listings. In fact, netrw provides a mapping for x so that the cursor selected file with one of those extensions can be visualized. We have enter to browse a file in the same window, 'o' to browse in a new horizontal window and 'v' to browse in a new vertical window. It would be nice to have 't' (not used) to browse in a new tab. I've generally tried to only use keys that have non-motion meanings in normal mode; the t (and T) keys both have motion effects. 'let g:netrw_browse_split = 3' has some strange behavior - it affects both 'o' and 'v' for example. Hmm, there does appear to be a bug here. I'll fix it. Also you have a local map Q (currently undocumented). Some of us already use Q to quit (nmap Q :q!CR). I'm afraid that I don't even remember why that map was in netrw; it'll be removed. Finally, I noticed that you only anticipate the use of cmd.exe as a Windows shell. Many of us not using training wheels g (sh, bash, etc.) use 4nt. Please replace if shell =~ cmd.exe$ with if shell =~ '\(cmd\)\|\(4nt\)\.exe$' When the need is pressed on me to use Windows, I use cygwin (and thus cygwin's bash shell). I assume 4nt's ftp doesn't support .netrc just like cmd.exe doesn't? That's what that test is used for determining in netrw. Regards, Chip Campbell
Re: R: open Explore in new tab
Cesar Romani wrote: Please try netrw v102i, available at my website: http://mysite.verizon.net/astronaut/vim/index.html#VimFuncs as Network Oriented Reading, Writing, and Browsing It supports the :Texplore command. Be sure to remove all netrw components from /usr/local/share/vim/vim70/plugin (and ../autoload) first (or from wherever you've put vim 7.0's runtime). Regards, Chip Campbell I've installed it (version 100) how you've said, but it doesn't recognize :Texplore It shows: E492: Not an editor command: Texplore Many thanks in advance. Hmm, you didn't take my advice! It was to get the version from my website (v102i), not from vim.sf.net, which currently has v100. I'll update the vim.sf.net version when v102 is ready (and I expect to send it on to Bram, too). Regards, Chip Campbell
Re: :e behaviour
FYI, I just made a vim tip with the solution to your question: http://www.vim.org/tips/tip.php?tip_id=1285 with credit to your nice example of :E command. Thanks all for your response. Yakov, my :E command does not open the file in the current tab if the buffer is empty, it always open a new tab. I'm still trying to find a solution for that.
Re: netrw with hiding
Charles E Campbell Jr wrote: Bill McCarthy wrote: (concerning updating to netrw v102i) After some struggling to get the .vba file, it installed nicely in my vimfiles/ directory. It didn't work at all until I removed the v98 distribution files: [c:\vim\vim70]zip -rm netrw98 . -i *netrw* Yes, that's why I said to be sure to remove all vestiges of older netrw. Netrw has the common to plugins feature to prevent itself from being loaded more than once. The vimball installs itself into the first accessible directories along your runtimepath; typically, this location is the user's personal plugins location. However, the system copy of plugins loads first; thus, the older copy of netrw ends up taking precedence if its not removed first. then it worked fine - but once Bram updates the official plugin directory, I like to have modified versions in my vimfiles so I can still apply patches to the release and have my modifications take precedence. Well, Bram typically doesn't release patches to plugins, syntax files, indent files, etc. Whenever vim 7.1 is released, it will install itself into the vim70 directory, Correction: it will create a new vim71 directory and install itself there; anything in the vim70 directory and its subdirs won't be used by Vim 7.1 and will include a version of netrw. Due to the logic mentioned above, it will take precedence over your personal copy of netrw anyway. [...] I'm not convinced. When loading plugins (after the vimrc has been run) they will run in the following sequence: 1) ~/.vim/plugin/*.vim (Unix) or ~/vimfiles/plugin/*.vim (Windows) 2) $VIM/vimfiles/plugin/*.vim 3) $VIMRUNTIME/plugin/*.vim 4) $VIM/vimfiles/after/plugin/*.vim 5) ~/.vim/after/plugin/*.vim or ~/vimfiles/after/plugin/*.vim When the distributed copy of the plugin is loaded (at step 3) it will notice the traffic light variable created by the upgraded version (at step 1 or 2) and do nothing. (But if the upgraded version was installed in $VIMRUNTIME/plugin it would of course be lost when upgrading to 7.1). Also, this scenario assumes that you restart Vim between installing the vimball and trying it out. Best regards, Tony.
Re: :e behaviour
On 7/17/06, Fabien Meghazi [EMAIL PROTECTED] wrote:
FYI, I just made a vim tip with the solution to your
question: http://www.vim.org/tips/tip.php?tip_id=1285
with credit to your nice example of :E command.
Thanks all for your response.
Yakov, my :E command does not open the file in the current tab if the
buffer is empty, it always open a new tab. I'm still trying to find a
solution for that.
Ah, I didn't pay enough attention to the contents of your E command.
The E command that checks for buffer-is-empty and opens new tab if buffer
is not empty will, I think, be:
command! -nargs=* -complete=file E if expand('%')=='' line('$')==1
getline(1)=='' :tabnew args | else | :edit args | endif
(That's one long line)
Does this work for you ?
Yakov
Re: :e behaviour
Yakov Lerner wrote:
On 7/17/06, Fabien Meghazi [EMAIL PROTECTED] wrote:
FYI, I just made a vim tip with the solution to your
question: http://www.vim.org/tips/tip.php?tip_id=1285
with credit to your nice example of :E command.
Thanks all for your response.
Yakov, my :E command does not open the file in the current tab if the
buffer is empty, it always open a new tab. I'm still trying to find a
solution for that.
Ah, I didn't pay enough attention to the contents of your E command.
The E command that checks for buffer-is-empty and opens new tab if buffer
is not empty will, I think, be:
command! -nargs=* -complete=file E if expand('%')=='' line('$')==1
getline(1)=='' :tabnew args | else | :edit args | endif
(That's one long line)
Does this work for you ?
Yakov
Yakov, haven't you got the if and else switched around? I think the
above will open the file in the current tab *unless* the buffer is
empty, not *only if* the buffer is empty.
Best regards,
Tony.
Re: Anchoring in a regex
A.J.Mechelynck wrote:
Tim Chase wrote:
syn match tclV ttk\(\(::\)\?\([[:alnum:]_.]*::\)*\)\a[a-zA-Z0-9_.]*
I only want this to work ttk at the start. I know that ^ means the
start but I am not sure how to add that (I did try just adding it) to
make the regex start with ttk.
Just put it at the beginning:
^ttk...
just as you would use the dollar-sign at the end to anchor something
to the end of the line:
regexp$
-tim
Similarly, to allow it as long as it is the first non-whitespace
characters, add zero or more whitespace between ^ and ttk :
^\s*ttk...
See :help pattern.txt for more info on Vim regular expressions (and
dont forget the .txt extension, or you'll be brought to a formal syntax
definition instead of to the table of contents of the helpfile).
Note that $^ in the middle of a pattern usually matches dollar followed
by caret, not a linebreak. ( \n matches a linebreak IIUC; but in
substitute you must use :s/\n/\r/ to replace a linebreak by itself.)
Thanks Tony and welcome back. : )
I figured out that ttk:: can occur after a left [ as in [ttk:: and I
am looking at the others as well.
Is there a way to do an or so that I can put ttk in {} [] and it be
colored or is there a better way like a region?
:Robert
delete buffers matching pattern
Is there a way to delete all buffers matching a certain pattern? For example, suppose I just read in all files in a directory and this is my buffer list: 1 a.txt 2 b.txt 3 1.exe 4 2.exe 5 c.txt 6 3.exe 7 d.txt I want to do something like :bdelete *.exe. I don't want to manually enumerate all the buffer nummers like :bdelete 3 4 6 Thanks, Wim
Re: :e behaviour
command! -nargs=* -complete=file E if expand('%')=='' line('$')==1
getline(1)=='' :tabnew args | else | :edit args | endif
(That's one long line)
Does this work for you ?
Yes it works but as Tony pointed out the expression should be switched.
And there is a pipe missing before :tabnew
Here it is :
if (v:version = 700)
command! -nargs=* -complete=file E if expand('%')=='' line('$')==1
getline(1)=='' | :edit args | else | :tabnew args | endif
cabbrev e c-R=(getcmdtype()==':' getcmdpos()==1 ? 'E' : 'e')cr
endif
Thanks a lot !
I can continue using :e and it now behaves like I want it to do.
--
Fabien Meghazi
Website: http://www.amigrave.com
Email: [EMAIL PROTECTED]
IM: [EMAIL PROTECTED]
Re: :e behaviour
On 7/17/06, Yakov Lerner [EMAIL PROTECTED] wrote: On 7/17/06, Fabien Meghazi [EMAIL PROTECTED] wrote: Hi all, I would like to change the :edit command behaviour in order to make it open a file in the current tab if the current buffer is empty or in a new tab otherwise. I've made a :E command like this : command! -nargs=* -complete=file E :tabnew args But I always forget to use :E instead of :e because I'm too used to type :e file Does the following work for you: cabbrev e c-R=(getcmdtype()==':' getcmdpos()==1 ? 'E' : 'e')cr I made a vimtip out of this http://www.vim.org/tips/tip.php?tip_id=1285 Tip #1285: change behaviour of builtin commands like :e using special case of cabbrev There were similar requests on the list before. Yakov
Re: delete buffers matching pattern
Is there a way to delete all buffers matching a certain pattern? For example, suppose I just read in all files in a directory and this is my buffer list: 1 a.txt 2 b.txt 3 1.exe 4 2.exe 5 c.txt 6 3.exe 7 d.txt I want to do something like :bdelete *.exe. The following seems to do the trick for me: :bufdo if bufname(%)=~'.exe$' | bdel | endif or its case-insensitive cousin :bufdo if bufname(%)=~?'.exe$' | bdel | endif HTH, -tim
Re: Mapping using Let in Autocmd
On 2006-07-13, JD Miller [EMAIL PROTECTED] wrote: Comment out a line by inserting # then move to the lower line map F10 i# Eschj Here I try to do the same thing but use the BufEnter event to make the comment character change depending on the file type (*.asp). let comment_char=# autocmd BufEnter *.asp let comment_char=' execute map F10 i . comment_char . Eschj But the comment_char variable never seems to see the let assignment in the autocmd statement. What have I missed here? Is there a better approach? Thank you. On 2006-07-13, JD Miller [EMAIL PROTECTED] wrote: Thanks much Hari, I added a space before the Esc and your method works nicely. map F1 iC-R=comment_charCR Eschj Another approach to this would be to make the mapping local to the buffer, e.g., map F10 i#Eschj autocmd BufEnter *.asp map buffer F10 i'Eschj HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Wireless Division | Spokane, Washington, USA
Re: Website Sign-up
On Mon, 17 Jul 2006 at 8:30am, Yakov Lerner wrote: On 7/17/06, Vigil [EMAIL PROTECTED] wrote: Aha, upload scripts and vote. Should not need to search around for reasons to sign up. Vim.org demands you you to login in order to search for script ? That's very strange. For me, it doesn't, Can't you open this page without being logged in :? http://www.vim.org/search.php Yakov I think OP meant searching for the information on why you need to sign-up, not for doing searches on vim.org. -- Hari __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
errorformat error munging
Hi all, I sent a question a couple of days ago about errorformat, but it was perhaps too ill-formed to garner a reply :) Here's a simpler one: When vim's quickfix mode recognizes a compiler error as valid, it munges the error in the error window to its own uniform format. Is there anyway to preserve the error as it was originally output by the compiler? This would have at least two benefits: (1) one could use au BufReadPost quickfix on the error window to do some extra action for valid errors, using the entire message as it was output by the compiler, and (2) people who have grown very accustomed to reading and recognizing their compiler's error messages would not have to acclimate themselves to a new format. cheers, William
Re: ftplugin not detected
[EMAIL PROTECTED] wrote:
When adding the filetype plugin on to my .vimrc file, my ftplugin file is
indeed loaded when I edit *.adb files (Ada).
But it seems other stuff does not work in that case. I use vim 6.3.82.
So I made the following test: with no local filetype.vim file and no file
in .vim/ftplugin directory, I added the line filetype plugin on to my
..vimrc file.
Then the Ctrl+] shortcut which usually search my tagfile does not work
any more. Instead, it echos in the command-line :call JumpToTad_ada(''),
whereas without the new line in .vimrc it would return a list of choices
for the keyword under the cursor.
In the end, adding that simple line to my .vimrc file seems to break the
default configuration from $VIMRUNTIME directory, even though no particular
file lies in my local $RUNTIMEPATH.
Any idea explaining that strange behaviour?
Did you have a $HOME/.vimrc file before including the filetype plugin
indent on line? If you didn't,
then you were using whatever your system had for a default (which can
vary by linux distributor,
for example).
The filetype plugin indent on line turns on your plugins; ie. they're
now being loaded, whereas they
were not being loaded before. Hence, the ctrl+] is likely to be
invoking some mapping that you didn't
have heretofore.
:verbose map c_ctrl-v_]?
should show you what plugin is re-defining ctrl+] in the command line.
Regards,
Chip Campbell
Re: colors
Bill Hollingsworth wrote: Hi, I recently upgraded to VIM 7.0 and now the color settings for my PERL programs are different. I liked the way the colors were before. Could someone tell me how to return to the old settings, or how to set the colors myself? For instance, now comments and variable names are the same color. Thanks and best wishes, Bill Hollingsworth University of Cambridge Computer Laboratory I guess the easiest way is to write your own colorscheme. For instance I use the attached colorscheme which I wrote, named $HOME/.vim/colors/almost-default.vim and invoked by :colorscheme almost-default. It is a simple example which might help you create your own. You will have to find out the names of the highlight groups for which you need a non-default color. (Try Comment and Identifier; I guess changing them will also change perlComment and PerlIdentifier, or however they are named). You can set different colors for console Vim and gvim by using, in the same :highlight command, arguments cterm= ctermfg= ctermbg= on the one hand, and gui= guibg= guifg= onthe other hand. There are also a number of colorschemes available in your distribution (in $VIMRUNTIME/colors) and at vim-online (which can be installed by dropping them in one of the following: - system-wide: $VIM/vimfiles/colors - user-private on Unix: ~/.vim/colors - user-private on Windows: ~/vimfiles/colors ). Don't change anything in $VIMRUNTIME or its subdirs, because any upgrade can silently overwrite any changes you made there. See :help :highlight :help :colorscheme :view $VIMRUNTIME/colors/README.txt HTH, Tony. Vim color file Maintainer: Tony Mechelynck [EMAIL PROTECTED] Last Change: 2006 Jun 21 This is almost the default color scheme. It doesn't define the Normal highlighting, it uses whatever the colors used to be. Only the few highlight groups named below are defined; the rest (most of them) are left at their compiled-in default settings. Set 'background' back to the default. The value can't always be estimated and is then guessed. hi clear Normal set bg Remove all existing highlighting and set the defaults. hi clear Load the syntax highlighting defaults, if it's enabled. if exists(syntax_on) syntax reset endif Set our own highlighting settings hi Errorguibg=red guifg=black hi clear ErrorMsg hi link ErrorMsg Error hi StatusLine gui=NONE,bold guibg=red guifg=white hi StatusLineNC gui=reverse,bold hi TabLine gui=NONEguibg=#DD guifg=black hi TabLineFill gui=NONEguibg=#AA guifg=red hi User1ctermfg=magenta guibg=white guifg=magenta hi User2ctermfg=darkmagenta guibg=#DD guifg=magenta remember the current colorscheme name let colors_name = almost-default vim: sw=2
Re: ftplugin not detected
Charles E Campbell Jr wrote:
[EMAIL PROTECTED] wrote:
When adding the filetype plugin on to my .vimrc file, my ftplugin
file is
indeed loaded when I edit *.adb files (Ada).
But it seems other stuff does not work in that case. I use vim 6.3.82.
So I made the following test: with no local filetype.vim file and no file
in .vim/ftplugin directory, I added the line filetype plugin on to my
..vimrc file.
Then the Ctrl+] shortcut which usually search my tagfile does not work
any more. Instead, it echos in the command-line :call
JumpToTad_ada(''),
whereas without the new line in .vimrc it would return a list of choices
for the keyword under the cursor.
In the end, adding that simple line to my .vimrc file seems to break the
default configuration from $VIMRUNTIME directory, even though no
particular
file lies in my local $RUNTIMEPATH.
Any idea explaining that strange behaviour?
Did you have a $HOME/.vimrc file before including the filetype plugin
indent on line? If you didn't,
then you were using whatever your system had for a default (which can
vary by linux distributor,
for example).
The filetype plugin indent on line turns on your plugins; ie. they're
now being loaded, whereas they
were not being loaded before. Hence, the ctrl+] is likely to be
invoking some mapping that you didn't
have heretofore.
:verbose map c_ctrl-v_]?
:verbose map C-]
(The terminology isn't the same in the :map command as in :help).
Also, IIUC, the OP means Ctrl-] in Normal mode (jump to tag), not in
Command-line mode (trigger abbreviation).
should show you what plugin is re-defining ctrl+] in the command line.
Regards,
Chip Campbell
Best regards,
Tony.
Re: Color Question
Hi Ralf, The colorscheme 'morning' has very little Cyan in it - cyan is the default for the 'Identifier' group, which is used for $variables and functions(). Just add something like this to colors/morning.vim: highlight Identifier ctermfg=Red guifg=Red If you want function calls in a distinguishable color, use: highlight Function ctermfg=Blue guifg=Blue ... otherwise, they are the same color as Identifiers. The 'cterm=' option is for color terminal use, the 'guifg=' option is if you are using the GUI. regards, Peter --- Ralf Schmitt [EMAIL PROTECTED] wrote: Hello all, I'm on vim7 with 'syntax on' and 'colorscheme morning'. The colors used by syntax highlighting for c / c++ and java are great but on php or perl I've got a lot of Cyan in it. I don't know why but reading Cyan Text is horror for me and vim highlights a lot in php and perl with that color. I've turned all Cyan to Black in colors/morning.vim but that didn't help. please let me know how I can get rid of that cyan in this colorscheme. regards Ralf On Yahoo!7 Messenger - Make free PC-to-PC calls to your friends overseas. http://au.messenger.yahoo.com
vim-get and vim-thread not working?
I have sent a few requests with the message ids for both [EMAIL PROTECTED] and [EMAIL PROTECTED] yesterday, but haven't heard back. Is this functionality still working? -- Thanks, Hari __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
A card game for Vim
I am creating a new card game for Vim7 and wonder if anyone is interested to try it and give me feedback. The game is quite usable at the current state, though there are some pending issues. Here are a couple of snapshots of the game to get you interested: http://haridara.googlepages.com/arimona.html http://haridara.googlepages.com/arimona-middle.html I have only tried the game so far on Windows, and the Unicode symbols that the game requires are found to be in the following fonts (out of those that I have installed): - Couriner New - Andale Mono - Lucida Console - MS Mincho - @MS Mincho You can download it from: http://haridara.googlepages.com/arimona.zip The game looks good with color schemes that have dark backgrounds (such as desert), but seems like I have to do some work for it to look good with some of the other schemes (like those that use ligher background, including the default). If you change your colorscheme, you need to use :Arimona! to reinitialize it. Here is the brief introduction from the plugin header. There is a known issues section which lists the issues that I am aware of. Instructions: To start the game use the :Arimona command. You can close the window and return back to the game anytime using the same command. To start a fresh game and discard the current state, suffix a bang(!) as :Arimona!. You have to move all the cards to the foundation (the top right corner). Use the below keys to play: h, j, k, l - move the focus. M, mm - move the card to foundation. C, cc - change the current pail between deck and cards. S, ss, CR - Select/Release cards. The game is pretty much like solitaire, but it is more likely to be finished because: - while moving cards on to card pails, symbol has no significance. - all the cards (including those on deck) are visible at all times. - you can move any card to empty pails (the first card doesn't need to be a King). Unlike in solitaire however, you can't move cards back from foundation. The game changes the global 'encoding' to utf-8, as it uses the Unicode symbols to show the card symbols. I don't know the complete impact of this on an existing Vim session, so I recommend you run the game in a separate Vim instance only for now. You need to choose a font which includes the Unicode symbols for the card suits, such as the Couriner New on windows. See the following Wikipedia article for details: http://en.wikipedia.org/wiki/Playing_card#Playing_card_symbols_in_Unicode -- Thanks, Hari __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
