Re: searchpos bug
Viktor Kojouharov wrote:
It seems that searchpos doesn't match under the cursor, when the
cursor itself is on the first column. You can try the simple search
pos command below, and try searching for anything non-whitespace. Even
with the 'c' flag, it will still move the cursor to the first matched
character on the previous line, instead of matching the character in
the first column.
call searchpos('[^[:space:]]', 'bWc')
I see the problem. I'll add it to the todo list.
--
hundred-and-one symptoms of being an internet addict:
253. You wait for a slow loading web page before going to the toilet.
/// 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: mapping g
Manfred Georg wrote: Apparently this isn't a very popular thing to do, but I remap g to help me do indentation. There are two problems with this. In gvimrc_example.vim , there is some code (which has been copied all sorts of places) which does automatic jump to last position when file was closed. This uses the command g' Unfortunately when g has been remapped it triggers this mapping. To fix this the line with \| exe normal g'\ | endif should read \| exe normal! g'\ | endif the ! stops it from remapping g to the local mapping. Right. Thanks for the fix. -- Emacs is a nice OS - but it lacks a good text editor. That's why I am using Vim. --Anonymous /// 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///
using vimball or netrw
Hi There, I work on windows OS and want to access(read/write) to remote server(UNIX). From the vim site I came to know this is possible, but how to use it is outa my mind. I check the two plugins netrw and vimball; I'm not getting much understanding regarding these two plugins and not much help available for these two. Can I get much detailed document to get more understanding on the same. Regards, Jagpreet
RE: --remote diff to tab
| | I am trying to set up my subversion client(s) so that I | can get any | | diffs open in a proper diff mode, in an existing gvim | |session, in a new tab... | | | | Did you try (untested by me) | | | |--remote-tab +diffsplit %2 %1 | | | |(Will the %2 need any special escaping inside the quotes? | |What if %2 has spaces in the file name (ugh)?) For the record, thanks to Benji Fisher, who got me on the right track. I was able to set up a gvimdiff.bat file that gets called with two (possibly quoted) files as arguments, and then it executes this: gvim.exe --remote-tab +diffsplit %~2 %~1 Seems to work fine with spaces in the filenames. The tilde in the argument specification is a Windows NT command extensions thing, that works on WinNT, Win2k + XP (And I assume Vista) - it un-quotes the file arguments. Thanks all! /Hugo
autocmd and netrw
Hello, I have such line in my .gvimrc autocmd BufEnter * :lcd %:p:h (this is vim tip: http://vim.sourceforge.net/tips/tip.php?tip_id=101) but when I work with remote files via netrw it produces warning every time, 'cause scp copies remote files to /tmp dir Is there any way to determine whether file is opening via netrw to disable that autocmd? -- regards, Hegai Ilya
Re:
Hi Tony, Thanks a lot. Works like a charm. Sean A.J.Mechelynck wrote: Sean Lerner wrote: Hello, Syntax highlighting with Vim 7 is working for some of my files, but for others it's not. They're all for lighttpd config files, but it only works for one of those files. Why is this? My situation: -rw-r--r-- 1 root root 2920 Nov 15 19:33 lighttpd.conf -rw-r--r-- 1 root root 2920 Nov 15 22:47 lighttpd.conf.b.old -rw-r--r-- 1 root root 2940 Nov 15 17:40 lighttpd.conf.mem -rw-r--r-- 1 root root 5606 Nov 15 14:52 lighttpd.conf.old -- syntax highlighting works -rw-r--r-- 1 root root 5606 Nov 15 22:53 lighttpd.conf.old.b -- syntax highlighting works (copy of light.conf.old) -rw-r--r-- 1 root root 2600 Nov 15 15:06 lighttpd.conf.special -rw-r--r-- 1 root root 2606 Nov 15 16:52 lighttpd.conf.working -rw-r--r-- 1 root root 2933 Nov 15 19:28 lighttpd.conf~ But for the rest of the files, syntax highlighting doesn't work. Any pointers / tips appreciated. Sean Create (if it doesn't yet exist) or add to ~/.vim/filetype.vim (on Unix) or ~/vimfiles/filetype.vim (on Windows) the uncommented lines below: augroup filetypedetect the line above must be first etc. autocmd BufRead,BufNewFile *.conf* setf conf etc the line below must be last augroup END Create the directory if it doesn't yet exist; replace conf (after setf) by whatever filetype (such as apache) you want it to be. Best regards, Tony. -- View this message in context: http://www.nabble.com/Syntax-highlighting-works-for-some-files%2C-but-not-for-others-tf2640675.html#a7377216 Sent from the Vim - General mailing list archive at Nabble.com.
Re: Commenting out TeX-text line by line in V-mode
Or you could skip step one, and only add percent signs on the lines with anything in them: (select lines visually) :','s/^\(.\)/% \1 -Dmitriy On 11/15/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Meino Christian Cramer wrote: Hi, a question more driven by curiosity than by the need to change anything. Suppose you have the following TeX-text: bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats and because this text is so fullfilled with wisdom and knowledge, that no one else than you will be able to handle its contents carefully ;) you decide to comment it out to not to harm the public. As a vim newbie I would do that using block oriented visual mode on the first line and I-nserting a '%' (TeX's comment sign), which results in: % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % bla blabla foo bar gnu gnats % % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % % bla blabla foo bar gnu gnats So far so nice...it works. But would be there a way to acchieve the following commenting: % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % bla blabla foo bar gnu gnats % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % bla blabla foo bar gnu gnats (blank lines not commented out) by a similiar simple command like CTRL-v SHIFT-i textESC ? As said: This Q is mostly curiosity - based...I even dont know, whether haveing such a feature would be really useful or not. But as always: Experimenting is fun! :O) Keep editing! mcc 1. Add all percent signs like you did above, even before blank lines. 2. Replace empty comments by blank (i.e. empty) lines as follows: :%s/^%\s*$// Best regards, Tony.
Re: using vimball or netrw
J A G P R E E T wrote: Hi There, I work on windows OS and want to access(read/write) to remote server(UNIX). From the vim site I came to know this is possible, but how to use it is outa my mind. I check the two plugins netrw and vimball; I'm not getting much understanding regarding these two plugins and not much help available for these two. Can I get much detailed document to get more understanding on the same. To get an up-to-date version of netrw, you'll also need to get an up-to-date version of vimball. So: 1) Get an up-to-date version of vimball: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimBall (the mysite.verizon.net one will be the more recent version) 2) Remove the old vimball plugin and install the new one: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/vimball*.vim autoload/vimball*.vim doc/pi_vimball.txt mv (wherever it was downloaded)/vimball.tar.gz . gunzip vimball.tar.gz tar -xvf vimball.tar Windows: Under Windows, check your runtimepath to determine where your vim 7.0's runtime directories are: vim :echo rtp :q The first directory is likely your personal plugins directory, the second one is your vim system directory. cd (to your vim system directory) del plugin\vimballPlugin.vim del autoload\vimball.vim del doc\pi_vimball.txt ren (wherever)\vimball.tar.gz vimball.tar.gz gunzip vimball.tar.gz tar -xvf vimball.tar 3) Remove system version of netrw: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/netrw*.vim autoload/netrw*.vim doc/pi_netrw.txt Windows: cd (to your vim system directory) del plugin\netrwPlugin.vim del autoload\netrw.vim del doc\pi_netrw.txt 4) Install an up-to-date version of netrw: vim netrw.vba.gz :so % :q Subsequently, whenever you wish to update netrw, all you'll need to do is to a) obtain a newer netrw b) perform step #4 Now, as to documentation: :help vimball and :help netrw have 129 lines and 1928 lines of help, respectively. Using vimball is particularly simple; see step #4 above. Using netrw is reasonably simple: vim scp://somehost/path/to/file.ext would invoke netrw to do the work via scp. Netrw supports a number of protocols, including scp, rcp, ftp, etc. I suggest reading :help netrw-start . Regards, Chip Campbell
Re: autocmd and netrw
Ilya Hegai wrote: Hello, I have such line in my .gvimrc autocmd BufEnter * :lcd %:p:h (this is vim tip: http://vim.sourceforge.net/tips/tip.php?tip_id=101) but when I work with remote files via netrw it produces warning every time, 'cause scp copies remote files to /tmp dir Is there any way to determine whether file is opening via netrw to disable that autocmd? * Check into :set acd , although this may not work if your vim doesn't support it. * I believe that BufEnter autocmds fire before BufRead and FileRead events, so when your autocmd fires, netrw's remote file handling events haven't fired yet. So you need a smarter event; perhaps something like (untested): au BufEnter * :if expand(afile) !~ '^\a\+://' | :lcd %:p:h | endif Regards, Chip Campbell
Re: Trouble with syntax highlighting in gvim70
Tony, I actually did have it as a colorscheme originally, but I was still calling it from _vimrc. Which lead to the same problem. I checked on my older machine, still using gvim6x, and it has the highlight commands directly in the _vimrc file. Obviously something changed between 6 and 7, because when I ran scriptnames in gvim6x it was calling _vimrc first as in gvim70, but I never saw a call to syncolor.vim. Thanks for the information. I may change over to that method on my other machine, and see if I like it better. Thanks, Dudley On 11/15/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Yegappan Lakshmanan wrote: Hi, On 11/15/06, Dudley Fox [EMAIL PROTECTED] wrote: Yegappan, It is actually _vimrc. I just mistyped it. The output of :scriptnames is listed below. It looks like the _vimrc is the first thing loaded, and it does explain the problem I am seeing though. Did this change from gvim6.x? And is there a way to get what I want without having to manually highlight what I want everytime (other than editing the default syntax files). As described under :help syncolor, place the highlight group definitions in the $VIM\vimfiles\after\syntax\syncolor.vim file. - Yegappan ... or else, place them in a colorscheme. That will be a .vim script in the colors/ subdirectory of a 'runtimepath' directory other than $VIMRUNTIME: typically something like (on Windows, but in Vim notation) ~/vimfiles/colors/dudleyfox.vim if you want to invoke it with :colors dudleyfox (without the quotes). I'm attaching a fairly simple (but working) colorscheme as an example. It defines only the groups for which other colours than the standard are desired, including User1 and User2 which normally default to Normal but have abbreviated codes for the status line, and PyjamaEven which is normally not defined but is included in a syntax script of mine (unpublished yet). I suppose you won't want to use this colorscheme as is but IMHO its simplicity makes it easier as a pedagogical tool. Best regards, Tony. Vim color file Maintainer: Tony Mechelynck [EMAIL PROTECTED] Last Change: 2006 Sep 06 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 SpecialKey guibg=NONE hi PyjamaEven ctermbg=greygui=NONEguibg=#FFD8FF white on red is not always distinct in the GUI: use black on red then hi Errorguibg=red guifg=black hi clear ErrorMsg hi link ErrorMsg Error show cursor line/column (if enabled) in very light grey in the GUI, underlined in the console if has(gui_running) hi clear CursorLine hi CursorLine guibg=#F4F4F4 endif hi clear CursorColumn hi link CursorColumn CursorLine do not make help bars and stars invisible hi clear helpBar hi link helpBarhelpHyperTextJump hi clear helpStar hi link helpStar helpHyperTextEntry the following were forgotten in the syntax/vim.vim (and ended up cleared) hi clear vimVar hi link vimVar Identifier hi clear vimGroupName hi link vimGroupName vimGroup hi clear vimHiClear hi link vimHiClear vimHighlight display the status line of the active window in a distinctive color: bold white on bright red in the GUI, white on green in the console (where the bg is never bright, and dark red is sometimes an ugly sort of reddish brown). hi StatusLine gui=NONE,bold guibg=red guifg=white \ cterm=NONE,bold ctermbg=green ctermfg=white make the status line bold-reverse (but BW) for inactive windows hi StatusLineNC gui=reverse,bold \ cterm=reverse,bold define colors for the tab line: file name of unselected tab hi TabLine gui=NONEguibg=#EE guifg=black \ cterm=NONE,bold ctermbg=lightgrey ctermfg=white file name of selected tab (GUI default is bold black on white) hi TabLineSel cterm=NONE,bold ctermbg=green ctermfg=white fillup and tab-delete X at right hi TabLineFill gui=NONE,bold guibg=#CC guifg=#AA \ cterm=NONE ctermbg=lightgrey ctermfg=red tab and file number 1:2/3 (meaning tab 1: window 2 of 3) for selected tab hi User1
Re: Trouble with syntax highlighting in gvim70
Dudley Fox wrote: Tony, I actually did have it as a colorscheme originally, but I was still calling it from _vimrc. Which lead to the same problem. I checked on my older machine, still using gvim6x, and it has the highlight commands directly in the _vimrc file. Obviously something changed between 6 and 7, because when I ran scriptnames in gvim6x it was calling _vimrc first as in gvim70, but I never saw a call to syncolor.vim. The way one should call a colorscheme: vim/colors/NewColorScheme.vim and, in your .vimrc: colors NewColorScheme Is that how you were doing it? Regards, Chip Campbell
Upcase every keyword while editing
Hello! I am looking for a way to mimic a functionality I've seen in the editor ED4Win (http://www.softasitgets.com/). What I want to do is to automagically upcase every written word that is considered a keyword. I program in Progress 4GL and use the syntax file from the gvim standard distribution. Theoretically, in my understanding of the problem, I would need to write a function to check the word before the cursor against the keywords list and map this one to something. Usually, I leave the boundaries of a keyword by using either space, tab, :, ,, enter or .. So I would have to map this function to every of those keys in insert mode. This is not very elegant, but it would work. I'm not very good in (g)vim scripting and would like to have some help in writing this function or a pointer on where I could find a plugin performing this feat. Thank you for your time, Thomas Engelke gvim.exe --version says: VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7 2006 16:23:43) MS-Windows 32 Bit GUI Version mit OLE-Unterstützung Übersetzt von [EMAIL PROTECTED] Große Version mit GUI. Ein- (+) oder ausschließlich (-) der Eigenschaften: +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 +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole -osfiletype +path_extra +perl/dyn -postscript +printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save +xpm_w32 System-vimrc-Datei: $VIM\vimrc Benutzer-vimrc-Datei: $HOME\_vimrc zweite Benutzer-vimrc-Datei: $VIM\_vimrc Benutzer-exrc-Datei: $HOME\_exrc zweite Benutzer-exrc-Datei: $VIM\_exrc System-gvimrc-Datei: $VIM\gvimrc Benutzer-gvimrc-Datei: $HOME\_gvimrc zweite Benutzer-gvimrc-Datei: $VIM\_gvimrc System-Menü-Datei: $VIMRUNTIME\menu.vim Übersetzt: cl -c /W3 /nologo -D_MT -MT -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYTR/ /Ox -DNDEBUG -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=\tcl83.dll\ -DDYNAMIC_TCL_VER=\8.3\ -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python24.dll\ -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\perl58.dll\ -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=18 -DDYNAMIC_RUBY_DLL=\msvcrt-ruby18.dll\ -DFEAT_BIG /Zi /Fd.\ObjGOLYTR/ Linken: link /RELEASE /nologo /subsystem:windows /incremental:no /nodefaultlib:libc advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib oldnames.lib kernel32.lib gdi32.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib /nodefaultlib:python24.lib e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib /PDB:.\ObjGOLYTR/gvim.pdb -debug -- GPG-Key: tengelke.de/thomas_michael_engelke.asc
Re: Commenting out TeX-text line by line in V-mode
From: A.J.Mechelynck [EMAIL PROTECTED] Subject: Re: Commenting out TeX-text line by line in V-mode Date: Thu, 16 Nov 2006 05:20:13 +0100 Meino Christian Cramer wrote: Hi, a question more driven by curiosity than by the need to change anything. Suppose you have the following TeX-text: bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats and because this text is so fullfilled with wisdom and knowledge, that no one else than you will be able to handle its contents carefully ;) you decide to comment it out to not to harm the public. As a vim newbie I would do that using block oriented visual mode on the first line and I-nserting a '%' (TeX's comment sign), which results in: % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % bla blabla foo bar gnu gnats % % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % % bla blabla foo bar gnu gnats So far so nice...it works. But would be there a way to acchieve the following commenting: % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % bla blabla foo bar gnu gnats % bla blabla foo bar gnu gnats bla blabla foo bar gnu gnats bla blabla % foo bar gnu gnats % bla blabla foo bar gnu gnats (blank lines not commented out) by a similiar simple command like CTRL-v SHIFT-i textESC ? As said: This Q is mostly curiosity - based...I even dont know, whether haveing such a feature would be really useful or not. But as always: Experimenting is fun! :O) Keep editing! mcc 1. Add all percent signs like you did above, even before blank lines. 2. Replace empty comments by blank (i.e. empty) lines as follows: :%s/^%\s*$// Best regards, Tony. Hi Tony, yes...I know that (which is an exception... ;) I thought there would be one command to achieve the same effect instead of doing it the wrong way first and the correct it by an additional command... Keep editing! mcc
using :ha under linux
Hi, In Linux how do I configure Vim to print a hard copy? Please include syntax example. I am running Ubuntu and the printer is named Laserjet-4 on LPT #1. I located the info once and did this but now it eludes me. Thank You! -- Marlin :wa
Re: using :ha under linux
Marlin Unruh wrote: Hi, In Linux how do I configure Vim to print a hard copy? Please include syntax example. I am running Ubuntu and the printer is named Laserjet-4 on LPT #1. I located the info once and did this but now it eludes me. Thank You! What Windows calls LPT1 is usually called something else on Linux -- maybe /dev/lp0 or something. On systems other than Windows, Vim prints in PostScript format. If your printer doesn't understand PostScript, you need some program like ghostscript to translate the PostScript file to whatever it is that your printer can use. Of course, your system must also recognise your printer and be able to interface with it. If no program is able to print on your LJ-4, don't expect that Vim will be. See :help printer.txt. Best regards, Tony.
Re: search and replace multiple lines
mark wrote: I want too change the order of three lines globally (there are thousands of entries that need reordering) and don't seem to be able to get my head around how to do it with vi. I want to change the order off these three 1=red 2=blue 3=orange into 3=orange 2=blue 1=red Is this a case of reverse ordering lines? If so: go to the 1=red line, type ma go to the 3=orange line, type \fr where you've previously defined \fr as: nno silent Leaderfr :set lzcr'aOescma'':'a+1,.g/^/m 'acrkdd:set lz!cr Regards, Chip Campbell
RE: Upcase every keyword while editing
-Original Message- From: Thomas Michael Engelke [mailto:[EMAIL PROTECTED] Sent: Thursday, November 16, 2006 10:42 AM To: vim-Mailingliste Subject: Upcase every keyword while editing Hello! I am looking for a way to mimic a functionality I've seen in the editor ED4Win (http://www.softasitgets.com/). What I want to do is to automagically upcase every written word that is considered a keyword. I program in Progress 4GL and use the syntax file from the gvim standard distribution. Theoretically, in my understanding of the problem, I would need to write a function to check the word before the cursor against the keywords list and map this one to something. Usually, I leave the boundaries of a keyword by using either space, tab, :, ,, enter or .. So I would have to map this function to every of those keys in insert mode. That is exactly why I wrote: SrchRplcHiGrp - Search and replace based on a syntax highlight group http://www.vim.org/script.php?script_id=848 Put your cursor on the word highlighted the colour that you want uppercased. :SRChooseHiGrp Or :SRChooseHiGrp! Visually select the range you want (or ggVG for whole file): :','SRHiGrp The defaults selected will uppercase the words. I wrote it mainly since I work with SQL and like the keywords uppercased. But you can do anything with Vim's regex to the matches. HTH, Dave
Problem with Quickfix and Latex
Pals,
I have a recurrent problem with quickfix and Latex. I use the
tex.vim compiler by Srinath Avadhanula. I tried both the 2003 version
contained in the last LatexSuite plugin
http://www.vim.org/scripts/script.php?script_id=475
and version '2006-03-20 09:45:45Z'. Same result.
The problem: After make, when there is an error, it jumps to an
unwanted file. This is so because the efm variable is not correctly set.
For example, after deleting a '$' in a file 'file.tex' and doing
make, I read this in the quickfix window:
##
|| ) (./file.aux)
/usr/share/texmf/tex/generic/xypic/xy.sty| error| Missing $
inserted. $ \lambda =1$) and identifying the upper $2\times 2$ matrix in
##
Then, a new buffer is loaded with the file xy.sty, and vim tries
to go to the line in that line (then it goes to the last).
It seems that the problem is that the string
'/usr/share/texmf/tex/generic/xypic/xy.sty' was not deleted by efm.
The only line in file 'file.log' contains a reference to xy.sty
is in this block:
...
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
\minCDarrowwidth=\dimen119
)
(/usr/share/texmf/tex/generic/xypic/xy.sty
(/usr/share/texmf/tex/generic/xypic/xy.tex Bootstrapíng: catcodes,
docmode,
(/usr/share/texmf/tex/generic/xypic/xyrecat.tex)
(/usr/share/texmf/tex/generic/xypic/xyidioms.tex)
...
This is the value of the efm variable:
#
set efm=
if !g:Tex_ShowallLines
call s:IgnoreWarnings()
endif
setlocal efm+=%E!\ LaTeX\ %trror:\ %m
setlocal efm+=%E!\ %m
setlocal efm+=%+WLaTeX\ %.%#Warning:\ %.%#line\ %l%.%#
setlocal efm+=%+W%.%#\ at\ lines\ %l--%*\\d
setlocal efm+=%+WLaTeX\ %.%#Warning:\ %m
exec 'setlocal efm+=%'.pm.Çl.%l\ %m'
exec 'setlocal efm+=%'.pm.Çl.%l\ '
exec 'setlocal efm+=%'.pm.Ç\ \ %m'
exec 'setlocal efm+=%'.pm.Ç%.%#-%.%#'
exec 'setlocal efm+=%'.pm.Ç%.%#[]%.%#'
exec 'setlocal efm+=%'.pm.Ç[]%.%#'
exec 'setlocal efm+=%'.pm.Ç%.%#%[{}\\]%.%#'
exec 'setlocal efm+=%'.pm.Ç%.%#%m'
exec 'setlocal efm+=%'.pm.Ç\ \ %m'
exec 'setlocal efm+=%'.pm.'GSee\ the\ LaTeX%m'
exec 'setlocal efm+=%'.pm.'GType\ \ H\ return%m'
exec 'setlocal efm+=%'.pm.'G\ ...%.%#'
exec 'setlocal efm+=%'.pm.'G%.%#\ (C)\ %.%#'
exec 'setlocal efm+=%'.pm.'G(see\ the\ transcript%.%#)'
exec 'setlocal efm+=%'.pm.'G\\s%#'
exec 'setlocal efm+=%'.pm.Ó(%*[^()])%r'
exec 'setlocal efm+=%'.pm.'P(%f%r'
exec 'setlocal efm+=%'.pm.'P\ %\\=(%f%r'
exec 'setlocal efm+=%'.pm.'P%*[^()](%f%r'
exec 'setlocal efm+=%'.pm.'P(%f%*[^()]'
exec 'setlocal efm+=%'.pm.'P[%\\d%[^()]%#(%f%r'
if g:Tex_IgnoreUnmatched !g:Tex_ShowallLines
setlocal efm+=%-P%*[^()]
endif
exec 'setlocal efm+=%'.pm.'Q)%r'
exec 'setlocal efm+=%'.pm.'Q%*[^()])%r'
exec 'setlocal efm+=%'.pm.'Q[%\\d%*[^()])%r'
if g:Tex_IgnoreUnmatched !g:Tex_ShowallLines
setlocal efm+=%-Q%*[^()]
endif
if g:Tex_IgnoreUnmatched !g:Tex_ShowallLines
setlocal efm+=%-G%.%#
endif
#
How can I solve this?
Thanks a lot,
Luis.
Re: XML file creation and validation based on schema]
On czw lis 16 2006, vim@vim.org wrote: Hi, Is it possible to create and validate xml files, based on xml schema (xsd files) in vim. The features, like automatic closing tags, automatic insertion of mandatory tags, suggestion of tags, based on the schema etc will be very useful. Is there any plugins available to do this.? No. Only through DTD (in fact through data file created from DTD, if you know tools to process Schema files...). m.
