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.
autodocumentation is ok. if its good enough for python and qt its good enough for me.
kate and vi
I mostly use THE, but occasionally I also use vi (ex-vi in particular).
I actually really like se but it doesn't work on modern *nix. Maybe I should update and port it.
>>103
THE? se? Links.
>>103
THE? se? Links.
>>104,105
This place sucks :(
ed for the win.
>>104 >>105
THE: http://hessling-editor.sourceforge.net/
You can probably find the "se" source code in the comp.unix.sources archive.
Both are descended from XEDIT, an editor for IBM mainframes.
There's also a related editor that works on windows, Kedit.
vim!
> You can probably find the "se" source code in the comp.unix.sources archive.
http://isc.org/sources/editors/se-1.3.php
I actually really like se but it doesn't work on modern *nix. Maybe I should update and port it.
http://www.gifford.co.uk/~coredump/se.htm
it compiles without any changes on ubuntu 8.04, i managed to get to compile and run on freebsd 7 with some minor modifications (removing a couple incorrect function declarations, replacing #include <termio.h>
with #include <termios.h>
, linking with libcompat, etc.; easy stuff)
> You can probably find the "se" source code in the comp.unix.sources archive.
http://isc.org/sources/editors/se-1.3.php
> I actually really like se but it doesn't work on modern *nix. Maybe I should update and port it.
http://www.gifford.co.uk/~coredump/se.htm
it compiles without any changes on ubuntu 8.04, i managed to get to compile and run on freebsd 7 with some minor modifications (removing a couple incorrect function declarations, replacing #include <termio.h> with #include <termios.h>, linking with libcompat, etc.; easy stuff)
Autodocumentation is fine, but shitty autodocumentation is shitty.
Problem is, to add enough autodocs to turn API documentation into a usable manual, both formats (Javadoc proper and .NET XMLified crap) are inadequate as they add to much formatting cruft. It would be better if we could just write Markdown in there and not have to think about tags except when linking to another method...
Me, I usually write a small game to teach me a new language.
Learn how to use a library that interests you and do something with it, anything.
Like, learn SDL and make a little arcade game. Or a crappy music player using GTK. You get the point.
And keep some open source programs for reference (or use google's code search) when you get stuck at something.
>>115
Uhh, that post was supposed to go into another thread.
I've used first Visual Studio, then Emacs, then vim for a few years. Then I switched to nano and never looked back.
I use GEdit occasionally, too.
>do you name it "strPathName"
No, you establish proper hungarian notation standards for your project and/or company, and name it fqfnRequestedFile (or cfn for canonical filename after resolving links, etc), because the compiler doesn't need you to name the variable "str" to know that it's a string, and you're looking at the function definition where the parameter is declared as a string so a sane human wouldn't need the name to know that either.
Also to the people griping about how caring about relative vs absolute paths is wrong: consider the case of server applications with permissions on given directories, and you need to know what directory your file is actually in.
On topic: vim
I use TECO.
I'm not even joking. It's a steep learning curve and it takes a little while to get used to, but so much power in so little space... literally every string of characters you can type on a standard US keyboard is a valid TECO command sequence. And yet the whole thing is small enough to fit on the tiniest embedded system!
Why yes, I am a total geek, how could you tell?
>>117man 3 realpath
ITECO isn't that hard$
>>118
this TECO?
@^UB#@S/{^EQQ,/#@^UC#@S/,^EQQ}/@-1S/{/#@^UR#.U1ZJQZ\^SC.,.+-^SXQ-^SDQ1J#@^U9/[]-+<>.,/<@:-FD/^N^EG9/;>J30000<0@I/
/>ZJZUL30000J0U10U20U30U60U7@^U4/[]/@^U5#<@:S/^EG4/U7Q7;-AU3(Q3-91)"=%1|Q1"=.U6ZJ@i/{/Q2\@i/,/Q6\@i/}/Q6J0;'-1%1'
>#<@:S/[/UT.U210^T13^TQT;QT"NM5Q2J'>0UP30000J.US.UI<(0A-43)"=QPJ0AUTDQT+1@I//QIJ@O/end/'(0A-45)"=QPJ0AUTDQT-1@I//
QIJ@O/end/'(0A-60)"=QP-1UP@O/end/'(0A-62)"=QP+1UP@O/end/'(0A-46)"=-.+QPA^T(-.+QPA-10)"=13^T'@O/end/'(0A-44)"=^TUT
8^TQPJDQT@I//QIJ@O/end/'(0A-91)"=-.+QPA"=QI+1UZQLJMRMB\-1J.UI'@O/end/'(0A-93)"=-.+QPA"NQI+1UZQLJMRMC\-1J.UI'@O/en
d/'!end!QI+1UI(.-Z)"=.=@^a/END/^c^c'C>
Though, in TECO's defence, brainfuck interpreters look like that in every language.
At work: VisualStudio + VisualAssist + nFringe
It just makes life much easier :P
At home: Notepad++ (Windows), CodeBlocks (Windows, Linux)
I seem to be the only one who uses Smultron, though I only use it on my Mac laptop (obviously).
Everywhere else I use good old vim.
I've used many editors and now I use emacs. I never looked back or doubted this choice.
gedit
C/C++ on windows I use bloodshed dev-c++ but on linux I use the gnome text editor or pico
Source code in the title is dcraw.c.
I like emacs on Linux/OS X, but I use Vim if I must
>>129
What do you mean "if I must"? When do you have to use vim in place of emacs? (btw, are you aware of the vi-emulation mode of emacs? M-x vi-mode)
>>130 + tramp mode
I recently spent some time using ed, so much power in that small thing. You also learn much more about vi/vim by using it.
Other than that, vim. I'd use emacs if it weren't for the whole hand strain thing. Maybe at some point I'll make the switch to emacs+viper-mode, mostly because vimscript isn't as cool looking as elisp.
>>132
try yi. oatmeal with toenail clippings in it isn't as cool looking as haskell.
>>132
I get much more strain trying to capitalize with shift rather than using the ctrl key. Just find a way to press it without using your pinky (I prefer using my palm). The hand strain thing is not even an issue if you don't write much anyway.
I use PSPad
I really like its FTP mode. I haven't seen any other editor that works like that.
TextMate and/or the editor built in Coda on Mac.
jgrasp or notepad++ on windows, vim or emacs on linux (I still haven't decided which one I like better)
notepad++ on windows, (g)vim or gedit on linux
notepad++/nano on windows, gedit/nano on linux
gedit, elvis, emacs on linux, depending on which computer.
gvim plus a crapton of scripts to make it much less vimmish on windows.
Notepad2 on Windows. Kate, vim and gVim on Linux. MacVim on Mac.
vi/vim
everything else is for fags.
Notepad++ on Windows, Textmate or nano on Mac, Gedit or nano on Linux.
Emacs
Do we really have 144 programmers visitting this board or are you guys replying multiple times to this thread?...
Are there any free editors for windows that can properly indent LISP code besides emacs?
>>146
JazzScheme's editor seems able to handle CL as well. I don't know how well that works though.
http://en.wikipedia.org/wiki/Sam_%28text_editor%29
Rules them all.
gtkemacs
gVim for both Windows and Unix. If I really needed to compile something on my Windows box, I have Cygwin installed with g++.
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