os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

DocBook police: open and close tags for <programlisting> should cuddle

Browse source 
up to the contents within.

Approved by:	nik
This commit is contained in:
Dima Dorfman 2001-04-09 00:33:58 +00:00
parent cb3edc9691
commit caa6994914
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9149
78 changed files with 1286 additions and 2506 deletions
Download patch file Download diff file Expand all files Collapse all files

26
en_US.ISO8859-1/articles/programming-tools/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v 1.12 2000/07/26 18:24:50 jim Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v 1.13 2000/08/22 20:03:31 marko Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -1069,8 +1069,7 @@ free(foo);
<para>Here's a very simple make file:</para>
<programlisting>foo: foo.c
cc -o foo foo.c
</programlisting>
cc -o foo foo.c</programlisting>
<para>It consists of two lines, a dependency line and a creation
line.</para>
@ -1114,8 +1113,7 @@ free(foo);
cc -o foo foo.c
install:
cp foo /home/me
</programlisting>
cp foo /home/me</programlisting>
<para>We can tell make which target we want to make by
typing:</para>
@ -1168,8 +1166,7 @@ install:
<programlisting>MASTER_SITES= ftp://freefall.cdrom.com/pub/FreeBSD/LOCAL_PORTS/
DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
.include &lt;bsd.port.mk&gt;
</programlisting>
.include &lt;bsd.port.mk&gt;</programlisting>
<para>Now, if we go to the directory for this port and type
<userinput>make</userinput>, the following happens:</para>
@ -1283,8 +1280,7 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
<filename>/usr/local/info</filename> directory to add an entry
for it. This involves adding a line like</para>
<programlisting> * Make: (make). The GNU Make utility.
</programlisting>
<programlisting> * Make: (make). The GNU Make utility.</programlisting>
<para>to the file. Once you have done this, you can type
<userinput>info</userinput> and then select
@ -1390,8 +1386,7 @@ main() {
int bazz(int anint) {
printf("You gave me %d\n", anint);
return anint;
}
</programlisting>
}</programlisting>
<para>This program sets <symbol>i</symbol> to be
<literal>5</literal> and passes it to a function
@ -1447,8 +1442,7 @@ main() {
i = 5;
printf("This is my program\n");
<lineannotation>&hellip</>
</programlisting>
<lineannotation>&hellip</></programlisting>
<para>but we left the <literal>i=5;</literal> line out. As we
didn't initialise <symbol>i</symbol>, it had whatever number
@ -2170,8 +2164,7 @@ in font-lock-auto-mode-list"
("\\.lsp$" . lisp-mode)
("\\.wiz$" . whizbang-mode)
("\\.scm$" . scheme-mode)
<lineannotation>&hellip;</>
</programlisting>
<lineannotation>&hellip;</></programlisting>
<para>This means that Emacs will automatically go into
<function>whizbang-mode</function> when you edit a file ending
@ -2184,8 +2177,7 @@ in font-lock-auto-mode-list"
<programlisting>;; Auto font lock mode
(defvar font-lock-auto-mode-list
(list 'c-mode 'c++-mode 'c++-c-mode 'emacs-lisp-mode 'whizbang-mode 'lisp-mode 'perl-mode 'scheme-mode)
"List of modes to always start in font-lock-mode")
</programlisting>
"List of modes to always start in font-lock-mode")</programlisting>
<para>This means that Emacs will always enable
<function>font-lock-mode</function> (ie syntax highlighting)