We linked the "split x" action to the first item in the list so you get a similar behavior to the word processing applications - but one must press ENTER twice. If the element is displayed as a block, then splitting it results in a "new line". As you can see, this is a very generic action and does not depend on the type of the edited document. One workaround is to bind the DITA insert paragraph action to another shortcut, for instance META-ENTER (on Mac). This can be done from: Options/Preferences/Document Type Association (Developer role) /DITA (Edit)/Author/Actions/paragraph. Regards, Dan Eliot Kimber wrote:
Eliot Kimber wrote:
I'm using OxygenXML for some heads-down authoring of DITA-based content.
I had gotten used to being able to do enter/enter to get a <p> element in body content.
However, after I entered a few <pre> elements, pre started coming to the top of the list, which broke my conditioning.
I think it's important that double enter always result in paragraph, as that's the way most people are conditioned, both by word processors and by other XML editors.
I just realized the problem is only when the insertion point is in a context in which <p> is allowed--if you're in a <p> then the normal "split x" option is the first item.
But this is still a problem because the "split x" behavior continues to reinforce the enter-enter behavior.
This issue may be more pronounced for me in my current case where I'm creating a more or less narrative document consisting of nested topics, so I creating a number of new topics, meaning new, empty topic bodies, where I still expect enter-enter to always give me a paragraph. But it will also occur when you're switching from a non-p element to p, such as creating a list and then creating paragraphs following the list.
Cheers,
E.