Moving Headers in TOC creates extra empty lines in document
I'm working on a document with several ## Headers under one # Header. I always leave exactly one empty line above and below my Headers.
Whenever I move a Header via the TOC (amazing feature BTW, and a big reason I upgraded without hesitation!), extra empty lines are inserted before most, if not all, of my Headers.
-Stu
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on 22 Feb, 2013 07:34 PM
When rearranging headers, Composer has to do something to ensure proper spacing before headers. The rule it follows is to make sure there are two empty lines above headers.
Why? Because I like two empty lines before headers, and I wrote the program. ;)
I can look at adding a preference to allow user to choose 1 or more lines instead of set at 2, but I have to admit that this will be a low priority compared to other fixes and changes I have lined up. (And before anyone else asks, I will not add an option to make it 0 lines before headers --- bad things happen with some Markdown implementations when you leave out a blank line before headers.)
Fletcher
PS> I was really pleased when I was able to get the drag-and-drop TOC working. I've been wanting that for a long time.
2 Posted by prolost on 22 Feb, 2013 07:50 PM
Thanks for the reply Fletcher. I admit that I'm hopeful that other one-liners like me will chime in and nudge you to bump this up in priority. :) Am I wrong to think that one empty line before headers is the more common Markdown practice?
Would it be possible to follow the user's precedent rather than require a setting? I.e. look at the first or second header in the document and take the number of empty lines before it as that document's preference?
-Stu
3 Posted by prolost on 10 Mar, 2013 12:46 AM
Hello again,
With the disclaimer that I suffer from overemphasitis, I just wanted to report that it's kind of killing me that I can't use this feature. It was one of the things that excited me most about the upgrade, but I can't use it because I write Markdown like most people do.
It's a bummer. I hope you can address this.
Thanks for listening,
-Stu
Fletcher closed this discussion on 21 Mar, 2013 04:19 PM.