4,494
edits
APL Orchard: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
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 === | ||
| Line 62: | Line 60: | ||
The room features a chat bot, '''Dyalog APL''', which can evaluate a safe subset of APL.<ref>Using [[Adám Brudzewsky]]'s [https://github.com/abrudz/dyalog-safe-exec Safe Execute for Dyalog APL] tool.</ref> To use it, prefix a chat message, inline code, or a code block with <source lang=apl inline>⋄</source>. Using markdown (for example <source lang=md inline>`⋄ 2+3`</source>) or fixed-width (4 or more initial spaces on each line, which can be inserted by pressing <kbd>Ctrl</kbd>+<kbd>k</kbd>) is highly recommended for readability and to avoids interpretation of APL symbols as markdown. | The room features a chat bot, '''Dyalog APL''', which can evaluate a safe subset of APL.<ref>Using [[Adám Brudzewsky]]'s [https://github.com/abrudz/dyalog-safe-exec Safe Execute for Dyalog APL] tool.</ref> To use it, prefix a chat message, inline code, or a code block with <source lang=apl inline>⋄</source>. Using markdown (for example <source lang=md inline>`⋄ 2+3`</source>) or fixed-width (4 or more initial spaces on each line, which can be inserted by pressing <kbd>Ctrl</kbd>+<kbd>k</kbd>) is highly recommended for readability and to avoids interpretation of APL symbols as markdown. | ||
== Conventions == | |||
Some use a reply of <source lang=md inline>+←1</source> to indicate agreement or appreciation,<ref>Thus is a pun on the APL expression <source lang=apl inline>counter+←1</source> increasing the counter (of "likes") by one.</ref> similar to how "+1" or "👍" is used in other social media. | |||
Announcements are made with the initial markdown <source lang=md inline>**Announcement:**</source> 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 prefaces with the markdown <source lang=md inline>**CMC:**</source> rendering the text in bold. | |||
== Live sessions == | == Live sessions == | ||