From c416d9b692346706d4ca3da7577a3f12a308e35e Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Wed, 17 Jan 2024 05:40:46 -0800 Subject: [PATCH 1/2] Remove reference to jargon file in 2000/rince The bugs.md file is all that's needed; the information is already there in bugs.md and the purpose of having the 'STATUS: ...' lines in the bugs and (mis)features section of the README.md files was to not have that. Still having the reference to DISPLAY being unset being a problem seems like a good idea. --- 2000/rince/README.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/2000/rince/README.md b/2000/rince/README.md index 928e3fa05..c9c5ea925 100644 --- a/2000/rince/README.md +++ b/2000/rince/README.md @@ -25,13 +25,6 @@ For more detailed information see [2000 rince in bugs.md](/bugs.md#2000-rince). If `DISPLAY` is not set the program will very likely crash or do something different. -This is supposed to happen. As is written in the -[The Jargon File](http://catb.org/jargon/html/F/feature.html): - -``` -That's not a bug, that's a feature. -``` - ## Try: From 1e76d6be10ab32abd60f7a4e976ee29c5609a045 Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Wed, 17 Jan 2024 05:43:58 -0800 Subject: [PATCH 2/2] Remove grawlixes from 2012/vik/README.md We all know what is meant by 'brain$#@$' and there's no need to censor it especially when it links to the article on wiki that does not censor it (not that grawlixes are even censoring anything). This means there's no need to escape the '$' as they are not there now. --- 2012/vik/README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/2012/vik/README.md b/2012/vik/README.md index 2d4d06af6..e0b0b8713 100644 --- a/2012/vik/README.md +++ b/2012/vik/README.md @@ -111,9 +111,9 @@ additional chunks are copied into the resulting image. For some reason the chocolate image seems to have some special properties. Apart from being quite big and a little bit noisy, it appears that when embedded into another image and extracted, the bitmap data is also a valid -[brain\$#@\$](https://en.wikipedia.org/wiki/Brainfuck) program. It is of course +[brainfuck](https://en.wikipedia.org/wiki/Brainfuck) program. It is of course possible to get the bitmap data from the extracted image, and run it through any -of the previous winning brain\$#@\$ interpreters, but I thought it would be easier +of the previous winning brainfuck interpreters, but I thought it would be easier to include an interpreter in the program to avoid the hassle: ```sh @@ -122,7 +122,7 @@ to include an interpreter in the program to avoid the hassle: ``` It is of course also possible to embed a -[brain\$#@\$](https://en.wikipedia.org/wiki/Brainfuck) program as a text file +[brainfuck](https://en.wikipedia.org/wiki/Brainfuck) program as a text file (as explained above) and decode it, e.g.: ```sh @@ -172,7 +172,7 @@ program to crash. Since a lot of care was taken to keep the code simple, it turned out to be quite easy to extend functionality. I did include a small -[brain\$#@\$](https://en.wikipedia.org/wiki/Brainfuck) after I +[brainfuck](https://en.wikipedia.org/wiki/Brainfuck) after I realized that the chocolate image had some interesting properties. But there is more functionality I added that didn't fit within the size @@ -181,9 +181,9 @@ format source code based on a PNG image. So the format of the program is actually done by the program itself. And to be honest, the chocolate image did not have a -[brain\$#@\$](https://en.wikipedia.org/wiki/Brainfuck) program +[brainfuck](https://en.wikipedia.org/wiki/Brainfuck) program embedded to begin with. I added functionality to the program to embed a -brain\$#@\$ into a PNG image and used it to create the image provided with +brainfuck into a PNG image and used it to create the image provided with the entry. I also added a method to analyze PNG images, to print the size and format,