10-23-2005
I use vi for shell scripts on Solaris (at work). I use xemacs for anything more involved, especially for Perl, with syntax highlighting. I've opened my emacs-edited Perl scripts under vi and been very, very afraid. It's like trying to watch a movie with no picture.
Emacs is more for the hardcore, IMHO. There's sooo much to it! But since work came to dominate my life, I don't have time to modify it any longer. If I was new to UNIX/GnuLinux, I probably wouldn't take the time to learn it.
However, vim has syntax highlighting and though I don't use it too much, it seems decent. I use vim mostly in Windows. It's great for those who are used to vi!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello everybody,
My question is: how to add /tmp/work at the end of line in vi editor.
my file looks like:
cp file1
cp file2
cp file3
****
I need to add " /tmp/work" at the end of each line.
I tried this
:%s/$/" /tmp/work"
and this
:%s/$/\ /tmp/work\/
but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies
2. HP-UX
I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one?
thx (6 Replies)
Discussion started by: diamond
6 Replies
3. UNIX for Advanced & Expert Users
Hi,
how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before.
for exemple if in my file i have
line 1
line 2
I want to have :
start line 1 end
start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies
4. UNIX Desktop Questions & Answers
We work on AIX 5L
We use vi as text editor (only scripts to create and modifiy).
What do you think of emacs ? Where can I find it ?
Do you know better text editor for scripts ?
Thank you for all answers. (1 Reply)
Discussion started by: annemar
1 Replies
5. HP-UX
I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work.
how can I enable them.
thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies
6. 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
7. 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
8. 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
9. Shell Programming and Scripting
How can ` character be printed on vi editor ?
empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies
10. Shell Programming and Scripting
Hello All,
Need one Help for one issue.
I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it.
It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies
LEARN ABOUT DEBIAN
vim-registry
vim-registry(5) vim addons vim-registry(5)
NAME
vim-registry - syntax for vim-addons registry files
SYNOPSIS
PACKAGE-NAME.yaml
DESCRIPTION
A registry file is a multi-document YAML file (i.e. it can be composed by several different YAML documents separated by "---" lines). Each
YAML document represents a registry entry, that is the information describing a single addon.
Ideally, the registry directory contains one file per package shipping addons; with a filename obeying to the convention PACKAGE-NAME.yaml.
Hence a single package can contribute to the registry with multiple entries described in a single YAML file.
For example, the "vim-scripts" package should ship a single /usr/share/vim/registry/vim-scripts.yaml file, containing one YAML document per
shipped addon. The first lines of such file can look like the following:
addon: alternate
description: "alternate pairing files (e.g. .c/.h) with short ex-commands"
basedir: /usr/share/vim-scripts/
disabledby: "let loaded_alternateFile = 1"
files:
- plugin/a.vim
- doc/alternate.txt
---
addon: whatdomain
description: "query the meaning of a Top Level Domain"
basedir: /usr/share/vim-scripts/
disabledby: "let loaded_whatdomain = 1"
files:
- plugin/whatdomain.vim
---
Each registry entry may contain the following fields, to be typeset according to the YAML specification:
addon (Required)
Name of the addon.
description (Required)
Human understandable textual description of the addon.
files (Required)
List of the files which compose the addon and are required to be present in a component of the Vim runtime path for the addon to be
enabled. Each file is specified relative to a component of the Vim runtime path.
basedir (Optional)
Directory where the files shipped by the addon (i.e., where the symlinks of the user/sysadm should point to) reside on the filesys-
tem. Default is /usr/share/vim/addons.
disabledby (Optional)
Vim script command that can be used (usually by adding it to ~/.vimrc) to prevent the addon from being used even when it is
installed. The intended usage of this field is to "blacklist" an undesired addon whose files are available, and hence automatically
loaded by Vim, in a component of the Vim runtime path.
AUTHOR
James Vega <jamessan@debian.org>
SEE ALSO
vim-addons(1), YAML specification <http://www.yaml.org/>
COPYRIGHT
Copyright (C) 2010 James Vega
This program is free software, you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as pub-
lished by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
Debian Project January 2010 vim-registry(5)