Emacs and Xemacs both support syntax highlighting, and text formating (IE you press tab on the next line after an "{" and it positions the cursor in the correct indentation) it is meant to be multi-use, some say it is an OS in itself, its just a matter of learning how to use it, but then, if you dont want to mess with makefiles, you wont like it, personally I find the plain text makefiles to be more elegant and simple than the 5 or so binary files you need for a single project to compile on Visual C++, have the lights gone out on you in the middle of editing a file or a compilation on VC++?. . . then you know what I mean.

"Emacs is a nice operating system. Too bad it lacks a decent text editor."

---

We knew that American voters had an anti-intellectual streak but they didn''t have to go that far. But as George said himself "they misunderestimated me". Today, at the dawn of the 21st century, the global village is finally complete. At last it has a global village idiot.
John O''Farrell

quote:

---

Original post by Kwizatz
personally I find the plain text makefiles to be more elegant and simple than the 5 or so binary files you need for a single project to compile on Visual C++

---

Nice try. Too bad its a damn lie.
You need exactly two(thats 2 - t.w.o) files to get a project to compile in VC++ - a project file( .dsp on VC++6, .vcproj on VC++.NET) and a workspace file to contain that project(.dsw on VC++6, .sln on VC++.NET).
Guess what? They are all text.

---

We knew that American voters had an anti-intellectual streak but they didn''t have to go that far. But as George said himself "they misunderestimated me". Today, at the dawn of the 21st century, the global village is finally complete. At last it has a global village idiot.
John O''Farrell

quote:

---

Original post by Arild Fines
Nice try. Too bad its a damn lie.
You need exactly two(thats 2 - t.w.o) files to get a project to compile in VC++ - a project file( .dsp on VC++6, .vcproj on VC++.NET) and a workspace file to contain that project(.dsw on VC++6, .sln on VC++.NET).
Guess what? They are all text.

---

Ok, First of all I want to make sure everyone understands I am not trying to convert anyone to the church of emacs, I was and I am only expresing my opinion, and point of view, you should come yo your own opinions, I dont like all the policies RMS comes up with eighter.

I wasnt lying, I made an uneducated statement, sometimes I just do that, you could have said, "its not true" without calling me a liar, yes most of the files needed are text, I was wrong.

Now, lets see, I will overlook the .aps,.clw,.plg,.odl and .nbc files VC++ generates, those are the ones I was refering when I said 5 or so, granted you might delete some of those and still be able to compile your project, but still make does not generates any other complementary files.

I opened up a .dsp file, and checked the first 2 lines:

Microsoft Developer Studio Workspace File, Format Version 6.00
# WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE!Microsoft Developer Studio Workspace File, Format Version 6.00

now the dsp:

# Microsoft Developer Studio Project File - Name="Admin" - Package Owner=<4>
# Microsoft Developer Studio Generated Build File, Format Version 6.00
# ** DO NOT EDIT **

Do not edit hmmm, doesnt matter if they''re all text, you still cant reconstruct them by hand, thats why sometimes the solution to fix a VC++ project is yo create an empty project and add all the files manually.

Again, if it works for you, use it, I said personally I still think a makefile is more elegant.

quote:

---

Original post by Kwizatz
I opened up a .dsp file, and checked the first 2 lines:

Microsoft Developer Studio Workspace File, Format Version 6.00
# WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE!Microsoft Developer Studio Workspace File, Format Version 6.00

now the dsp:

# Microsoft Developer Studio Project File - Name="Admin" - Package Owner=<4>
# Microsoft Developer Studio Generated Build File, Format Version 6.00
# ** DO NOT EDIT **

Do not edit hmmm, doesnt matter if they''re all text, you still cant reconstruct them by hand

---

You can, if you know what you''re doing. Most people don''t so Microsoft put those warnings/disclaimers there so idiots don''t try to fiddle with them. You can delete all except the .dsp and .dsw and still compile the project (it wont rebuild, though it might regenerate the deleted files).

quote:

---

Original post by Kwizatz
I wasnt lying, I made an uneducated statement, sometimes I just do that, you could have said, "its not true" without calling me a liar, yes most of the files needed are text, I was wrong.

---

It was more than an uneducated statement - you made an offhand remark that came off as authoritative and would have been perceived as such by a casual reader. If you had indicated that you were not sure about these things, I would have corrected you and let it be with that.
And as Oluseyi pointed out, all you need is the workspace file and the project file - check out some of the open source projects that compile on VC++(Apache httpd comes to mind). You will see that all they include is a .dsp and a .dsw.
As for manually editing it - people have made tools to generate them from makefiles, so I doubt its that much of a problem when you know what you are doing.
I dont find makefiles very elegant. I am not opposed to the idea of text-based build configuration systems, but make is beginning to show it''s age. Inertia and its ubiquitiousness on UNIX systems is pretty much what keeps it alive. There are alternatives(Ant[1] comes to mind).

[1]http://jakarta.apache.org/ant/

---

I cannot conceive of a God who rewards and punishes his creatures, or has a will of the type of which we are conscious in ourselves. An individual who should survive his physical death is also beyond my comprehension, such notions are for the fears or absurd egoism of feeble souls.
Albert Einstein

Alright, I just did not liked being called a liar.
We have different views thats all, let the casual reader try both and come up with his own view.

I''ve been messing around with some editors lately, and a pretty good one I''ve found is Cooledit. Don''t remember the URL, but I think it was at sourceforge, so figure it out

I used to use Nedit, but when I installed Slack 8.1, it doesn''t work anymore for some queer reason... I''ll have to figure that one out someday.

rm -rf /bin/laden

quote:

---

Original post by Ziphnor
Also things like the collapsing funtion definitions(in Anjuta) seem very useful, especially when writing graphics code which tends to take up alot of space, and easily makes things impossible to work with.

---

Just for all your info, I thought I''d point out that Emacs and Xemacs both support collapsing of functions also.

--It''s with other text editors vs emacs like with women. Those inflatable ones might be fun to fiddle around with for awhile, but nothing beats the real thing.

Oh goodie. Another ____ vs. emacs war.

Can we talk about what distribution roxxors next? Or maybe about how much microsoft sucks? Ooooh, I know, I know! Let''s talk about how cool we are for running linux while all those lamers run windows!

Gimme a break. No, Dev-C++ will not come out for linux at this time. Production is halted. Use one of the hundreds of alternatives available.

Problem solved.