Well, you know what would be next level for a dev? If (s)he clicks on it, the color is copied to the clipboard. We can't use this behavior, because behaviors loose their state in the remarkup cache...

This should be ready to merge now, if someone wouldn't mind reviewing it.

(I've put a note in Dependencies for now)

Updated Pygments with pip to 2.17.2 und cut the time in half. So yeah, that's already an improvement.

I guess we could also try to cache the individual rendered code-blocks.

Well, good to know that it is not something in the phorge codebase. Our server has pygmentize 2.14.0 - but the server itself is really not the best, so that could be an explanation. Maybe we could make some remarks about performance and keeping the versions fresh on the diviner page...

Update: I've installed pygments (2.15.1), and it took about 3 seconds to render. It takes about 14 seconds here (with pygments 2.3.1).

mm, dumping this file in my dev env renders pretty much immediately; that's a good sign that it's the code blocks, because (1) pygments is known to be slow and (2) I don't have it installed.

I'm quite sure the problem is limited on repeated code blocks.

"slow remarkup" often boils down to 1-2 inefficient regexp in a rule somewhere.

Can reproduce

Added documentation in D25547: Diviner: Improve documentation for remarkup code blocks

Yeah enjoy this feature! Already part of our glorious 2023 Week 32

Hahah I guess I could have tested it first.

I think we already did - @valerio.bozzolan ?

Gotcha. Probably this is generating the attachment transactions but should be "ignored on no effects":

This feature is not complete also for Conpherence AFAIK

In T15743#15855, @valerio.bozzolan wrote:

• https://github.com/xemlock/php-latex (PHP server side)

Interestingly, I just discovered Wikimedia has a pretty cool project to render math on the server side, by transpiling some js into php:

There is also MathJax, a subset of LaTex that only covers the mathematical notation without the page layout functionality.

I see that it depends on a NodeJS external script (server-side).

This would be useful for discussions about design, specifically I wished for this feature while reviewing D25491: Improve contrast of Links in Dark Mode

Values given in em units may produce unexpected results...

If it's only for a small number of such words, they should probably just be added to the blacklist remarkup.ignored-object-names - in fact, we should probably add S3 at least as a default; And probably find a way to expose this config option. Maybe a button on the Remarkup box that will help adding things to the blacklist?

In T15712#15124, @avivey wrote:

Is the motivation only to allow not-magicking things like "S3" and "F1", or is there more?

Looks like the tickets end in a Wontfix in https://secure.phabricator.com/T5301; I didn't follow the whole thing, but often the reasoning in Remarkup boils down to performance.

mm, see this one: https://secure.phabricator.com/T5301#211340

Is the motivation only to allow not-magicking things like "S3" and "F1", or is there more?

Since I can, thanks to that revision, at work I've put this additional CSS rule for extra nonsense scary climax.

I had communicated these upstream (almost exactly a year ago~) and some helpful information was provided

Note: the <ins> tag is typically rendered as underlined text, so this would be very similar to the <u> formatting that is produced with __foobar__ → foobar. In fact, it might be worth repurposing that rule to produce <ins> instead, since ~~foobar~~ actually creates a semantic <del> tag rather than the presentational equivalent <s> (strikethrough) tag.

Ugh. I added this to the UX project but forgot to remove the test content from the comment box, so my changes ended up coupled with a comment that said "- List Item". I tried to delete the comment but now it looks weird like some sort of redacted content :( anway, though I'd leave the note here in case anyone is confused with the deleted comment.

While it could be nice to have this, in the meanwhile I think that having something minimal like D25434 would be nice

• Automatically continued bulleted list upon new line

Should this be documented here? I think yes

Workaround 😎

(The file F315310 is not public)

Interestingly, it works ._.

Interestingly, Remarkup allowed too many things, so this Task cannot be 99.99999% safe.

Please describe the thing using 3 backticks like in this comment (see raw remarkup)

I think the current revision is a good compromise. The current behavior makes no sense from the perspective of modern UX patterns:

In T15161#4416, @avivey wrote:

I agree with this, but I think we should let this wait for broader discussion - there maybe good counter-arguments.

Another use case: Drag & Drop on a new Object description, even if the Object is not already created, should attach by default to it.

I think a more generic solution here is "Make the Remarkup Help Page Extensible", so that Remarkup rules can add their own sections (Possibly under the Guides application, if it still exists?)