improve markdown references to FAQ entries
We quasi-canonicalized markdown links to FAQ entries. **IMPORTANT NOTE**: This is a useful step in completing issue #2417. This commit is consistent with the top level TODO comment requirements. Nevertheless, this changes made by this commit needs to be examined and in some cases improved. A link to an FAQ entry is of the form: ``` FAQ on "[the link text](....faq.html#string)" FAQ on "[the link text](....faq.html#string)" ``` The "FAQ" is at the start of the line, or in rare cases is preceded only by whitespace. The reference to the FAQ starts outside of the markdown link with the string **FAQ ON "**. After the markdown link is a **"** followed by either the end of line or a single punctuation character such as a period or comma. We reduced the size of "the link text" that refer to an FAQ to at most 3 words. In some cases the sentence and/or text surrounding the markdown link to a FAQ may need to be further adjusted to better accommodate this new style. **IMPORTANT NOTE**: References to a FAQ entry are on a separate line. p.s. When linking to the `faq.html` file itself, we use markdown of the form "`the [IOCCC FAQ](..../faq.html)`" and place the word "the" outside of the "IOCCC FAQ" link text. Given the above system (and because references to an FAQ entry is on a separate line), the following command shows links to FAQ entries, sorted by FAQ entry "link #name" so that one may evaluate the way a given FAQ entry is referenced: ```sh find * -name '*.md' -print0 | xargs0 grep -E '^[[:space:]]*FAQ on "' | sed -e 's/^\([^:]*\):\( *FAQ on "[^#]*\)#\([^)]*\)\()".*\)$/#\3\t\1\t\2#\3\4/' | sort ``` The above command shows the value of consistency when it comes to FAQ references. **NOTE**: There are a few differences on how a given FAQ is references. That is probably OK as there is NOT an "total mandate" that all references to a given FAQ must have the same "link text" for example. On the other hand if references to a given FAQ can be identical, that might be helpful. We are certain that in some contexts the "link text" might need to change. Should we decide to change the way FAQ are referenced, we will be able to modify identify and modify them with greater ease.' Examine the changes made by this commit and adjust and/or improve as needed. Performed `make www` to accomplish the above and to test under macOS.
This commit is contained in:
Landon Curt Noll committed
1 parent
d852734d98
commit
0bc6c3e413
104 files changed
+1051
-687
No files matched your search
+22
-17
@@ -395,9 +395,11 @@ and are <strong>VERY LIKELY</strong> to be updated before the next IOCCC.
|
||||
They are are provided as a <strong>VERY TENTATIVE</strong> hint at <strong>what
|
||||
MIGHT</strong> be used in the next IOCCC. In some cases they might
|
||||
even be a copy of the guidelines from the previous IOCCC.</p>
|
||||
<p>See our <a href="../faq.html#feedback">FAQ about providing feedback</a> as well
|
||||
as our <a href="../faq.html#question">FAQ about asking questions</a> about
|
||||
these guidelines.</p>
|
||||
<p>See our
|
||||
FAQ on “<a href="#feedback">rules, guidelines, tools feedback</a>”.
|
||||
as well as our
|
||||
FAQ on “<a href="../faq.html#question">asking questions</a>”
|
||||
about these guidelines.</p>
|
||||
<h1 id="the-ioccc-is-closed">The IOCCC is closed</h1>
|
||||
<p>The IOCCC is <strong>NOT</strong> accepting new submissions at this time. See the
|
||||
<a href="../years.html">IOCCC winning entries page</a> for the entries that have won the
|
||||
@@ -476,8 +478,8 @@ The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:
|
||||
The <a href="rules.html">IOCCC rules</a>, <a href="guidelines.html">IOCCC
|
||||
guidelines</a> will be available on the <a href="https://www.ioccc.org">Official IOCCC
|
||||
website</a> on or slightly before start of this IOCCC. Please check
|
||||
<a href="../faq.html#submit">the IOCCC FAQ about how to submit</a> to see how
|
||||
to submit entries, on or after the start of this IOCCC, to be sure
|
||||
FAQ on “<a href="../faq.html#submit">how to submit</a>”
|
||||
to see how to submit entries, on or after the start of this IOCCC, to be sure
|
||||
you are using the correct versions of these items before using the
|
||||
IOCCC submission URL.
|
||||
</p>
|
||||
@@ -672,8 +674,8 @@ below) fails to validate the <code>.auth.json</code> or <code>.info.json</code>
|
||||
it is an error and possibly a bug that you should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E">report as a bug at the
|
||||
mkiocccentry issues
|
||||
page</a>.
|
||||
<strong>PLEASE run the <code>bug_report.sh</code> script to help us out here!</strong> See the <a href="../faq.html#mkiocccentry_bugs">the FAQ
|
||||
about reporting bugs in the mkiocccentry repo</a>.
|
||||
<strong>PLEASE run the <code>bug_report.sh</code> script to help us out here!</strong> See the
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
However, just because there are errors <strong>does not</strong> mean it is a bug in the
|
||||
@@ -897,8 +899,8 @@ not pass and you used <code>mkiocccentry(1)</code> it is very possibly a bug and
|
||||
<a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E">report
|
||||
it as a bug at the mkiocccentry issues
|
||||
page</a>.
|
||||
See the <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting
|
||||
bugs in the mkiocccentry repo</a>.
|
||||
See the
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
Assuming that <code>chkentry(1)</code> validates both <code>.auth.json</code> and
|
||||
@@ -940,8 +942,8 @@ compressed tarball; if any issues are found (‘<code>feathers are stuck in the
|
||||
<code>mkiocccentry(1)</code></strong>, then it is very possibly a bug in one of the tools and you
|
||||
should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E">report it as a bug at the mkiocccentry issues
|
||||
page</a>. <strong>PLEASE run the
|
||||
<code>bug_report.sh</code> script to help us out here!</strong> See <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting bugs
|
||||
in the mkiocccentry repo</a>.
|
||||
<code>bug_report.sh</code> script to help us out here!</strong> See
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
As part of its sanity checks, <code>txzchk(1)</code> will run <code>fnamchk(1)</code> on the
|
||||
@@ -955,8 +957,8 @@ would prevent this from happening as it would not create such a file anyway. If
|
||||
<code>mkiocccentry(1)</code> was used it would rather suggest a bug in one of the tools and
|
||||
you should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E">report it as a bug at the mkiocccentry issues
|
||||
page</a>.
|
||||
See <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting bugs in the mkiocccentry
|
||||
repo</a>.
|
||||
See
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
If verbosity level is > 0, <code>txzchk(1)</code> will show the contents of the tarball which is
|
||||
@@ -1045,8 +1047,9 @@ by modifying the <code>CSTD</code> Makefile variable. For example, to use <code>
|
||||
<pre><code> CSTD= -std=c17</code></pre>
|
||||
<p class="leftbar">
|
||||
For compilers, such as <code>clang</code>, that have the <code>-Weverything</code> option,
|
||||
while you may wish to try it, you should look at <a href="../faq.html#weverything">the FAQ about clang
|
||||
-Weverything</a>. We do <strong>NOT</strong> recommend that you put
|
||||
while you may wish to try it, you should look at
|
||||
FAQ on “<a href="../faq.html#weverything">clang -Weverything</a>”.
|
||||
We do <strong>NOT</strong> recommend that you put
|
||||
the use of <code>-Weverything</code> into your submission’s <code>Makefile</code> for the reasons
|
||||
cited there. This goes even if your version does not trigger a warning as some
|
||||
other version might!
|
||||
@@ -1884,7 +1887,8 @@ It has been shown that receiving <strong>anonymous</strong> gifts provides the
|
||||
<a href="../judges.html">IOCCC judges</a> help make the <a href="../index.html">IOCCC</a> better for everyone. :-)
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
See <a href="../faq.html#support">FAQ: How may I support the IOCCC?</a>.
|
||||
See
|
||||
FAQ on “<a href="../faq.html#support">support the IOCCC</a>”.
|
||||
</p>
|
||||
<p>More often than not, we select a small submission (usually one line) and a
|
||||
strange/creative layout submission. We sometimes also select a
|
||||
@@ -1987,7 +1991,8 @@ See the <a href="../news.html">Official IOCCC website news</a> for additional in
|
||||
<p class="change marker">
|
||||
For the updates and breaking <a href="../news.html">IOCCC news</a>, you are encouraged to follow
|
||||
the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a>. See our
|
||||
<a href="../faq.html#try_mastodon">FAQ on Mastodon</a> for more information. <strong>Please be
|
||||
FAQ on “<a href="../faq.html#try_mastodon">Mastodon</a>”
|
||||
for more information. <strong>Please be
|
||||
aware</strong> that unless you are mentioned you most likely will <strong>NOT</strong> get a
|
||||
notification so you should make sure to check the page.
|
||||
</p>
|
||||
|
||||
+22
-17
@@ -8,9 +8,11 @@ They are are provided as a **VERY TENTATIVE** hint at **what
|
||||
MIGHT** be used in the next IOCCC. In some cases they might
|
||||
even be a copy of the guidelines from the previous IOCCC.
|
||||
|
||||
See our [FAQ about providing feedback](../faq.html#feedback) as well
|
||||
as our [FAQ about asking questions](../faq.html#question) about
|
||||
these guidelines.
|
||||
See our
|
||||
FAQ on "[rules, guidelines, tools feedback](#feedback)".
|
||||
as well as our
|
||||
FAQ on "[asking questions](../faq.html#question)"
|
||||
about these guidelines.
|
||||
|
||||
|
||||
# The IOCCC is closed
|
||||
@@ -115,8 +117,8 @@ The submit URL should be active on or slightly before **2024-MMM-DD HH:MM:SS UTC
|
||||
The [IOCCC rules](rules.html), [IOCCC
|
||||
guidelines](guidelines.html) will be available on the [Official IOCCC
|
||||
website](https://www.ioccc.org) on or slightly before start of this IOCCC. Please check
|
||||
[the IOCCC FAQ about how to submit](../faq.html#submit) to see how
|
||||
to submit entries, on or after the start of this IOCCC, to be sure
|
||||
FAQ on "[how to submit](../faq.html#submit)"
|
||||
to see how to submit entries, on or after the start of this IOCCC, to be sure
|
||||
you are using the correct versions of these items before using the
|
||||
IOCCC submission URL.
|
||||
</p>
|
||||
@@ -354,8 +356,8 @@ below) fails to validate the `.auth.json` or `.info.json`
|
||||
it is an error and possibly a bug that you should [report as a bug at the
|
||||
mkiocccentry issues
|
||||
page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E).
|
||||
**PLEASE run the `bug_report.sh` script to help us out here!** See the [the FAQ
|
||||
about reporting bugs in the mkiocccentry repo](../faq.html#mkiocccentry_bugs).
|
||||
**PLEASE run the `bug_report.sh` script to help us out here!** See the
|
||||
FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
@@ -558,8 +560,8 @@ not pass and you used `mkiocccentry(1)` it is very possibly a bug and you should
|
||||
[report
|
||||
it as a bug at the mkiocccentry issues
|
||||
page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E).
|
||||
See the [the FAQ about reporting
|
||||
bugs in the mkiocccentry repo](../faq.html#mkiocccentry_bugs).
|
||||
See the
|
||||
FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
@@ -613,8 +615,8 @@ tarball`' :-) ) **AND if and _ONLY IF_ you used
|
||||
`mkiocccentry(1)`**, then it is very possibly a bug in one of the tools and you
|
||||
should [report it as a bug at the mkiocccentry issues
|
||||
page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E). **PLEASE run the
|
||||
`bug_report.sh` script to help us out here!** See [the FAQ about reporting bugs
|
||||
in the mkiocccentry repo](../faq.html#mkiocccentry_bugs).
|
||||
`bug_report.sh` script to help us out here!** See
|
||||
FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
@@ -630,8 +632,8 @@ would prevent this from happening as it would not create such a file anyway. If
|
||||
`mkiocccentry(1)` was used it would rather suggest a bug in one of the tools and
|
||||
you should [report it as a bug at the mkiocccentry issues
|
||||
page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E).
|
||||
See [the FAQ about reporting bugs in the mkiocccentry
|
||||
repo](../faq.html#mkiocccentry_bugs).
|
||||
See
|
||||
FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
@@ -753,8 +755,9 @@ by modifying the `CSTD` Makefile variable. For example, to use `c17` instead:
|
||||
|
||||
<p class="leftbar">
|
||||
For compilers, such as `clang`, that have the `-Weverything` option,
|
||||
while you may wish to try it, you should look at [the FAQ about clang
|
||||
-Weverything](../faq.html#weverything). We do **NOT** recommend that you put
|
||||
while you may wish to try it, you should look at
|
||||
FAQ on "[clang -Weverything](../faq.html#weverything)".
|
||||
We do **NOT** recommend that you put
|
||||
the use of `-Weverything` into your submission's `Makefile` for the reasons
|
||||
cited there. This goes even if your version does not trigger a warning as some
|
||||
other version might!
|
||||
@@ -1768,7 +1771,8 @@ It has been shown that receiving **anonymous** gifts provides the
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
See [FAQ: How may I support the IOCCC?](../faq.html#support).
|
||||
See
|
||||
FAQ on "[support the IOCCC](../faq.html#support)".
|
||||
</p>
|
||||
|
||||
More often than not, we select a small submission (usually one line) and a
|
||||
@@ -1903,7 +1907,8 @@ See the [Official IOCCC website news](../news.html) for additional information.
|
||||
<p class="change marker">
|
||||
For the updates and breaking [IOCCC news](../news.html), you are encouraged to follow
|
||||
the [IOCCC on Mastodon](https://fosstodon.org/@ioccc). See our
|
||||
[FAQ on Mastodon](../faq.html#try_mastodon) for more information. **Please be
|
||||
FAQ on "[Mastodon](../faq.html#try_mastodon)"
|
||||
for more information. **Please be
|
||||
aware** that unless you are mentioned you most likely will **NOT** get a
|
||||
notification so you should make sure to check the page.
|
||||
</p>
|
||||
|
||||
+27
-18
@@ -395,9 +395,11 @@ and are <strong>VERY LIKELY</strong> to be updated before the next IOCCC.
|
||||
They are are provided as a <strong>VERY TENTATIVE</strong> hint at <strong>what
|
||||
MIGHT</strong> be used in the next IOCCC. In some cases they might
|
||||
even be a copy of the rules from the previous IOCCC.</p>
|
||||
<p>See our <a href="../faq.html#feedback">FAQ about providing feedback</a> as well
|
||||
as our <a href="../faq.html#question">FAQ about asking questions</a> about
|
||||
these rules.</p>
|
||||
<p>See our
|
||||
FAQ on “<a href="#feedback">rules, guidelines, tools feedback</a>”.
|
||||
as well as our
|
||||
FAQ on “<a href="../faq.html#question">about asking questions</a>”
|
||||
about these rules.</p>
|
||||
<h1 id="the-ioccc-is-closed">The IOCCC is closed</h1>
|
||||
<p>The IOCCC is <strong>NOT</strong> accepting new submissions at this time. See the
|
||||
<a href="../years.html">IOCCC winning entries page</a> for the entries that have won the
|
||||
@@ -472,7 +474,8 @@ provisional <strong>BETA</strong> versions and <strong>may be adjusted <em>AT AN
|
||||
<p>When the IOCCC is open, the submission URL is:
|
||||
<a href="https://submit.ioccc.org">https://submit.ioccc.org</a>; at all other
|
||||
times that link is likely to be unresponsive.</p>
|
||||
<p>Please check the <a href="../faq.html#submit">How to enter FAQ</a>
|
||||
<p>Please check the
|
||||
FAQ on “<a href="../faq.html#submit">how to submit</a>”
|
||||
for <strong>important information</strong> on how to submit to the IOCCC.</p>
|
||||
<p class="leftbar">
|
||||
The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:SS UTC</strong>.<br>
|
||||
@@ -482,7 +485,7 @@ The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:
|
||||
<p>The official <a href="rules.html">IOCCC rules</a> and <a href="guidelines.html">IOCCC guidelines</a> will be
|
||||
available on the <a href="../index.html">official IOCCC website</a> on or slightly before
|
||||
the start of this IOCCC. The <code>mkiocccentry</code> toolkit may be obtained at any time
|
||||
at the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>.</p>
|
||||
at the <a href="https://github.com/ioccc-src/mkiocccentry">report mkiocccentry bugs</a>.</p>
|
||||
<p><strong>Please recheck on or after the start of this IOCCC to be sure you
|
||||
are using the correct versions of these items <em>before using the IOCCC
|
||||
submission URL</em></strong>.</p>
|
||||
@@ -570,7 +573,8 @@ as a command like argument to the <code>iocccsize(1)</code> tool. For example:
|
||||
<h2 id="rule-3">Rule 3</h2>
|
||||
</div>
|
||||
<p>Submissions should be performed using the instructions outlined at:
|
||||
the <a href="../faq.html#submit">How to enter FAQ</a>.</p>
|
||||
the
|
||||
FAQ on “<a href="../faq.html#submit">how to submit</a>”</p>
|
||||
<p>To submit to an open IOCCC, you must use the <a href="https://submit.ioccc.org/">IOCCC submit
|
||||
server</a>. Unless the IOCCC is open, that link will
|
||||
likely be unresponsive.</p>
|
||||
@@ -696,8 +700,9 @@ In order to register for the IOCCC, you <strong>MUST</strong> have a valid email
|
||||
enough time for one automated exchange of email as part of your
|
||||
submission.</p>
|
||||
<p class="leftbar">
|
||||
See <a href="../faq.html#register">the FAQ on how to register for the IOCCC</a> in the
|
||||
<a href="../faq.html">FAQ</a> for details.
|
||||
See
|
||||
FAQ on “<a href="../faq.html#register">how to register</a>”
|
||||
for details.
|
||||
</p>
|
||||
<div id="rule16">
|
||||
<h2 id="rule-16">Rule 16</h2>
|
||||
@@ -824,14 +829,18 @@ those requirements.
|
||||
The <code>Makefile</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in <strong><a href="https://www.gnu.org/software/make/manual/make.html">GNU
|
||||
Makefile</a></strong> form. See the
|
||||
<a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">Makefile.example</a>,
|
||||
the <a href="../faq.html#submission_makefiles">FAQ about your submission’s Makefile</a> and
|
||||
the <a href="../faq.html#make_compatibility">FAQ about IOCCC Makefile compatibility</a> for help.
|
||||
the
|
||||
FAQ on “<a href="../faq.html#submission_makefiles">submission Makefile</a>”
|
||||
and the
|
||||
FAQ on “<a href="../faq.html#make_compatibility">Makefile compatibility</a>”
|
||||
for help.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
The <code>remarks.md</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in markdown form. See also
|
||||
<a href="#rule18">Rule 18</a> and our <a href="../faq.html#remarks_md">FAQ about what to put in your
|
||||
remarks.md</a> and the <a href="../faq.html#markdown">FAQ about IOCCC best markdown
|
||||
practices</a>.
|
||||
<a href="#rule18">Rule 18</a> and our
|
||||
FAQ on “<a href="../faq.html#remarks_md">remarks.md</a>”
|
||||
and the
|
||||
FAQ on “<a href="../faq.html#markdown">markdown practices</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
See also the <a href="https://www.markdownguide.org/basic-syntax">markdown syntax</a> guide
|
||||
@@ -957,8 +966,8 @@ If you run into a problem with one or more of these tools, <strong>PLEASE</stron
|
||||
as a bug at the mkiocccentry issues
|
||||
page</a>,
|
||||
<strong>making sure to run <code>bug_report.sh</code></strong>. See the <a href="guidelines.html">guidelines</a>
|
||||
for help here and also read <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting bugs in the mkiocccentry
|
||||
repo</a>.
|
||||
for help here and also read
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">mkiocccentry repo bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
At the risk of stating the obvious: submissions that violate <a href="#rule17">Rule
|
||||
@@ -991,8 +1000,7 @@ Basics</a>.
|
||||
We currently use <a href="https://pandoc.org">pandoc</a> to convert markdown to HTML.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
Please see our <a href="../faq.html#remarks_md">FAQ about what to put in your
|
||||
remarks.md</a> and the <a href="../markdown.html">IOCCC markdown
|
||||
Please see our FAQ “<a href="../faq.html#remarks_md">remarks.md</a>” and the <a href="../markdown.html">IOCCC markdown
|
||||
guidelines</a> for additional markdown guidance.
|
||||
</p>
|
||||
<div id="rule20">
|
||||
@@ -1104,7 +1112,8 @@ You should be sure you have the current <a href="rules.html">IOCCC rules</a> and
|
||||
<p class="leftbar">
|
||||
For the updates and breaking IOCCC news, you are encouraged to follow
|
||||
the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a> account. See our
|
||||
<a href="../faq.html#try_mastodon">FAQ about Mastodon</a> for more information. Please do note that unless
|
||||
FAQ on “<a href="../faq.html#try_mastodon">Mastodon</a>”
|
||||
for more information. Please do note that unless
|
||||
you are mentioned by us you will <strong>NOT</strong> get a notification from the app <em>so you
|
||||
should refresh the page <strong>even if you do follow us</strong></em>.
|
||||
</p>
|
||||
|
||||
+27
-18
@@ -8,9 +8,11 @@ They are are provided as a **VERY TENTATIVE** hint at **what
|
||||
MIGHT** be used in the next IOCCC. In some cases they might
|
||||
even be a copy of the rules from the previous IOCCC.
|
||||
|
||||
See our [FAQ about providing feedback](../faq.html#feedback) as well
|
||||
as our [FAQ about asking questions](../faq.html#question) about
|
||||
these rules.
|
||||
See our
|
||||
FAQ on "[rules, guidelines, tools feedback](#feedback)".
|
||||
as well as our
|
||||
FAQ on "[about asking questions](../faq.html#question)"
|
||||
about these rules.
|
||||
|
||||
|
||||
# The IOCCC is closed
|
||||
@@ -112,7 +114,8 @@ When the IOCCC is open, the submission URL is:
|
||||
[https://submit.ioccc.org](https://submit.ioccc.org); at all other
|
||||
times that link is likely to be unresponsive.
|
||||
|
||||
Please check the [How to enter FAQ](../faq.html#submit)
|
||||
Please check the
|
||||
FAQ on "[how to submit](../faq.html#submit)"
|
||||
for **important information** on how to submit to the IOCCC.
|
||||
|
||||
<p class="leftbar">
|
||||
@@ -125,7 +128,7 @@ Please wait to submit your entries until after that time.
|
||||
The official [IOCCC rules](rules.html) and [IOCCC guidelines](guidelines.html) will be
|
||||
available on the [official IOCCC website](../index.html) on or slightly before
|
||||
the start of this IOCCC. The `mkiocccentry` toolkit may be obtained at any time
|
||||
at the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry).
|
||||
at the [report mkiocccentry bugs](https://github.com/ioccc-src/mkiocccentry).
|
||||
|
||||
**Please recheck on or after the start of this IOCCC to be sure you
|
||||
are using the correct versions of these items _before using the IOCCC
|
||||
@@ -249,7 +252,8 @@ as a command like argument to the `iocccsize(1)` tool. For example:
|
||||
</div>
|
||||
|
||||
Submissions should be performed using the instructions outlined at:
|
||||
the [How to enter FAQ](../faq.html#submit).
|
||||
the
|
||||
FAQ on "[how to submit](../faq.html#submit)"
|
||||
|
||||
To submit to an open IOCCC, you must use the [IOCCC submit
|
||||
server](https://submit.ioccc.org/). Unless the IOCCC is open, that link will
|
||||
@@ -429,8 +433,9 @@ enough time for one automated exchange of email as part of your
|
||||
submission.
|
||||
|
||||
<p class="leftbar">
|
||||
See [the FAQ on how to register for the IOCCC](../faq.html#register) in the
|
||||
[FAQ](../faq.html) for details.
|
||||
See
|
||||
FAQ on "[how to register](../faq.html#register)"
|
||||
for details.
|
||||
</p>
|
||||
|
||||
<div id="rule16">
|
||||
@@ -554,15 +559,19 @@ those requirements.
|
||||
The `Makefile` **MUST** be a **non**-empty file in **[GNU
|
||||
Makefile](https://www.gnu.org/software/make/manual/make.html)** form. See the
|
||||
[Makefile.example](https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example),
|
||||
the [FAQ about your submission's Makefile](../faq.html#submission_makefiles) and
|
||||
the [FAQ about IOCCC Makefile compatibility](../faq.html#make_compatibility) for help.
|
||||
the
|
||||
FAQ on "[submission Makefile](../faq.html#submission_makefiles)"
|
||||
and the
|
||||
FAQ on "[Makefile compatibility](../faq.html#make_compatibility)"
|
||||
for help.
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
The `remarks.md` **MUST** be a **non**-empty file in markdown form. See also
|
||||
[Rule 18](#rule18) and our [FAQ about what to put in your
|
||||
remarks.md](../faq.html#remarks_md) and the [FAQ about IOCCC best markdown
|
||||
practices](../faq.html#markdown).
|
||||
[Rule 18](#rule18) and our
|
||||
FAQ on "[remarks.md](../faq.html#remarks_md)"
|
||||
and the
|
||||
FAQ on "[markdown practices](../faq.html#markdown)".
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
@@ -690,8 +699,8 @@ If you run into a problem with one or more of these tools, **PLEASE** [report it
|
||||
as a bug at the mkiocccentry issues
|
||||
page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E),
|
||||
**making sure to run `bug_report.sh`**. See the [guidelines](guidelines.html)
|
||||
for help here and also read [the FAQ about reporting bugs in the mkiocccentry
|
||||
repo](../faq.html#mkiocccentry_bugs).
|
||||
for help here and also read
|
||||
FAQ on "[mkiocccentry repo bugs](../faq.html#mkiocccentry_bugs)".
|
||||
</p>
|
||||
|
||||
<p class="leftbar">At the risk of stating the obvious: submissions that violate [Rule
|
||||
@@ -735,8 +744,7 @@ We currently use [pandoc](https://pandoc.org) to convert markdown to HTML.
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
Please see our [FAQ about what to put in your
|
||||
remarks.md](../faq.html#remarks_md) and the [IOCCC markdown
|
||||
Please see our FAQ "[remarks.md](../faq.html#remarks_md)" and the [IOCCC markdown
|
||||
guidelines](../markdown.html) for additional markdown guidance.
|
||||
</p>
|
||||
|
||||
@@ -890,7 +898,8 @@ See the [Official IOCCC website news](../news.html) for additional information.
|
||||
<p class="leftbar">
|
||||
For the updates and breaking IOCCC news, you are encouraged to follow
|
||||
the [IOCCC on Mastodon](https://fosstodon.org/@ioccc) account. See our
|
||||
[FAQ about Mastodon](../faq.html#try_mastodon) for more information. Please do note that unless
|
||||
FAQ on "[Mastodon](../faq.html#try_mastodon)"
|
||||
for more information. Please do note that unless
|
||||
you are mentioned by us you will **NOT** get a notification from the app _so you
|
||||
should refresh the page **even if you do follow us**_.
|
||||
</p>
|
||||
|
||||
Reference in new issue
Block a user