IDE :D
-
- Member
- Posts: 190
- Joined: Tue Sep 26, 2006 1:40 pm
- Libera.chat IRC: Nokurn
- Location: Ontario, CA, USA
- Contact:
Bash, Gnome-Terminal (URxvt's copy/paste finally drove me away), Gedit, GVim, Vim (when X is turned off), make, gcc, g++, binutils, nasm, fasm, Qemu, Bochs. True IDEs suck. If there's a "Build" thing that runs make, or a project/file browser, great, but when you put it all together, you get a slow, unorganized mess of menus and collapsible panels.
yep... and color syntaxing.Jeremiah Griffin wrote:Bash, Gnome-Terminal (URxvt's copy/paste finally drove me away), Gedit, GVim, Vim (when X is turned off), make, gcc, g++, binutils, nasm, fasm, Qemu, Bochs. True IDEs suck. If there's a "Build" thing that runs make, or a project/file browser, great, but when you put it all together, you get a slow, unorganized mess of menus and collapsible panels.
I couldn't image writing an OS in just a terminal window... that seems a bit hectic.
Website: https://joscor.com
-
- Member
- Posts: 190
- Joined: Tue Sep 26, 2006 1:40 pm
- Libera.chat IRC: Nokurn
- Location: Ontario, CA, USA
- Contact:
I did my 16-bit assembly OS + boot loader entirely without X. It was, actually, faster than it would have been with X.01000101 wrote:yep... and color syntaxing.Jeremiah Griffin wrote:Bash, Gnome-Terminal (URxvt's copy/paste finally drove me away), Gedit, GVim, Vim (when X is turned off), make, gcc, g++, binutils, nasm, fasm, Qemu, Bochs. True IDEs suck. If there's a "Build" thing that runs make, or a project/file browser, great, but when you put it all together, you get a slow, unorganized mess of menus and collapsible panels.
I couldn't image writing an OS in just a terminal window... that seems a bit hectic.
As for being hectic, no way. If you're proficient with Screen and Vim, it's easy to stay organized and focused.
I use VIM plus the vim command 'map #5 ^[:w ^M:make! run^M:cope 8^M' for command line Linux programming. And eclipse for java and VS for Windows.
This runs make run, if an error occurs during the compilation it goes to the line that the error occurred on and shows a description of the error, if no error occurs the compiled program runs and then the output of the program is then shown (if the output is in the correct format, you can trace the steps that the program took) which is mapped to F5.
This runs make run, if an error occurs during the compilation it goes to the line that the error occurred on and shows a description of the error, if no error occurs the compiled program runs and then the output of the program is then shown (if the output is in the correct format, you can trace the steps that the program took) which is mapped to F5.
Microsoft: "let everyone run after us. We'll just INNOV~1"
I usually run my shell-only tools in X / Konsole, but mostly because I like to have music or a movie playing in a small window, ICQ in the background etc. (Too little sensory input and I tend to get bored / sidetracked.) Everything else - switching terminals, syntax highlighting, edit / make / test / edit without leaving the editor etc., I could have on a non-X terminal too.Jeremiah Griffin wrote:I did my 16-bit assembly OS + boot loader entirely without X. It was, actually, faster than it would have been with X.01000101 wrote:I couldn't image writing an OS in just a terminal window... that seems a bit hectic.
As for being hectic, no way. If you're proficient with Screen and Vim, it's easy to stay organized and focused.
Every good solution is obvious once you've found it.
Visual C++, for both applications and OS dev
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
-
- Member
- Posts: 190
- Joined: Tue Sep 26, 2006 1:40 pm
- Libera.chat IRC: Nokurn
- Location: Ontario, CA, USA
- Contact:
That's what mpg321 and Finch are for!Solar wrote:I usually run my shell-only tools in X / Konsole, but mostly because I like to have music or a movie playing in a small window, ICQ in the background etc. (Too little sensory input and I tend to get bored / sidetracked.) Everything else - switching terminals, syntax highlighting, edit / make / test / edit without leaving the editor etc., I could have on a non-X terminal too.