06-21-2005
Quote:
Originally Posted by jim mcnamara
UltraEdit because it supports syntax highlighting for many dozens of languages/environments.
The bad part is it runs on Windows - I think there is an X version coming out, dunno.
UltraEdit is a great editor but, as you said, it's Windows only. You can use the ftp save as but that is still not that great.
I prefer vi since it is just about on every Unix box that I've ever used and, once you get used to it, navigation and feature use is only a couple of keystokes away. A couple of features that are very handy are bookmarks, copy and paste buffers, launching a program and automatically reading its output into your text, lauching a program using your text as input. These will become second nature and you'll get going pretty fast. I kind of wish UltraEdit could switch on a vi mode once in awhile.
Thomas
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 OPENDARWIN
set_display_switch_mode
set_display_switch_mode(3alleg4) Allegro manual set_display_switch_mode(3alleg4)
NAME
set_display_switch_mode - Tells Allegro how the program handles background switching.
SYNOPSIS
#include <allegro.h>
int set_display_switch_mode(int mode);
DESCRIPTION
Sets how the program should handle being switched into the background, if the user tabs away from it. Not all of the possible modes will be
supported by every graphics driver on every platform. The available modes are:
SWITCH_NONE
Disables switching. This is the default in single-tasking systems like DOS. It may be supported on other platforms, but you should use it
with caution, because your users won't be impressed if they want to switch away from your program, but you don't let them!
SWITCH_PAUSE
Pauses the program whenever it is in the background. Execution will be resumed as soon as the user switches back to it. This is the default
in most fullscreen multitasking environments, for example the Linux console, but not under Windows.
SWITCH_AMNESIA
Like SWITCH_PAUSE, but this mode doesn't bother to remember the contents of video memory, so the screen, and any video bitmaps that you
have created, will be erased after the user switches away and then back to your program. This is not a terribly useful mode to have, but it
is the default for the fullscreen drivers under Windows because DirectDraw is too dumb to implement anything better.
SWITCH_BACKGROUND
The program will carry on running in the background, with the screen bitmap temporarily being pointed at a memory buffer for the fullscreen
drivers. You must take special care when using this mode, because bad things will happen if the screen bitmap gets changed around when your
program isn't expecting it (see below).
SWITCH_BACKAMNESIA
Like SWITCH_BACKGROUND, but this mode doesn't bother to remember the contents of video memory (see SWITCH_AMNESIA). It is again the only
mode supported by the fullscreen drivers under Windows that lets the program keep running in the background.
Note that you should be very careful when you are using graphics routines in the switching context: you must always call acquire_screen()
before the start of any drawing code onto the screen and not release it until you are completely finished, because the automatic locking
mechanism may not be good enough to work when the program runs in the background or has just been raised in the foreground.
RETURN VALUE
Returns zero on success, invalidating at the same time all callbacks previously registered with set_display_switch_callback(). Returns -1
if the requested mode is not currently possible.
SEE ALSO
set_display_switch_callback(3alleg4), get_display_switch_mode(3alleg4), exmidi(3alleg4), exswitch(3alleg4)
Allegro version 4.4.2 set_display_switch_mode(3alleg4)