Re: [Cygwin] Configure Detects Incorrect Ruby Version
On Sun, 3 Jun 2007 23:59:54 -0700 Gary Johnson [EMAIL PROTECTED] wrote: On 2007-06-03, Taylor Venable [EMAIL PROTECTED] wrote: Hello, When I compile Vim 7.1.2 under Cygwin (on Windows XP), the configure script incorrectly identifies the version of my Ruby interpreter. The output from the configure script is as follows: checking --enable-rubyinterp argument... yes checking for ruby... /usr/bin/ruby checking Ruby version... too old; need Ruby version 1.6.0 or later But running `ruby --version` yields: ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-cygwin] Any ideas? Thanks. I don't know anything about Ruby and not much about the inner workings of configure, but it appears that the ruby version is being checked at line 881 of vim71/src/configure.in: if $vi_cv_path_ruby -e '(VERSION rescue RUBY_VERSION) = 1.6.0 or exit 1' /dev/null 2/dev/null; then where I think $vi_cv_path_ruby is /usr/bin/ruby. That doesn't tell me anything other than that the version is not being determined by executing ruby --version, but maybe it tells you something useful. I think the problem may be a bug in Cygwin's Ruby. When you run that command with Cygwin's Ruby you get: ruby: no such file to load -- ubygems (LoadError) This is pretty clearly supposed to be the rubygems module, not the ubygems module, so probably there's a misspelling in the code somewhere. The Windows version of 1.8.6 (the same version) does not have this problem, so it seems very obviously *not* to be a bug in Vim or in the way the configure script operates. I'll delve a little deeper before filing a bug report with the Cygwin folks... thanks for the idea! Best regards, -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: Bug: .viminfo file gets deleted and re-created with 666 permissions
Micah Cowan [EMAIL PROTECTED] writes: Is there a good reason not to simply follow symlinks when they are encountered, as this user obviously expected? If it did follow the symlink to /dev/null, and tried to read from that device, it would fail. You can't (or at least, shouldn't) read from /dev/null because it's a sink, not a source. What kind of behavior would you expect, trying to read from /dev/null? I realize that unsetting viminfo is preferable to linking .viminfo to /dev/null; but I believe we still have a responsibility to users who just happen to try a different route (perhaps being unaware of the canonical method), for which they have a reasonable expectation that it will DTRT. I think soft linking a file that is meant to be both read and written to the bit bucket demonstrates that the user has just enough knowledge to be dangerous but without knowing exactly how to get what they want. As that kind of a user, I would expect an error message of some sort, in this situation. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: how to open an already opened file into an new tab?
On Tue, 08 May 2007 15:45:40 -0600 lin q [EMAIL PROTECTED] wrote: This causes that on the tabline, the full path of f2 shows after some abbreviation. Now I want to open f2 into another tab, but I do not find an easy way to do that. If use :tabe, I need to type in the full path of f2, for my case, it is very long. You can substitute the full path of the current file with the character % in an ex-command. So, assuming you're already viewing f2, you can do the following: :tabe % And it will re-open the current file in another tab. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Vim Logo Use
I can't find anything about it on the Vim website, so I was wondering what the status of the Vim logo is. Does someone own the copyright to it? Is it in the public domain? Would it be alright to create, say, a wallpaper with the Vim logo in it and release the wallpaper under a CC-BY-SA license? Thanks for clarification! -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: How to set -P argument for the cscope being run by the vim6.3
On Wed, 2 May 2007 09:05:38 -0700 (PDT) Natesh Kedlaya [EMAIL PROTECTED] wrote: As one can see from the output, the prepend path is set to none. How do I set the prepend path to some value that I want? I am able to use -P argument of cscope outside the vim to get the intended results but, not in the vim. I am using the Vim 6.3. I'm not sure about Vim 6.3 - but in Vim 7.0 you can pass another argument to :cscope add which sets the prepend path. So for example: :cscope add /path/to/database/cscope.out /home/username This sets /home/username as the prepend path, as if you had done -P on the command line. (Upon further inspection, I don't see anything in version7.txt about this being new in Vim 7.0 so it should work (I would imagine) in the version of Vim you're running.) -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: wish: allow a: in the function def
On Mon, 23 Apr 2007 21:10:20 -0500 Robert Lee [EMAIL PROTECTED] wrote: Nikolai Weibull wrote: On 4/23/07, Yakov Lerner [EMAIL PROTECTED] wrote: wish: allow a: in the function definition line: function foo(a:line1, a:line2) This is currently not allowed. But it seems logical to allow it. Why should it be? Extra typing? Counterwish: implement better semantics for VimScript so that the lookup order of variables alleviates the need for explicit environments. Yes, this will break backwards compatibility. Tough. nikolai Counterwish #2: Dump VimScript and replace it with EMCAScript (maybe using SpiderMonkey) so that people don't need to learn a new language just to change the color scheme or keyboard mappings. Yes, this will break backwards compatibility. Tough. This sounds like flame bait, and it seems that an unusually high number of very decent folks have taken it. Healthy discussion is all well and good, but I think if you're really interested in implementing extensions to Vim in ECMAScript, you should build an interface like those that already exist for Perl, Python, Ruby, etc. I know that ECMAScript is fairly popular, so finding some help along the way shouldn't be too difficult. If it's a feature you honestly want, go for it. When its working well enough, submit it for consideration to be included into the official Vim release. But for starters, I'd recommend taking a look at src/if_python.c and src/if_ruby.c to see how this has been done with other languages. As for eliminating Vim script, I think choice is a good thing, and Vim script is very well suited to programming the Vim editor. If you can write an interface for ECMAScript, you don't need to worry about Vim script. You can write in the language you like, and those who still favor Vim script can continue to use it. Live and let live. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: What plugin is the one that does the following ...
On Mon, 23 Apr 2007 09:27:18 -0600 Andrew Falanga [EMAIL PROTECTED] wrote: I'm doing some reading on vim.org in the documentation areas and found that the ability to browse a directory from within a buffer is actually accomplished by plugins rather than being built into the vim binary. I didn't know this. So, what plugin is it that accomplishes what is referenced here http://vimdoc.sourceforge.net/htmldoc/usr_22.html? Do you mean the ability to edit a directory and read its contents? The documentation says that it's distributed with vim. However, I installed vim using the FreeBSD ports system on my FreeBSD system and this pluglin, apparently, isn't installed along with the rest of vim. That's odd. The FreeBSD ports build method for Vim is simply to download the patches, apply them, and do a standard build. To my knowledge, nothing is removed. One possibility I can think of: did you build a LITE version? (Using `make -DLITE install` for example.) What leads you to believe that this functionality isn't present? Do you get some sort of error messages when you try to do something? While browsing for the plugin, I've found all sorts of plugins, but the descriptions don't seem to match what this describes (or the behavior I'm used to because I use the feature a lot in Linux). I'm seeing minibufexplr.vim, bufexplorer.vim, SelectBuf.vim and a pluthra of others, but the closest I've found yet is winmanager.vim. However, like I said, it doesn't sound quite like what I'm looking for and I'm hoping someone here knows the plugin I need. I actually use the Project plugin to do file navigation -- the downside (or I rather think of it as a benefit) is that you have to register what files you want it to list. Anyway, I think with a little more info, we may be able to further examine why the builtin version isn't working on your setup. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: Two different versions of Vim...
On Fri, 20 Apr 2007 11:09:11 -0400 Marv Boyes [EMAIL PROTECTED] wrote: Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance. I think the problem with the GUI is that Ubuntu installs its X11 libraries and headers in non-standard locations; you have to pass these locations to the configure script. Unfortunately, if you fail to pass these, and configure can't find the X11 libs or includes in their default locations, but receives the --enable-gui option, it won't quit. Instead, it will quietly build a non-gui version, despite what you told it. I'd wager that's probably what you're experiencing. AAP is OK for patching and keeping up-to-date, as long as the recipe is updated as patches are released. Unfortunately, I have not always found these to be right in sync, and it has been my experience that a more time-accurate way to track patches is through the patch README file, located on the Vim website. I've also had issues with AAP builds generating segmentation faults when you run the :version command. (Ironically, manually building source from an AAP fetch works fine...) To get around these, I wrote a Perl script that automatically fetches source and patches, then configures Vim for a very full-featured installation. Downloads are conserved so that when a new patch comes out, you just re-run the script which will then fetch only the new patch and rebuild the source tree from the archives it has kept. It's not extremely user-friendly (yet) and may require some tweaking by hand, but by default offers these configuration options: * features = huge * gui = gtk2 * multibyte * perl / python / ruby / scheme If you're interested (and by now I certainly am tooting my own horn, sorry) you can fetch it from my website at: http://www.metasyntax.net/?section=codepage=devel#vim-builder You may also want to check out the Vi Improved page on my site for more information about installation on Ubuntu, including how to enable Scheme support. If you decide to use my script, please let me know that it works / what you think about it. I'd like to add some more user-friendly features (prompts or command-line switches to enable config options, etc) when I get some more time / motivation to work on it. Happy Vimming! -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: How can I get rid of this popup?
On Fri, 20 Apr 2007 22:34:35 -0400 cga2000 [EMAIL PROTECTED] wrote: Is there any way I can turn of this completion popup .. ? One way to turn it off completely is to compile Vim without the insert_expand feature. Or remap C-p in insert mode to do nothing. Since unwanted popups is one of the absolute evils of the web .. I'm unsure why this should have become a default feature of the current version vim and I sincerely hope it will cease to be the default with the next release. I don't really see how this relates to the Internet, but I for one find this feature highly useful, especially when typing some long function name that I've already used before. Plus it's very flexible in what it can do, and where it will look for completions. Maybe this might make some sense for GUI users .. but could it be left our of the terminal version? I think the prevailing thought is that this feature is pretty valuable -- and you can always turn it off if you don't like it (see above). REFERENCES - :help insert_expand :help 'complete' -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: RAM issues
On Thu, 19 Apr 2007 04:23:22 +0200 A.J.Mechelynck [EMAIL PROTECTED] wrote: fREW wrote: [...] Which window manager(s) do you have installed? There may or may not be a similar tool (showing the various running processes with their CPU and memory use) in the same package. If there isn't, you may try to use top, a console tool, but it is less precise (IIUC, it shows memory use as %, not as KBytes) and you would have to sort its output to make sure that your Vim processes are not pushed off the bottom of the display (I guess sorting either A to Z or Z to A by command name might do it). (Once it's running, hit h for help. Most commands are single-letter and case-sensitive.) Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 177. You log off of your system because it's time to go to work. I have windowmaker installed. I am honestly a little surprised that I can't get top to do this accurately. Isn't there any general purpose unix command that can do this? -fREW I don't know; the problem is finding it. You may try starting top anyway, and see if its VIRT, RES and SHR columns are what you want; or you may try fishing after something more suitable using the apropos utility (I'll let you guess which keywords to use). Best regards, Tony. Try `ps aux` at your shell. It will give you columns indicating the VSZ and RSS of each process. VSZ represents the full virtual memory size of the process in kilobytes; RSS is the resident set size, or the amount of unswapped physical memory in use by the process (also in kilobytes). These two figures will give you an idea of how much memory is being consumed -- the latter (RSS) is your RAM use. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: how to replace ESC to some other key?
On Wed, 4 Apr 2007 10:22:43 -0400 Yakov Lerner [EMAIL PROTECTED] wrote: On 4/4/07, wangxu [EMAIL PROTECTED] wrote: ESC is so far from the center of the keyboard. Can I replace this key to Caps Lock,for example? I heard some people use Tab as a substitute for Esc. Weird. But it's easier to do in platform-independent way. Yakov If Wikipedia is correct in that vi was originally written on ADM-3A terminals (I think I also read that on here at one time as well) and that this particular terminal had it's escape key where nearly all modern keyboards have a tab key, it kinda makes sense. Here's the page, for reference: http://en.wikipedia.org/wiki/Vi Although I'm not going to switch to that scheme any time soon - ^[ works just as well. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: how to setup gvim as view source editor for Opera?
On Sat, 17 Mar 2007 15:42:49 + (UTC) zzapper [EMAIL PROTECTED] wrote: Taylor Venable [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: On Sat, 17 Mar 2007 15:01:17 + (UTC) zzapper [EMAIL PROTECTED] wrote: I've forgotten how to setup gvim as view source editor for Opera (got a new Vista PC). Also can anyone recommend the best solution for FireFox, I've only got the one where viewing source with vim is an additional option For Opera, open the preferences, click on the Advanced tag, then choose Programs from the list on the left. At the bottom of the right-hand side, there's the option to set the source viewer program. ## Couldn't see it for looking!### Hmm... well, on the Linux version of Opera 9.10 it looks like this: http://www.metasyntax.net/images/screenshots/opera-view-source.png Maybe it's not available on Windows? (For what reason that would be, I have no idea...) -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Matched Pairs Filetype Indentation
Hello all, When using the filetype indentation functionality, setting matchpairs to the right value will automatically indent after a newline, e.g. in Java when typing an opening curly brace and then hitting enter the next line indents according to shiftwidth. The opposite thing happens when you close a matched pair, e.g. in Java by hitting a closing curly brace: the indentation goes back to where it should be. This is very handy functionality. The only bad thing is that when you type the ending part of a matched pair, the cursor jumps back to the opening one to show you how they relate. (I have matchparen disabled.) This too is very handy to see where your matches are, but... Currently, the cursor jumps to the opening matched pair before the indentation is adjusted, which to me feels a little clunky. So my question is this: is it possible to have the indentation adjusted *before* the cursor jumps back to show the opening part of the matched pair? As always, thanks for any ideas. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra
Adding Keywords to Highlight Group
Hello all, I'm trying to find a way to add keywords to the Todo highlight group, such that they are only highlighted when inside a comment. Reading through the help files, I thought this would work: :syntax keyword Todo containedin=Comment contained WARNING NOTE But unfortunately it doesn't seem to highlight anything at all. Basically, I want WARNING and NOTE to be highlighted only inside comments, like TODO and FIXME are by default. Thanks in advance for any ideas. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra
Re: Adding Keywords to Highlight Group
On Sat, 24 Feb 2007 19:31:23 +0100 A.J.Mechelynck [EMAIL PROTECTED] wrote: 2) The name of the comment syntax group is different for each language. For instance, it may be vimComment, cComment, htmlComment, cssComment, etc., depending on what kind of file you're editing. (The corresponding _highlight_ groups are all linked to Comment by default, but that can be changed, and IIUC it only applies after all _syntax_ groups have been determined, so I guess you need to use the correct syntax group name). Ah, OK. I didn't realize this. 3) Taking point 2 into account, I guess the right place for your command is in an after-syntax-script; for instance for vimscript: --- start ~/.vim/after/syntax/vim.vim syn keyword Todo containedin=vimComment contained WARNING NOTE --- end This works, but then I have to do it for each file type, which is what I was trying to avoid. For a more ambitious solution (untested) autocmd Syntax * syn keyword Todo containedin=amatchComment \ contained WARNING NOTE The above may have to be defined late in your vimrc. When I tried this, I got E15: invalid expression amatch. No worries, though, because I figured it out. The trick is to use a pattern to match the containedin parameter so that it works for all comment syntax specifications -- vimComment, javaComment, whatever. The pattern is expanded whenever the syntax command gets executed, so it needs to be in an autocmd to apply to newly-registered syntaxes. :autocmd Syntax * syntax keyword myTodo \ containedin=.*Comment contained WARNING NOTE Rather than using the Todo group (which works) I put it into myTodo instead, then linked that to Todo. Best regards, Tony. Thanks for the clarification. I was almost pining for Emacs Lisp macros there for a second, but Vim came through (as usual). :) -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra
Re: Vim + MzScheme on Ubuntu
On Wed, 07 Feb 2007 00:08:29 -0800 George V. Reilly [EMAIL PROTECTED] wrote: I tried to build Vim with MzScheme support on Ubuntu a few months ago and couldn't figure out what I needed to do to get MzScheme included in Vim. I got everything all the other supported languages working. Can you summarize what you did? This took a little playing around with, because the configure script thinks that you've got all your PLT stuff installed in the same place, which on Ubuntu isn't the case. The MzScheme packages on Ubuntu install some stuff into /usr/lib/plt and the include files into /usr/include/plt. Configure needs to know about both of these paths, but only allows you to specify one, using --with-plthome, which you should set to /usr/lib/plt. Then inside this directory create a symlink called include which points to /usr/include/plt. You shouldn't need any packages other than mzscheme (at least, I didn't need any that weren't already installed). It was kind of a tricky process in total, so I chronicled my adventures in compiling Vim for Xubuntu on my website. I used Aap to fetch the source, but the standard make procedure to install it. Here's the URL: http://www.metasyntax.net/?section=unixpage=vim#xubuntu Please let me know if you notice that I've missed anything important. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra
2html Doesn't Work with Scheme / Lisp Code and Line Numbers
Hello, This seems like a bug to me, but maybe I'm just doing something wrong. When I try to convert my Lisp or Scheme code into HTML or XHTML (both with and without CSS) using 2html.vim, I get an error and the only syntax highlighting in the HTML is the line numbering. When you look at the resulting HTML, it still has all the CSS classes in the code, rather than the font colors that actually represent that code in the current color scheme. I'm using Vim 7.0.35 on Xubuntu Linux 2.6.17-10 (using the pre-built vim-full package from the Universe repository). The output of `vim --version` is in the attached version.txt file. Here's the exact error I get: Error detected while processing /usr/share/vim/vim70/syntax/2html.vim: line 496: E486: Pattern not found: span class=\([^]*\)/span Turning off the line numbering (:let html_number_lines = 0) makes everything work just fine. I tried to do a little debugging on 2html.vim and I find that the script crashes when s:id = 0, a:style_name = 'lnr' (derived from s:HtmlFormat, line 125). 'lnr' seems to be for line numbers, which probably explains why it doesn't crash when I turn off line numbering in the HTML. I can't tell for sure if this is a bug in 2html or a bug in the Lisp and Scheme syntax files. Or maybe I'm just not hitting on the right options somewhere. So far, I've only found that it doesn't work for Scheme and Lisp syntaxes. Other languages I've tested (Smalltalk, Ada, OCaml, et al) seem to be alright. Attached is an example Scheme file (example.scm) and the HTML that 2html generates from it (example.scm.html). If anybody has any ideas about this, I'd greatly appreciate it. Thank you. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra example.scm Description: Binary data html head title~/programs/testing/scheme/smalltalk.scm.html/title meta name=Generator content=Vim/7.0 meta http-equiv=content-type content=text/html; charset=UTF-8 /head body bgcolor=#33 text=#ff pre font color=#00 1 /fontspan class=Special(/spanspan class=Statementdefine/spanspan class=schemeStruc /spanspan class=schemeOtherfind-all/span font color=#00 2 /fontspan class=schemeStruc /spanspan class=Special(/spanspan class=Statementlambda/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=schemeOtheralist/spanspan class=schemeStruc /spanspan class=schemeOtherpredicate/spanspan class=Special)/span font color=#00 3 /fontspan class=schemeStruc/spanspan class=Special(/spanspan class=schemeOtherfind-all-r/spanspan class=schemeStruc /spanspan class=schemeOtheralist/spanspan class=schemeStruc /spanspan class=schemeOtherpredicate/spanspan class=schemeStruc /spanspan class=Constant1/spanspan class=Special)))/span font color=#00 4 /font font color=#00 5 /fontspan class=Special(/spanspan class=Statementdefine/spanspan class=schemeStruc /spanspan class=schemeOtherfind-all-r/span font color=#00 6 /fontspan class=schemeStruc /spanspan class=Special(/spanspan class=Statementlambda/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=schemeOtheralist/spanspan class=schemeStruc /spanspan class=schemeOtherpredicate/spanspan class=schemeStruc /spanspan class=schemeOtherindex/spanspan class=Special)/span font color=#00 7 /fontspan class=schemeStruc/spanspan class=Special(/spanspan class=Statementlet/spanspan class=schemeStruc /spanspan class=Special((/spanspan class=schemeOtherrange/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=schemeOtherfind-first/spanspan class=schemeStruc /spanspan class=schemeOtheralist/spanspan class=schemeStruc /spanspan class=schemeOtherpredicate/spanspan class=schemeStruc /spanspan class=schemeOtherindex/spanspan class=Special)))/span font color=#00 8 /fontspan class=schemeStruc /spanspan class=Special(/spanspan class=Statementif/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=Identifiernull?/spanspan class=schemeStruc /spanspan class=schemeOtherrange/spanspan class=Special)/spanspan class=schemeStruc /spanspan class=Special'()/span font color=#00 9 /fontspan class=schemeStruc /spanspan class=Special(/spanspan class=Identifiercons/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=Identifierlist/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=Identifiercar/spanspan class=schemeStruc /spanspan class=schemeOtherrange/spanspan class=Special)/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=Identifiercadr/spanspan class=schemeStruc /spanspan class=schemeOtherrange/spanspan class=Special))/span font color=#0010 /fontspan class=schemeStruc /spanspan class=Special(/spanspan class=schemeOtherfind-all-r/spanspan class=schemeStruc /spanspan class=Special(/spanspan class=Identifiercaddr/spanspan class=schemeStruc /spanspan class=schemeOtherrange
Re: 2html Doesn't Work with Scheme / Lisp Code and Line Numbers
On Wed, 07 Feb 2007 00:13:41 +0100 A.J.Mechelynck [EMAIL PROTECTED] wrote: With default settings in gvim 7.0.191 running in console mode in /dev/tty (i.e., a pure-text console, not an xterm), I get no errors. The generated example.scm.html (attached) displays OK (AFAICT) in Firefox 2, in Konqueror 3.4.0 and (but not with all colours) in Lynx 2.8.5rel.2. All colors are different (in yours, the background is of a lighter grey and there are no syntax highlights). My syntax/2html.vim is dated 2007 Jan 27 and my syntax/scheme.vim is dated Nov 28, 2004 (in the text, not in the directory listing). You have an outdated version of Vim, and maybe you have an outdated version of 2html.vim too. See http://ftp.vim.org/pub/vim/runtime/7.0/patches/README for the table of contents of current patches to Vim 7.0. I suggest that you uninstall the Ubuntu version of Vim then build your own, see http://users.skynet.be/antoine.mechelynck/vim/compunix.htm Well, after a lot of playing around (tracking down dependencies in Ubuntu) I finally got everything I needed and built Vim + all patches (resulting in 7.0.192 as of tonight) from source. Still no luck, though; it has exactly the same problems. [As an interesting side note, I fetched and patched it with Aap, but when I tried to build with Aap it would segfault when you tried to get version info out of the resulting binary. Doing the standard `./configure make make install` rather than using Aap to build fixed that problem. Also, building with Aap didn't seem to allow using MzScheme (got a pre-processor error about the collects/ directory not being found).] Furthermore, it doesn't seem to be an encoding problem, at least not at the level of the source file. Both UTF-8 and ISO-8859-1 have the same problem. It's probably some sort of environment problem, though, seeing as there are now two confirmed cases of it working (not me). Thanks for the ideas though. It feels good to have a custom-built version of Vim, and now with MzScheme support, too! Still... it would be nice to know why this is not working. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra
Re: 2html Doesn't Work with Scheme / Lisp Code and Line Numbers
On Tue, 6 Feb 2007 22:25:05 -0500 Theerasak Photha [EMAIL PROTECTED] wrote: BTW---where can I find a syntax highlighting file for Smalltalk? It should be syntax/st.vim -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/ Simplicity is prerequisite for reliability. -- Edsger Dijkstra
