Attachment 13301 Details for Bug 30559 – Random extracts from halibut tutorial

Random extracts from halibut tutorial

sample.but (text/plain), 3.70 KB, created by Len Lawrence on 2022-06-17 19:31:58 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: Len Lawrence

Created: 2022-06-17 19:31:58 CEST

Size: 3.70 KB

patch

obsolete

>This is a line of text.
>This is another line of text.
>
>This line is separated from the previous one by a blank line.
>
>This \\ is a backslash, and these are \{braces\}.
>Here is some \e{emphasised
>text}.
>
>Here is some \e{emphasised text}.
>
>Possibly the most obvious piece of formatting you might want
>to use in a document is \e{emphasis}.
>
>This sentence contains some \c{code} and some \cw{weak code}.
>
>the Pentium's \cw{EAX} and \cw{EDX} registers
>
>the Unix command \c{man}
>
>the special formatting command \cq{\\.}.
>the special formatting command \q{\cw{\\.}}
>
>Here is some \q{text in quotes}.
>
>the Emacs command \c{M\-x\_psychoanalyze\-pinhead}
>
>This document was generated on \date{%Y-%m-%d %H:%M:%S}
>Try searching on \W{http://www.google.com/}{Google}
>Google is at \W{http://www.google.com/}\cw{www.google.com}
>
>This is likely to cost \u20AC{EUR\_}2500 at least.
>
>
>The typical behaviour of an antelope \#{do I mean
>gazelle?} is...
>
>This function is \#{very, \e{very}} important.
>
>\c #include <stdio.h>
>\c
>\c int main(int argc, char **argv) {
>\c     printf("hello, world\n");
>\c     return 0;
>\c }
>
>\c #include <stdio.h>
>\e iiiiiiiiiiiiiiiiii
>\c
>\c int main(int argc, char **argv) {
>\e bbb      bbb       bbbb
>\c     printf("hello, world\n");
>\c     return 0;
>\e     bbbbbb
>\c }
>
>\rule
>
>Here's a list:
>
>\b One.
>
>\b Two.
>
>\b Three.
>
>Here's a numbered list:
>
>\n One.
>
>\n{this-one} Two.
>
>\n Three.
>
>\n Now go back to step \k{this-one}.
>
>
>Here is a description list:
>
>\dt Pelican
>
>\dd This is a large bird with a big beak.
>
>\dt Panda
>
>\dd This isn't.
>
>
>Here's a list:
>
>\n One. This item is followed by a code paragraph:
>
>\lcont{
>
>\c code
>\c paragraph
>
>}
>
>\n Two. Now when I say \q{two}, I mean:
>
>\lcont{
>
>\n Two, part one.
>
>\n Two, part two.
>
>\n Two, part three.
>
>}
>
>\n Three.
>
>\rule
>
>In \q{Through the Looking Glass}, Lewis Carroll wrote:
>
>\quote{
>
>\q{The question is,} said Alice, \q{whether you \e{can} make
>words mean so many different things.}
>
>\q{The question is,} said Humpty Dumpty, \q{who is to be
>master - that's all.}
>
>}
>
>So now you know.
>
>
>\rule
>
>The three special paragraph types are:
>
>\C{foo} Using Foo
>
>\H{foo-intro} Introduction to Foo
>
>\H{foo-running} Running the Foo program
>
>\S{foo-inter} Running Foo interactively
>
>\S{foo-batch} Running Foo in batch mode
>
>\H{foo-trouble} Troubleshooting Foo
>
>\C{bar} Using Bar instead of Foo
>
>
>\title My First Manual
>
>    This defines the overall title of the entire document. This title is treated specially in some output formats (for example, it's used in a <TITLE> tag in the HTML output), so it needs a special paragraph type to point it out. 
>
>\copyright
>    This command indicates that the paragraph attached to it contains a copyright statement for the document. This text is displayed inline where it appears, exactly like a normal paragraph; but in some output formats it is given additional special treatment. For example, Windows Help files have a standard slot in which to store a copyright notice, so that other software can display it prominently. 
>
>\versionid
>    This command indicates that the paragraph contains a version identifier, such as those produced by CVS (of the form $Id: thingy.but,v 1.6 2004/01/01 16:47:48 simon Exp $). This text will be tucked away somewhere unobtrusive, so that anyone wanting to (for example) report errors to the document's author can pick out the version IDs and send them as part of the report, so that the author can tell at a glance which revision of the document is being discussed.
>
>Here's a (fairly short) paragraph which will be displayed.
>
>That was it.
>
>\# Here's a comment paragraph which will not be displayed, no
>matter how long it goes on. All I needed to indicate this was
>the single \# at the start of the paragraph; I don't need one
>on every line or anything like that.
>

This is a line of text.
This is another line of text.

This line is separated from the previous one by a blank line.

This \\ is a backslash, and these are \{braces\}.
Here is some \e{emphasised
text}.

Here is some \e{emphasised text}.

Possibly the most obvious piece of formatting you might want
to use in a document is \e{emphasis}.

This sentence contains some \c{code} and some \cw{weak code}.

the Pentium's \cw{EAX} and \cw{EDX} registers

the Unix command \c{man}

the special formatting command \cq{\\.}.
the special formatting command \q{\cw{\\.}}

Here is some \q{text in quotes}.

the Emacs command \c{M\-x\_psychoanalyze\-pinhead}

This document was generated on \date{%Y-%m-%d %H:%M:%S}
Try searching on \W{http://www.google.com/}{Google}
Google is at \W{http://www.google.com/}\cw{www.google.com}

This is likely to cost \u20AC{EUR\_}2500 at least.


The typical behaviour of an antelope \#{do I mean
gazelle?} is...

This function is \#{very, \e{very}} important.

\c #include <stdio.h>
\c
\c int main(int argc, char **argv) {
\c     printf("hello, world\n");
\c     return 0;
\c }

\c #include <stdio.h>
\e iiiiiiiiiiiiiiiiii
\c
\c int main(int argc, char **argv) {
\e bbb      bbb       bbbb
\c     printf("hello, world\n");
\c     return 0;
\e     bbbbbb
\c }

\rule

Here's a list:

\b One.

\b Two.

\b Three.

Here's a numbered list:

\n One.

\n{this-one} Two.

\n Three.

\n Now go back to step \k{this-one}.


Here is a description list:

\dt Pelican

\dd This is a large bird with a big beak.

\dt Panda

\dd This isn't.


Here's a list:

\n One. This item is followed by a code paragraph:

\lcont{

\c code
\c paragraph

}

\n Two. Now when I say \q{two}, I mean:

\lcont{

\n Two, part one.

\n Two, part two.

\n Two, part three.

}

\n Three.

\rule

In \q{Through the Looking Glass}, Lewis Carroll wrote:

\quote{

\q{The question is,} said Alice, \q{whether you \e{can} make
words mean so many different things.}

\q{The question is,} said Humpty Dumpty, \q{who is to be
master - that's all.}

}

So now you know.


\rule

The three special paragraph types are:

\C{foo} Using Foo

\H{foo-intro} Introduction to Foo

\H{foo-running} Running the Foo program

\S{foo-inter} Running Foo interactively

\S{foo-batch} Running Foo in batch mode

\H{foo-trouble} Troubleshooting Foo

\C{bar} Using Bar instead of Foo


\title My First Manual

    This defines the overall title of the entire document. This title is treated specially in some output formats (for example, it's used in a <TITLE> tag in the HTML output), so it needs a special paragraph type to point it out. 

\copyright
    This command indicates that the paragraph attached to it contains a copyright statement for the document. This text is displayed inline where it appears, exactly like a normal paragraph; but in some output formats it is given additional special treatment. For example, Windows Help files have a standard slot in which to store a copyright notice, so that other software can display it prominently. 

\versionid
    This command indicates that the paragraph contains a version identifier, such as those produced by CVS (of the form $Id: thingy.but,v 1.6 2004/01/01 16:47:48 simon Exp $). This text will be tucked away somewhere unobtrusive, so that anyone wanting to (for example) report errors to the document's author can pick out the version IDs and send them as part of the report, so that the author can tell at a glance which revision of the document is being discussed.

Here's a (fairly short) paragraph which will be displayed.

That was it.

\# Here's a comment paragraph which will not be displayed, no
matter how long it goes on. All I needed to indicate this was
the single \# at the start of the paragraph; I don't need one
on every line or anything like that.

Actions: View

Attachments on bug 30559: 13301