Ah, I think that's parsing as K4 (Passphrase Credential #4) plus some other stuff. We allow hyphens after an object reference (like "T9479-should be fixed ASAP").

Hmm, that would make sense. However I first came across this with user K4-713 on Wikimedia's install which doesn't fit either of those rules.

Oh, it may be a little more involved than that. I think the user in the original report (C933103) is conflicting with the Countdown rule.

I think the actual rule is "if a username is at least 8 characters long and contains only [a-fA-F0-9]".

We don't need no escaping!

I'm just going to merge this into T3278 since I think that covers this completely.

Ah, I think you're right. I thought that cow just had a nice thick neck (a sign of good breeding), but her tail is a little bristly.

Does the new PHP cowsay implementation need to convert the escaped backslashes to single backslashes?

Yeah, that makes sense. I think this is straightforward and won't create a big ball of mess or anything, so I'll see if I can slip it in somewhere.

Given CORGI, would this be nice to pursue sooner than later? That is, I'd rather write all CORGI copy with Remarkup, and there is a lot of it.

I don't anticipate implementing these in the upstream. Remarkup is extensible enough that these could be implemented as extensions.

I encountered the same when I tried to write "Amazon S3". I don't think using `backticks` is really appropriate here. Further: How to escape the backticks themselves?

@aaron11496 Community Resources would be a great place to add your code as well.

@robla Every open task here will be dealt with by the upstream, that is our intention. People are welcome to shift upstream's priority via Paid Paid Prioritization or wait until the upstream naturally prioritizes it (see Planning). We'd love to be able to address more concerns than we currently can, but we're a very small team.

I think that if Phabricator is going to insist on its own markup language, then y'all should play to win, and not limp in with a "me too" format. Evan's writeup in this task is compelling, but being buried in Phabricator in a four digit ticket number is not really playing to win. @aaron11496 has some promising looking work on a Remarkup conversion plugin for pandoc, but it's clearly only a start.

@moy.easwaran and anyone else interested, I just went through the process of migrating a wiki from GitHub to Phriction. Here's the code I wrote to do it: https://github.com/aaron11496/github-wiki-to-phriction

I remember trying to make something implement PhabricatorMarkupInterface a while back for a custom app, and it was so painful and I couldn't figure out what was going on so I ended up just using PhabricatorMarkupOneOff instead, even though it didn't feel like the right way to do things.

This comes up quite regularly among my users. Even for me it is rather annoying to always have to type full paths - the common case in our (including my) workflow seems to be to link to sub-pages, which becomes unnecessarily cumbersome in Phriction. Additionally this is contrary to experience with well known filesystem functions like symlinks, for example.

Resolved, Tables.

But I guess that works.

Tables? Eww.

Poster child for "describe problems".

My specific use case is to show a "before and after" comparison. Ideally, I'd want to show two images side-by-side with the left image captioned "Before" and the right image captioned "After".

I don't particularly see any value here, that is a caption would be very limited where you can limitlessly describe an image either with Pholio or with Remarkup. What other problem is this solving?

I would recommend just using icons:

See some prior discussion in T3945.

👍

😉

Ooooh. Twitter's emoji are open source.

I'm still not a super fan of how different browsers render different emojis, but it seems we could at least map the basic ones like @swisspol suggests.

OK, I love you. Much love!

No, I fixed it manually.

I am sorry to have deleted the "B"....

However this is, as you already mentioned, rather useless, because clicking the link will not allow to send an email

As I see it, rP58fbb0ae532f implements parsing of mailto://. However this is, as you already mentioned, rather useless, because clicking the link will not allow to send an email (in KMail, it opens a new-mail window with an empty To: field). Is it possible to reconsider fixing this in a way that actually works?

Hmm, nevermind me.

I can't reproduce this:

Yup! When I regenerate the graph it's well-sized.

I'll confirm in a moment.

(I think this is fixed?)

D13548 will only correct images when they are newly built. If you have existing images that don't fit, you'll need to regenerate them.