I've been looking at Coda2. It isn't easy to discover what it does. I downloaded the book too. Does it allow you to step through PHP and see the sate of variables? I spent the morning failing to get anywhere with Xdebug in VSCode and feel it would be as bad in Atom and PHPStorm. So maybe I'll just have to plug away with var_dump()s

//

Thanks. Will definitely investigate tomorrow.

/

I know this is probably an impossible question, but would you recommend Atom or VSCode as a starting point. I've been editing my PHP in BBedit and I feel about ready to to move up a little.

I refuse to go there.

Density.

Seconded.

/

Anyway, s'all good. Git did save me from myself, and all's well with the world, except that one of the bits that Grav CMS uses had a recent security update that broke the way it renders markdown outside the main text, for example in image captions and footnotes.

I can live with that, for a little while.

//

I suppose it does. I mean, I know it does. But say you did a major upgrade, and everything was working just fine, might you not want to start history again at day 0

//

Thanks for the encouragement. I did try, nothing went wrong (so far) and everything seems to be working as I expect.

One more question: As this really was a major cleanup, I wonder whether there is some way to get Git to abandon all the previous commits and just start from fresh again. I'm sure they don't take up a lot of storage or anything, but I know that I won't need any of them ever again. Or maybe it just isn't worth it.

//

I'm not yet seeing error message because I have not tried to commit! There are so many changed files -- 240 of them according to SourceTree -- and I just don't know whether I should just sync them all.

Maybe I should just try.

/