Author Topic: Command Line Programming Editor? (Read 6688 times)

Capn_Fish · « **on:** June 15, 2007, 02:45:13 pm »

Are there any good command line/text-based programming editors out there for C++? I've been looking, but haven't found much. Being small and not having many deps would be nice, too.

Thanks in advance.

jfv · « **Reply #1 on:** June 15, 2007, 04:04:19 pm »

Capn_Fish · « **Reply #2 on:** June 15, 2007, 04:51:32 pm »

Vi won't die on my Z. I'll start it, then mash buttons until it finally "closes," at which point my Z will become very slow, so I check top, which shows that it is eating 99% of the CPU. "killall vi" appears to kill it (e.g., outputs nothing), but doesn't, so I have to reboot.

Also, I have no idea what Vi's keybindings are.

EDIT: It's better on r198...Just sits there and eats 1% of my RAM, but still won't die. Still not acceptable in my book.

speculatrix · « **Reply #3 on:** June 15, 2007, 06:01:33 pm »

have you tried ":q" or "ZZ" to exit/save vim.

it's not a wysiwyg text editor.

Capn_Fish · « **Reply #4 on:** June 15, 2007, 06:02:55 pm »

I've been using Ctrl-Z to quit, I believe.

EDIT: Oops...That doesn't quit. How do I get back to a program that I've Ctrl-Z'd?

jfv · « **Reply #5 on:** June 15, 2007, 06:07:41 pm »

Ctrl-Z is not a way to quit vi.

tanjian2 · « **Reply #6 on:** June 15, 2007, 08:23:55 pm »

Quote

Ctrl-Z is not a way to quit vi.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163260\"][{POST_SNAPBACK}][/a][/div]

No Ctrl-z suspends your foreground task. You can type fg to get it back or bg if you are happy to run it in the background.... unlikely for vi but maybe ok for other tasks.

Also look for vim (vi-improved) its better - syntax colouring etc... and still reasonably light.
Must admit I'm an emacs fan for all editing - but its not light by any means...still compile mode for jumping to compiler errors, version control (via rcs/cvs) etc...

T3_slider · « **Reply #7 on:** June 15, 2007, 10:44:49 pm »

If "killall vi" doesn't work you can always try "killall -9 vi" which should definitely work (otherwise you can use "ps aux | grep vi" to find the pid of vi and then use "kill -9 pid" to kill it for sure). I personally use pico for any editing because it's easy (I hate vi because, although I can use it if I have to, it is unintuitive to me). I like emacs but it is a little heavy for casual use on the Z.

Capn_Fish · « **Reply #8 on:** June 15, 2007, 11:38:22 pm »

How do you make it start up with C++ syntax highlighting? The example vimrc doesn't really help.

TIA.

tanjian2 · « **Reply #9 on:** June 16, 2007, 05:14:41 am »

Quote

How do you make it start up with C++ syntax highlighting? The example vimrc doesn't really help.

TIA.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163276\"][{POST_SNAPBACK}][/a][/div]

I believe it depends on which terminal type you are using it in. It works fine for me in aterm, xterm/gtkterm2/terminal uses bold/underline instead of colour. I think it has more to do with how your terminals are configured... I recently upgraded to pdaxii13 5.4.6 and even how 'ls' colours its listings changed.....

check your TERM environment variable - "env | grep -i term"

I have ansi - in aterm and xterm everywhere else. Vim site I looked at suggested "linux" as the terminal. Try
export TERM=linux and then run vim and see if that helps.

Like pgas I assume you know vi is not vim - but certainly Meanie replaced vi with vim on pdaxii13....
good luck

pgas · « **Reply #10 on:** June 16, 2007, 06:42:56 am »

Maybe you know this but just in case:

note that vi != vim

There is a vi that comes from busybox, that doesn't do all the fancy
things vim does.

(emacs also runs in a terminal)

Capn_Fish · « **Reply #11 on:** June 16, 2007, 10:22:49 am »

Still a no-go. I exported TERM to be linux, and COLORTERM to be true (I also tried 'linux,' but to the same effect).

EDIT: Never mind, I just had to open a file with the right extention to get the highlighting to show up. It works now! Thank you, this looks promising.

kopsis · « **Reply #12 on:** June 16, 2007, 12:09:24 pm »

Of course none of these suggestions are command-line editors. If you want one of those then of course THE choice is ED (click for more info) -- the one true editor

Note for the humor impaired: No, I'm definitely not being serious

tanjian2 · « **Reply #13 on:** June 16, 2007, 03:48:59 pm »

Quote

Still a no-go. I exported TERM to be linux, and COLORTERM to be true (I also tried 'linux,' but to the same effect).

EDIT: Never mind, I just had to open a file with the right extention to get the highlighting to show up. It works now! Thank you, this looks promising.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163295\"][{POST_SNAPBACK}][/a][/div]

Silly me - I assumed you were editing a .c, .h .hpp or .cpp file - broke my own rule - never assume anything!

Capn_Fish · « **Reply #14 on:** June 16, 2007, 06:42:04 pm »

Well, I was...It just hadn't been saved yet.

News:

Author Topic: Command Line Programming Editor? (Read 6688 times)