NOT A VALID BOX STRUCTURE ERROR TEXMACS UPDATE

One thing I would say is that LyX always writes the newline endings native to your platform. I fix merge errors in a text editor if they occur (maybe once every few months, takes a few minutes to repair.) And no times where Git merged wrongly and corrupted the document or similar. We've been using this for 2 years, with many many commits. What I mean to say is, we're not just using Git to 'check out, check in', we are also merging and branching as well. When we merge, everything gets merged together.

NOT A VALID BOX STRUCTURE ERROR TEXMACS UPDATE

We love feature branches, so we update not only the code, but the documentation as well, in the branch. lyx file in a 'doc' directory of our Git repository, which stores our software source code. We put the software architecture document (about 100 pages) in a single. I assumed dragging did the same as the buttons.) And the indent/outdent buttons do work take their contents with them as well.

I'll concede that dragging in Word does give the desired effect (I admit I never tried drag before you mentioned it, despite having used Word for 25 years and always wishing for that feature.

LyX moves the sections around, Word only moves the headings. What you want, when you move a heading, is not only to move the heading, but to really move the whole section, including: the heading, its text, and sub-headings, the text under the sub-headings, etc.

If you take 'SUB-HEADING 2' and click 'move up', the document is now: On Word, if you move a heading up/down with the buttons (in 'View'|'Outline') the heading moves but the text and sub-sections underneath it don't move. The 'move heading up/down' don't work as well as LyX.

Not a valid box structure error texmacs