Try updating to after rP7c6320d21121 ?

No one's mentioned anything to us about this. I suspect most of our users are not using Apple Mail though.

@chad I won't object to closing as Wontfix but to be clear: this use case is not limited to public installs or nor to installs with dot installed. I was just giving an example of a 'complicated' remarkup example.

Its come up in two cases:
(a) I want to have a template page per team or group that users shouldn't edit, but should be able to copy to make their own
(b) someone else made something interesting and complicated such using using dot {{{}}} and I want to see how they did so to be able to make something else.

after some further testing and using of ./bin/policy unlock of all relevant files this may not be the exact cause: I am certain though that creating such a file results in logged out users from seeing only a broken file while logged in I see it just fine.

@fzhan try bin/cache purge --purge-remarkup first?

I agree with @chad and @lpriestley: meeting minutes on calendar events would be hard to find or search. Typically one doesn't remember the day the meeting took place, they remember the type of meeting and search all the minutes. Being able to tag wiki articles with a date or calendar would be useful though: or being able to couple an agenda + minutes + calendar entry.

I agree with @epriestley here. For real time chat about a diff conpherence or in person usually works better than comments. Its not uncommon for me to write something like "see above" or "see comment" or "this is an example" when I haven't written the meta-comment yet.

Just some additional feedback here: I find the exclamation marks confusing. I like them on "commits need audits" but dislike them for tasks.

This should be marginally easier now that mailing lists are just a special type of user. there is still some UI work but it isn't a different type of token anymore.

another example of a commit which should have closed a review but did not https://reviews.freebsd.org/rS283923 and https://reviews.freebsd.org/D2019

@epriestley I think they esentially want this: https://help.github.com/articles/setting-your-organization-s-billing-email/

@epriestley the latter is particularly important for the FreeBSD case. Already users are getting annoyed at the sheer amount of email that phabricator generates, so having a way to minimize that for particular mailing lists would be great.

@chad: it may be nice to have a coalesced list of all "referenced in the comments" tasks. Right now you need to skim through all the comments or have someone manually edit the description.

fwiw, as expected, this is an issue on prod

to the best of my knowledge, no, but I will comment on the implementation if I see anything incompatible.

FWIW I hope whatever solution is built is not specific to Linux and the LSB but will work with other non-linux POSIX systems as well.

What's wrong with permitting reading from named pipes? While the trivial example I showed may not be useful, I've wanted to modify my commit template using sed or the like.

I think named phurls would almost fully solve this use case.

So, this isn't really related to being a CMS, though having that ability might be nice (though much more complex). This task comes from a real use case. I am looking at migrating an existing wiki, and we have comments like "this list must be kept in sorted order" or "if you change this list, also modify that XML file". While I could translate these to small font italics or something, having a real comment syntax would be nice.

In this case I tried to describe the problem as well, but let me try differently.