Late friday night brings good ideas

everytime I type D3 meaning the javascript visualization lib,
it references that Diff #. Similarly with common strings like
#servers looking up projects. I want the auto-linking behavior
most times, I just want a simple escape character for the few
times when I don't.

Per the latest update in D17502, this remains involved.

Thanks to chad for marking my related T12490 as a duplicate.

Oh, yeah, in Conpherence you'd have to like :+3+space+delete+⏎ or something.

Ah true, this was SOE issue I guess.

Can you just type :+3+Space?

is srs bsness mode taking over? i'm in a panic :[

THANKS FOR RUINING THE JOKE EVERYONE

Probably resolved?

I can't reproduce this any more.

high priority!

I don't see anything here worth moving forward. I don't think the bar needs to cover more advanced topics and more advanced users should be OK with reading documentation.

Well we also have a lunch today.

We could probably ship it (.md in Diffusion rendering as GitHub Flavored Markdown) this week -- it wouldn't be perfect, but we do have total freedom there to iterate as we find cases we're missing there -- it's just a pretty hard sell as a priority for me relative to the development cost. Obviously it would be nice if you bring in your repository to Phabricator and the README.md renders perfectly instead of rendering mostly-okay-but-a-bit-buggy, but it's hard for me to imagine we're losing many users there.

Having markdown rendered in documentation as expected probably alleviates 90% of my concerns. At least, having to retype or reformat large chunks of text is un-cool and arduous. Learning some new markup, less so. But it sounds like thats years away.

My anecdote here is Betamax vs. VHS. Yes, one is superior, the other has 95% of the market. I believe we're both right, but weigh certain issues differently. I see the new user coming from GitHub as the more important customer, as it leads to growth. The more things are different in Phabricator, the steeper the climb. You're right from a technical standpoint, and I do believe Remarkup is superior, so I'm stuck.

I think the two goals are sufficiently in conflict and the value of supporting these rules is so low that it probably isn't worth the effort to try to get it right most of the time.

Maybe a different question is, what percentage of block of Remarkup here include code-related discussions. I'm not saying rendering those well shouldn't be a high-priority, I just see Remarkup used for much much more (task discussions, documents, conpherence, etc).

Are you strictly saying both goals here are not attainable?

My viewpoint is that Markdown was developed for writing first-party blog posts, not for technical discussions about software.

Just going to reopen this as a wishlist item. Italics/Bold here is probably the biggest requests for cross-functionality Remarkup <-> Markdown I'd personally have. And at least in your test cases, it seems even GitHub fails at them (and CommonMark), though Slack does not, so I think these are workable in the general sense, just will likely come with lost of test cases and regex support. I think correctness of expectation is your main concern (and the maintenance cost), not adhering to a "spec"?

I'm going to probably re-design this page a little.

We tested this style (black with shadow) on our install, but the consensus is that it looks awful...
I guess a simple black text color is a little subtle, but at least it isn't confusing (like the blue color) or ugly (like the shadow).
@chad what do you think?

I think we could even default it to "fancy mode" without a setting, at least to start with. I'm not sure anyone will want to access the plain text mode with enough frequency that we need it to be sticky.

@epriestley this doesn't seem hard to build for a fledgling designer/intern engineer.

T9789 has stabilized (the majority of major transaction types now run through ModularTransactions) although it didn't end up providing much clarity here. This is no longer blocked on anything, I just need to develop a specific technical plan to resolve the "adjust" vs "expand" sequence inside transaction application so the "expand" code has access to the old text by the time it runs.

Thank you for your quick reaction (and sorry that I didn't reply sooner). I think a black color with a 1px black text-shadow looks better. The blue is confusing (it sort of looks like a link).
So I suggest:

.phui-document-view .phabricator-remarkup .remarkup-header strong {
  color: #000000;
  text-shadow: 0 0 1px #000000;
}

I'd love to see anchor indicators when hovering headings.

I went with a different color, but we could also do text-shadow or a background-color... lmk if this seems bad in practice.

In T12357#214422, @chad wrote:

What would you suggest as a fix?

What would you suggest as a fix?

It's pretty big deal for us because we are using phriction to collect helpdesk FAQ. We have modified TOC to be displayed in the beginning of the page and would like to use ponder are storing questions. Atm using ponder links in phriction as headings also shows toc values as X.