- 8,625
- 31,276
Pst what's an IDE!? ISPF represent!
Actually is our resident C# / Biztalk guru still about? Khane I think?
- 1
IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
-
Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!
Go here and give us your nominations!Who's been the biggest Asshat in the last year? Give us your worst ones!
Pst what's an IDE!? ISPF represent!
Actually is our resident C# / Biztalk guru still about? Khane I think?
Noodleface
A Mod Real Quick
- 38,380
- 16,303
chaos
Buzzfeed Editor
- 17,324
- 4,839
- 16,970
- 7,989
WTB console editor with fully featured GUI. Does such a thing exist? My frustration with things like vim, vi, emacs, and even nano is that things I know how to do in other editors like PyCharm and Notepad++ are not immediately(or even somewhat) obvious in console editors due to the arcane shortcuts they have to assign them.
I don't use them often enough to invest the time memorizing these shortcuts either. Except for save and quit in emacs, got that one down. Still working on vi.
I don't use them often enough to invest the time memorizing these shortcuts either. Except for save and quit in emacs, got that one down. Still working on vi.
alavaz
Trakanon Raider
- 2,003
- 714
You should be able to either VNC connect to your nix machine or run X11 over SSH and use a GUI editor. Notepadqq is the linux np++ knockoff and is pretty awesome. If you use Ubuntu it should be available via apt. You can compile it from source on any distro though. I've even compiled it on Solaris before.
Cad
scientia potentia est
- 25,884
- 50,910
vi takes a while to get quick with. Once you do get quick with it, you will HATE using guis for a while because taking your hands off the keyboard slows you down so much.
- 1
Cad
scientia potentia est
- 25,884
- 50,910
Yea, and after 6 months of using vi daily, you'll be quick with the shortcuts.
Find some old dude with a neckbeard and suspenders in your office and watch him edit a file in vi.
Noodleface
A Mod Real Quick
- 38,380
- 16,303
- 519
- 210
As
Cad
says.... learn to love vi as a programmer. Can find it on almost any environment these days except Mainframe where the 3270 and ISPF still rules.
When vi and macros are too cumbersome for me hacking up a Perl reg/ex script usually works well to do more complex automations.
If you have trouble remembering the shortcuts use a Sticky Notes app to pin common stuff you need/use onto your screen for easy cut/pasting to the command line.
Perhaps consider using vi as your primary editor for a while if that is not enough, until you grasp the basics.
Cad
says.... learn to love vi as a programmer. Can find it on almost any environment these days except Mainframe where the 3270 and ISPF still rules. When vi and macros are too cumbersome for me hacking up a Perl reg/ex script usually works well to do more complex automations.
If you have trouble remembering the shortcuts use a Sticky Notes app to pin common stuff you need/use onto your screen for easy cut/pasting to the command line.
Perhaps consider using vi as your primary editor for a while if that is not enough, until you grasp the basics.
Vim is a really powerful tool and any developer should know it. However like every tool it is also bastardized by some. Sure vim CAN be a full featured IDE. But it really shouldn't be. It gets a bit of a bad rap because people can and will overuse vim so it is synonymous with old neckbeard hackers. But for editing scripts and txt files vim is the way to go.
I am far from a VI wizard but there are some things that I've memorized simply because I need them. I can give a short list
"/" + <word> + enter = search. Use 'n' to cycle through hits. Shift + n to go backwards a hit.
ctrl + d / ctrl + u for going down and up a document
shift + ^ = start of line / shift + $ = end of line
dd = cut current line (visual + d for cutting blocks)
p = paste
(while not in insert mode) x = delete at cursor
Those are ones I use every day. This also glosses over the absolute basics like saving/quit without save/quit with save/insert mode/visual mode.
I also suggest a good vim config. I use this one. GitHub - amix/vimrc: The ultimate Vim configuration: vimrc
"/" + <word> + enter = search. Use 'n' to cycle through hits. Shift + n to go backwards a hit.
ctrl + d / ctrl + u for going down and up a document
shift + ^ = start of line / shift + $ = end of line
dd = cut current line (visual + d for cutting blocks)
p = paste
(while not in insert mode) x = delete at cursor
Those are ones I use every day. This also glosses over the absolute basics like saving/quit without save/quit with save/insert mode/visual mode.
I also suggest a good vim config. I use this one. GitHub - amix/vimrc: The ultimate Vim configuration: vimrc
- 2,663
- 4,287
If you are a beginner, especially coming from a Windows background maybe you should start with "easy mode" vim. This automatically starts when you launch vim as "evim" or with "vim -y".
The main difference to "normal mode" vim is that you start in edit mode where you can enter text right away, and have to explicitly enter "command mode" with ctrl-o. Surprinsingly, this distinction seems also the hardest thing for people new to vi to grasp, as in "the stuff I enter does not show up and the editor does weird things with my file instead."
Once you understand that usually the next lesson is "commands can be repeated by prefixing them with numbers". So if you enter "yy" you copy the current line into the thing called "yank buffer" (which is not the system copy&paste buffer), and entering "3p" pastes the content of that three times. Like that "y3y" copies three lines into the yank buffer.
Repeating the "y" for a single line (and "d" as "delete into yank buffer") seems redundant at first, but once you get to the fun parts like "y$" (yank from cursor to end of line) or "ytx" (which is "yank from cursor to first occurence of, but not including character x") the basic principles fall into place.
Everything else is learing the shortcuts, like "V}gq" (visually mark current paragraph and reformat it), but you don't have to learn everything at once.
The main difference to "normal mode" vim is that you start in edit mode where you can enter text right away, and have to explicitly enter "command mode" with ctrl-o. Surprinsingly, this distinction seems also the hardest thing for people new to vi to grasp, as in "the stuff I enter does not show up and the editor does weird things with my file instead."
Once you understand that usually the next lesson is "commands can be repeated by prefixing them with numbers". So if you enter "yy" you copy the current line into the thing called "yank buffer" (which is not the system copy&paste buffer), and entering "3p" pastes the content of that three times. Like that "y3y" copies three lines into the yank buffer.
Repeating the "y" for a single line (and "d" as "delete into yank buffer") seems redundant at first, but once you get to the fun parts like "y$" (yank from cursor to end of line) or "ytx" (which is "yank from cursor to first occurence of, but not including character x") the basic principles fall into place.
Everything else is learing the shortcuts, like "V}gq" (visually mark current paragraph and reformat it), but you don't have to learn everything at once.
alavaz
Trakanon Raider
- 2,003
- 714
It's always interesting to see what everyone does with vim. Not many people actually use it enough to learn all of the tricks, but everyone has there few things that make their life easier.
Generally me being the admin-y type, I edit a lot of configs so 'dd' (delete line), 'R' (replace characters), 'G' and '#G' (move to last line / line number) get used a lot and then of course / and %s/find/rep/g
Generally me being the admin-y type, I edit a lot of configs so 'dd' (delete line), 'R' (replace characters), 'G' and '#G' (move to last line / line number) get used a lot and then of course / and %s/find/rep/g
Noodleface
A Mod Real Quick
- 38,380
- 16,303