08-31-2012
I am getting error message like
bash: vi: command not found
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
when i open a file to edit and type i to insert and the type # for #!/bin/bash
in vi and vim editor the message come that no string under cursor plz somebody help (0 Replies)
Discussion started by: mrityunjay22
0 Replies
2. UNIX for Dummies Questions & Answers
I have downloaded latest cygwin editor for windows xp.
vi editor is not working on it.
the error i get is "vi : command not found"
I have already seen a post in this forum regarding the issue but the links in the post are broken.
So please help on this issue.
thanks in advance (1 Reply)
Discussion started by: arparwan
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
4. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
5. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
6. UNIX for Dummies Questions & Answers
now i am new to unix... i installed cygwin on windows because i want to make c++ program... and i need vi editor... whenever i write (vi anything) in the cygwin terminal it says vi: command not found ...since i installed all the packages (1 Reply)
Discussion started by: mostafamagdy
1 Replies
7. Shell Programming and Scripting
Hi,
I am using CYGWIN for script testing. I have found that vi command does not work in this. Kindly suggest how can I edit a script that is stored in a file ??? (5 Replies)
Discussion started by: himvat
5 Replies
8. UNIX for Dummies Questions & Answers
I ran into this issue and thanks to various postings in various forums, was
able to figure out the solution but didn't see one posting that laid the
whole issue out cleanly. So thought the following might help others ...
------------------------------------------------------------------------... (2 Replies)
Discussion started by: oxysep
2 Replies
9. Shell Programming and Scripting
I installed Cygwin today and my vi editor was not working i.e. on while using vi command, I was getting "command not found" error.
I realized that many have faced this problem and the previous threads on this have been closed without complete answers.
I tried something and it worked. Wanted to... (1 Reply)
Discussion started by: erora
1 Replies
10. Shell Programming and Scripting
I'm using cygwin on win7, What I would like to do is something like this:
cygstart cygwin tail -f /foo/test.log | perl -pe 's/error/\e
I know I can start a new instance using either of these:
mintty -e ...
cygstart tail ...
But neither of those open in ANSI mode, so I can't do... (0 Replies)
Discussion started by: Validatorian
0 Replies
LEARN ABOUT DEBIAN
git-sh-setup
GIT-SH-SETUP(1) Git Manual GIT-SH-SETUP(1)
NAME
git-sh-setup - Common git shell script setup code
SYNOPSIS
. "$(git --exec-path)/git-sh-setup"
DESCRIPTION
This is not a command the end user would want to run. Ever. This documentation is meant for people who are studying the Porcelain-ish
scripts and/or are writing new ones.
The git sh-setup scriptlet is designed to be sourced (using .) by other shell scripts to set up some variables pointing at the normal git
directories and a few helper shell functions.
Before sourcing it, your script should set up a few variables; USAGE (and LONG_USAGE, if any) is used to define message given by usage()
shell function. SUBDIRECTORY_OK can be set if the script can run from a subdirectory of the working tree (some commands do not).
The scriptlet sets GIT_DIR and GIT_OBJECT_DIRECTORY shell variables, but does not export them to the environment.
FUNCTIONS
die
exit after emitting the supplied error message to the standard error stream.
usage
die with the usage message.
set_reflog_action
set the message that will be recorded to describe the end-user action in the reflog, when the script updates a ref.
git_editor
runs an editor of user's choice (GIT_EDITOR, core.editor, VISUAL or EDITOR) on a given file, but error out if no editor is specified
and the terminal is dumb.
is_bare_repository
outputs true or false to the standard output stream to indicate if the repository is a bare repository (i.e. without an associated
working tree).
cd_to_toplevel
runs chdir to the toplevel of the working tree.
require_work_tree
checks if the current directory is within the working tree of the repository, and otherwise dies.
require_work_tree_exists
checks if the working tree associated with the repository exists, and otherwise dies. Often done before calling cd_to_toplevel, which
is impossible to do if there is no working tree.
require_clean_work_tree <action> [<hint>]
checks that the working tree and index associated with the repository have no uncommitted changes to tracked files. Otherwise it emits
an error message of the form Cannot <action>: <reason>. <hint>, and dies. Example:
require_clean_work_tree rebase "Please commit or stash them."
get_author_ident_from_commit
outputs code for use with eval to set the GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL and GIT_AUTHOR_DATE variables for a given commit.
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-SH-SETUP(1)