Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

OS version: Ubuntu 12.04

I wrote veditor in my terminal and got the following message:

No command 'veditor' found, but there are 39 similar ones

My question is how can I view those 39 similar commands?

share|improve this question
Possible duplicate of: – saji89 Jan 24 '13 at 6:24
Seems to be same situation, and it is common in Ubuntu. e.g from my machine: saji@geeklap:~$ veditor No command 'veditor' found, but there are 39 similar ones veditor: command not found – saji89 Jan 24 '13 at 6:40

Just to be clear what kind of editor did you mean by veditor?

Looks to me like a typo. If you type in editor a predefined text editor will start. In my case itś Nano.

Other editors you can use are gedit, vim, vi, etc.

Even man -k veditor doesn't even show suggenstions.

share|improve this answer
No No, you did not get my point. I know there is no such command as veditor and i am not even interested in running an editor, i know how to do that. what i am interested is in those <b> 39 similar ones </b> . is there a way to have a look at those commands? – kba1541 Feb 3 '13 at 7:04

for example if you know only starting of the command like vi then type vi and press tab then you will get the commands which starts from the name vi.

share|improve this answer
This is not always correct. By using the tab key- you show the possible solutions to any command starting on "vi-". That means, it might not be similar, but actually it will be exactly those two ++ more. – denNorske Apr 23 '13 at 19:49

The command-not-found script doesn't seem to have any way to do this by default.

Here's a modified version that takes a --all option. (click the permalink button in the top right to download the file)

python ./command-not-found --all veditor

This prints a list of every package that provides the 'editor' command.

The algorithm used to check for misspelled commands is very simple, so I doubt this will ever be helpful.

This page pointed me toward the right script:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.