On Mon, Feb 07, 2011 at 11:52:15AM -0800, Kirk Wallace wrote:
> I like using gEdit to write C code, but it would be nice when I open a
> file it would automatically save the freshly opened file as a numbered
> backup, so that if needed, I could go back and retrieve the original, or
> maybe have it save two files when the do a "save", a plain file name and
> a numbered.
You'd better take a look at Mercurial or Git for such tasks.
Mercurial is easy to use and have nice GUI. Also it's possible to
integrate both of them into gEdit as External Tools. VCS will save
you lot of work.
> Does anyone use gEdit for light duty development, and if so,
> what should I know in order to be more effective with using it for
> writing C code? Thanks.
> Another thing comes to mind. If I change gEdit for code, it may not be
> good for normal files. Should I just use a different editor for code?
vim! :)
Pavel
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
