What's your favorite IDE/text editor when it comes to programming? Also, what's the setup in the banner up top? http://static.4-ch.net/images/boardtitles/programming.gif, that is.
Is anyone Harverd or MIT?
Emacs
EditPadPro
qwe
Dunno if anyone's mentioned it, but you can change your keyboard bindings to switch the caps-lock key with the control key. It takes a little bit to get used to, but it makes much more sense, when you think about it. When's the last time you used caps lock (other than for cruise control) anyway?
nvi, for editing in general.
>i've just discovered this: http://ex-vi.sourceforge.net/
>it's much more lightweight than vim, and has the one feature i really wanted that nvi doesn't have: support for utf-8.
>i've been using nvi, but the lack of utf-8 support meant that i had to use some other editor (usually mined 2000) whenever i wanted to edit a utf-8 encoded file.
nvi has had UTF-8 support since 2000:
https://en.wikipedia.org/wiki/Nvi
>Sven Verdoolaege added support for Unicode in 2000.[3]
>BSD projects continue to use nvi version 1.79 due to licensing differences between Berkeley Database 1.85 and the later versions by Sleepycat Software.
Fucking tools.
EditPad Lite.
If I've got to work in a *nix text mode, JOE.
VS a shit.
vim + http://vim.spf13.com/
Nedit, nvi, GNU Emacs/XEmacs and Xedit.
Get on my level scrub.
Sublime Text, vi on servers, Visual Studio is fine too.
Depends what I'm working on. If i'm working on some bloated e-commerce mess for a .net client, visual studio is opan obvious choice,
Everything else, ST or if unavailable vi
BSD vi, ed, mg on Unix. Sam and acme on Plan 9. Pe on Haiku.
I like vim with solarized dark colorscheme and the linter syntastic. All is very comfortable that way.
Well, I started with "vi" on my very first shell account (a SunOS 4.x box, back in 1995). No idea what exact version of vi it was, but I didn't have any colors or visual mode, or anything like that. Soon after that, I installed Slackware and started using "vi" there as well. And since I completely stayed away from Windows all these years (except when required for a job), I just kept using vi or vim.
Somewhere along the way I got the crazy idea to swap the Escape and CapsLock keys, using either xmodmap or its console equivalent (e.g. wsconsctl in OpenBSD). That made things a lot more comfortable...
Speaking of OpenBSD, their /usr/bin/vi program is a slightly enhanced version of nvi, because it allows you to split the screen and have several text windows displayed at once. I didn't even realize this until one of the developers mentioned it on openbsd.misc:
our vi has multiple windows.
:E new_file
then ^W to move from file to file.
:viusage
will give you some help.
Granted, the <Control-W> thing is explicitely mentioned in the manpage, but it doesn't explain the differences between the :e and :E commands. All it says is this:
[Ee][dit][!] [+cmd] [file]
[Ee]x[!] [+cmd] [file]
Edit a different file.But anyway, it's a nice feature to have (although I guess you could get similar functionality with tmux windows also).
I also know the basics of "ed", just in case - because at least /bin/ed is statically linked and might be the only thing available to edit files with if /usr is fubar, or the dynamic linker is broken. Well it's not like it's that much different from vi anyway...
Back in my home computer days, I mainly used Notepad on my Amiga 500 (it's the default editor there, but not identical to Windows Notepad). There was also uemacs (microemacs) on one of the Workbench floppies, but I didn't bother with it. I think AmigaBasic (the version shipped with Workbench 1.3) had its own IDE though. I played around with that, but didn't do much except write some character generators and other tools for our tabletop AD&D games.
Before that I had an Amstrad CPC and there of course just used the ROM BASIC screen editor. It works quite well, especially when you switch to 80-column mode (just typing "mode 2" at the prompt did the trick). Their BASIC dialect (Locomotive BASIC) was also fairly powerful, giving you access to many graphics and sound functions without needing to go through the PEEK/POKE mumbo-jumbo. That machine also shipped with CP/M disks, which contained an "ed" program but I didn't really bother with that.
>>164
there's no such thing as vi that doesn't have visual mode. perhaps you're thinking of ex?
>>165
Sorry I meant no visual block operations (select, copy, paste) like vim has. Yeah, the SunOS vi was running in regular full screen mode.
Now the "mail" or "mailx" programs, those dropped you into ed or maybe ex by default, for some reason. I mostly used Pine those days, and only occasionally mail in command line mode, e.g.:
mail -s "hi there" recipient@host < msg.txt
Later on when I started doing sysadmin work, I found myself just telnet'ing to SMTP and POP3 ports a lot (for testing purposes). Those interfaces are actually pretty simple; there's just no nice command-line editing/history or saving of messages to "sent-mail" folder or whatever (unless you're logging the session via typescript or whatever).
Emacs is love; Emacs is life.
mg
Been using textadept lately. Like it a lot.
>>171
I just started mg a few weeks ago after getting fed up once too often with emacs. It's certainly the best lite emacs out there. I wish it had:
- better support for unicode
- better documentation for binding things. Sometimes you have to put a \, sometimes a ^, and the examples are completely unhelpful.
I'd probably switch full time if it had syntax highlighting (yes, I'm weak) and if I had a good stand-alone LaTeX reformatter.
I tried Spacemacs after using Vim for years, and have now settled on neovim.
tbh, php is shit. java is pretty dank though