Win32 vim.exe blows up reading from stdin
Hello all, Somewhere between v7.0.118 and v7.0.131 Vim started blowing up when started with a - to read from stdin. Ex. vim -u NONE - If no one else is having this problem I'll supply more compile/environment info. I use gvim as a less program all the time so I know this wasn't happening earlier. Thanks, - Dave
Re: Convert2HTML Again
On 12/10/06, Benji Fisher [EMAIL PROTECTED] wrote: span class=bar (text) /span in the body, while the non-CSS version will have something like font color=#EEE bgcolor=333 (text) /font and now the CSS version is easier to read. Yes I see, If i had written this from scratch i would have not included font tags atall because they are depricated. I was just respecting the existing code to be honest. This would have to be something you take up with the original writer(?) or Bram(?). I'll check the syntax error highlight for you too. Will probably get a chance at the weekend. Thanks for your time. Best Regards Edd
Patch 7.0.132
Patch 7.0.132 (after 7.0.130)
Problem:Win32: Crash when Vim reads from stdin.
Solution: Only use mch_nodetype() when there is a file name.
Files: src/fileio.c
*** ../vim-7.0.131/src/fileio.c Tue Oct 10 18:43:50 2006
--- src/fileio.cThu Oct 12 20:50:35 2006
***
*** 416,435
msg_scroll = msg_save;
return FAIL;
}
- }
- #endif
! #if defined(MSDOS) || defined(MSWIN) || defined(OS2)
! /*
! * MS-Windows allows opening a device, but we will probably get stuck
! * trying to read it.
! */
! if (!p_odev mch_nodetype(fname) == NODE_WRITABLE)
! {
! filemess(curbuf, fname, (char_u *)_(is a device (disabled with
'opendevice' option), 0);
! msg_end();
! msg_scroll = msg_save;
! return FAIL;
}
#endif
--- 416,435
msg_scroll = msg_save;
return FAIL;
}
! # if defined(MSDOS) || defined(MSWIN) || defined(OS2)
! /*
!* MS-Windows allows opening a device, but we will probably get stuck
!* trying to read it.
!*/
! if (!p_odev mch_nodetype(fname) == NODE_WRITABLE)
! {
! filemess(curbuf, fname, (char_u *)_(is a device (disabled with
'opendevice' option), 0);
! msg_end();
! msg_scroll = msg_save;
! return FAIL;
! }
! # endif
}
#endif
*** ../vim-7.0.131/src/version.cTue Oct 10 21:56:37 2006
--- src/version.c Thu Oct 12 21:13:34 2006
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 132,
/**/
--
hundred-and-one symptoms of being an internet addict:
31. You code your homework in HTML and give your instructor the URL.
/// 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: Win32 vim.exe blows up reading from stdin
Dave Roberts wrote: Somewhere between v7.0.118 and v7.0.131 Vim started blowing up when started with a - to read from stdin. Ex. vim -u NONE - If no one else is having this problem I'll supply more compile/environment info. I use gvim as a less program all the time so I know this wasn't happening earlier. I'll fix it. -- hundred-and-one symptoms of being an internet addict: 30. Even though you died last week, you've managed to retain OPS on your favorite IRC channel. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
RE: Why not commit runtime files?
A.J.Mechelynck wrote: Suresh Govindachar wrote: Hello, I have just found out that while the runtime directory is periodically updated on the ftp site, it is not committed to the cvs repository. What is the reason for not committing runtime files into cvs? I see some comment about runtime files not having patches; but committing to cvs does not require creating a patch; one can just command cvs to commit a local directory to the repository. I don't know exactly; but I think the various repositories (rsync, FTP, CVS, SVN) are not maintained by the same people. I think CVS and SVN use the FTP site as a master with automated updates (but not every day), so that the FTP updates trickle down to the CVS/SVN repositories after a delay of a few days or weeks. I thought Bram (and only Bram) maintained the cvs repository; and that all other repositories, such as svn, are copies of the cvs repository. Anyway, even though the .c and .h files in the svn repository change, the runtime files in the svn repository are not changing -- at least netrw seems to be stuck at v98. --Suresh
Re: Why not commit runtime files?
A.J.Mechelynck wrote: I see some comment about runtime files not having patches; but committing to cvs does not require creating a patch; one can just command cvs to commit a local directory to the repository. I don't know exactly; but I think the various repositories (rsync, FTP, CVS, SVN) are not maintained by the same people. I think CVS and SVN use the FTP site as a master with automated updates (but not every day), so that the FTP updates trickle down to the CVS/SVN repositories after a delay of a few days or weeks. That used to be the case (before vim 7). I was the latest person who pushed the patches through to cvs. I got them the same time everyone else did, and had scripts that would push them through to CVS. Now Bram is maintaining CVS himself, which is probably why the runtime files don't get maintained regularly, since he's not the one that regularly does that. I had the same kind of problem when maintaining CVS for vim 6. I tried updating the runtime files, and would occasionally get a patch that wouldn't apply, because something did get patched in a runtime file. Dave
Re: Why not commit runtime files?
I don't know exactly; but I think the various repositories (rsync, FTP, CVS, SVN) are not maintained by the same people. I think CVS and SVN use the FTP site as a master with automated updates (but not every day), so that the FTP updates trickle down to the CVS/SVN repositories after a delay of a few days or weeks. Only source files and some runtime files maintained directly by Bram. Updates send by other authors are rarely or never committed to CVS. SVN is synchronised only with CVS. Yes, it is a pity runtime files are not updated in CVS :( Theoretically I (and probably other people) could rsync directory according to your tip but it would wreak havoc in CVS structure... m.
Re: Why not commit runtime files?
David Brown wrote: [...] I had the same kind of problem when maintaining CVS for vim 6. I tried updating the runtime files, and would occasionally get a patch that wouldn't apply, because something did get patched in a runtime file. Dave Yeah. Nowadays I rsync my runtime files from time to time; and now and then there is a hunk for a runtime file that gets rejected in a patch. Then I compare the file with the patch text and usually it's because the patch is already included in the file I have. Not really a problem. Best regards, Tony.
Re: vim and 64bit xp
Brian Krusic wrote: Thanks fo rthe reply. Still no shell extension. I did the regedit approach. Any ideas? Is Gvimext.dll in a directory in your PATH? Check it at the dos-box prompt: echo %PATH% or in Vim: :echo $PATH If it isn't, you can set it in (IIRC) Control Panel - System - Advanced - Environment variables The Dos/Windows PATH is a semicolon-separated list of directories; the directory containing that DLL may be either the same as for gvim.exe (usually something like C:\Program Files\Vim\vim70) or a gvimext subdirectory of that (I'm not on Windows at the moment and can't check). Best regards, Tony.
[Fwd: Re: vimshell feature? [oops]]
Apparently the second try didn't succeed any better than the first one. This way you (David) won't need to try a third time. I'm sending it to vim-dev rather than vim@ because IMHO it's more on-topic for that list. Original Message Subject: Re: vimshell feature? [oops] Date: Thu, 12 Oct 2006 17:47:21 -0700 (PDT) From: David Thompson [EMAIL PROTECTED] To: A.J.Mechelynck [EMAIL PROTECTED] oops, I meant to send that vim@vim.org ... stand by as I resend ... --- David Thompson [EMAIL PROTECTED] wrote: --- A.J.Mechelynck [EMAIL PROTECTED] wrote: David Thompson wrote: I've been playing with ':vimshell' command from http://www.wana.at/vimshell/ and was wondering what the current opinion is about officially adding a shell feature into vim. Please please, Bram, can you add this to vim? (*ducks for cover*) I think you're right to duck for cover: AFAIK, Bram's standing on that matter has not changed for years and is not going to change overnight: see :help design-not. Yeah, I recall some of that history. But Vim windows are a viewport onto a buffer, and just because the buffer is being filled with text from shell commands, and I can input commands into that buffer that are executed by a shell, well ... It just seems like vim is becoming extremely powerful and customizable enough that *it should be able* to handle the simple thought extension that a window is a viewport onto a shell (or debugger) session, kinda like the thought process of what this vimshell patch tries to do. Besides, Bram's argument is antiquated. Vim has become bloated to the point of interfacing with everything else under the sun, such as perl, python, c-scope ... and, mind you, there exists feature.h which can DISABLE these cool bloated things which are pet projects and wonderful features for their believers. So, why not interface vim with a shell? Then, why not add a #define to feature.h to disable this feature? It seems this argument of pinciple is becoming abused. For those who spend all day interfacing to perl, python, cscope, etc, it is a Good Thing for vim to interface to their environment. I see no difference in this argument in why the shell and the debugger don't qualify for such interfaces. (*runs for cover again*) -- David Personally I don't feel any need to run bash or cmd inside Vim rather than as a distinct process. This feeling of mine (or lack of one) may be related to the fact that I can open any number of program windows (gvim, a shell, a browser, a mail client, ...) in a Windows or X11 session, and that even in the non-X runlevels of Linux I can have up to six virtual consoles in parallel (so I can run Vim in, say, /dev/tty2, and a shell in /dev/tty3, and switch from one to the other by [Ctrl-]Alt-F2 or [Ctrl-]Alt-F3. Also, I'm not convinced of the portability of shell embedding between Unix and Windows. Is it worth trying to add a complex feature of dubious utility if it cannot even be reconciled between the two major Vim platforms? (And I'm not forgetting the Mac but I don't know it well enough.) As an unofficial patch (or set of patches), I'm not against it as long as I don't have to maintain or compile it myself; but I don't see the usefulness of having it in the official distribution (where Bram would have to maintain it if ever its maintainer disappeared). Best regards, Tony.
Re: ctags for new Vim scripting features
On 2006-10-11, Hari Krishna Dara [EMAIL PROTECTED] wrote: On Wed, 11 Oct 2006 at 10:30pm, David Fishburn wrote: From: Hari Krishna Dara [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 9:18 PM Is anyone working or planning to work on enhancing exuberant ctags to recognize the dict and autoloaded functions ? Does this require modifying the code, or just some regex patterns? What language elements are you referring to? That would allow me to create a test case. What I see is that ctags fails to extract the right function name, in the below syntax (it basically reports dict and plug as functions): function! dict.func() function! plug#func() In my new plugins, most of the functions are these so I hardly get to make use of ctags. As a workaround, you could create a ~/.ctags file and put something like this line in it: --regex-Vim=/^[ \t]*function!?[ \t]+([a-zA-Z0-9_\.#]*)\(/\1/f,function/ That will include the dict. and plug# prefixes in the tag. If you want only the func portion, that's easy to fix. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Wireless Division | Spokane, Washington, USA
Re: Paren highlighting and jump to
Meino Christian Cramer wrote: Hi, (I am vim 7.0.131 on the console only on a recent gentoo Linux system) I looked into :h paren but found nothing appropiate... Currently my vim highlights matching parens. This is nice as long the corrosponding paren are on different lines or at least not grouped like this: (x) Additionally my cursor changes its color depending on whether it is in insert or normal mode. When the cursor is at the position of the x in the above example, confusion arises, since so much color on one place is...confusing. I would like to make the cursor to jump shortly to the other paren as long there is nothing typed in. Hi, I thing what you're looking for is showmatch (:h showmatch), you can set it with :set showmatch or :set sm Cheers, Wolfgang
Re: syntax highlighting - a separate colour for each word
On 10/12/06, Eric Smith [EMAIL PROTECTED] wrote: Yes exactly. And the script must dynamically apply say blue for the word: January and red for the word apples and yellow for the word Monday wherever these words occur. On 11/10/06, Yakov Lerner [EMAIL PROTECTED] wrote: On 10/11/06, Yakov Lerner [EMAIL PROTECTED] wrote: On 10/11/06, Eric Smith [EMAIL PROTECTED] wrote: Like I want all instances of a word in a file to have its own color. Amy one done something like that? Like this : match ToDo /\word\/ ? Yakov Or else, did you mean as many colors as there are different words in the file ? Yes exactly. Heh. But won't you have problem with number of available colors vs number of different words in the file ? Number of different words in the file can be in thousands. What do you do when number of words number of colors ? Yakov
Re: Local scope ?
On Tue, Oct 03, 2006 at 10:00:51PM -0700, Hari Krishna Dara wrote: Yegappan already answered your question. However, in case you want to do the whole of it in the same function, I recommend the below pattern: let _ic = ignorecase set noic try do something finally let ignorecase = _ic endtry So far, I have been too lazy to use try/finally/endtry. I guess the point is that if the do something generates an error, then the option is still restored? (Of course, my vim scripts never generate errors. ;) Another refinement is to avoid setting the global option. Use l:ignorecase to access (read and write) the local value of the option. If the option happens to be global, I do not think using the l: prefix will cause any problems. HTH --Benji Fisher
Re: Auto-guessing file encoding and integration with Vim (works for Latin1, GBK, and Big5 now)
On Sat, Oct 07, 2006 at 12:37:33AM +0800, Yongwei Wu wrote: This is a report of what I have already achieved. If you are dealing with more encodings than the fileencodings option can handle, esp. if you read and write Simplified and Traditional Chinese, please read on. I write English almost exclusively, so this is not something I will use. If this is useful for others (and I expect it will be) then I suggest posting it as a script at http://www.vim.org/scripts/index.php . In the description, you can post a link (as snipped below) to tellenc. Perhaps you can package your vim functions as a plugin so that they can be used without adding anything to the vimrc file. :help write-plugin HTH --Benji Fisher
Re: BOF
On Fri, Oct 06, 2006 at 02:49:57AM -0500, Bill McCarthy wrote: Hello Vim List, I listened to Bram's BOF this past weekend. I still don't know what BOF means. From Wikipedia: BoF is an acronym for: Basic Oxygen Furnace Birds of a Feather beginning of file Body-on-frame Breath of Fire [snip] I would guess Birds of a Feather. Which is it? Yes, I think that is right. It is used in the aphorism Birds of a feather flock together. At a large meeting, a group of people with a common interest (or some other commonality) may be referred to as BOF and hold a BOF session. HTH --Benji Fisher
Re: visual block calculator
* El 11/10/06 a las 17:18, Benji Fisher chamullaba:
On Thu, Sep 28, 2006 at 02:30:37PM -0300, Luis A. Florit wrote:
Pals: I want to evaluate a block selection with formulas to its value.
So, if you have 2 lines like:
home roof 89.4 + 76 home roof
home roof 17 + 13.3 home roof
I would like to replace 89.4 + 76 by 165.4 and 17 + 13.3 by 30.3
by selecting the block with the formulas and applying some command
sequence (for example, using perl, bc, python, etc).
Of course, I want this for arbitrary aritmetic formulas.
Thanks!
Luis.
On Linux, I can use the bc command like this:
:s/\d[0-9 .+*/-]*/\=substitute(system('echo ' . submatch(0) . ' | bc'), '\n',
'', 'g')
That is,
:s/pat/\=expr
where my pattern pat is '\d[0-9 .+*/-]*', a first attempt at capturing
the sort of arithmetic string you have in mind. Inside expr,
submatch(0) is replaced by the matched text, such as 89.4 + 76. Then
system('echo 89.4 + 76 | bc')
will pass the string to bc as stdin and return the result. I wrapped
this in substitute() to strip off the trailing newline character.
It will be easier to read and maintain if you do something like
this (untested):
fun! EvalMath(str)
let res = system('echo ' . a:str . ' | bc')
return substitute(res, '\n', '', 'g')
endfun
:s/\d[0-9 .+*/-]*/\=EvalMath(submatch(0))
HTH --Benji Fisher
Benji,
I only received this today, October 12. I've already found a solution,
that is quite similar to yours, even with the newline trick. I put it as a
vimtip a couple of weeks ago: http://www.vim.org/tips/tip.php?tip_id=1349
I found the mappings I made very handy also that, for example,
computes math expressions in visual block selections and replaces
(or adds) the computation, or adds a block of math expressions.
These maps use Chip's vis.vim plugin #1195.
Below is the 'last version' of the tip, with comments for using
each map. Just add the code to your .vimrc.
Thanks, and sorry for the delay,
Luis.
==
let g:MyCalcPresition = 2
function MyCalc(str)
return system(echo \'scale= . g:MyCalcPresition . ; print . a:str .
\' | bc -l)
endfunction
Use \C to replace a (block of) visual math expression(s) by the value of the
computation:
vmap silent leaderc :B s/.*/\=MyCalc(submatch(0))/cr
Same in normal mode, for the whole current line
map silent leaderc :s/.*/\=MyCalc(submatch(0))/cr
With \C= no replace, but add the result
vmap silent leaderc= :B s/.*/\=submatch(0) . = .
MyCalc(submatch(0))/cr
Same in normal mode, for the whole current line
map silent leaderc= :s/.*/\=submatch(0) . = . MyCalc(submatch(0))/cr
Try: :B s/.*/\=MyCalc(1000 - . submatch(0))/
The concatenation is important, since otherwise it will try
to evaluate things like in :echo 1000 - ' 1748.24'
vmap leaderc+ :B s/.*/\=MyCalc(' +' .
submatch(0))/C-LeftC-LeftC-LeftLeft
vmap leaderc- :B s/.*/\=MyCalc(' -' .
submatch(0))/C-LeftC-LeftC-LeftLeft
With \Cs you add a block of expressions, whose result appears in the command
line
vmap silent leaderct y:echo MyCalc(substitute(@0, *\n,+,g))cr
Try: :MyCalc 12.7 + sqrt(98)
command! -nargs=+ MyCalc :echo MyCalc(args)
Re: number of folds in foldtext
On Sun, Oct 08, 2006 at 05:49:38PM +0200, Eric Smith wrote: Is it possible for foldtext to show the number of the fold block. For example there are n paragraphs in a document and folding is by expression defined as a blank line. I want the number of the paragraph to show in the foldtext. This is just proof of concept: set foldtext=MyFoldText() function MyFoldText() let parcnt = 0 execute v:foldstart . , . v:foldend . g/^$/let parcnt += 1 return parcnt . paragraphs endfunction You might want to return something like substitute(foldtext, :, , . parcnt . paragraphs:, ) (untested). HTH --Benji Fisher
Re: syntax highlighting - a separate colour for each word
On 12/10/06, Yakov Lerner [EMAIL PROTECTED] wrote: Or else, did you mean as many colors as there are different words in the file ? Yes exactly. Heh. But won't you have problem with number of available colors vs number of different words in the file ? Number of different words in the file can be in thousands. What do you do when number of words number of colors ? Its not prose, so there are not that many unique words. You could specify that the script processes only the first n words. -- Eric Smith
Re: Paren highlighting and jump to
From: Wolfgang Schmidt [EMAIL PROTECTED] Subject: Re: Paren highlighting and jump to Date: Thu, 12 Oct 2006 10:45:49 +0200 Meino Christian Cramer wrote: Hi, (I am vim 7.0.131 on the console only on a recent gentoo Linux system) I looked into :h paren but found nothing appropiate... Currently my vim highlights matching parens. This is nice as long the corrosponding paren are on different lines or at least not grouped like this: (x) Additionally my cursor changes its color depending on whether it is in insert or normal mode. When the cursor is at the position of the x in the above example, confusion arises, since so much color on one place is...confusing. I would like to make the cursor to jump shortly to the other paren as long there is nothing typed in. Hi, I thing what you're looking for is showmatch (:h showmatch), you can set it with :set showmatch or :set sm Cheers, Wolfgang Hi Wolfgang! oh YES! (this is a classical flat hand against my fore head-effect)! Once one sees the solution, it is totally unclear, why one has asked for it... :) Thanks a lot ! Have a nice weekend! mcc
Re: Problem in dos runtime on Vim FTP
Bill McCarthy wrote: On Wed 11-Oct-06 3:36pm -0600, Bram Moolenaar wrote: The script that fixes the permissions was missing the autoload directory. It's fixed now. Sorry for the inconvenience. Thanks for the quick fix! Doing a 'ls -lR' on the FTP runtime, I've noted: the following reasonable results: All directories have permission 'drwxrwsr-x'. Nearly all files now have permission '-rw-r--r--'. All '.sh' files are executable. and the following, perhaps, inconsistent results: All '.pl' files are executable except: ./doc/vim2html.pl ./dos/doc/vim2html.pl ./dos/tutor/tutor.pl ./tutor/tutor.pl All '.awk' files are executable except: ./doc/makehtml.awk ./doc/maketags.awk ./dos/doc/makehtml.awk ./dos/doc/maketags.awk All file without extensions are NOT executable except: ./tools/dos/ref ./tools/dos/vim132 ./tools/dos/vimm ./tools/ref ./tools/vim132 ./tools/vimm These files should be executable: ./doc/vim2html.pl ./dos/doc/vim2html.pl ./doc/makehtml.awk ./doc/maketags.awk ./dos/doc/makehtml.awk ./dos/doc/maketags.awk Otherwise it's OK. tutor.pl is the Polish tutor file, not Perl! -- Give a man a computer program and you give him a headache, but teach him to program computers and you give him the power to create headaches for others for the rest of his life... R. B. Forest /// 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: Vim7: Spell checking not working with ft=mail
I'm using Vim with a filetype of mail right now, and it's able to do on-the-fly spell-checking :) A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? HTH! Tom Purl Hi, I'm using Vim 7.0.10 and wanted to try out the new on-the-fly spell checking. It works great, but as soon as I set ft=mail, it stops working (no highlighting anymore). Any clues why? Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/
vim and 64bit xp
Hi, New to vim project as I didn't want to install a whole subsystem (cygwin) just to use vi. Anyway, I installed vim on a 64 bit XP env (Opteron, not IA64) and then copied 64 bit vim binaries/files (x64) from georgevreilly.com/vim. But I don't see the shell extensions but can run it manually. Any tips or ideas? Thanks in advance, Bri-
Re: Planet Vim
Are there enough people out there users/developers that blog about Vim? I'm sure that you could find a critical mass. If so, it would be great to have a planet vim to aggregate these blog posts. I don't see why planet web sites still exist. I can basically recreate this functionality using an rss-aggregating web site such as Bloglines. You can search for Vim-related blogs using their blog search engine, and then track your favorite Vim-related sites in a Vim folder. I'm not trying to be negative - I just wanted to save you some time if the functionality that I described is what you require. HTH! Tom Purl
Re: Vim7: Spell checking not working with ft=mail
On Thu, Oct 12, 2006 at 02:40:48PM -0500, Tom Purl wrote: A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I read about that; however, mail.vim doesn't seem to do that (I could be wrong here). I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? No, I wasn't quoting anything... Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/ pgpIVVucbYnYs.pgp Description: PGP signature
Re: Vim7: Spell checking not working with ft=mail
I'm using Vim with a filetype of mail right now, and it's able to do on-the-fly spell-checking :) A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? Whoops, it's too bad that Vim doesn't yet come with on-the-fly grammar checking :) here's what I meant to say in the second-to-last sentence in the above paragraph: I think that the mail filetype turns off spell checking if what you're typing is after an arrow (, , etc.). HTH! Tom Purl Hi, I'm using Vim 7.0.10 and wanted to try out the new on-the-fly spell checking. It works great, but as soon as I set ft=mail, it stops working (no highlighting anymore). Any clues why? Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/
Re: Vim7: Spell checking not working with ft=mail
On Thu, Oct 12, 2006 at 02:40:48PM -0500, Tom Purl wrote: A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I read about that; however, mail.vim doesn't seem to do that (I could be wrong here). I think I've checked this before and I'm pretty sure that mail.vim does pick and choose where it spell-checks. I know that on my version of Vim (Windows 7.0), new text is spell-checked while text after an arrow is not. I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? No, I wasn't quoting anything... Could you post an example of the text that isn't being spell-checked?
Re: Vim7: Spell checking not working with ft=mail
[EMAIL PROTECTED] wrote: On Thu, Oct 12, 2006 at 02:40:48PM -0500, Tom Purl wrote: A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I read about that; however, mail.vim doesn't seem to do that (I could be wrong here). I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? No, I wasn't quoting anything... Well, syntax/mail.vim *does* have a lot of NoSpell cluster referrals in it. What part of the email message are you referring to? Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. Regards, Chip Campbell
Re: Planet Vim
On Thu, 12 Oct 2006 14:45:31 -0500 (CDT) Tom Purl [EMAIL PROTECTED] wrote: Are there enough people out there users/developers that blog about Vim? I'm sure that you could find a critical mass. If so, it would be great to have a planet vim to aggregate these blog posts. I don't see why planet web sites still exist. I can basically recreate this functionality using an rss-aggregating web site such as Bloglines. You can search for Vim-related blogs using their blog search engine, and then track your favorite Vim-related sites in a Vim folder. I'm not trying to be negative - I just wanted to save you some time if the functionality that I described is what you require. You are right. I have another idea :-) Lets just mention all vim related blogs in this thread and then people can add them to their rss aggregators themself. -- Kim Schulz| Private : http://www.schulz.dk [EMAIL PROTECTED] | Business: http://www.devteam.dk +45 5190 4262 | Sparetime: http://www.fundanemt.com
Re: Vim7: Spell checking not working with ft=mail
On Thu, Oct 12, 2006 at 04:18:21PM -0400, Charles E Campbell Jr wrote: Well, syntax/mail.vim *does* have a lot of NoSpell cluster referrals in it. You're right, I just looked at ftplugins/mail.vim. What part of the email message are you referring to? Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. I'm talking about the body, i.e. I'm just starting to write stuff at the top without any headers. Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/ pgpCxw508y8wk.pgp Description: PGP signature
Re: Vim7: Spell checking not working with ft=mail
On Thu, Oct 12, 2006 at 03:01:04PM -0500, Tom Purl wrote: I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? No, I wasn't quoting anything... Could you post an example of the text that isn't being spell-checked? Sure, here goes the whole file: SNIP --- this is a tset. SNIP --- when ft=mail is off, this is marked blue because it doesn't start with a capital 't' and tset is red, as it is obviously the victim of a typographic error. With ft=mail on nothing shows up. Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/ pgpgJ89wK0GG5.pgp Description: PGP signature
Re: Vim7: Spell checking not working with ft=mail
[EMAIL PROTECTED] wrote: On Thu, Oct 12, 2006 at 04:18:21PM -0400, Charles E Campbell Jr wrote: Well, syntax/mail.vim *does* have a lot of NoSpell cluster referrals in it. You're right, I just looked at ftplugins/mail.vim. What part of the email message are you referring to? Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. I'm talking about the body, i.e. I'm just starting to write stuff at the top without any headers. Leslie Ah, there's your problem. In an email, everything until the first empty line is headers. Add the following 4 lines at the top of your email: From: To: Subject: (i.e., 3 nonempty lines and one empty line). You may add more headers, and/or fill them in. Then your body text will be after the first empty line, and it will not be regaded as headers. Best regards, Tony.
Re: Vim7: Spell checking not working with ft=mail
What part of the email message are you referring to? Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. I'm talking about the body, i.e. I'm just starting to write stuff at the top without any headers. Leslie Ah, there's your problem. In an email, everything until the first empty line is headers. Add the following 4 lines at the top of your email: From: To: Subject: (i.e., 3 nonempty lines and one empty line). You may add more headers, and/or fill them in. Then your body text will be after the first empty line, and it will not be regaded as headers. That's weird. I use Gvim to edit web mail via the Mozex extension. I can place this is a tset at line one in my message after executing the `set filetype=mail` command, and it will be spell-checked. I don't have to include any headers or empty lines or anything else like that.
Re: Vim7: Spell checking not working with ft=mail
On 2006-10-12, A.J.Mechelynck [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: On Thu, Oct 12, 2006 at 04:18:21PM -0400, Charles E Campbell Jr wrote: Well, syntax/mail.vim *does* have a lot of NoSpell cluster referrals in it. You're right, I just looked at ftplugins/mail.vim. What part of the email message are you referring to? Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. I'm talking about the body, i.e. I'm just starting to write stuff at the top without any headers. Leslie Ah, there's your problem. In an email, everything until the first empty line is headers. I don't believe that's true in this case. I hardly ever include any headers in the buffer when I'm editing e-mail messages, and syntax highlighting and spelling both work fine. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Wireless Division | Spokane, Washington, USA
Re: vim and 64bit xp
Brian Krusic wrote: Hi, New to vim project as I didn't want to install a whole subsystem (cygwin) just to use vi. Anyway, I installed vim on a 64 bit XP env (Opteron, not IA64) and then copied 64 bit vim binaries/files (x64) from georgevreilly.com/vim. But I don't see the shell extensions but can run it manually. Any tips or ideas? Thanks in advance, Bri- - You may run the install program (which is normally installed in the same directory as your Vim executable) to add Edit with gvim functionality to Windows Explorer. This ought to work out of the box, but if it doesn't, you can add the same functionality by editing the Windows registry, see :help install-registry. - You can create a shortcut (on your desktop or elsewhere) pointing to your gvim.exe program if you want to be able to start it by clicking an icon or by dropping a file on an icon, rather than running gvim.exe from the dos-box prompt or the Windows Execute... prompt. To do that, click right wherever it is that you want to create that icon, then select New - Shortcut; the rest ought to be obvious. Best regards, Tony.
Re: Vim7: Spell checking not working with ft=mail
On 2006-10-12, Charles E Campbell Jr [EMAIL PROTECTED] wrote: Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. It checks spelling in Subject:, too, but not in the rest of the headers. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Wireless Division | Spokane, Washington, USA
Re: Vim7: Spell checking not working with ft=mail
Tom Purl wrote: [...] That's weird. I use Gvim to edit web mail via the Mozex extension. I can place this is a tset at line one in my message after executing the `set filetype=mail` command, and it will be spell-checked. I don't have to include any headers or empty lines or anything else like that. Hm. Apparently you're right. By doing the following: :new :setl ft=mail :setl spell a this is a tset with a space at the end of the line, I get a blue curly underline under this and a red one under tset. Do you have spell checking on? Normally yes, but still... what is the reply to :verbose setlocal spell? when you do it (with the question mark) in a window where the 'filetype' is set to mail but you don't see spell-check highlights? Unless you yourself set 'spell' on, e.g. by having set spell in your vimrc, Vim will by default do no spell-checking at all. Best regards, Tony.
Re: Planet Vim
I don't see why planet web sites still exist. I can basically recreate this functionality using an rss-aggregating web site such as Bloglines. You can search for Vim-related blogs using their blog search engine, and then track your favorite Vim-related sites in a Vim folder. I use Google Reader, to subscribe to individual feeds, or planets ie: planet.gnome, etc. I haven't heard of bloglines, but I will give it a look. What I find easy about planets, is that you can just subscibe to it and get all the good stuff at once, while if I went through searching for tags 'vim' etc, I would have to hand-pick them myself, 'cause some RSS feeds are not user oriented, like a linux distro, management system may provide info for an vim meant only for maintainers etc as an example. Plus, users who don't have a web based RSS aggregator, can just browse it for fun :) I'm not trying to be negative - I just wanted to save you some time if the functionality that I described is what you require. I'm glad that you mentioned bloglines and I can give it a look. Can it do the stuff that I mentioned above? You are right. I have another idea :-) Lets just mention all vim related blogs in this thread and then people can add them to their rss aggregators themself. -- Kim Schulz| Private : http://www.schulz.dk [EMAIL PROTECTED] | Business: http://www.devteam.dk +45 5190 4262 | Sparetime: http://www.fundanemt.com -- Panos Laganakos
vimshell feature?
I've been playing with ':vimshell' command from http://www.wana.at/vimshell/ and was wondering what the current opinion is about officially adding a shell feature into vim. Please please, Bram, can you add this to vim? (*ducks for cover*) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: vimshell feature?
David Thompson wrote: I've been playing with ':vimshell' command from http://www.wana.at/vimshell/ and was wondering what the current opinion is about officially adding a shell feature into vim. Please please, Bram, can you add this to vim? (*ducks for cover*) I think you're right to duck for cover: AFAIK, Bram's standing on that matter has not changed for years and is not going to change overnight: see :help design-not. Best regards, Tony.
Re: Planet Vim
--- Panos Laganakos [EMAIL PROTECTED] wrote: I searched the archives, but didn't find any reference to this. Google can't find it either, so therefore it can't exist. Are there enough people out there users/developers that blog about Vim? Personally I don't think so, but one way is to set up the aggregator and see for yourself. It depends how much volume you call 'enough'. I would love to see a planet Vim site, but unfortunately most Vim articles I read tend to be very technical and rather boring. :-( If so, it would be great to have a planet vim to aggregate these blog posts. Absolutely. I don't want to traul the web myself to find those Vim bloggers, if/when they exist. You might also be able to pinch the source code from another OS 'planet' site. All the best, Peter On Yahoo!7 Music: Create your own personalised radio station. http://au.launch.yahoo.com/
VimL and Exuberant tags - Suggestions please
I have taken over maintenance of the VimL exuberant tags component.
For the vim plugin writers, are there any outstanding bugs or new feature
requests you have for ctags.exe?
Hari just mentioned Vim7 introduces some additional syntax items to function
names:
function mydict.len() dict
endfunction
function autoloadFunc#subdirname#Funcname()
endfunction
Support for this has been added to the next version of ctags (possibly 5.7).
I noticed a bug in variables which shows up in Vim7, since we introduced the
for/endfo construct. Ctags starts generating variable tags for tags that
are within functions after encountering an endfo since the short form for
a endfunction is endf.
- Also fixed in the next version.
These are the items ctags currently flags:
augroup, autocommand groups
function, function definitions
variable, variable definitions
Does it make sense to also identify autocommands?
Or possibly only autocommands if they are outside of an augroup?
When variables are identified we strip off the scope:
let s:ignoreNextCursorMovedI = 0 == ignoreNextCursorMovedI
Should the scope be left on == s:ignoreNextCursorMovedI
Instead of simply grouping everything under variables, should we distinguish
between different types?
let forms#form = {
\ 'title': 'Address Entry Form',
\ 'fields': [],
\ 'defaultbutton': 'ok',
\ 'fieldMap': {},
\ 'hotkeyMap': {},
\ }
Right now this is identified as a variable, should we identify it as a
Dictionary by adding another kind of tag?
What about identifying commands:
command! -nargs=+ Select :call s:DB_execSql(select . q-args)
What about [ion]maps (though we cannot give them a name really, but at least
identifying where they are in the source?
We could also pick up local variables (have this off by default) and produce
something like this:
function! s:DB_runCmd(cmd, sql)
let l:display_cmd_line = 'blah'
let display_shell = 'blah'
endf
Local variables
s:DB_runCmd.display_cmd_line
s:DB_runCmd.display_shell
I am open to suggestions.
If you have suggestions, please provide code snippets so I have examples to
work from.
We can add these tags and leave them on or off by default, so having that
information is useful as well.
At this point the sky is the limit, we can hash out details as we move
forward. Somethings might not be worth the effort.
TIA,
Dave
Re: VimL and Exuberant tags - Suggestions please
David Fishburn wrote:
[...]
When variables are identified we strip off the scope:
let s:ignoreNextCursorMovedI = 0 == ignoreNextCursorMovedI
Should the scope be left on == s:ignoreNextCursorMovedI
How are scopes handled in other languages?
Notice that varname (in a function) is the same as l:varname while varname (in
a script, but outside of all functions) is the same as g:varname. Similarly,
s:funcname is the same as SIDfuncname
If you identify scopes, should or shouldn't ctags qualify the non-global
variables by their script (if script-local) or script and function (if
function-local)? (I see you mention this in a further paragraph. If it's not
too hard to program, it might be useful as an option.)
And how to treat buffer- and window-local variables?
Instead of simply grouping everything under variables, should we distinguish
between different types?
let forms#form = {
\ 'title': 'Address Entry Form',
\ 'fields': [],
\ 'defaultbutton': 'ok',
\ 'fieldMap': {},
\ 'hotkeyMap': {},
\ }
Right now this is identified as a variable, should we identify it as a
Dictionary by adding another kind of tag?
[...]
When a script has
:let var1 = var2
there is nothing there (maybe nothing in the script) which says whether the
variable in question is a simple variable (Number/String), a List, or a
Dictionary. Wouldn't it be a headbreaker to try to label all cases correctly?
Best regards,
Tony.
Re: vimshell feature?
--- A.J.Mechelynck [EMAIL PROTECTED] wrote: David Thompson wrote: I've been playing with ':vimshell' command from http://www.wana.at/vimshell/ and was wondering what the current opinion is about officially adding a shell feature into vim. Please please, Bram, can you add this to vim? (*ducks for cover*) I think you're right to duck for cover: AFAIK, Bram's standing on that matter has not changed for years and is not going to change overnight: see :help design-not. Yeah, I recall some of that history. But Vim windows are a viewport onto a buffer, and just because the buffer is being filled with text from shell commands, and I can input commands into that buffer that are executed by a shell, well ... It just seems like vim is becoming extremely powerful and customizable enough that *it should be able* to handle the simple thought extension that a window is a viewport onto a shell (or debugger) session, kinda like the thought process of what this vimshell patch tries to do. Besides, Bram's argument is antiquated. Vim has become bloated to the point of interfacing with everything else under the sun, such as perl, python, c-scope ... and, mind you, there exists feature.h which can DISABLE these cool bloated things which are pet projects and wonderful features for their believers. So, why not interface vim with a shell? Then, why not add a #define to feature.h to disable this feature? It seems this argument of pinciple is becoming abused. For those who spend all day interfacing to perl, python, cscope, etc, it is a Good Thing for vim to interface to their environment. I see no difference in this argument in why the shell and the debugger don't qualify for such interfaces. (*runs for cover, much faster than before*) -- David __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: gvim start with alternate size (than 80X25)
Luke Vanderfluit wrote: Hi. I'm a great fan of vim and this is the best list! I'm programming java and use konqueror as an explorer. I have set konqueror to open java files with gvim. That's cool. Now I want to set the size of the window that gvim starts in. The default seems to be 80X25. How can I change that. Can I pass some args to gvim on invocation? Thanks. Kind regards. Luke Vanderfluit see :help 'lines' :help 'columns' If you try to set these options to higher values than fit onscreen, Vim will adjust them down until they do. This means that: a) :set lines= columns= will maximize gvim; b) since different fonts can have different sizes, you should set 'guifont' first, and 'lines' and 'columns' afterwards. Note 1: Some console terminals can have their lines x columns geometry changed; others not, but I suppose you wouldn't want to set the same values in gvim and in console vim. You can either: 1) set 'lines' and 'columns' in your gvimrc, so console Vim won't see those lines; 2) bracket them by if has(gui_running) ... endif so that console Vim won't execute them; or even: 3) if has(gui_running) settings for gvim elseif term =~ 'xterm' || term =~ '^vt\d\d\d' settings for xterm and vtnnn elseif term == 'win32' settings for the Dos Box in Windows else do nothing endif Note 2: If you set those options in a vimrc, gvim will remember them until it displays the GUI. Best regards, Tony.
Re: diffoff
On Tue, Oct 10, 2006 at 12:29:51PM +0100, Vigil wrote: The :diffoff command resets the relevant options to their default value. This may be different from what the values were before diff mode was started, the old values are not remembered. Is it on the to-do list to make diffoff restore from previous values rather than default ones, or is there already an option somewhere that toggles the behaviour? AFAIK you have to save the options before starting diff mode and restore them later. At least, that is the answer to the question you asked. Maybe if you give more detail about what you are trying to do, someone can give a more helpful answer. HTH --Benji Fisher
Re: VimL and Exuberant tags - Suggestions please
Hello David,
Can I suggest support for these commands:
:set/setlocal/setglobal
:syntax
:highlight (and maybe :HiLink because it is so commonly used)
Some examples:
set foldmethod=syntax
setlocal formatoptions+=roq
setglobal completeopt-=preview
syntax keyword phpFunction ...
syn match phpIdentifier ...
syn region phpRegion ...
sy cluster phpClTop ...
syntax clear phpMethods
highlight String ...
hi clear Constant ...
hi link Number ...
hi! link Number ...
hi def link Function ...
HiLink Number ...
These are all pretty straightforward to find.
Also, for dictionary functions would it make sense to mark them twice, since
they get a new 'name' if the dictionary is copied to a new variable? For
example:
let foo = { }
function! foo.func1() dict
endfunction
let bar = foo
There is now a function called 'bar.func1()', so maybe func1 should be tagged
as:
Dictionary Functions
foo.bar /^function! foo.bar() dict/
.bar /^function! foo.bar() dict/
I wouldn't mind if mappings could be tagged as well.
Is there or will there be any way to toggle options for the way ctags scans vim
files?
regards,
Peter
--- David Fishburn [EMAIL PROTECTED] wrote:
I have taken over maintenance of the VimL exuberant tags component.
For the vim plugin writers, are there any outstanding bugs or new feature
requests you have for ctags.exe?
Hari just mentioned Vim7 introduces some additional syntax items to function
names:
function mydict.len() dict
endfunction
function autoloadFunc#subdirname#Funcname()
endfunction
Support for this has been added to the next version of ctags (possibly 5.7).
I noticed a bug in variables which shows up in Vim7, since we introduced the
for/endfo construct. Ctags starts generating variable tags for tags that
are within functions after encountering an endfo since the short form for
a endfunction is endf.
- Also fixed in the next version.
These are the items ctags currently flags:
augroup, autocommand groups
function, function definitions
variable, variable definitions
Does it make sense to also identify autocommands?
Or possibly only autocommands if they are outside of an augroup?
When variables are identified we strip off the scope:
let s:ignoreNextCursorMovedI = 0 == ignoreNextCursorMovedI
Should the scope be left on == s:ignoreNextCursorMovedI
Instead of simply grouping everything under variables, should we distinguish
between different types?
let forms#form = {
\ 'title': 'Address Entry Form',
\ 'fields': [],
\ 'defaultbutton': 'ok',
\ 'fieldMap': {},
\ 'hotkeyMap': {},
\ }
Right now this is identified as a variable, should we identify it as a
Dictionary by adding another kind of tag?
What about identifying commands:
command! -nargs=+ Select :call s:DB_execSql(select . q-args)
What about [ion]maps (though we cannot give them a name really, but at least
identifying where they are in the source?
We could also pick up local variables (have this off by default) and produce
something like this:
function! s:DB_runCmd(cmd, sql)
let l:display_cmd_line = 'blah'
let display_shell = 'blah'
endf
Local variables
s:DB_runCmd.display_cmd_line
s:DB_runCmd.display_shell
I am open to suggestions.
If you have suggestions, please provide code snippets so I have examples to
work from.
We can add these tags and leave them on or off by default, so having that
information is useful as well.
At this point the sky is the limit, we can hash out details as we move
forward. Somethings might not be worth the effort.
TIA,
Dave
On Yahoo!7
Caller tones: Replace your ring tone with your favourite sound clip!
http://callertones.yahoo7.mnetcorporation.com/ctonesmailtag
RE: Vim7: Spell checking not working with ft=mail
Has spell been turned off by something? If you enter :verbose set spell? does it tell you if some plugin has been messing with your spell settings FWIW: I tried this and it worked. Opena clean instance of vim, :set spell, insertthis is a tsetesc (observe highlighting), :set ft=mail (observe highlighting still present). Max -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 12, 2006 1:38 PM To: Tom Purl Cc: vim@vim.org Subject: Re: Vim7: Spell checking not working with ft=mail On Thu, Oct 12, 2006 at 03:01:04PM -0500, Tom Purl wrote: I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? No, I wasn't quoting anything... Could you post an example of the text that isn't being spell-checked? Sure, here goes the whole file: SNIP --- this is a tset. SNIP --- when ft=mail is off, this is marked blue because it doesn't start with a capital 't' and tset is red, as it is obviously the victim of a typographic error. With ft=mail on nothing shows up. Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/
