The best feature of Phabricator and Remarkup is Macros.
Details
Feb 20 2019
Probably a good idea, but not worth keeping a task around for.
Jan 14 2019
Jan 2 2019
Jul 26 2018
Jul 20 2018
how did this ever escape us
Mar 13 2018
I wasn't able to reproduce the black background issue, exactly, but here's what I changed:
Mar 8 2018
very good memes
hmmm
Actually, HTML mail has an issue now.
This is technically fixed now but the meme stuff is real old and rough so I'm going to maybe make some kind of effort to get through more of T5258, etc.
This is conceptually easy but no trigger character really makes a ton of sense. I'm going to decline this until it's more clear what the desired behavior actually is.
Mar 7 2018
Feb 9 2018
See PHI357.
Sep 30 2017
Well, it half-works in email, so that's something!
You can do this
Ahhh, so you can't have multiple adjacent macros on the same line; that was my problem. I guess that could be special-cased, which would be linear with the number of "tokens that are macros coming before a non-macro" appearing on a line, but I'm probably the only one clamoring for multiple horizontally aligned parrots.
They need to be on their own line. I think this rule got added in 2011, shortly after I left FB.
Aug 3 2017
I'm just going to merge this into T5258. There are two separate issues here:
This bug does exist on this server, but unclear why. Maybe related to size of image, but probably best solution is some command-line tool to regenerate all file transforms? I don't think making PHIDs easy to find inside the app is very user friendly.
Aug 2 2017
Why did they need regenerating in the first place?
May 23 2017
May 15 2017
@jeffprouty Shoot us an email at support@phacility.com with details about your instance and the issue you're hitting if you're a paying customer; see also https://admin.phacility.com/book/phacility/article/support/.
Just confirming this is broken for phacility hosted instances (it is for us at least) and that there is no work around to date? Should this be it's own issue? Or should we reopen this issue?