From: Harry Putnam <reader@newsguy.com>
To: help-gnu-emacs@gnu.org
Subject: [OT] about vim plugins when necessary
Date: Wed, 18 Feb 2015 17:02:11 -0500 [thread overview]
Message-ID: <87a90aubdo.fsf@reader.local.lan> (raw)
Yes, I know I must be a screwball to try to post here with vim
questions, but I'm pretty sure I'm more likely to get knowledgable
answers or help here than anywhere else.
I'm sure others here find themselves in this situation sometimes too.
Where for whatever reason it is easier and faster to just use vim for
some coding on certain machines. Especially when you find yourself on
a wide variety of hosts.
I use emacs exclusively for perl coding on my home machines and rely
heavily on cperl mode.
When shifting to vim, for whatever reason, and although I am fairly
familiar with the basic functionality, I feel terribly crippled when
coding.
I've never taken or maybe had the time to dig anywhere near as much
into vim as I have emacs... so don't really know where or even how to
find some kind of plugin that would answer in vim for what
`cperl-mode' does in emacs.
Currently wrestling with a plugin family called `vim-plugins-master' but
having a serious bit of trouble figuring out how to edit some of the
templates to my liking. Or maybe how to employ something like emacs
`skeletons' capabilities .. where I write a bunch of helper
inserts. only for vim. Similar to how I've done with emacs.
So, cutting to the chase: Can anyone here either help directly or
guide me to well documented vim plugins for perl coding.
next reply other threads:[~2015-02-18 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 22:02 Harry Putnam [this message]
2015-02-19 17:56 ` [OT] about vim plugins when necessary Robert Thorpe
[not found] <mailman.377.1424296950.31049.help-gnu-emacs@gnu.org>
2015-02-19 0:45 ` Dan Espen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a90aubdo.fsf@reader.local.lan \
--to=reader@newsguy.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.