Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master

Merge pull request #24 from tc-0/master

filetype of diary entries configurable
latest commit b340c43835
mattn authored
Octocat-spinner-32 autoload filetype of diary files configurable January 14, 2014
Octocat-spinner-32 doc Merge pull request #24 from tc-0/master January 14, 2014
Octocat-spinner-32 plugin Issue #10 October 27, 2013
Octocat-spinner-32 .gitignore Add .gitignore March 19, 2013
Octocat-spinner-32 Makefile Add Makefile March 26, 2013
Octocat-spinner-32 README.md Fixes doc, close #16 July 08, 2013
Octocat-spinner-32 calendar.vim.vimup Fix vimup source March 26, 2013
README.md

calendar.vim

calendar.vim creates a calendar window you can use within vim. It is useful in its own right as a calendar-inside-vim. It also provides hooks to customise its behaviour, making it a good basis for writing new plugins which require calendar functionality (see :help calendar-hooks for more information).

Installation

You can install calendar.vim in the usual way, by copying the contents of the plugin, autoload and doc directories into the equivalent directories inside .vim.

Alternatively, if you manage your plugins using pathogen.vim, you can simply clone into the bundle directory:

cd ~/.vim/bundle
git clone git://github.com/mattn/calendar-vim

Or, using submodules:

cd ~/.vim
git submodule add git://github.com/mattn/calendar-vim bundle/calendar-vim

Usage

Bring up a calendar based on today's date in a vertically split window:

:Calendar

Bring up a calendar showing November, 1991 (The month Vim was first released):

:Calendar 1991 11

The above calendars can alternatively be displayed in a horizontally split window:

:CalendarH

Bring up a full-screen:

:CalendarT

Fast mappings are provided:

  • <LocalLeader>cal: Vertically-split calendar
  • <LocalLeader>caL: Horizontally-split calendar

For full documentation, install the plugin and run :help calendar from within Vim.

Something went wrong with that request. Please try again.