Merge pull request #26 from clvv/master

Custom Filetype Detection Support via `vimpager_ptree`
add clvv to CONTRIBUTORS
All <Up> and <Down> actions page as expected

I usually expect after firing off my pager that pressing down will scroll me
one line down (if possible), and that pressing up will scroll me one line up
(if possible).

With vimpager, I have the trouble that scrolling upwards at the beginning of a
document moves my cursor up, but if I want to move down, I have to invest
keystrokes to move my cursor back to the "scrolloff point" in the document
before any scrolling actually happens.

When quickly viewing man pages or scrolling long git-logs, my fingers will
sometimes move up and down as part of my rhythm, and I've started expecting my
pager to ignore this. Moving up in the beginning of a document or down at the
end of a document has always been meaningless in a read-only paging
environment, so I patched it to behave like that.
Merge pull request #27 from iftekhar25/master

Scrolling <Up> and <Down>
noremap up/down mappings into preceding -c

Squash the new up/down mappings into the preceding -c with the
:nohlsearch mapping to keep the number of -c commands low, because there
is a limit on them.

Change the nmap to an nnoremap, as that seems to work much better. For
me with just an nmap <Down> was jumping too many lines down.

Add the mapping to the GUI vim invocation section as well.

Add iftekhar25 to CONTRIBUTORS section.
add vimpager_ptree example to docs

Example is from github pull request:

https://github.com/rkitover/vimpager/pull/26

Regenerate README and man page.
release 1.6.7
Turn off relative line numbers.
Merge pull request #28 from simono/nornu

Turn off relative line numbers.
Vim versions < 7.3 don't have the "relativenumber" feature

Ignore errors when setting nornu
Merge pull request #29 from anisse/master

Error when using vim versions < 7.3
fix: safe mode for temp directory, else any user can read you stdin file
Merge pull request #31 from amsibamsi/master

safe mode for temp directory
fix custom scrolloff setting (GitHub Issue #30)

There was a problem with 98caa3e in how the scrolloff value was read, so
it was being set to a very high number and it was screwing up the first
'n' after a search.
add recent contributors
release 1.6.8
stop sourcing vimrc/gvimrc twice

Sourcing vimrc/gvimrc twice was causing problems for some people:

https://github.com/rkitover/vimpager/pull/32

however this was done in 7b92857 because the "syntax on" statement in
less.vim resets highlights.

The requestor suggested a more elegant solution to that issue, which
also fixes his, that is to use --cmd 'runtime! macros/less.vim' instead
of -c to source less.vim. This seems to not cause any problems, and we
can remove the re-sourcing of the rc files.
release 1.6.9
try fix for OpenBSD ps (GitHub Issue #33)

OpenBSD ps uses -o command instead of -o comm format for the ps command,
according to the man page and the submitter. I haven't tried this fix
yet, going to install an OpenBSD VirtualBox image to try it out.
add mapping for q (GitHub Issue #34)

As of a8f81d6 plugins could override less.vim's mapping of q since the
sourcing of less.vim was moved to a --cmd.

Add a noremap for q to -c (which is after .vimrc/.gvimrc and plugins are
loaded.)