Prefer <br> over <div></div> in Editor #925

[garrettm30]

@heinfl

Not really, because I want to differentiate a new line <br> and a paragraph <div> .

I agree that there should be a way to differentiate between a new line and a carriage return, as there was formerly. <br> does not count as a new element, thus, a new paragraph, so things like padding, margin, and text indent do not work with <br>. This was the position I took in a similar thread:

New line break handling

I recently updated to 2.1.42 from a version installed just a few months earlier (I think it may have been 2.1.38). I am disappointed to find that line break handling has been changed in an unfortunately unhelpful way. To be precise, I am talking about using the return key whilst typing in a field on a note, whether when adding a new note or when editing a note in the browse window. Formerly, typing a return closed the current <div> and opened a new <div>, but now it simply inserts a <br>. This …

In my case, since we can still manually edit the HTML of every note, I just work around it by adding <div> myself, and in the scenario where I need it, I just use a Keyboard Maestro macro to quickly add the HTML to selected text to save me time so that I don’t feel the “pain” of this particular change anymore, at least for my needs. But I see that this change upsets other flows such as yours as well.