Become a fan of Slashdot on Facebook


Forgot your password?
Programming Software IT Technology

Vim 6.4 Released 419

file cabinet writes to tell us that for the first time in more than a year Vim has released a new version. Version 6.4 stable was released yesterday and while there are no new features added they are touting dozens of bug fixes.
This discussion has been archived. No new comments can be posted.

Vim 6.4 Released

Comments Filter:
  • "Because we use vi [], son; they use emacs."

    In good sadness, though, I'm looking forward to the spell-checking [] in Vim 7.

    • The vimspell script works well.
    • by falzer ( 224563 ) on Monday October 17, 2005 @01:41AM (#13807407)
      VIM is *not* user friendly, and until it is VIM will stay with <= 1% marketshare.

      Take editing text. Vim zealots are now saying "oh editing text is so easy, just use the hjkl keys to move around and use ":%s/apple/apricot/gi" to do a search and replace. Yes, because typing in "5kck}" is so much more intuitive than simply moving the cursor, selecting two lines of text with the mouse, then hitting the } key.

      VIM zealots are far too forgiving when judging the difficultly of VIM interface issues and far too harsh when judging the difficulty of Notepad issues. Example comments:

      User: "How do I fucking edit this goddamn text file!? Why does Linux only come with vi installed?"
      Zealot: "Oh that's easy! Just go vim <the file you want to edit>. No no, wait, don't type anything yet. It won't work the sa-- ok hit escape, ok, hit u a few times, ok you're back to where you started. Now vi works a little differently than most text editors: there is command mode and edit mode. Vim starts in command mode where you issue commands (such as hjkl) to move the cursor around, d followed by a movement command to delete lines of text, or i (for example) to insert text. Pretty much almost every letter of the alphabet (upper and lower case) is a command. When you go into a text editing mode by issuing the appropriate command, you type your text like normal then hit escape to back out. You type :q to quit, or ZZ / :wq to save and quit. Sometimes you need to put in a ! after a : command to force it. Quite elegant, don't you think?"

      User: "How do I edit text files using notepad?"
      Zealot: "Oh God, you have to use the graphical luser interface to open a text file. Then use the arrow keys (or optionally mouse) to position the cursor where you want to type. Now you've gotta actually enter in the text using the keyboard! Careful though, it might break, it just blithely assumes that what you're typing is text and not commands!"

      So, I guess the point I'm trying to make is that what seems easy and natural to VIM geeks is definitely not what regular people consider easy and natural. Hence, the preference towards notepad.
      • by Demerol ( 306753 ) on Monday October 17, 2005 @01:48AM (#13807428) Homepage
        No one says vim is user friendly. It's not supposed to be. It's supposed to be powerful, and it is. It's hard to learn and it probably always will stay with 1% of the market share but I don't think the developers really care for increasing market share.'s free in every sense.

        And in reply to the troll before you:

        vim does have mouse support (:set mouse=a) in both terminal and, obviously, gui modes.

        Also, :set wrap will solve your other qualm.
        • by p2sam ( 139950 ) on Monday October 17, 2005 @04:45AM (#13807867)
          I'd disagree with you about the user friendlyness of vim. I think Vim is one of the most user friendly editors out there. It's highly ergonomic, and easy to use. BUT!! It is not easy to learn.

          That's right. Easy to use, and Easy to learn are two different things. Easy to use means that one can accomplish a task with minimal effort. Easy to learn means just that, easy to learn. The two are not necessary mutually exclusive, but I have yet to see a text editor that has both.

          Modern UI designers have fallen into the tar pit of designing ONLY for new users, so that tasks can be performed easily by new users, but becomes difficult to use for the power user. In that sense, most modern IDE's are easy to learn, but hard to use.

          In my opinion, I'd rather spend a few days learning to use a tool that will increase my long term productivity.
        • No one says vim is user friendly. It's not supposed to be.

          Actually, when vi was first released, it was very user-friendly, at least compared to the default editor ed, which is a line editor, and which was generally the only other text editor available on most UNIX systems.
          (If you want to compare the two, type "ed <some file>" at the command prompt on most *IX systems (including cygwin under MS-Windows), and try to edit the file.
          Vi(m) is so much better.)
          Even when editing on a DECWriter (a hard-copy t

      • Hm, for some reason notepad doesn't work from ssh. With commands like cl, cw and so on. VIM makes the perfect editor for quick edits on a remote computer.
      • by hereticmessiah ( 416132 ) on Monday October 17, 2005 @02:25AM (#13807522) Homepage
        Have you read Neal Stevenson's "In the Beginning Was the Command Line"? If you had, you wouldn't be spouting this nonsense.

        Seriously, go read this section: []

        In it, he compares two devices: a heavy duty industrial drill called the Hole Hawg, and your basic power drill. Both do the same thing--drill holes--but their intent is different. The Hole Hawg is designed to drill through anything, whereas the regular power drill is designed for household use. The power drill lacks the power of the Hole Hawg, but has safety features that the Hole Hawg can't afford to have because of this. Whereas the Hole Hawg will keep spinning if it hits something hard (and therefore requires a large amount of strength to keep steady), whereas the power drill will slow down if it encounters too much resistance.

        Similarly, Vim is the Hole Hawg of text editors, whereas notepad is a regular powerdrill. Both have different intentions, with the former being designed for heavy-duty text editing as a programmer or highly technical user would need, and the latter designed for occasional light editing, the kind most non-technical users do. The intent is different and so the interfaces differ.

        It's very, very difficult to create a deep, powerful interface that is easily discoverable. At best, you can make it as learnable as possible. This is what Vim attempts to do. Notepad goes for a shallow, easily discoverable interface at the expense of power.
        • > ...Vim is the Hole Hawg of text editors, whereas notepad is a
          > regular powerdrill. Both have different intentions, with the
          > former being designed for heavy-duty text editing as a programmer
          > or highly technical user would need, and the latter designed for
          > occasional light editing, the kind most non-technical users do.
          > The intent is different and so the interfaces differ.

          Exactly correct. That's why a lot of people preferred WordStar to Word or WordPerfect. and we still remember the hot
        • The conclusion most will draw from your argument rests on a faulty implication: that vi was intended to be more featureful than Notepad.

          If Bill Joy had had access to the screen capabilities of a graphics engine, instead of a glass-TTY, there might never have been a Notepad, because vi would have had a mouse and a cursor and still would have had need to put all of vi's "power" into the editor he chose to write.

          Vi isn't as "easy to use" as Notepad because Bill Joy lacked the technology. Notepad isn't as "po
      • I've been using vi editors fo ages for the simple reason that nothing else was available. Well, I wouldn't have used Notepad (I don't think I've ever used notepad) but something with a more modern interface would certainly have been welcome. And if you don't like vi, go play with the system editor on VMS, it's not much better.

        The purpose of vim isn't to make a user friendly editor, it's to make a better vi. vi isn't a user friendly editor, it's a horrible relic from another age which however happens to be :
      • Vim's not easy to use?

        I beg to differ: Cream for Vim [].

  • by CyricZ ( 887944 ) on Monday October 17, 2005 @12:00AM (#13807024)
    I want to say thanks to all of the VIM developers who have helped create such an amazing piece of software. Indeed, I don't think we can even begin to consider how much other software has been written by developers using VIM.

  • by poind3xt3r ( 890661 ) on Monday October 17, 2005 @12:02AM (#13807035)
    Dozens of bugs have been fixed, runtime files were added and updated. There are no new features They are focusing more on fixing problems rather than add new features and in essence adding new bugs. Its rare to see updates which are meant for donzens of fixes. A smart approach.
    • by CyricZ ( 887944 )
      I mean, it is the 6.4 release. Many projects typically do not add features after a major release. It's the minor point releases that focus on fixing bugs. So in this case it's the fourth round of bugfixes.

    • by keesh ( 202812 ) on Monday October 17, 2005 @12:27AM (#13807156) Homepage
      No no no. The features are being added in the 7.x branch, which you can get from CVS. 6.x is purely for maintenance (ie bugfixes). This is a mixed blessing... It means 6.x is extremely stable, but if you want new goodies like spellchecking and intelligent autocompletion, you have to switch to the CVS only branch.

      It's a tricky decision. Some projects are way over on the side of "keep throwing out new versions with new features and new bugs". Vim is way over on the other extreme: "release 'new feature' releases every few years and keep the stable branch working". For end users it's a mixed blessing.

      Fortunately, the 7.x branch is pretty much stable (as in every day usable) at the moment. I've been using the Gentoo ebuilds (package.masked), which means I get a CVS snapshot which has been at least reasonably well checked and had any icky bugs fixed. I'd hate to miss out on the new toys. The 'numberwidth feature alone makes it worth the upgrade, even if 'spell didn't exist.
      • by m50d ( 797211 )
        No no no. The features are being added in the 7.x branch, which you can get from CVS. 6.x is purely for maintenance (ie bugfixes). This is a mixed blessing... It means 6.x is extremely stable, but if you want new goodies like spellchecking and intelligent autocompletion, you have to switch to the CVS only branch.

        For a piece of basic system software, it's more important that there's a stable branch that's actually stable. Now if only Linus would see things this way.

  • More than a year? At least that's quicker than Microsoft....
  • by Morganth ( 137341 ) on Monday October 17, 2005 @12:07AM (#13807066) Journal
    I just wanted to point out that Intellisense (context-sensitive completion based on parsing or "understanding" code) is the #1 most voted VIM feature. You should add your own votes (with your hard-earned cash, if you will) if you want to see this feature come to VIM.

    I personally do want this feature. It would make VIM the perfect text editor, IMO. Right now, VIM's completion is already pretty good, and a couple people have implemented completion as a plugin, but it usually ends up being a hack. I think Bram can figure out a nice way to do it for Vim 7.

    People who know how to use VIM well find themselves really productive in it. But, that said, I end up being slightly more productive writing Java code in Eclipse, ONLY because of completion, even though all my other editing features from VIM aren't there (or are buried).

    What I usually end up doing is keeping a console handy and switching between Eclipse and VIM when I have to do Java, but that's not that nice. I think Vim can pull this off. []
    • Indeed, finding out a "nice" way of doing it is essential. Nothing is more of a hassle than having Eclipse or the Visual Studio IDE autocomplete a keyword, identifier, and so on, incorrectly. Going back and correcting its error can take three or four times the amount of time it would've taken to type in the text manually.

      At least it's possible that it would not be enabled by default.

    • by kaisyain ( 15013 ) on Monday October 17, 2005 @12:54AM (#13807247)
      He's already added it in the Vim 7 sources. It was initially called occult completion but is now called omni completion. (Intellisense is a trademarked term.) Read the vim dev list for more details.
    • I'd actually like to see a Java port of vim. I looked at the source code and it doesn't seem too hard. The vast majority of code is ifdef's for various architectures; this could all be replaced with one straight implementation in Java. The rest of the code seems fairly well encapsulated in object-like structures, so it should be somewhat easy.

      This would make integrating jvim into eclipse and adding intellisense into it much easier. Of course it would be slower and hunkier, but it would still be cool to
    • by Anthony Liguori ( 820979 ) on Monday October 17, 2005 @02:17AM (#13807497) Homepage
      People who know how to use VIM well find themselves really productive in it. But, that said, I end up being slightly more productive writing Java code in Eclipse, ONLY because of completion, even though all my other editing features from VIM aren't there (or are buried).

      Sorry, I don't mean to be a bastard here, but this is my biggest pet peeve. I *hate* Intellisense or whatever the hell it's called. I think syntax autocompletion is ruining a new generation of programmers.

      Here's my reasoning. Writing code that always works is hard. Writing code that works some of the time is easy. To write code that works all of the time you have to understand the exact behavior of every function you call and handle all possible scenarios properly. It's the difference between writing:
      read(fd, &myInt, 4);
      And then writing a wrapper around read that checks for EAGAIN, EINTR, performs endianness conversion, handles partial reads, and potentially implements this all asynchronously. Back to my original point though, it takes time to learn all of the sublities of an API. The best way to learn them is by studying the interfaces (reading manuals, man pages, whatever).

      If you cannot remember the name of a function, go back to the manual and study it. You're going to not handle the edge cases of it. If it's Java, you'll ignore a potential exception. If it's C, you'll miss a potential error code.

      I'm not against all the features in things like Eclipse. Some of the refactoring stuff is useful. It's just intellisense that drives me nuts.
      • Guess what. You don't have to use intellisense if you don't want to. That was easy wasn't it.
      • by plastik55 ( 218435 ) on Monday October 17, 2005 @03:01AM (#13807616) Homepage
        Eh? When Eclipse offers completions of a function for me it shows me the javadoc! So when I 'm getting ready to call a function I can see all the edge cases and caveats documented for me on the screen. That's much better than being a macho/masochistic programmer and thinking I remember everything about a function from the last time I used in in a different context.

        No one remembers all the edge cases, especially people who think they've got it all so memorized that they don't bother to double-check the documented behavior while they're calling functions.

      • If you cannot remember the name of a function, go back to the manual and study it.

        Don't think it's just for when you forget something - most of the time, I remember how to type gtk_menu_get_attach_widget(), and what arguments it needs; I just can never be bothered to type it over and over again.
      • Autocompletion is not meant (at least as I perceive it) to help you remember the names of functions (although it's a big help there). It's meant to make you type the names faster, which can be a GODSEND if you use names like "intDocumentClassFontState" (overkill, but you get the meaning, and I know using prefixes in dynamically typed languages is wrong, but I like it). I want to be able to read my code when I look at it after having forgotten what it's about. Comments help, but they can only get you so far
  • by yagu ( 721525 ) * <> on Monday October 17, 2005 @12:08AM (#13807071) Journal

    Sometimes I think Bram Moolenaar doesn't get enough credit for what he's done almost single-handedly. vim is an amazing piece of software. I've been using it almost since the day it arrived, and I was a vi user who thought vi was everything. But Bram brought vim and immediately began carefully, but boldly, extending vi, without the constraints of waiting for POSIX standards anointing any changes to vi.

    Credit to Bill Joy also (and to AT&T, for "sc") for the pre-cursors and inspirations for vim.

    vi in and of itself is a workhorse with its philosophy of "no gui or mouse necessary", and while vim now has its gui rendition (I never use it), the underlying philosophy and principles remain intact. Color syntax alone is worth it. If you haven't tried vim, you should. For raw and pure editing, there's nothing better (don't flame me, emacs people... please). I've often challenged people to editing faceoffs... where I'd dialup at 1200 baud (yes, I've been around for a while), and they could use ANY editor, at any connection speed, and I'd beat them at making a set of edits against a file.)

    (Aside: how many vi users out there have spuriously put "www, jjj, bbb, G " in their comments when they used the browser text widgets.)

    • by CyricZ ( 887944 ) on Monday October 17, 2005 @12:22AM (#13807134)
      ... but it is also a fantastic pager. Using it instead of less or more to quickly scan over source code is a blessing! Indeed, you get the syntax highlighting of a GUI editor, but without the overhead. You can view files instantly from the command line, and they're very nicely formatted.

    • Editor faceoffs. I've won several of those with vi on my belt. When we get to use the whole toolkit, I'll often whip out some temp files and use awk a bit (for column processing). I've got two questions for someone out there with better vi skills than I.

      How would a vi pro do CSV test processing? How would you take the text between the second and third commas and replace it with arbitrary text?

      Ignoring CSV for a minute, if you'd like to replace all text from the 20th through 23rd characters of arbitrar

      • How would a vi pro do CSV test processing?

        with a perl script. written on vim of course!!
      • Ignoring CSV for a minute, if you'd like to replace all text from the 20th through 23rd characters of arbitrary text with the string "abcd", how would you do it?

        You mean something like this ? :%s@^\(.\{19\}\).\{4\}@\1abcd@g

        Although I would usually do that using sed, not vim.

        In text processing, the workload determines the ability of a "ve" user (internal IBM tool) to surpass my vi efficiency. Typically, it's when the ve user mouse selects a column and then does replaces on it. I'd like to mimic this behavior
    • by trb ( 8509 ) on Monday October 17, 2005 @01:12AM (#13807305)
      Credit to Bill Joy also (and to AT&T, for "sc") for the pre-cursors and inspirations for vim.

      Joy wrote vi, with help from Mark Horton, both then at UC Berkeley. This back around 1980, on PDP-11s, and eventually Vaxen. If by se, you mean the Bell Labs PWB screen editor, that was quite a clumsy piece of software meant to compete with vi, and with the ports of emacs to UNIX (separate versions by Gosling and Zimmerman, predating the GNU effort). I am shocked that anyone remembers PWB se, it was short-lived and pretty obscure. How obscure? Is there one ref to it on the web? That's obscure!

      While you're thanking, you might want to thank the UNIX folks who brought us "ed," Ken Thompson (and Kernighan wrote the docs, as always). The ed command set survives as the basis for vi/vim :command mode - including the regexes. ed was based on editors that came before it of course, especially QED.

  • Bug fixes (Score:5, Funny)

    by patrickclay ( 898576 ) on Monday October 17, 2005 @12:11AM (#13807084) Homepage
    I hope they fixed the bug that made you type all those weird key combinations to write to a file and save.
    • :w

      Wow, ain't that hard?

      Type "ZZ" to save and quit. Those are indeed capitalised, and Shift is right next to Z.
    • Re:Bug fixes (Score:2, Interesting)

      by Waffle Iron ( 339739 )
      You can fix it yourself. Add to your .vimrc file:
      nmap <C-S> :w<CR>
      imap <C-S> <Esc>:w<CR>
      Now Ctl+S works just like it does in notepad.exe.
      • Re:Bug fixes (Score:3, Informative)

        by dedazo ( 737510 )
        Or you could just source mswin.vim (typically found under $VIMRUNTIME) and essentially have a MS-style keymap emulation. Put it in your ~/.vimrc, and make sure you include the 'behave mswin' line before you source it.
  • by _Hellfire_ ( 170113 ) on Monday October 17, 2005 @12:18AM (#13807109)
    ...welcome our new 18 fingered overlords!

    (yes I'm a daily vim user)

    Keep up the fantastic work guys - vim is one of those apps which is actually a pleasure to use.
  • by earthbound kid ( 859282 ) on Monday October 17, 2005 @12:18AM (#13807116) Homepage
    The last version of Emacs came complete with Vim v. 10.03c! ;)
  • by Rhinobird ( 151521 ) on Monday October 17, 2005 @12:38AM (#13807198) Homepage
    Because, I thought that I distinctly heard the words "Flame On".

    Like priming an enclosed area with flammable fumes. Someone is going to mention Emacs and this place is going to explode.
  • by MrBoring ( 256282 ) on Monday October 17, 2005 @12:47AM (#13807224)
    First, I use VIM not so much because I think it's the best text editor, but because it's corrupted my thought process so much that I keep using those cryptic Vi commands in other programs when typing more than a few words. That said, I do feel most productive in Vim or Vi on systems which don't have Vim (such as z/OS). People don't understand why one would use Vi, until they've mastered it so well that they can nearly look at a point in the screen or think of where they want to be, and the cursor arrives there without remembering which keystrokes got them there. One of my biggest reasons for using it is that there is *no* project, workspace, solution or whatever, that I have to set up before being able to do real work. I like that.

    As for wishes:
    1. Better language completion, if any, language completion.
    2. Better editing of binary files.
    3. Support for multiple code pages. This may be possible already, but I haven't deciphered the manual enough to figure out how.
    4. Support for working with change control systems. I'd like to be able to edit a file in a CCS and have the title bar reflect the release, level, etc that I'm editing, rather than a cryptic temporary file.
    5. A better head on my own shoulders to remember all the set commands needed to operate it.

    I really can't complain though, because if the above never got implemented, I'd still use it. I've used the editor for years, and still keep learning it.

  • by wk633 ( 442820 ) on Monday October 17, 2005 @12:47AM (#13807226)
    Ok, some vim guru on here must know, what's the windows vim equivelent of vi's ^V? In vim, it does a frickin' paste! So how do I search for, say ^M? Or enter a macro which includes inserts I need to esc from? Not being able to find that anywhere in the help is the one thing I hate about vim.
  • I have been a ardent fan of this editor and have been using it consistently for over 3 years now. And I really feel that vim has reached a maturity level where no more development is necessary.
    And if it lacks a feature, just write a plugin for the same. If you ask me this is how softwares must be developed - in a fully modular manner.

    Kudos to vim developers :)
  • VIM? (Score:2, Funny)

    by thomble ( 642879 )
    ...puh-lease. I write everything in machine code.
  • Yipee! (Score:4, Interesting)

    by callipygian-showsyst ( 631222 ) on Monday October 17, 2005 @01:07AM (#13807289) Homepage
    I am a VIM (and vi) fanatic! Which people find strange, because I'm also a Windows Zealot! I have the GUI version of VIM installed on every Windows machine I use, and I even have a version of Visual Studio that substitutes VIM as the editor.

    The problem is I learned vi so long ago (back in the late 70s when Bill Joy released it), that I simply can't learn anything else. Of course, growing up on TICO and other editors before vi made moving to vi natural.

    I have tried many, many times to switch to emacs and always fail. I'm just too old and too stuck in my ways to switch.

    • Re:Yipee! (Score:3, Funny)

      by p2sam ( 139950 )
      I started using Emacs in 2nd year university, but switched to Vim after realizing that I don't want to learn elisp. :) I also think I'm too old to change now, I'm 25. ;-)
      • Re:Yipee! (Score:3, Interesting)

        by chthon ( 580889 )

        You should be modded funny. I am 39, I have used vi(m) for almost 6 years, and now I am learning emacs. I like them both.

        I find the opening of files and switching between buffers easier on emacs.

        Also, when I do a compile on Emacs with 'perl -c' I can automatically go to the errors in the Perl code. In vim, I had to enter manually the regular expressions for matching those.

        I do not know with what I am going to end up in the long run. vim is faster for editing config files, emacs makes it easier on long ru

    • Re:Yipee! (Score:4, Funny)

      by commodoresloat ( 172735 ) on Monday October 17, 2005 @03:07AM (#13807628)
      I am a VIM (and vi) fanatic! Which people find strange, because I'm also a Windows Zealot!

      I bet you're loads of fun at parties!

  • by 2Bits ( 167227 ) on Monday October 17, 2005 @01:15AM (#13807320)
    Look, as good as vim could be, at this rate, you are not going to catch up with emacs, which is already at version 21.x or something. Which just proved that emacs is much better. If you don't believe, here is some proofs:

    1- Emacs has a much higher version number, which proves to be a more mature software, which proves to be better (more mature is better)

    2- Even an icon such as RMS whom has been proved to be more intelligent than the average USians, uses Emacs. This shows that smart people always make the right choice, and in reverse, proves that Emacs is better than Vim.

    3- Everyone in Cryptonomicon, which is the bibile of all geeks, uses Emacs. We even have a module for encryption. It would take a long time for Vim to catch up to that kind of functionalities.

    4- Only in Emacs can you do Ctrl-A to move the beginning of a line. In one shot. How could you do that in
    Vim? You have to Esc, then press 0, which is lame. Which just shows how advanced Emacs is in terms of maturity and functionality.

    5- As the theorem goes, computer science is a science for minimizing keystrokes. Emacs, in contrast to Vim, can prove this theorem right. Emacs users press less keys than Vim users.

    6- Humans have 10 fingers (some may have more, but I don't know how to grow them), and Emacs allows you to use all your fingers at one. Which shows you that Emacs has a better human user interface. In contrast, Vim users can only type one key at a time, which has no concept of fingers. That is like an interface for dogs, which can only press one key at a time with their paws.

    7- Emacs allows users to stretch their fingers more, and finger exercise has been proved, again and again, scientifically, to help increase human intelligence. The more you use Emacs, the more you become intelligent. Unlike Vim users, who become dumber and dumber, and end up with paws.

    8- Everyone knows that geeks do no exercise. But we Emacs users have our daily dose of finger exercise. As a result, Emacs users have better shape. Take a look at the comparison: RMS (Emacs user) vs ESR (Vi user). RMS definitely looks better, with a nicer beard too. ESR can only have a lousy Asterix moustache. And look at what these two persons said in public, which just proved points 2, 6, and 7.

    9- Look at this deductive proof I'm giving right now. Only an Emacs user can attain this level of intellect.

    10- As a result of the last 9 points, this proves that Emacs is better. And from an evolutionary point of view, Emacs is like modern humans, and Vim like chimpanzee.

    * putting on flame suite *

  • by fm6 ( 162816 ) on Monday October 17, 2005 @01:17AM (#13807329) Homepage Journal
    ... don't forget that it's charityware [].
  • by Pecisk ( 688001 ) on Monday October 17, 2005 @01:23AM (#13807353)
    When I first saw vi, I thought - WTF. It is suitable for text editing!? Vi, for my point of view, is one of underdogs of software world. And yes, it really truely shines when we talk about remotently editing 40K file over 2800 baud modem or even on system with space about...emm...four megabytes? :)

    Yes, there are Word, OO.o Writer, Gedit, Kedit, Pico, Nano, whatever...and there is vi. Freedom of choice does strange things, doesn't it?
  • change log (Score:3, Informative)

    by m()p3s ( 888808 ) on Monday October 17, 2005 @01:32AM (#13807385)
    The change log;
    This section is about improvements made between version 6.3 and 6.4.

    This is a bug-fix release. There are also a few new features. The major number of new items is in the runtime files and translations.

    The big MS-Windows version now uses:
    Ruby version 1.8.3
    Perl version 5.8.7
    Python version 2.4.2

    Changed *changed-6.4*

    Removed runtime/tools/tcltags, Exuberant ctags does it better.

    Added *added-6.4*
    Alsaconf syntax file (Nikolai Weibull)
    Eruby syntax, indent, compiler and ftplugin file (Doug Kearns)
    Esterel syntax file (Maurizio Tranchero)
    Mathematica indent file (Steve Layland)
    Netrc syntax file (Nikolai Weibull)
    PHP compiler file (Doug Kearns)
    Pascal indent file (Neil Carter)
    Prescribe syntax file (Klaus Muth)
    Rubyunit conpiler file (Doug Kearns)
    SMTPrc syntax file (Kornel Kielczewski)
    Sudoers syntax file (Nikolai Weibull)
    TPP syntax file (Gerfried Fuchs)
    VHDL ftplugin file (R. Shankar)
    Verilog-AMS syntax file (S. Myles Prather)

    Bulgarian keymap (Alberto Mardegan)
    Canadian keymap (Eric Joanis)

    Hungarian menu translations in UTF-8 (Kantra Gergely)
    Ukrainian menu translations (Bohdan Vlasyuk)

    Irish message translations (Kevin Patrick Scannell)

    Configure also checks for tclsh8.4.

    Fixed *fixed-6.4*
    "dFxd;" deleted the character under the cursor, "d;" didn't remember the exclusiveness of the motion.

    When using "set laststatus=2 cmdheight=2" in the .gvimrc you may only get one line for the cmdline. (Christian Robinson) Invoke command_height() after the GUI has started up.

    Gcc would warn "dereferencing type-punned pointer will break strict -aliasing rules". Avoid using typecasts for variable pointers.

    Gcc 3.x interprets the -MM argument differently. Change "-I /path" to "-isystem /path" for "make depend".

    Patch 6.3.001
    Problem: ":browse split" gives the file selection dialog twice. (Gordon Bazeley) Same problem for ":browse diffpatch".
    Solution: Reset cmdmod.browse before calling do_ecmd().
    Files: src/diff.c, src/ex_docmd.c

    Patch 6.3.002
    Problem: When using translated help files with non-ASCII latin1 characters in the first line the utf-8 detection is wrong.
    Solution: Properly detect utf-8 characters. When a mix of encodings is detected continue with the next language and avoid a "no matches" error because of "got_int" being set. Add the directory name to the error message for a duplicate tag. Files: src/ex_cmds.c

    Patch 6.3.003
    Problem: Crash when using a console dialog and the first choice does not have a default button. (Darin Ohashi)
    Solution: Allocate two more characters for the [] around the character for the default choice.
    Files: src/message.c

    Patch 6.3.004
    Problem: When searching for a long string (140 chars in a 80 column terminal) get three hit-enter prompts. (Robert Webb)
    Solution: Avoid the hit-enter prompt when giving the message for wrapping around the end of the buffer. Don't give that message again when the string was not found.
    Files: src/message.c, src/search.c

    Patch 6.3.005
    Problem: Crash when searching for a pattern with a character offset and starting in a closed fold. (Frank Butler)
    Solution: Check for the column to be past the end of the line. Al
  • by MichaelSmith ( 789609 ) on Monday October 17, 2005 @02:07AM (#13807468) Homepage Journal

    Neither of these two editors works like the sort of editor which people are exposed to these days. Why do you have to have an insert mode? This "feature" came from vi but for me it is exactly like bolting primitive editing behaviors on to more or less

    In my day job as a senior programmer I introduce new staff to nedit []. I also tell them to make their own choices about the tools they use. Most continue to use nedit because it has a few simple features which enhance usability. For example each function has a menu item, and each menu item tells you which key to use as an alternate way to reach the function. You don't have to worry about which mode it is in. Simple standard actions like opening and closing a file work in exactly the same way as other editors like gedit.

    So for me people use vi(m) and emacs out of habit. Unless these tools improve they have no serious future in competition with eclipse, etc. Neither does nedit, for that matter but it will at least provide a better option for people new to *nix.

    • by oneandoneis2 ( 777721 ) * on Monday October 17, 2005 @06:19AM (#13808056) Homepage

      Why do you have to have an insert mode? This "feature" came from vi but for me it is exactly like bolting primitive editing behaviors on to more or less

      Try this: Go into Microsoft Windows, press the "Alt" button once, and then try to type Hello, world.

      Funnily enough, instead of the key presses resulting in text going into the document, it'll navigate the menus. Why? Because it's just gone from Insert mode to a Command mode. It's exactly the same principle as Vi - sometimes you want key presses to result in text on the screen, and sometimes you want it to do something. It's not "primitive editing behaviour", it's exactly the same behaviour as is used in the most advanced word processors available. (And MS Word as well ;o) It's just not a visible, GUI-based Command mode in vi, is all.

      So for me people use vi(m) and emacs out of habit.

      I don't - I came to Linux a few years ago, needed a text editor, tried a few and settled on vi. Well, vim actually. It's a really good text editor once you learn it.

  • by chrysalis ( 50680 ) on Monday October 17, 2005 @04:04AM (#13807754) Homepage
    int main(void)
    for(;;) {
    return 0; /* NOTREACHED */
  • by vigilology ( 664683 ) on Monday October 17, 2005 @08:38AM (#13808398)
    Sorry if this rant is misplaced, but I see this as not an insignificant problem amongst newer GUI editors today.

    There seems to be a growing (or at least more and more visible) practise of editors (especially GUI editors) not including EOL at the end of every line. They treat it as a line separator, not a line terminator, resulting in no EOL at the end of the last line.

    Because of this, they also display lines incorrectly. I have noticed it with the editors in ZDE, Eclipse, and Scite. It only serves to create confusion when they interpret an EOL as 'start a new line', and actually start to display another line as if it already existed. This is very visible if you create a 'proper' text file you'll have to use a well-behaved text editor like vim for this) and open it in one of the above editors. It will display an extra line below the real last line of the file. You see something like this:

    1 first line
    2 middle line
    3 last line

    There are actually three lines in the text file and you can confirm this with 'wc -l '.

    There is a lot of confusion with people who don't understand the concept of EOL and what these editors are doing. For example, I have people at work who use ZDE and when they open a text file created by me (vim), they go bonkers because they think I've put an extra blank line at the bottom of my scripts. There have been problems in the past with people really putting unnecessary blank lines at the bottom of scripts, and of course this lead to premature headers errors. Naturally, they think I'm doing the same, because they don't realise that their editor is displaying the file incorrectly.

    I have one colleague who even wrote into our 'coding guidelines' recommending people not use vim because "it puts in extra characters that you don't ask for".

    I have noticed that Redhat's default emacs configuration (FC3 at least) also opens text files in binary mode by default, resulting in a missing EOL on the last line of a newly created text file.

    I'd like to know if I have the wrong idea about anything, but the question remains: what is the reason for these editors behaving this way?

    • If I had the points, I'd mod you up. I'm not familiar with ZDE or Scite, but I work with data transferred between different companies with a variety of systems. We end up writing custom adapter scripts to correct this kind of data format. End of line and end of file characters and character sequences are not universally standard. But sometimes they are completely and uniquely querky.

      I don't mind that so much. What winds me up is when they ask us to write export adaptor scripts to screw the data up a

%DCL-MEM-BAD, bad memory VMS-F-PDGERS, pudding between the ears