CODEWITHSUNDEEP
vimmacvimjanus
Flov
Flov

Reputation: 1587

Janus upgrade important functionality missing after upgrade

I just upgraded to the newest Janus and there are alot of things that I miss since December 2011 :(

For example when i entered :cd it changed to :ChangeDirectory and after changing the directory the nerdtree also updated. The same thing applies for :e which changes to :Edit

This is not anymore the case with the newest Janus.

Command-T is also not anymore available anymore. What is the easiest way to add Command-T as a plugin?

Greetings from Nepal and Thank you :)

Upvotes: 1

Views: 295

Answers (1)

romainl
romainl

Reputation: 196886

First, what happens to you is the number one reason why using Janus (and other packages for Vim) is a terrible idea.

Instead of controlling your environment your are almost totally dependent on someone else's desiderata: because Janus's author appears to have decided against some of his previous choices and upgrading Janus is an "all or none" affair you are left in the cold with a Vim you don't understand or are not accustomed to.

You don't have to trust me but I assure you that the right way to customize Vim is to start with nothing fancy, do it yourself, little by little, without copying other people's entire vimrcs and try and install the plugins you like by yourself. Because you start from nothing and know what you add you'll never be in that kind of situation.

Second, whenever you upgrade something you owe it to yourself to review the changes before actually performing the upgrade. $ rake is easy, I must admit, but if you had taken a couple of minutes to look at Janus's Github page you would have seen that Command-T is not included anymore and replaced by CtrlP.

Third, Command-T is not and has never been a part of Janus. It's a separate project run by someone else that used to be included as a Git submodule. To install it, you need to download it separately and follow the instructions. Or add it yourself as a submodule.

Four, greetings from France, lucky bastard ;).

EDIT

To answer your comments…

I went through the TM > Vim transition myself. I started by trying to turn Vim into a TM clone but the whole idea was flawed in so many ways. Many of these flaws apply to Janus as well, IMO.

  • You have too many custom "mac-like" mappings that seem to make your life easier because they don't require you to learn new shortcuts. That's cool until you need to use Vim on a remote server via a terminal emulator which actively blocks many Ctrl- mappings, doesn't make the difference between Ctrl+Shift and Ctrl and don't even register the Cmd key.

    If your vimrc is well organised (and it is, more or less, in Janus) your <D-> custom mappings won't be activated when not in MacVim but you'll end up with two sets of custom mappings to learn and maintain! What if Janus's author decides one day that he prefers <leader>x to jump to tab x instead of the current <D-x>/<C-x>? Are you going to unlearn the previous mappings? Are you going to modify Janus's mappings.vim to get the old mappings back?

    Why not learn and use Vim's native commands instead? 2gt is easy and will likely work on every Vim you'll ever come across.

    You grow accustomed and dependent to too many plugins, some of them not doing much more than native commands or even overlaping each other like the current Buffergator and CtrlP.

  • Customizing Vim is a great way to learn how to use it. It takes time, maybe, but the win is big.

ENDEDIT

Upvotes: 1

Related Questions