id       = "janus"
name     = "Janus"
homepage = "https://github.com/carlhuda/janus"
description = "A distribution of plug-ins and mappings for Vim, Gvim and MacVim."

# Janus is a distribution installed into ~/.vim by its own rake task; it defines
# no command, so there is no binary a user types and no bundle identifier. The
# entry is filed and detected under the project's name, the way the other editor
# and shell frameworks in this catalog are. Deliberately not `vim`: that maps to
# Vim's own entry, whose ~/.vim is the tree Janus installs itself into.
executables   = ["janus"]

[dotfiles]

# README, Customization: "You can use ~/.gvimrc.before and ~/.vimrc.before for
# settings Janus itself uses, such as the leader setting. You may also use
# ~/.gvimrc.after and ~/.vimrc.after for any additional settings; it is also a
# good place for overriding Janus settings, as both files will be loaded at the
# end of Janus." Those four files are the user's half of a Janus setup and the
# only part the project asks them to write.
#
# ~/.vim and ~/.vimrc are not listed: Janus owns them after installation and
# they are Vim's entry, not this one.
paths = [
  "~/.vimrc.before",
  "~/.vimrc.after",
  "~/.gvimrc.before",
  "~/.gvimrc.after",
]

# Same section: "~/.janus" is the custom plugins directory, where the user adds
# their own plugins "either via git clone or as git submodules" and which "is
# treated like a normal pathogen directory". Those are checkouts — Janus
# reinstalls them from their remotes — so the directory never syncs as content
# and is not listed above either.
exclude = []
secret  = []

# No machine_lines: leader keys, mappings and plugin settings are exactly what a
# user wants on a second machine.
side_effect = false