Senliture From Australia, joined May 2000, 431 posts, RR: 0
Reply 11, posted (10 years 6 months 4 weeks 1 day 15 hours ago) and read 1269 times:
Quoting B744F (Reply 10): vi is nice, except no page down functions really hurts when im looking through logs
I doubt. What version of os you are using? Have you ever tried vim? Some unix and SunOs seperate vi and vim while most of the linux have actually lniked the vi to vim. Once loaded the vim, type
(remember the colon)
or, you can create a file (or open if exists) called
(remember the dot at the beginning)
and type the :set nocp into it and store/exit.
btw, I use vim as it was the first editor that my school taught me when we were introduced to linux. Took me a while to get used to the commands, but they make senses.
Klaus From Germany, joined Jul 2001, 21652 posts, RR: 53
Reply 13, posted (10 years 6 months 4 weeks 1 day 12 hours ago) and read 1251 times:
I use vi (or, if available, pico) if I must, but fortunately BBEdit covers practically all cases I currently need. Where necessary I use BBEdit's built-in SFTP client to access files on remote servers transparently.
It's nice to have console-based editors as an ultimate backup if everything else should fail, but that is inceasingly rarely the case. And I'm happy about it as the console editors are incredibly cumbersome and slow compared with a proper graphical one.
Key bindings, regular expressions, programmable text processing, integrated CVS support and many other features are available in BBEdit as well (combined with cross-application scripting through AppleScript).
I'm not missing anything - and the Editor is my primary working tool.