4,493
edits
APL Orchard: Difference between revisions
Jump to navigation
Jump to search
m
Text replacement - "</source>" to "</syntaxhighlight>"
m (Text replacement - "</source>" to "</syntaxhighlight>") |
|||
| Line 24: | Line 24: | ||
To post an image which is already hosted online, submit a message consisting exclusively of the URL to the image. Users with sufficient Stack Exchange reputation, see an <kbd>upload…</kbd> button to the right of the <kbd>send</kbd> button, allowing uploading images directly from their computer. | To post an image which is already hosted online, submit a message consisting exclusively of the URL to the image. Users with sufficient Stack Exchange reputation, see an <kbd>upload…</kbd> button to the right of the <kbd>send</kbd> button, allowing uploading images directly from their computer. | ||
A user can be pinged (audio is played on their device) by writing <source lang=md inline>@</ | A user can be pinged (audio is played on their device) by writing <source lang=md inline>@</syntaxhighlight>, followed by the username without spaces. On the top-right, to the left of <kbd>all rooms</kbd> you can configure the sound of notifications. If the user hasn't been in the room before, or hasn't been in it for long enough, they might not be pingable. The Stack Exchange Android app allows receiving ping notifications as push notifications regardless of whether you're in the room. There is no way to ping everyone in the room, although <code>@all</code> is used as a non-pinging convention when addressing everyone. | ||
To mark a message as potentially valuable for others, hover over it and and click the dark grey star (<span style=color:#222222>★</span>). This will cause it to turns yellow (<span style=color:#f3c200>★</span>) and the message will be visible on the starboard (the right sidebar) for some time. Click again to un-star. | To mark a message as potentially valuable for others, hover over it and and click the dark grey star (<span style=color:#222222>★</span>). This will cause it to turns yellow (<span style=color:#f3c200>★</span>) and the message will be visible on the starboard (the right sidebar) for some time. Click again to un-star. | ||
| Line 32: | Line 32: | ||
=== Replies === | === Replies === | ||
To reply to a specific message, hover over the message you want to reply to and click <kbd>↳</kbd> in the bottom-right corner of that message. This will insert a code similar to <code>:12345678</code> into the input field. Proceed to type your response and press enter or click <kbd>send</kbd> to send it. Note that replying to a message pings the user who wrote the message. <!-- To reply to users posting from IRC, via the chat bot, it is preferred to use <source lang=md inline>name:</ | To reply to a specific message, hover over the message you want to reply to and click <kbd>↳</kbd> in the bottom-right corner of that message. This will insert a code similar to <code>:12345678</code> into the input field. Proceed to type your response and press enter or click <kbd>send</kbd> to send it. Note that replying to a message pings the user who wrote the message. <!-- To reply to users posting from IRC, via the chat bot, it is preferred to use <source lang=md inline>name:</syntaxhighlight> instead of <code>@name</code>. Note that IRC users do not see edits, deletions, or formatting. --> | ||
You can view what a message was a reply to by clicking the reply indicator icon <kbd>↰</kbd> to the left of a message, which will either focus the target message on the screen, or, if the target message is too far in the past, open up the transcript pointing to the target message. Alternatively, hovering over a message will highlight the message it is replying to, and all its replies. | You can view what a message was a reply to by clicking the reply indicator icon <kbd>↰</kbd> to the left of a message, which will either focus the target message on the screen, or, if the target message is too far in the past, open up the transcript pointing to the target message. Alternatively, hovering over a message will highlight the message it is replying to, and all its replies. | ||
=== Basic formatting === | === Basic formatting === | ||
* '''Italics''': <source lang=md inline>*italics*</ | * '''Italics''': <source lang=md inline>*italics*</syntaxhighlight> or <source lang=md inline>_italics_</syntaxhighlight> | ||
* '''Bold''': <source lang=md inline>**bold**</ | * '''Bold''': <source lang=md inline>**bold**</syntaxhighlight> or <source lang=md inline>__bold__</syntaxhighlight> | ||
* '''Strike through''': <source lang=md inline>---strike through---</ | * '''Strike through''': <source lang=md inline>---strike through---</syntaxhighlight> | ||
* {{Anchor|inline|'''Inline code:'''}} <source lang=md inline>`inline code`</ | * {{Anchor|inline|'''Inline code:'''}} <source lang=md inline>`inline code`</syntaxhighlight> <ref>Backticks can be escaped with a backslash (<source lang=md inline>`\`x\`y`</syntaxhighlight> renders as <code>`x`y</code>). Alternatively, <code>```multiple``backticks\```</code>, which also disable <code>\</code>-escaping, can be used, giving <code>multiple``backticks\</code> - use a delimiter with one more backtick than the longest run of backticks in the code. Note that inline code cannot have leading white-space.</ref> | ||
* '''Link''': <source lang=md inline>https://example.com</ | * '''Link''': <source lang=md inline>https://example.com</syntaxhighlight> or <source lang=md inline>[display me](https://example.com)</syntaxhighlight> or <source lang=md inline>[display me](https://example.com "hover text")</syntaxhighlight><ref>Long URLs will be truncated with an ellipsis. A URL that exceeds the maximum message length of 500 characters can still be posted as a raw URL (without markdown): Follow it by <kbd>Shift</kbd>+<kbd>Enter</kbd>.</ref> | ||
* '''Spoiler''': <source lang=md inline>[spoiler](ftp:// "text hidden until hovered over")</ | * '''Spoiler''': <source lang=md inline>[spoiler](ftp:// "text hidden until hovered over")</syntaxhighlight> | ||
* '''Tags''': <source lang=md inline>[tag:code-golf]</ | * '''Tags''': <source lang=md inline>[tag:code-golf]</syntaxhighlight> or <source lang=md inline>[meta-tag:discussion]</syntaxhighlight> (tags from Stack Exchange's [[code golf]] community, [https://codegolf.stackexchange.com/ Code Golf & Coding Challenges]) | ||
* '''Oneboxes:''' When posted alone in a message, optionally preceded by a reply indicator (<code>:12345678</code>), some links (images, Wikipedia pages, Stack Exchange links, etc.) get "oneboxed", giving them an expanded display with special formatting. | * '''Oneboxes:''' When posted alone in a message, optionally preceded by a reply indicator (<code>:12345678</code>), some links (images, Wikipedia pages, Stack Exchange links, etc.) get "oneboxed", giving them an expanded display with special formatting. | ||
| Line 74: | Line 74: | ||
Since a lot of questions are repeated, it is courteous to search for an answer on [[APLcart]] before asking in the APL Orchard. | Since a lot of questions are repeated, it is courteous to search for an answer on [[APLcart]] before asking in the APL Orchard. | ||
Announcements are made with the initial markdown <source lang=md inline>**Announcement:**</ | Announcements are made with the initial markdown <source lang=md inline>**Announcement:**</syntaxhighlight> rendering the text in bold. | ||
Some abbreviations are ubiquitous, like ''TMN'' for ''[[Comparison with traditional mathematics|Traditional Mathematical Notation]]'', and ''CMC'' for ''Chat Mini Challenge'' which usually implies an informal [[code golf]] competition. Additional terms an abbreviations are shared with [https://codegolf.meta.stackexchange.com/questions/12537/what-are-our-specific-abbreviations-and-terms/12538#12538 those of the Stack Exchange code golf community]. When posting such a chat mini challenge, the task specification is prefaced with the markdown <source lang=md inline>**CMC:**</ | Some abbreviations are ubiquitous, like ''TMN'' for ''[[Comparison with traditional mathematics|Traditional Mathematical Notation]]'', and ''CMC'' for ''Chat Mini Challenge'' which usually implies an informal [[code golf]] competition. Additional terms an abbreviations are shared with [https://codegolf.meta.stackexchange.com/questions/12537/what-are-our-specific-abbreviations-and-terms/12538#12538 those of the Stack Exchange code golf community]. When posting such a chat mini challenge, the task specification is prefaced with the markdown <source lang=md inline>**CMC:**</syntaxhighlight>, rendering the text in bold. | ||
Some use a reply of <source lang=md inline>+←1</ | Some use a reply of <source lang=md inline>+←1</syntaxhighlight> to indicate agreement or appreciation,<ref>This is a pun on the APL expression <source lang=apl inline>counter+←1</syntaxhighlight> increasing the counter (of "likes") by one.</ref> similar to how "+1" or "👍" is used in other social media. | ||
=== Emoticons === | === Emoticons === | ||
{| | {| | ||
| <source lang=md inline>○/</ | | <source lang=md inline>○/</syntaxhighlight> || greeting, farewell | ||
|- | |- | ||
| <source lang=md inline>⍨</ | | <source lang=md inline>⍨</syntaxhighlight> || frown, displeasure, "hmpf" | ||
|- | |- | ||
| <source lang=md inline>\○/</ | | <source lang=md inline>\○/</syntaxhighlight> || despair, wonderment, "wow" (be careful as this can be positive or negative) | ||
|- | |- | ||
| <source lang=md inline>¯\_(⍨)_/¯</ | | <source lang=md inline>¯\_(⍨)_/¯</syntaxhighlight> || "oh well" | ||
|- | |- | ||
| <source lang=md inline>∘.○</ | | <source lang=md inline>∘.○</syntaxhighlight> || "I'm confused" | ||
|} | |} | ||