Re: Suitable text editor [NOT word processor] or workaround?
On Wed, Sep 06, 2017 at 02:31:08AM -0400, Gene Heskett wrote:
> On Wednesday 06 September 2017 00:09:31 kamaraju kusumanchi wrote:
>
> > On Fri, Mar 17, 2017 at 7:37 AM, Gene Heskett <gheskett@shentel.net>
> wrote:
> > > On Friday 17 March 2017 05:49:30 Jonathan Dowland wrote:
> > >> On Thu, Mar 16, 2017 at 09:54:42AM -0400, Gene Heskett wrote:
> > > 3 times. The problem with that is that the status of the backup was
> > > 15 to 20 hours old, so I lost that days work and had to re-invent
> > > that particular batch of work.
> >
> > FWIW, I also thought that you lost 6 months of work based on what you
> > wrote initially. Happy to hear that the damage is much less. But even
> > that can be very frustrating, right?
> >
> > Along with the backups, may I suggest you to store all your work in
> > version control such as git so that even if the editor crashes, you
> > can recover everything up until the last commit.
>
> I have considered something along those lines, but mentally I can't seem
> to make the coupling between a single file that has to be ready to go
> anytime I run linuxcnc -l (where the -l says to use the same config it
> used the last time) and a git database that usually has to be compiled
> before its capable of running. Normally we keep a separate directory
> for each machine configuration, although there may be N parallel
> directories as the configuration is developed.
So it looks like:
/cncmaster/cnc-machine-A-20150603.1/configfile
/cncmaster/cnc-machine-A-20150603.2/configfile
/cncmaster/cnc-machine-A-20150605.1/configfile
/cncmaster/cnc-machine-A-20150608.1/configfile
/cncmaster/cnc-machine-A-20150803.1/configfile
/cncmaster/cnc-machine-A-20150803.2/configfile
/cncmaster/cnc-machine-B-20150603.1/configfile
/cncmaster/cnc-machine-B-20150805.1/configfile
/cncmaster/cnc-machine-B-20150805.2/configfile
or something similar?
This is a perfect case for git (which does not require any
compilation).
Right now your workflow is, basically:
mkdir /cncmaster/cnc-machine-A-20170809.1
cp /cncmaster/cnc-machine-A-20150608.1/configfile \
/cncmaster/cnc-machine-A-20170809.1/
edit /cncmaster/cnc-machine-A-20170809.1/configfile
linuxcnc /cncmaster/cnc-machine-A-20170809.1/configfile
....wait....
.... inspect ....
..... sigh .....
edit /cncmaster/cnc-machine-A-20170809.1/configfile
and loop until you get it right?
Replace all that file and directory management with git.
edit /cncmaster/cnc-machine-A/config
git commit /cncmaster/cnc-machine-A/config
linuxcnc /cncmaster/cnc-machine-A/config
and when you want to go back to a previous version you can
either get a diff to apply or pull the old version out directly.
Subversion (SVN) would also work well instead of git, here.
git is more powerful, but not necessarily in a compelling way
for you.
-dsr-
Reply to: