Sponsored Content
Top Forums Programming Open Source What editor does everyone use? Post 302975069 by azurite on Wednesday 8th of June 2016 12:49:42 AM
Old 06-08-2016
Seems like Vi(m) is the popular choice. Any suggestions on what is friendly for a beginner?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Vi editor ?

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

instead VI editor - which one?

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

vi editor

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

best editor

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

vi editor

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

Pasting text in VI editor from a different editor

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

set EDITOR=vi -> default editor not setting for cron tab

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 :Licen

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

About vi editor

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

Not able to use @ in VI editor

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
ACHECK.1(1)						User Contributed Perl Documentation					       ACHECK.1(1)

NAME
acheck - Check common localization mistakes SYNOPSIS
acheck [OPTIONS] [INPUT_FILE] DESCRIPTION
This program parses a file checking for syntax rules and optionally asking Aspell for checking word spelling. It makes fix suggestions and outputs a corrected file accordingly adding review comments if requested. It tries to find the file type according to the extension or the first lines and loads rules accordingly. It displays lines when they are parse. When an error is found, a menu is displayed. Just press Enter if you don't want to change anything. If a choice suits you, enter the corre- sponding number. If you want to fix it but no choice is correct, enter a space, then you will be asked for a string to replace the high- lighted text. The script will replace the highlighted text with your choice and parse it again for new errors. Here are all the available commands: Enter, ignore. Ignore. Ctrl+L, redraw. Rewrite the last line, suggestions and hints. Space, edit. Edit the highlighted text. E, edit line. Edit the whole line. H, add hint. Add the displayed hint as review comment. Use this if you want the translator to see the corresponding warning or error but you have no correction. N, next line. Skip the rest of this line. X, exit and discard all changes. Quit without saving modifications, the script ask you for confirmation, you have to enter `yes' to exit otherwise parsing starts again at the current mistake. a, add in dictionary. Add the highlighted word to you personal dictionary, capitalized as it is. l, add lowercase in dictionary. Lowercase the highlighted word to add it to your personal dictionary. i, ignore word. Ignore the highlighted word, same as Enter. I, ignore all. Ignore the highlighted word and add it to your session dictionary. OPTIONS
Verbosity level: -q, --quiet quiet mode. -v verbose, start at level $Debug + 1, add more for more verbosity (see below). --verbose n set verbosity level to n (see below). Files: -i, --input input filename, can be '-' to read data from standard input. -o, --output output filename, can be '-' to write data to standard ouput. If no output filename is provided, input file is backed up with `bak_ext' extension and input filename is used. Spell check: -s, --spell check spelling with Aspell. -d language, --dict language use language dictionary for Aspell. -n, --nospell don't check spelling. Mode: -r, --review review mode, add comments on lines beginning with $Comment after parsed line. -t, --trans translator mode, don't add comments, just fix errors. others: --rules ruleset use ruleset rules set. --type filetype use filetype whatever the file type is. --dump Dump the rules to check and exit, use this for debugging purposes. -V, --version print version and exit. -h, --help print a short usage message and exit. Verbosity Level 0 quiet, normal only warnings and errors 1 debug names of subroutines 2 debug verbose names and arguments of subroutines 3 .. 5 debug very verbose output parsing and checking details SEE ALSO
acheck(5), acheck-rules(5) AUTHOR
Nicolas Bertolissio <bertol@debian.org> perl v5.8.4 2003-10-05 ACHECK.1(1)
All times are GMT -4. The time now is 08:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy