Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8923111
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T07:01:50+00:00 2026-06-15T07:01:50+00:00

Using Ubuntu 12. I installed jshint with sudo npm install jshint -g which jshint

  • 0

Using Ubuntu 12.

I installed jshint with

sudo npm install jshint -g

which jshint

shows
/usr/local/bin/jshint, which is also in the PATH variable

Then, I downloaded https://github.com/walm/jshint.vim/blob/master/plugin/jshint.vim
and put it in ~/.vim/bundle/jshint.vim (I am using Pathogen)

Now, when opening a js-File, such as

vim test.js

errors are not detected.

:JSHint 

results in “Not an editor command: JSHint”

:Helptags 

results in, well, nothing.. I don’t really see what that command is for, anyway..

I am a vim noob, but other pathogen bundles seem to work, so I do not really know what is not working here..

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T07:01:52+00:00Added an answer on June 15, 2026 at 7:01 am

    The default way to install plugins is to put their individual pieces in some subdirectories of your ~/.vim/ directory. Taking this plugin as example:

    ~/.vim/plugin/jshint.vim
    ~/.vim/doc/jshint.txt
    

    The :Helptags command is used to generate the index (tags) used by Vim to navigate through the documentation of third party plugins. You are supposed to use it like that:

    :Helptags ~/.vim/doc
    

    The idea behind Pathogen and other plugin managers is that each plugin should be in its own directory rather than be scattered through your ~/.vim/ directory. In Pathogen’s case (and others followed, but there’s no standard), that’s the bundle directory: ~/.vim/bundle/.

    Therefore, the correct location for your plugin should be:

    ~/.vim/bundle/jshint/plugin/jshint.vim
    ~/.vim/bundle/jshint/doc/jshint.txt
    ~/.vim/bundle/jshint/README.md
    ~/.vim/bundle/jshint/LICENSE
    

    In order for pathogen to work its magic, you are supposed to add these two lines to your ~/.vimrc:

    silent! call pathogen#infect()
    silent! call pathogen#helptags()
    

    The first line takes care of “registering” and loading each plugin found in ~/.vim/bundle/. The second line indexes their documentation, the equivalent of :Helptags … that you don’t need to run, then.

    So…

    1. Make sure Pathogen is installed and configured correctly.

    2. Install the JSHint plugin where it should be.

    3. ?

    4. Enjoy writing JavaScript in Vim!


    To run :JSHint on the current buffer every time you write it, add this line to your ~/.vimrc:

    autocmd! BufWritePost *.js JSHint
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Under Ubuntu 10, I installed using: npm install js2coffee Seems to install smoothly I
I'm using Ubuntu 9.10 Karmic Koala and Ruby 1.9.1. I installed Rails using sudo
I installed django using sudo pip install django after entering into the virual environment
I'm using Ubuntu 11.10, which came pre-installed with Python 2.7.3. I installed the python3
I am using Ubuntu 12.04. I also have ruby and rails installed on my
I am using Ubuntu and I have Qt offline which is installed from an
I am using Ubuntu 10.04 LTS version which has Firefox 3.6.3 version installed. I
I have installed the vim-latex package using Ubuntu Synaptic package manager and updated my
I am using Ubuntu 9.04 I have installed the following package versions: unixodbc and
I am using Ubuntu 9.04 I just installed ruby and rails in my system

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.