Slashdot Mirror


The Union of Vim with KDE

Philippe Fremy writes "Thomas Capricelli, Mickael Marchand and me are pleased to present the first ever stable version of KVim, finally bringing "the power of VIM with KDE's friendliness". This release contains a port of the standalone editor Vim 6.0 to Qt/KDE (2 and 3) and a KDE KPart Component. The component can currently embed either of GVim or KVim in Konqueror (screenshots), with out-of-process embedding. Further work is required before proper support for KDevelop, KMail and Kate is available, but things are moving forward." As everyone knows, Vim is the best (only?) text editor, and KDE is the best (only?) desktop system. Heh.

10 of 287 comments (clear)

  1. Re:Erm... by sydneyfong · · Score: 4, Informative

    Vim is scriptable.
    You can implement almost ANY function in Vim provided that it can be invoked from a shell. And with the powerful shell of linux, you can almost add any kind of "tricks up its sleeve" to Vim easily.

    Remember the UNIX philosophy of everything being small and doing just its own job?

    --
    Don't quote me on this.
  2. Google Cache by bobdown2001 · · Score: 5, Informative

    Well it looks like we Slashdotted it already.

    As usual you can view using the trusty Google cache by clicking here.

    Yeah I know I know ....karma whore :0p

    --
    Why do today what you can put off until tomorrow?
  3. Re:Nice, serious, but no thanks by Rentar · · Score: 3, Informative
    vim is all about those wierd keystrokes you learn that funnily enough grow on you and multiply your productivity.

    Of course, but the real beauty of KVim is the KPart. You can use the kvim kpart to edit any textfile in konqueror without opening another terminal and/or window. This is great for hybrid users who love the CLI/Shell but use konqueror or any other file manager every now and then. I usually use graphical file managers primarily for browsing (the local filesystem, not the web) and not for doing real work (like moving files around and editing text files). The KVim kpart might change this a bit.

  4. Re:Flamewar attempt by Anonymous Coward · · Score: 1, Informative

    GTK was/is LGPLed
    QT is now GPLed

  5. Re::x Re:Nice, serious, but no thanks by Pogue+Mahone · · Score: 3, Informative
    :x saves you one key
    ZZ saves you two keys.

    And both save you from touching the file if you didn't make any changes.

    --
    Every bloody emperor has his hand up history's skirt [Peter Hammill/VdGG]
  6. Re:Whatever next - KEmacs & GEmacs? by pipacs · · Score: 4, Informative
    Given that there is now a version of Vim for both Gnome & KDE, does it make sense for (X)Emacs to make the jump too? I know the origins of Xemacs are as much political as technical - but does it not make sense to try to branch off 2 versions of emacs into the 2 guis?
    First steps: XEmacs on the GTK platform.
  7. Re:Erm... by anshil · · Score: 2, Informative

    What's the big deal? VI rocked back in the days when 80x24 amber/green monitors / terminals were the thing to use, but today editors which are SMART are way more productive, since they let the developer focus on the job that has to be done, instead of looking up information that should be available at the fingertips. Any editor without intellisense-like functionality is a waste of time. Seriously.


    Thats what I would call the windows way of thinking. My edtior of choice is the one beeing effektive, not the one with the most tricks in it's sleeve. Yes tricks are these things that make people ohhh and ahhh, when showing, but in a day-to-day live they hardly proove useful. vim keycodes and sequences - once you know them - are very very very effektive, I can edit files twice as fast as with i.e. visual things like visual studio. About code insight, I don't like it as it is. It doesn't show right either way, how can the editor know how the compiler really sees the file?

    --

    --
    Karma 50, and all I got was this lousy T-Shirt.
  8. Re:Matching #if ... #else ... #endif by owenb · · Score: 3, Informative

    Yes, it does. Switch now!

  9. Re:Nice, serious, but no thanks by reynaert · · Score: 5, Informative
    Defies the whole persona of vim. vim loses what makes it useful when you stick it in a window and add menus and buttons.

    You'd better reread Vim's design goals. From the documentation:

    Vim is not a shell or an Operating System. You will not be able to run a shell inside Vim or use it to control a debugger. This should work the other way around: Use Vim as a component from a shell or in an IDE. A satirical way to say this: "Unlike Emacs, Vim does not attempt to include everything but the kitchen sink, but some people say that you can clean one with it. ;-)"
    Vim is designed to be embedded in other applications. An example of this is the integration with Sun Visual Workshop, support for which is included in the official version.
  10. Re:Nice, serious, but no thanks by Paladin128 · · Score: 3, Informative

    Actually, the real benefit is using KVim embedded in other KDE applications. If you REALLY like VI's input method, and want to use it in your mailer, IDE, etc., that's where KVim comes in.

    Now if only there was a KEmacs :)

    --
    Lex orandi, lex credendi.