2011-05-29 19:20:24 +02:00
|
|
|
@title Remarkup Reference
|
|
|
|
@group userguide
|
|
|
|
|
2011-07-04 22:04:22 +02:00
|
|
|
Explains how to make bold text; this makes your words louder so you can win
|
2011-06-23 22:04:52 +02:00
|
|
|
arguments.
|
2011-05-29 19:20:24 +02:00
|
|
|
|
|
|
|
= Overview =
|
|
|
|
|
|
|
|
Phabricator uses a lightweight markup language called "Remarkup", similar to
|
|
|
|
other lightweight markup langauges like Markdown and Wiki markup.
|
|
|
|
|
|
|
|
This document describes how to format text using Remarkup.
|
|
|
|
|
|
|
|
= Basic Styling =
|
|
|
|
|
|
|
|
Format **basic text styles** like this:
|
|
|
|
|
|
|
|
**bold text**
|
|
|
|
//italic text//
|
|
|
|
##monospaced text##
|
|
|
|
|
|
|
|
Those produce **bold text**, //italic text// and ##monospaced text##,
|
|
|
|
respectively.
|
|
|
|
|
|
|
|
= Layout =
|
|
|
|
|
|
|
|
Make **headers** like this:
|
|
|
|
|
|
|
|
= Large Header =
|
|
|
|
== Smaller Header ==
|
|
|
|
===== Very Small Header =====
|
|
|
|
|
|
|
|
This produces headers like the ones in this document.
|
|
|
|
|
|
|
|
Make **lists** by indenting two spaces and beginning each item with a "-":
|
|
|
|
|
|
|
|
lang=demo
|
|
|
|
- milk
|
|
|
|
- eggs
|
|
|
|
- bread
|
|
|
|
|
|
|
|
This produces a list like this:
|
|
|
|
|
|
|
|
- milk
|
|
|
|
- eggs
|
|
|
|
- bread
|
|
|
|
|
|
|
|
Make **code blocks** by indenting two spaces:
|
|
|
|
|
|
|
|
f(x, y);
|
|
|
|
|
|
|
|
You can specify a language for syntax highlighting with "lang=xxx":
|
|
|
|
|
|
|
|
lang=demo
|
|
|
|
lang=html
|
|
|
|
<a href="#">...</a>
|
|
|
|
|
|
|
|
This will highlight the block using a highlighter for that language, if one is
|
|
|
|
available (in most cases, this means you need to configure Pygments):
|
|
|
|
|
|
|
|
lang=html
|
|
|
|
<a href="#">...</a>
|
|
|
|
|
|
|
|
You can also use a "COUNTEREXAMPLE" header to show that a block of code is
|
|
|
|
bad and shouldn't be copied:
|
|
|
|
|
|
|
|
lang=demo
|
|
|
|
COUNTEREXAMPLE
|
|
|
|
function f() {
|
|
|
|
global $$variable_variable;
|
|
|
|
}
|
|
|
|
|
|
|
|
This produces a block like this:
|
|
|
|
|
|
|
|
COUNTEREXAMPLE
|
|
|
|
function f() {
|
|
|
|
global $$variable_variable;
|
|
|
|
}
|
|
|
|
|
|
|
|
= Linking URIs =
|
|
|
|
|
|
|
|
URIs are automatically linked: http://phabricator.org/
|
|
|
|
|
|
|
|
If you have a URI with problematic characters in it, like
|
|
|
|
"##http://comma.org/,##", you can surround it with angle brackets:
|
|
|
|
|
|
|
|
<http://comma.org/,>
|
|
|
|
|
|
|
|
This will force the parser to consume the whole URI: <http://comma.org/,>
|
|
|
|
|
|
|
|
= Linking to Objects =
|
|
|
|
|
|
|
|
You can link to Differential revisions, Diffusion commits and Maniphest tasks
|
|
|
|
by mentioning the name of an object:
|
|
|
|
|
|
|
|
D123 # Link to Differential revision D123
|
|
|
|
rX123 # Link to SVN commit 123 from the "X" repository
|
|
|
|
rXaf3192cd5 # Link to Git commit "af3192cd5..." from the "X" repository.
|
|
|
|
# You must specify at least 7 characters of the hash.
|
|
|
|
T123 # Link to Maniphest task T123
|
|
|
|
|
2011-05-31 19:23:31 +02:00
|
|
|
You can also link directly to a comment in Maniphest and Differential:
|
|
|
|
|
|
|
|
T123#4 # Link to comment #4 of T123
|
|
|
|
|
2011-05-29 19:20:24 +02:00
|
|
|
= Quoting Text =
|
|
|
|
|
|
|
|
To quote text, preface it with an ">":
|
|
|
|
|
|
|
|
> This is quoted text.
|
|
|
|
|
|
|
|
This appears like this:
|
|
|
|
|
|
|
|
> This is quoted text.
|
|
|
|
|
|
|
|
= Embedding Media =
|
|
|
|
|
|
|
|
If you set configuration flags, you can embed media directly in text:
|
|
|
|
|
|
|
|
- **files.enable-proxy**: allows you to paste in image URLs and have them
|
|
|
|
render inline.
|
|
|
|
- **remarkup.enable-embedded-youtube**: allows you to paste in YouTube videos
|
|
|
|
and have them render inline.
|
|
|
|
|
|
|
|
These options are disabled by default because they have security and/or
|
|
|
|
silliness implications, read their descriptions in ##default.conf.php## before
|
2011-06-12 01:23:57 +02:00
|
|
|
enabling them.
|
|
|
|
|
|
|
|
= Image Macros =
|
|
|
|
|
|
|
|
You can upload image macros (Files -> Image Macros) which will replace text
|
|
|
|
strings with the image you specify. For instance, you could upload an image of a
|
|
|
|
dancing banana to create a macro named "peanutbutterjellytime", and then any
|
|
|
|
time you type that string it will be replaced with the image of a dancing
|
2011-06-24 21:01:19 +02:00
|
|
|
banana.
|
|
|
|
|
|
|
|
= Mentioning Users =
|
|
|
|
|
|
|
|
In Differential and Maniphest, you can mention another user by writing:
|
|
|
|
|
|
|
|
@username
|
|
|
|
|
|
|
|
When you submit your comment, this will add them as a CC on the revision or task
|
2011-07-12 17:28:07 +02:00
|
|
|
if they aren't already CC'd.
|
|
|
|
|
|
|
|
= Phriction Documents =
|
|
|
|
|
|
|
|
You can link to Phriction documents with a name or path:
|
|
|
|
|
Require double brackets for Phriction links
Summary:
Single brackets are getting some troublesome false positives in Facebook's
install. Particularly, there's a weird convention at Facebook of tagging diffs
by putting stuff like "[perf]" or "[chat]" in the title, although this isn't
turned into structured data at any stage. When commits appear in Diffusion, we
currently link such ad-hoc tags to Phriction.
Wikipedia uses double-bracket sytnax, as do many other wikis, so this seems like
a reasonable burden to place on the lightweightness of the markup. The
alternative is selectively disabling Phriction markup in some interfaces, but
I'd rather allow integration in commit messages and just guard the syntax more
closely.
(I'm not providing any sort of migration plan since this landed less than a week
ago and I'm pretty confident no one has built a huge wiki yet, but I added a
CHANGELOG note.)
Test Plan: Edited a wiki document and added some links. Verified single brackets
were unlinked and double brackets were linked.
Reviewed By: jungejason
Reviewers: hsb, aran, jungejason, tuomaspelkonen
CC: aran, jungejason, epriestley
Differential Revision: 689
2011-07-18 17:52:40 +02:00
|
|
|
Make sure you sign and date your [[legal/Letter of Marque and Reprisal]]!
|
2011-07-12 17:28:07 +02:00
|
|
|
|
|
|
|
With a pipe (##|##), you can retitle the link. Use this to mislead your
|
|
|
|
opponents:
|
|
|
|
|
Require double brackets for Phriction links
Summary:
Single brackets are getting some troublesome false positives in Facebook's
install. Particularly, there's a weird convention at Facebook of tagging diffs
by putting stuff like "[perf]" or "[chat]" in the title, although this isn't
turned into structured data at any stage. When commits appear in Diffusion, we
currently link such ad-hoc tags to Phriction.
Wikipedia uses double-bracket sytnax, as do many other wikis, so this seems like
a reasonable burden to place on the lightweightness of the markup. The
alternative is selectively disabling Phriction markup in some interfaces, but
I'd rather allow integration in commit messages and just guard the syntax more
closely.
(I'm not providing any sort of migration plan since this landed less than a week
ago and I'm pretty confident no one has built a huge wiki yet, but I added a
CHANGELOG note.)
Test Plan: Edited a wiki document and added some links. Verified single brackets
were unlinked and double brackets were linked.
Reviewed By: jungejason
Reviewers: hsb, aran, jungejason, tuomaspelkonen
CC: aran, jungejason, epriestley
Differential Revision: 689
2011-07-18 17:52:40 +02:00
|
|
|
Check out these [[legal/boring_documents/ | exciting legal documents]]!
|