From f54a502a128d58c9a8a8aab0ee7c67589682cc0e Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Fri, 18 Oct 2024 16:18:52 -0700 Subject: [PATCH] More progress on FAQ reordering More work must be done but to make sure that things are safe I am committing what has been done so far as this is very error prone and right now it seems okay. --- faq.html | 442 +++++++++++++++++++++++-------------------- faq.md | 568 ++++++++++++++++++++++++++++++------------------------- 2 files changed, 542 insertions(+), 468 deletions(-) diff --git a/faq.html b/faq.html index 438363caf..23400c002 100644 --- a/faq.html +++ b/faq.html @@ -893,127 +893,6 @@ for more up to date information on downloading, compiling, and related FAQ infor Jump to: top
Yes! The mkiocccentry(1) tool has some options to help write OR read from an
-answers file so you do not have to input the author(s) or the submission
-details (like the abstract, summary etc.), just to change a file.
To write to answers.txt try:
mkiocccentry -a answers.txt ...
-Alternatively, if you wish to overwrite a file, you can use the -A
-flag with the same option argument. Be very careful that you do not accidentally
-overwrite your prog.c or some other important file!
To make use of the answers file, use the -i answers option like:
mkiocccentry -i answers.txt ...
-There are types of entries that are frequently submitted to the IOCCC. -While we do not wish to prevent people from sending -a submission to the IOCCC on a frequently submitted theme, -we do wish to provide a fair warning to those who do.
-IMPORTANT HINT: It is not fatal to send in those types of -entries, it is just HARDER to win with such a submission. A -submission on a frequently submitted theme will have to do something -in a really unique AND interesting way to even make it into the -final judging rounds. It will have to compete with previous IOCCC -winners based on the same theme.
-IMPORTANT HINT: If you really wish send in a submission on a -frequently submitted theme, be sure that it is obfuscated in several -new and novel ways.
-IMPORTANT HINT: Be sure to clearly explain near the beginning
-of your remarks.md file, see the
-FAQ on “remarks.md”,
-why you are submitting an entry based on a frequently
-submitted theme and how compares with previous IOCCC winners
-of the same theme.
While it is possible to win a new IOCCC with one of these -frequently submitted types of entries, level of the competition from -previous IOCCC entries make it more challenging to be successful.
-It is also important to note that the guidelines often -state something along the lines of:
- We tend to dislike programs that: are similar to previous winning entries.
-FAIR WARNING: Be sure to clearly explain near the beginning
-of your remarks.md file, see the
-FAQ on “remarks.md”,
-why you are submitting an entry based on a frequently
-submitted theme and how compares with previous IOCCC winners
-of the same theme.
Jump to: top
-Jump to: top
While your entry’s source filename, as submitted, must be prog.c, your entry’s Makefile
-may copy prog.c to a different filename as part of the compiling/building process. For example:
# Makefile continues above ...
-
- all: desired_name
-
- desired_name: desired_name.c
- rm -f $@
- cc desired_name.c -o $@
-
- desired_name.c: prog.c
- rm -f $@
- cp -f prog.c $@
-
- clean:
- rm -f desired_name.o
-
- clobber: clean
- rm -f desired_name.c desired_name
-
- # Makefile continues below ...
-We recommend that the make clobber rule remove files that your entry
-creates as part of the compiling/building process.
You may also copy the compiled prog into a different file as part of compiling process.
-For example:
# Makefile continues above ...
-
- all: desired_name
-
- different_name: prog
- rm -f $@
- cp -f prog $@
-
- clean:
- rm -f prog.o
-
- clobber: clean
- rm -f desired_name
-
- # Makefile continues below ...
-Jump to: top
-See also the FAQ on “rules, guidelines, tools feedback”.
Jump to: top
-The IOCCC makes extensive use of markdown.
-For example, we submitting to the IOCCC, we have people
-to submit remarks about entry in markdown format. Every
-winning IOCCC entry uses a README.md markdown file
-as the basis for forming the index.html web page for that entry.
-All generated HTML pages on the Official IOCCC website
-start with some markdown content.
IMPORTANT: Please read the IOCCC markdown best practices guide -as it lists things you should not use in markdown files.
-See the markdown syntax guide. -See also CommonMark Spec.
-Jump to: top
- -mkiocccentry tool?As the mkiocccentry toolkit is -crucial in the contest, both for submitters and the judges, if you find a bug -(or you think you find a bug) we would be grateful if you were to report it at -the mkiocccentry issues -page.
-Please see the -FAQ on “reporting bugs and other issues in the mkiocccentry repo” -in the mkiocccentry repo.
-Jump to: top
Yes! The mkiocccentry(1) tool has some options to help write OR read from an
+answers file so you do not have to input the author(s) or the submission
+details (like the abstract, summary etc.), just to change a file.
To write to answers.txt try:
mkiocccentry -a answers.txt ...
+Alternatively, if you wish to overwrite a file, you can use the -A
+flag with the same option argument. Be very careful that you do not accidentally
+overwrite your prog.c or some other important file!
To make use of the answers file, use the -i answers option like:
mkiocccentry -i answers.txt ...
+Jump to: top
+While your entry’s source filename, as submitted, must be prog.c, your entry’s Makefile
+may copy prog.c to a different filename as part of the compiling/building process. For example:
# Makefile continues above ...
+
+ all: desired_name
+
+ desired_name: desired_name.c
+ rm -f $@
+ cc desired_name.c -o $@
+
+ desired_name.c: prog.c
+ rm -f $@
+ cp -f prog.c $@
+
+ clean:
+ rm -f desired_name.o
+
+ clobber: clean
+ rm -f desired_name.c desired_name
+
+ # Makefile continues below ...
+We recommend that the make clobber rule remove files that your entry
+creates as part of the compiling/building process.
You may also copy the compiled prog into a different file as part of compiling process.
+For example:
# Makefile continues above ...
+
+ all: desired_name
+
+ different_name: prog
+ rm -f $@
+ cp -f prog $@
+
+ clean:
+ rm -f prog.o
+
+ clobber: clean
+ rm -f desired_name
+
+ # Makefile continues below ...
+Jump to: top
+The IOCCC makes extensive use of markdown.
+For example, we submitting to the IOCCC, we have people
+to submit remarks about entry in markdown format. Every
+winning IOCCC entry uses a README.md markdown file
+as the basis for forming the index.html web page for that entry.
+All generated HTML pages on the Official IOCCC website
+start with some markdown content.
IMPORTANT: Please read the IOCCC markdown best practices guide +as it lists things you should not use in markdown files.
+See the markdown syntax guide. +See also CommonMark Spec.
+Jump to: top
+mkiocccentry tool?As the mkiocccentry toolkit is +crucial in the contest, both for submitters and the judges, if you find a bug +(or you think you find a bug) we would be grateful if you were to report it at +the mkiocccentry issues +page.
+Please see the +FAQ on “reporting bugs and other issues in the mkiocccentry repo” +in the mkiocccentry repo.
+Jump to: top
+Jump to: top
There are types of entries that are frequently submitted to the IOCCC. +While we do not wish to prevent people from sending +a submission to the IOCCC on a frequently submitted theme, +we do wish to provide a fair warning to those who do.
+IMPORTANT HINT: It is not fatal to send in those types of +entries, it is just HARDER to win with such a submission. A +submission on a frequently submitted theme will have to do something +in a really unique AND interesting way to even make it into the +final judging rounds. It will have to compete with previous IOCCC +winners based on the same theme.
+IMPORTANT HINT: If you really wish send in a submission on a +frequently submitted theme, be sure that it is obfuscated in several +new and novel ways.
+IMPORTANT HINT: Be sure to clearly explain near the beginning
+of your remarks.md file, see the
+FAQ on “remarks.md”,
+why you are submitting an entry based on a frequently
+submitted theme and how compares with previous IOCCC winners
+of the same theme.
While it is possible to win a new IOCCC with one of these +frequently submitted types of entries, level of the competition from +previous IOCCC entries make it more challenging to be successful.
+It is also important to note that the guidelines often +state something along the lines of:
+ We tend to dislike programs that: are similar to previous winning entries.
+FAIR WARNING: Be sure to clearly explain near the beginning
+of your remarks.md file, see the
+FAQ on “remarks.md”,
+why you are submitting an entry based on a frequently
+submitted theme and how compares with previous IOCCC winners
+of the same theme.
Jump to: top
+Jump to: top
@@ -3300,8 +3306,32 @@ Jump to: topJump to: top
+Jump to: top
+Jump to: top
Jump to: top
Jump to: top
Jump to: top
diff --git a/faq.md b/faq.md index 7518f0998..abcf2f9ca 100644 --- a/faq.md +++ b/faq.md @@ -408,168 +408,8 @@ for more up to date information on downloading, compiling, and related FAQ infor Jump to: [top](#)