This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
tutorials:gopher [2012/01/28 16:17] – [Mole examples] chals | tutorials:gopher [2012/01/28 16:21] – [Mole examples] chals | ||
---|---|---|---|
Line 258: | Line 258: | ||
=== figlet.cgi === | === figlet.cgi === | ||
- | You can add some interactivity by using the itemtype 7. This itemtype is intended to make it possible to type some characters in a search field in your browser. However, you can use it to make it possible to pass arguments to your scripts. The following example will use some text you type in the search field and will pass it through the program figlet. | + | You can add some interactivity by using the itemtype 7. This itemtype is intended to make it possible to type some characters in a search field in your browser. However, you can use it to make it possible to pass arguments to your scripts. The following example will use the text you type in the search field and will pass it through the program figlet. |
<code bash> | <code bash> | ||
Line 273: | Line 273: | ||
When you access the script via gopher:// | When you access the script via gopher:// | ||
- | The i in the echo... line is important here. Indeed, the document is been accessed with an itemtype 7 (but the same applies for itemtype 1), so the document should be structured similarly to gophermaps. It's not a gophermap, though. That's why you need to explicitily state the line should be displayed as simple (or inline) text. | + | The i in the echo... line is important here. Indeed, the document is being accessed with an itemtype 7 (but the same applies for itemtype 1), so the document should be structured similarly to gophermaps. It's not a gophermap, though. That's why you need to explicitily state the line should be displayed as simple (or inline) text. |
==== Caveat ==== | ==== Caveat ==== |