1995 entries checked
Fixed formatting of README.md files. Some typo fixes. All entries work well. Added some try commands.
This commit is contained in:
1 parent
be60ae60ed
commit
fa2a763f6c
13 files changed
+455
-396
No files matched your search
+31
-25
@@ -9,51 +9,57 @@
|
||||
|
||||
make all
|
||||
|
||||
### To run
|
||||
## To run:
|
||||
|
||||
./garry.test.sh
|
||||
|
||||
## Judges' comments
|
||||
|
||||
In general, try:
|
||||
|
||||
./garry <input_file >output_file
|
||||
|
||||
While it may not have been the intention of the submitter, the
|
||||
judges noted that the C pre-processed version (with the #includes
|
||||
left intact) looked very much like a rat "dropping core". See
|
||||
garry.cpp and judge for yourself!
|
||||
## Try:
|
||||
|
||||
The author was kind enough to provide a less obfuscated version of
|
||||
the source called garry.fmt.c.
|
||||
./garry.test.sh
|
||||
|
||||
./garry < README.md
|
||||
|
||||
## Judges' comments
|
||||
|
||||
In general, try:
|
||||
|
||||
|
||||
While it may not have been the intention of the submitter, the
|
||||
judges noted that the C pre-processed version (with the `#include`s
|
||||
left intact) looked very much like a rat "dropping core". See
|
||||
`garry.cpp` and judge for yourself!
|
||||
|
||||
The author was kind enough to provide a less obfuscated version of
|
||||
the source called `garry.fmt.c`.
|
||||
|
||||
## Author's comments
|
||||
|
||||
This program is a file filter, designed to do environment-expansion and
|
||||
incorporating the ability to create binary from escaped data in the
|
||||
environment variables.
|
||||
This program is a file filter, designed to do environment-expansion and
|
||||
incorporating the ability to create binary from escaped data in the
|
||||
environment variables.
|
||||
|
||||
The calling syntax is pretty simple, just use it with stdio-redirection
|
||||
or inside pipelines, e.g.:
|
||||
The calling syntax is pretty simple, just use it with stdio-redirection
|
||||
or inside pipelines, e.g.:
|
||||
|
||||
progname <file_to_convert >converted_file
|
||||
|
||||
or
|
||||
or
|
||||
|
||||
cat all_my_files/* | progname | lp
|
||||
|
||||
The syntax of the conversion of the input file is as follows: To include
|
||||
the value of an environment variable in the output file, place the name
|
||||
of the variable between "$"-signs in the input, e.g.:
|
||||
The syntax of the conversion of the input file is as follows: To include
|
||||
the value of an environment variable in the output file, place the name
|
||||
of the variable between "$"-signs in the input, e.g.:
|
||||
|
||||
My Home-Directory is: $HOME$
|
||||
I'm using the path: $PATH$
|
||||
|
||||
Unknown Env-variables or misformed expressions are ignored and kept
|
||||
intact.
|
||||
Unknown Env-variables or malformed expressions are ignored and kept
|
||||
intact.
|
||||
|
||||
Additionally, the filter replaces escaped octal values in the
|
||||
environment variables by their binary representation, e.g.:
|
||||
Additionally, the filter replaces escaped octal values in the
|
||||
environment variables by their binary representation, e.g.:
|
||||
|
||||
$ TEST="\110\145\154\154\157"
|
||||
$ export TEST
|
||||
|
||||
Reference in new issue
Block a user