Nikolaos Chatzikonstantinou <nchatz...@gmail.com> writes: >> So, I think this is probably slightly unusual in practice, but also fine to >> do. Consistency with the klipsify version seems worth it, regardless of >> which way we go. > > In HTML they'd need a way to denote short code fragments like > <code>int x = 0;</code> and long code fragments like a source file. > The former would have to be inline; instead of using <code> and > <blockcode> they kill two birds with one stone with a single <code>, > which necessarily has to be an inline element. Both whatwg and mozilla > mention <pre><code> as a means to include larger snippets. I don't > think the fact that the element is inline means that you must only use > it within other text.
So it looks like we should merge this. Nikolaos, may you also add an ORG-NEWS entry? Users may want to know about the change. For updating/improving CSS selectors, if nothing. > Furthermore, let me add one more idea: we should perhaps also add > <samp>, > <https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/samp> > for the case of #+RESULTS: that occurs when babel blocks are evaluated > and exported. #+RESULTS does not always represent verbatim output. It depends on :results header argument. Also, src block output is sometimes used for purposes like dynamically generating parts of the HTML output and should not be marked blindly. So, rather than talking in terms of #+RESULTS keyword, we need to talk in terms of Org markup, regardless whether it has or does not have #+RESULTS keyword above: 1. verbatim 2. example blocks 3. fixed-width -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
