HybridDog/geany
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove all docbook related files and use reST to generate the documentation.

Browse Source 
Thanks to John Gabriele for his great work on converting from docbook to the reST format.


git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@1774 ea778897-0a13-0410-b9d1-a72fbfd435f5
This commit is contained in:
Enrico Tröger 2007-08-09 10:05:00 +00:00
parent 023a60cda5
commit 38b5dbe53a
45 changed files with 4936 additions and 7908 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,11 @@
2007-08-09 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de>
* doc/*, doc/html/*:
Remove all docbook related files and use reST to generate the
documentation. Thanks to John Gabriele for his great work on
converting from docbook to the reST format.
2007-08-07 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
* src/symbols.c, tagmanager/python.c:

38
doc/Makefile.am
View File

@ -1,31 +1,21 @@
man_MANS=geany.1
DOCDIR = $(DESTDIR)/$(datadir)/doc/@PACKAGE@
HTML_FILES = html/*.html
IMAGE_FILES = images/*.png
EXTRA_DIST = geany.css geany.xsl make_webable.sh geany.txt geany_gpl.docbook geany.1 \
scikeybinding.docbook geany.docbook $(srcdir)/$(HTML_FILES) $(srcdir)/$(IMAGE_FILES)
EXTRA_DIST = geany.html geany.css make_webable.sh geany.txt geany.1 \
$(srcdir)/$(IMAGE_FILES)
pdf:
SP_ENCODING=XML SP_CHARSET_FIXED=YES jw -b pdf $(srcdir)/geany.docbook
mv doc/geany.pdf geany-$(VERSION).pdf
pdf: geany.txt
rst2latex -stg --documentoptions="10pt,a4paper" --output-encoding=utf8 $(srcdir)/geany.txt >geany.tex
pdflatex geany.tex
rm -f geany.tex geany.aux geany.log geany.out
mv $(srcdir)/geany.pdf geany-$(VERSION).pdf
geany.txt:
jw -b txt $(srcdir)/geany.docbook
htmldoc: geany.docbook
if [ geany.docbook -nt "./html/index.html" ]; then \
$(mkinstalldirs) html; \
xmlto -m geany.xsl -o html/ xhtml $(srcdir)/geany.docbook; \
test -f html/geany.css || cp $(srcdir)/geany.css html/; \
fi
doc: geany.txt htmldoc
doc: geany.txt
rst2html -stg --stylesheet=geany.css $(srcdir)/geany.txt >geany.html
doc-clean:
rm -rf html/*.html
rm -f html/geany.css
rm -f geany.html
rm -f geany.1
rm -f geany.txt
rm -f *.pdf
uninstall-local:
@ -33,19 +23,13 @@ uninstall-local:
install-data-local:
$(mkinstalldirs) $(DOCDIR)/html/images
for file in `ls $(srcdir)/$(HTML_FILES)`; do \
if [ -f $$file ]; then \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(DOCDIR)/html/$$basefile; \
fi \
done
for file in `ls $(srcdir)/$(IMAGE_FILES)`; do \
if [ -f $$file ]; then \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(DOCDIR)/html/images/$$basefile; \
fi \
done
$(INSTALL_DATA) $(srcdir)/geany.css $(DOCDIR)/html/geany.css
$(INSTALL_DATA) $(srcdir)/geany.html $(DOCDIR)/html/index.html
$(INSTALL_DATA) $(srcdir)/geany.txt $(DOCDIR)/manual.txt
$(INSTALL_DATA) $(top_srcdir)/README $(DOCDIR)
$(INSTALL_DATA) $(top_srcdir)/ChangeLog $(DOCDIR)

145
doc/geany.css
View File

@ -1,97 +1,108 @@
body address
{
line-height: 1.3;
margin: .6em 0;
/*
:Author: Enrico Troeger
:Contact: enrico(dot)troeger(at)uvena(dot)de
:Copyright: This stylesheet has been placed in the public domain.
Stylesheet for Geany's documentation based on a version of John Gabriele.
*/
/*@import url(html4css1.css);*/
body {
background-color: #f2f2f2;
color: #404040;
margin-left: 0.4em;
width: 60em;
font-size: 90%;
}
body blockquote
{
margin-top: .75em;
line-height: 1.5;
margin-bottom: .75em;
a {
color: #990000;
}
html body
{
margin: 1em 2% 1em 2%;
line-height: 1.2;
background-color: #ffffff;
a:visited {
color: #7E558E;
}
body pre
{
margin: .75em 0;
line-height: 1.3;
color: #4f3f3f;
font-weight: bold;
a:hover {
text-decoration: none;
}
body div
{
margin: 0;
h1 {
border-top: 1px dotted;
margin-top: 2em;
}
dl
{
margin: .4em 0;
line-height: 1.2;
h1, h2, h3 {
font-family: sans-serif;
color: #5D0606;
}
.legalnotice
{
font-size: small;
h1.title {
text-align: left }
h2 {
margin-top: 30px;
}
h1,h2,h3,h4,h5,h6,
div.example p b,
.question,
div.table p b,
div.procedure p b
{
color: #990000;
h2.subtitle {
text-align: left }
h3 {
padding-left: 3px;
}
.option
{
color: #0000ca;
font-weight: bold;
blockquote, pre {
border: 1px solid;
padding: 0.4em;
}
.parameter
{
color: #007a00;
font-weight: bold;
blockquote {
font-family: sans-serif;
background-color: #DBEDD5;
border: 1px dotted;
border-left: 4px solid;
border-color: #9FD98C;
}
a
{
color: #000000;
pre {
background-color: #ECDFCE;
border: 1px dotted;
border-left: 4px solid;
border-color: #D9BE9A;
}
a:hover
{
color: #3c3c3c;
border-bottom: 1px solid #dc0000;
tt, pre, code {
color: #6D4212;
}
hr
{
background-color: #9c9c9c;
border-style: none;
height: 1px;
table {
border: 1px solid #D9BE9A;
}
li
{
list-style-type: square;
th {
background-color: #ECDFCE;
border: 1px dotted #D9BE9A;
}
.programlisting, .screen
{
background-color: #F8F9FD;
border-color: #907777;
border-width: 1px;
border-style: solid;
padding: 0.5em;
td {
border: 1px dotted #D9BE9A;
}
.docinfo-name {
color: #5D0606;
}
p.admonition-title {
color: #990000;
font-weight: bold;
}
div.note {
margin: 1em 3em;
padding: 0em;
}
dt {
font-style: italic;
}

2917
doc/geany.docbook
View File

File diff suppressed because it is too large Load Diff

2862
doc/geany.html Normal file
View File

File diff suppressed because it is too large Load Diff

4103
doc/geany.txt
View File

File diff suppressed because it is too large Load Diff

14
doc/geany.xsl
View File

@ -1,14 +0,0 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version='1.0'
xmlns="http://www.w3.org/TR/xhtml1/transitional"
exclude-result-prefixes="#default">
<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl"/>
<!-- Use stylesheet -->
<xsl:param name="html.stylesheet" select="'geany.css'"/>
<xsl:param name="chunker.output.encoding" select="'UTF-8'"/>
</xsl:stylesheet>

417
doc/geany_gpl.docbook
View File

@ -1,417 +0,0 @@
<appendixinfo>
<title>GNU General Public License</title>
<pubdate>Version 2, June 1991</pubdate>
<copyright>
<year>1989, 1991</year>
<holder>Free Software Foundation, Inc.</holder>
</copyright>
<legalnotice>
<para>
<address>Free Software Foundation, Inc.
<street>59 Temple Place, Suite 330</street>,
<city>Boston</city>,
<state>MA</state>
<postcode>02111-1307</postcode>
<country>USA</country>
</address>.
</para>
<para> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
</para>
</legalnotice>
<releaseinfo> Version 2, June 1991</releaseinfo>
</appendixinfo>
<title>GNU General Public License</title>
<sect1>
<title>Preamble</title>
<para> The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public License is
intended to guarantee your freedom to share and change
free software - to make sure the software is free for all its users.
This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit
to using it. (Some other Free Software Foundation software is covered
by the GNU Library General Public License instead.) You can apply it
to your programs, too.
</para>
<para> When we speak of free software, we are referring to freedom, not price.
Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free software (and charge for this
service if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
</para>
<para> To protect your rights, we need to make restrictions that forbid anyone
to deny you these rights or to ask you to surrender the rights. These
restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it.
</para>
<para> For example, if you distribute copies of such a program, whether gratis or
for a fee, you must give the recipients all the rights that you have. You
must make sure that they, too, receive or can get the source code. And you
must show them these terms so they know their rights.
</para>
<para> We protect your rights with two steps:
<orderedlist>
<listitem>
<para> copyright the software, and
</para>
</listitem>
<listitem>
<para> offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
</para>
</listitem>
</orderedlist>
</para>
<para> Also, for each author's protection and ours, we want to make certain that
everyone understands that there is no warranty for this free software. If
the software is modified by someone else and passed on, we want its
recipients to know that what they have is not the original, so that any
problems introduced by others will not reflect on the original authors'
reputations.
</para>
<para> Finally, any free program is threatened constantly by software patents.
We wish to avoid the danger that redistributors of a free program will
individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be
licensed for everyone's free use or not licensed at all.
</para>
<para> The precise terms and conditions for copying, distribution and modification
follow.
</para>
</sect1>
<sect1>
<title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title>
<sect2>
<title>Section 0</title>
<para> This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms
of this General Public License. The "Program", below, refers to any such
program or work, and a
<quote>work based on the Program
</quote> means either
the Program or any derivative work under copyright law: that is to say, a
work containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter, translation
is included without limitation in the term
<quote>modification
</quote>.) Each licensee is addressed as <quote>you</quote>.
</para>
<para> Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does.
</para>
</sect2>
<sect2 id="sect1">
<title>Section 1</title>
<para> You may copy and distribute verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License
along with the Program.
</para>
<para> You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.
</para>
</sect2>
<sect2 id="sect2">
<title>Section 2</title>
<para> You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifications
or work under the terms of
<link linkend="sect1">Section 1</link> above, provided
that you also meet all of these conditions:
<orderedlist>
<listitem>
<para> You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.
</para>
</listitem>
<listitem>
<para> You must cause any work that you distribute or publish, that in whole or
in part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this License.
</para>
</listitem>
<listitem>
<para> If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying
that you provide a warranty) and that users may redistribute the program
under these conditions, and telling the user how to view a copy of this
License.
<note>
<title>Exception:
</title>
<para> If the Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print an
announcement.)
</para>
</note>
</para>
</listitem>
</orderedlist>
</para>
<para> These requirements apply to the modified work as a whole. If identifiable sections
of that work are not derived from the Program, and can be reasonably considered
independent and separate works in themselves, then this License, and its terms,
do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.
</para>
<para> Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to control
the distribution of derivative or collective works based on the Program.
</para>
<para> In addition, mere aggregation of another work not based on the Program with the Program
(or with a work based on the Program) on a volume of a storage or distribution medium
does not bring the other work under the scope of this License.
</para>
</sect2>
<sect2>
<title>Section 3
</title>
<para> You may copy and distribute the Program (or a work based on it, under
<link linkend="sect2">Section 2</link> in object code or executable form under the terms of
<link linkend="sect1">Sections 1</link> and
<link linkend="sect2">2</link> above provided that you also do one of the following:
<orderedlist>
<listitem>
<para> Accompany it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
</para>
</listitem>
<listitem>
<para> Accompany it with a written offer, valid for at least three years, to give any
third party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code,
to be distributed under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
</para>
</listitem>
<listitem>
<para> Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommercial
distribution and only if you received the program in object code or executable form
with such an offer, in accord with Subsection b above.)
</para>
</listitem>
</orderedlist>
</para>
<para> The source code for a work means the preferred form of the work for making modifications
to it. For an executable work, complete source code means all the source code for all modules
it contains, plus any associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system
on which the executable runs, unless that component itself accompanies the executable.
</para>
<para> If distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the same place
counts as distribution of the source code, even though third parties are not compelled to
copy the source along with the object code.
</para>
</sect2>
<sect2>
<title>Section 4
</title>
<para> You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the
Program is void, and will automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this License will not have their
licenses terminated so long as such parties remain in full compliance.
</para>
</sect2>
<sect2>
<title>Section 5
</title>
<para> You are not required to accept this License, since you have not signed it. However, nothing
else grants you permission to modify or distribute the Program or its derivative works.
These actions are prohibited by law if you do not accept this License. Therefore, by modifying
or distributing the Program (or any work based on the Program), you indicate your acceptance
of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.
</para>
</sect2>
<sect2>
<title>Section 6
</title>
<para> Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify
the Program subject to these terms and conditions. You may not impose any further restrictions
on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
compliance by third parties to this License.
</para>
</sect2>
<sect2>
<title>Section 7
</title>
<para> If, as a consequence of a court judgment or allegation of patent infringement or for any other
reason (not limited to patent issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot distribute so as to satisfy simultaneously
your obligations under this License and any other pertinent obligations, then as a consequence
you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or
indirectly through you, then the only way you could satisfy both it and this License would be
to refrain entirely from distribution of the Program.
</para>
<para> If any portion of this section is held invalid or unenforceable under any particular circumstance,
the balance of the section is intended to apply and the section as a whole is intended to apply
in other circumstances.
</para>
<para> It is not the purpose of this section to induce you to infringe any patents or other property
right claims or to contest validity of any such claims; this section has the sole purpose of
protecting the integrity of the free software distribution system, which is implemented by public
license practices. Many people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that system; it is up
to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
</para>
<para> This section is intended to make thoroughly clear what is believed to be a consequence of the
rest of this License.
</para>
</sect2>
<sect2>
<title>Section 8
</title>
<para> If the distribution and/or use of the Program is restricted in certain countries either by patents
or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such case, this License
incorporates the limitation as if written in the body of this License.
</para>
</sect2>
<sect2>
<title>Section 9
</title>
<para> The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ
in detail to address new problems or concerns.
</para>
<para> Each version is given a distinguishing version number. If the Program specifies a version number of
this License which applies to it and "any later version", you have the option of following the terms
and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.
</para>
</sect2>
<sect2>
<title>Section 10
</title>
<para> If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted
by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all
derivatives of our free software and of promoting the sharing and reuse of software generally.
</para>
</sect2>
<sect2>
<title>Section 11 NO WARRANTY
</title>
<para> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
</para>
</sect2>
<sect2>
<title>Section 12
</title>
<para> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
</para>
<para>END OF TERMS AND CONDITIONS
</para>
</sect2>
</sect1>
<sect1>
<title>How to Apply These Terms to Your New Programs
</title>
<para>
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
</para>
<para>
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
</para>
<para>
&lt;one line to give the program's name and a brief idea of what it does.&gt;
Copyright (C) &lt;year&gt; &lt;name of author&gt;
</para>
<para>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
</para>
<para>
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
</para>
<para>
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
</para>
<para>
Also add information on how to contact you by electronic and paper mail.
</para>
<para>
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
</para>
<para>
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
</para>
<para>
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
</para>
<para>
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
</para>
<para>
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
</para>
<para>
&lt;signature of Ty Coon&gt;, 1 April 1989
Ty Coon, President of Vice
</para>
<para>
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
</para>
</sect1>

15
doc/html/apa.html
View File

@ -1,15 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix A. Contributing to this document</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="ch04s03.html" title="Templates"><link rel="next" href="apb.html" title="Appendix B. Scintilla keyboard commands"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix A. Contributing to this document</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apb.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="contrib"></a>Appendix A. Contributing to this document</h2></div></div></div><p>This document is written in Docbook XML. The source file for it is located in the
subdirectory "doc" of the source directory of <span class="application">Geany</span>.
If you intend on making changes, you should grab the source right from SVN to make
sure you have got the newest version. After editing that file, to build the docs and
see how your changes look, run "make doc" in the subdirectory "doc" of the source
directory of <span class="application">Geany</span> to build HTML pages and a text file.
Your updated HTML docs will end up in the <code class="filename">./html</code> directory.
To generate a PDF file, use the command "make pdf" which should generate a
file called <code class="filename">geany-0.11.pdf</code>.
</p><p>After you are happy with your changes, create a patch:
</p><pre class="screen">
<code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">svn diff geany.docbook &gt; whatever.patch</strong></span></code></strong></pre><p>
and then submit that file to the mailing list for review.
</p><p>Note, you will need the docbook-xml and xmlto software packages installed to build the docs.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s03.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="apb.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Templates </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix B. Scintilla keyboard commands</td></tr></table></div></body></html>

25
doc/html/apb.html
View File

@ -1,25 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix B. Scintilla keyboard commands</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="apa.html" title="Appendix A. Contributing to this document"><link rel="next" href="apc.html" title="Appendix C. Compile time options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix B. Scintilla keyboard commands</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apa.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apc.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="scikeybinding"></a>Scintilla keyboard commands</h1></div><div><p class="copyright">Copyright © 1998, 2006 Neil Hodgson &lt;neilh@scintilla.org&gt;</p></div><div><div class="legalnotice"><a name="id2815404"></a><p>
This appendix is distributed under the terms of the License for
Scintilla and SciTE.
A copy of this license can be found in the file scintilla/License.txt
included with the source code of this
program and in the
appendix of this document.
See <a href="ape.html" title="Appendix E. License for Scintilla and SciTE">Appendix E, <i>License for Scintilla and SciTE</i></a>.
</p></div></div><div><p class="pubdate">20 June 2006</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="apb.html#id2815430">
Keyboard commands
</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815430"></a>
Keyboard commands
</h2></div></div></div><p>
Keyboard commands for Scintilla mostly follow common Windows and GTK+ conventions.
All move keys (arrows, page up/down, home and end)
allows to extend or reduce the stream selection when holding the Shift key,
and the rectangular selection when holding the Shift and Alt keys.
Some keys may not be available with some national keyboards or because
they are taken by the system such as by a window manager on GTK+.
Keyboard equivalents of menu commands are listed in the menus.
Some less common commands with no menu equivalent are:
</p><p>
</p><div class="table"><a name="id2816064"></a><p class="title"><b>Table B.1. Scintilla keyboard commands</b></p><div class="table-contents"><table summary="Scintilla keyboard commands" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col></colgroup><thead><tr><th>Action</th><th>Shortcut key</th></tr></thead><tbody><tr><td>Magnify text size.</td><td>Ctrl+Keypad+</td></tr><tr><td>Reduce text size.</td><td>Ctrl+Keypad-</td></tr><tr><td>Restore text size to normal.</td><td>Ctrl+Keypad/</td></tr><tr><td>Indent block.</td><td>Tab</td></tr><tr><td>Dedent block.</td><td>Shift+Tab</td></tr><tr><td>Delete to start of word.</td><td>Ctrl+BackSpace</td></tr><tr><td>Delete to end of word.</td><td>Ctrl+Delete</td></tr><tr><td>Delete to start of line.</td><td>Ctrl+Shift+BackSpace</td></tr><tr><td>Delete to end of line.</td><td>Ctrl+Shift+Delete</td></tr><tr><td>Go to start of document.</td><td>Ctrl+Home</td></tr><tr><td>Extend selection to start of document.</td><td>Ctrl+Shift+Home</td></tr><tr><td>Go to start of display line.</td><td>Alt+Home</td></tr><tr><td>Extend selection to start of display line.</td><td>Alt+Shift+Home</td></tr><tr><td>Go to end of document.</td><td>Ctrl+End</td></tr><tr><td>Extend selection to end of document.</td><td>Ctrl+Shift+End</td></tr><tr><td>Go to end of display line.</td><td>Alt+End</td></tr><tr><td>Extend selection to end of display line.</td><td>Alt+Shift+End</td></tr><tr><td>Scroll up.</td><td>Ctrl+Up</td></tr><tr><td>Scroll down.</td><td>Ctrl+Down</td></tr><tr><td>Line cut.</td><td>Ctrl+L</td></tr><tr><td>Line copy.</td><td>Ctrl+Shift+T</td></tr><tr><td>Line delete.</td><td>Ctrl+Shift+L</td></tr><tr><td>Line transpose with previous.</td><td>Ctrl+T</td></tr><tr><td>Selection duplicate.</td><td>Ctrl+D</td></tr><tr><td>Previous paragraph. Shift extends selection.</td><td>Ctrl+[</td></tr><tr><td>Next paragraph. Shift extends selection.</td><td>Ctrl+]</td></tr><tr><td>Previous word. Shift extends selection.</td><td>Ctrl+Left</td></tr><tr><td>Next word. Shift extends selection.</td><td>Ctrl+Right</td></tr><tr><td>Previous word part. Shift extends selection</td><td>Ctrl+/</td></tr><tr><td>Next word part. Shift extends selection.</td><td>Ctrl+\</td></tr></tbody></table></div></div><p><br class="table-break">
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apa.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="apc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. Contributing to this document </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix C. Compile time options</td></tr></table></div></body></html>

172
doc/html/apbs02.html
View File

@ -1,172 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="apb.html" title="Appendix B. GNU General Public License"><link rel="prev" href="apb.html" title="Appendix B. GNU General Public License"><link rel="next" href="apbs03.html" title="How to Apply These Terms to Your New Programs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apb.html">Prev</a> </td><th width="60%" align="center">Appendix B. GNU General Public License</th><td width="20%" align="right"> <a accesskey="n" href="apbs03.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2799855"></a>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2799861"></a>Section 0</h3></div></div></div><p> This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms
of this General Public License. The "Program", below, refers to any such
program or work, and a
“<span class="quote">work based on the Program
</span>” means either
the Program or any derivative work under copyright law: that is to say, a
work containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter, translation
is included without limitation in the term
“<span class="quote">modification
</span>”.) Each licensee is addressed as “<span class="quote">you</span>”.
</p><p> Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sect1"></a>Section 1</h3></div></div></div><p> You may copy and distribute verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License
along with the Program.
</p><p> You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sect2"></a>Section 2</h3></div></div></div><p> You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifications
or work under the terms of
<a href="apbs02.html#sect1" title="Section 1">Section 1</a> above, provided
that you also meet all of these conditions:
</p><div class="orderedlist"><ol type="1"><li><p> You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.
</p></li><li><p> You must cause any work that you distribute or publish, that in whole or
in part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this License.
</p></li><li><p> If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying
that you provide a warranty) and that users may redistribute the program
under these conditions, and telling the user how to view a copy of this
License.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Exception:
</h3><p> If the Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print an
announcement.)
</p></div><p>
</p></li></ol></div><p>
</p><p> These requirements apply to the modified work as a whole. If identifiable sections
of that work are not derived from the Program, and can be reasonably considered
independent and separate works in themselves, then this License, and its terms,
do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.
</p><p> Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to control
the distribution of derivative or collective works based on the Program.
</p><p> In addition, mere aggregation of another work not based on the Program with the Program
(or with a work based on the Program) on a volume of a storage or distribution medium
does not bring the other work under the scope of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800047"></a>Section 3
</h3></div></div></div><p> You may copy and distribute the Program (or a work based on it, under
<a href="apbs02.html#sect2" title="Section 2">Section 2</a> in object code or executable form under the terms of
<a href="apbs02.html#sect1" title="Section 1">Sections 1</a> and
<a href="apbs02.html#sect2" title="Section 2">2</a> above provided that you also do one of the following:
</p><div class="orderedlist"><ol type="1"><li><p> Accompany it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
</p></li><li><p> Accompany it with a written offer, valid for at least three years, to give any
third party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code,
to be distributed under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
</p></li><li><p> Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommercial
distribution and only if you received the program in object code or executable form
with such an offer, in accord with Subsection b above.)
</p></li></ol></div><p>
</p><p> The source code for a work means the preferred form of the work for making modifications
to it. For an executable work, complete source code means all the source code for all modules
it contains, plus any associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system
on which the executable runs, unless that component itself accompanies the executable.
</p><p> If distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the same place
counts as distribution of the source code, even though third parties are not compelled to
copy the source along with the object code.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800147"></a>Section 4
</h3></div></div></div><p> You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the
Program is void, and will automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this License will not have their
licenses terminated so long as such parties remain in full compliance.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800165"></a>Section 5
</h3></div></div></div><p> You are not required to accept this License, since you have not signed it. However, nothing
else grants you permission to modify or distribute the Program or its derivative works.
These actions are prohibited by law if you do not accept this License. Therefore, by modifying
or distributing the Program (or any work based on the Program), you indicate your acceptance
of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800184"></a>Section 6
</h3></div></div></div><p> Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify
the Program subject to these terms and conditions. You may not impose any further restrictions
on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
compliance by third parties to this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800201"></a>Section 7
</h3></div></div></div><p> If, as a consequence of a court judgment or allegation of patent infringement or for any other
reason (not limited to patent issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot distribute so as to satisfy simultaneously
your obligations under this License and any other pertinent obligations, then as a consequence
you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or
indirectly through you, then the only way you could satisfy both it and this License would be
to refrain entirely from distribution of the Program.
</p><p> If any portion of this section is held invalid or unenforceable under any particular circumstance,
the balance of the section is intended to apply and the section as a whole is intended to apply
in other circumstances.
</p><p> It is not the purpose of this section to induce you to infringe any patents or other property
right claims or to contest validity of any such claims; this section has the sole purpose of
protecting the integrity of the free software distribution system, which is implemented by public
license practices. Many people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that system; it is up
to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
</p><p> This section is intended to make thoroughly clear what is believed to be a consequence of the
rest of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800251"></a>Section 8
</h3></div></div></div><p> If the distribution and/or use of the Program is restricted in certain countries either by patents
or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such case, this License
incorporates the limitation as if written in the body of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800269"></a>Section 9
</h3></div></div></div><p> The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ
in detail to address new problems or concerns.
</p><p> Each version is given a distinguishing version number. If the Program specifies a version number of
this License which applies to it and "any later version", you have the option of following the terms
and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800302"></a>Section 10
</h3></div></div></div><p> If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted
by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all
derivatives of our free software and of promoting the sharing and reuse of software generally.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800320"></a>Section 11 NO WARRANTY
</h3></div></div></div><p> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800341"></a>Section 12
</h3></div></div></div><p> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
</p><p>END OF TERMS AND CONDITIONS
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apb.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apb.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apbs03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix B. GNU General Public License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> How to Apply These Terms to Your New Programs
</td></tr></table></div></body></html>

60
doc/html/apbs03.html
View File

@ -1,60 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>How to Apply These Terms to Your New Programs</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="apb.html" title="Appendix B. GNU General Public License"><link rel="prev" href="apbs02.html" title="TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION"><link rel="next" href="apc.html" title="Appendix C. License for Scintilla and SciTE"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">How to Apply These Terms to Your New Programs
</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apbs02.html">Prev</a> </td><th width="60%" align="center">Appendix B. GNU General Public License</th><td width="20%" align="right"> <a accesskey="n" href="apc.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800366"></a>How to Apply These Terms to Your New Programs
</h2></div></div></div><p>
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
</p><p>
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
</p><p>
&lt;one line to give the program's name and a brief idea of what it does.&gt;
Copyright (C) &lt;year&gt; &lt;name of author&gt;
</p><p>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
</p><p>
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
</p><p>
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
</p><p>
Also add information on how to contact you by electronic and paper mail.
</p><p>
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
</p><p>
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
</p><p>
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
</p><p>
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
</p><p>
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
</p><p>
&lt;signature of Ty Coon&gt;, 1 April 1989
Ty Coon, President of Vice
</p><p>
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apbs02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apb.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix C. License for Scintilla and SciTE</td></tr></table></div></body></html>

27
doc/html/apc.html
View File

@ -1,27 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix C. Compile time options</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="apb.html" title="Appendix B. Scintilla keyboard commands"><link rel="next" href="apd.html" title="Appendix D. GNU General Public License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix C. Compile time options</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apb.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apd.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="cto"></a>Appendix C. Compile time options</h2></div></div></div><p>
There are some options which can only be changed at compile time. To change these
options, edit the file <code class="filename">src/geany.h</code>.
Look for a block of lines starting with “<span class="quote">#define GEANY_*</span>”.
Any definitions which are not listed here should not be changed.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Most users should not need to change these options.</p></div><p>
</p><div class="table"><a name="id2815782"></a><p class="title"><b>Table C.1. Compile time options</b></p><div class="table-contents"><table summary="Compile time options" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Option</th><th>Description</th><th>Default</th></tr></thead><tbody><tr><td>GEANY_WORDCHARS</td><td>
These characters define word boundaries when
making selections and searching using word matching
options.
</td><td>(look at sourcecode)</td></tr><tr><td>GEANY_MAX_AUTOCOMPLETE_WORDS</td><td>How many auto completion suggestions should
<span class="application">Geany</span> provide.
</td><td>30</td></tr><tr><td>GEANY_MAX_AUTOCOMPLETE_HEIGHT</td><td>How many suggestions should be visible in the auto completion list.</td><td>10</td></tr><tr><td>GEANY_PROJECT_EXT</td><td>The default filename extension for Geany project files.
It is used when creating new projects and as filter mask
for the project open dialog.</td><td>geany</td></tr><tr><td>GEANY_STRING_UNTITLED</td><td>A string used as the default name for new files. Be aware
that the string can be translated,
so change it only if you know what you are doing.</td><td>untitled</td></tr><tr><td>GEANY_CHECK_FILE_DELAY</td><td>Time in seconds between checking a file for external
changes.</td><td>30</td></tr><tr><td>GEANY_WINDOW_MINIMAL_WIDTH</td><td>The minimal width of the main window.</td><td>620</td></tr><tr><td>GEANY_WINDOW_MINIMAL_HEIGHT</td><td>The minimal height of the main window.</td><td>440</td></tr><tr><td>GEANY_WINDOW_DEFAULT_WIDTH</td><td>The default width of the main window at the first start.</td><td>900</td></tr><tr><td>GEANY_WINDOW_DEFAULT_HEIGHT</td><td>The default height of the main window at the first start.</td><td>600</td></tr><tr><td colspan="3" align="left">Default values</td></tr><tr><td>GEANY_DEFAULT_TOOLS_MAKE</td><td>The make tool. This can also include a path.</td><td>"make"</td></tr><tr><td>GEANY_DEFAULT_TOOLS_TERMINAL</td><td>A terminal emulator. It has to accept the command line
option "-e". This can also include a path.</td><td>"xterm"</td></tr><tr><td>GEANY_DEFAULT_TOOLS_BROWSER</td><td>A web browser. This can also include a path.</td><td>"mozilla"</td></tr><tr><td>GEANY_DEFAULT_TOOLS_PRINTCMD</td><td>A printing tool. It should be able to accept and process
plain text files. This can also include a path.</td><td>"lpr"</td></tr><tr><td>GEANY_DEFAULT_TOOLS_GREP</td><td>A grep tool. It should be compatible with GNU grep.
This can also include a path.</td><td>"grep"</td></tr><tr><td>GEANY_DEFAULT_MRU_LENGHTH</td><td>The length of the "Recent files" list.</td><td>"10"</td></tr><tr><td>GEANY_DEFAULT_FONT_SYMBOL_LIST</td><td>The font used in sidebar to show symbols and open files.
</td><td>"Sans 9"</td></tr><tr><td>GEANY_DEFAULT_FONT_MSG_WINDOW</td><td>The font used in the messages window.</td><td>"Sans 9"</td></tr><tr><td>GEANY_DEFAULT_FONT_EDITOR</td><td>The font used in the editor window.</td><td>"Monospace 10"</td></tr><tr><td colspan="3" align="left">Windows specific</td></tr><tr><td>GEANY_USE_WIN32_DIALOG</td><td>Set this to 1 if you want to use the default Windows
file open dialog instead GTK's file open dialog. The default
Windows file open dialog is missing some nice features like
choosing a filetype or an encoding. Do not touch this
setting when building on a non-Win32 system.</td><td>0</td></tr></tbody></table></div></div><p><br class="table-break">
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apb.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="apd.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix B. Scintilla keyboard commands </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix D. GNU General Public License</td></tr></table></div></body></html>

172
doc/html/apcs02.html
View File

@ -1,172 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="apc.html" title="Appendix C. GNU General Public License"><link rel="prev" href="apc.html" title="Appendix C. GNU General Public License"><link rel="next" href="apcs03.html" title="How to Apply These Terms to Your New Programs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apc.html">Prev</a> </td><th width="60%" align="center">Appendix C. GNU General Public License</th><td width="20%" align="right"> <a accesskey="n" href="apcs03.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2817538"></a>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817544"></a>Section 0</h3></div></div></div><p> This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms
of this General Public License. The "Program", below, refers to any such
program or work, and a
“<span class="quote">work based on the Program
</span>” means either
the Program or any derivative work under copyright law: that is to say, a
work containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter, translation
is included without limitation in the term
“<span class="quote">modification
</span>”.) Each licensee is addressed as “<span class="quote">you</span>”.
</p><p> Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sect1"></a>Section 1</h3></div></div></div><p> You may copy and distribute verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License
along with the Program.
</p><p> You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sect2"></a>Section 2</h3></div></div></div><p> You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifications
or work under the terms of
<a href="apcs02.html#sect1" title="Section 1">Section 1</a> above, provided
that you also meet all of these conditions:
</p><div class="orderedlist"><ol type="1"><li><p> You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.
</p></li><li><p> You must cause any work that you distribute or publish, that in whole or
in part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this License.
</p></li><li><p> If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying
that you provide a warranty) and that users may redistribute the program
under these conditions, and telling the user how to view a copy of this
License.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Exception:
</h3><p> If the Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print an
announcement.)
</p></div><p>
</p></li></ol></div><p>
</p><p> These requirements apply to the modified work as a whole. If identifiable sections
of that work are not derived from the Program, and can be reasonably considered
independent and separate works in themselves, then this License, and its terms,
do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.
</p><p> Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to control
the distribution of derivative or collective works based on the Program.
</p><p> In addition, mere aggregation of another work not based on the Program with the Program
(or with a work based on the Program) on a volume of a storage or distribution medium
does not bring the other work under the scope of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817730"></a>Section 3
</h3></div></div></div><p> You may copy and distribute the Program (or a work based on it, under
<a href="apcs02.html#sect2" title="Section 2">Section 2</a> in object code or executable form under the terms of
<a href="apcs02.html#sect1" title="Section 1">Sections 1</a> and
<a href="apcs02.html#sect2" title="Section 2">2</a> above provided that you also do one of the following:
</p><div class="orderedlist"><ol type="1"><li><p> Accompany it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
</p></li><li><p> Accompany it with a written offer, valid for at least three years, to give any
third party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code,
to be distributed under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
</p></li><li><p> Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommercial
distribution and only if you received the program in object code or executable form
with such an offer, in accord with Subsection b above.)
</p></li></ol></div><p>
</p><p> The source code for a work means the preferred form of the work for making modifications
to it. For an executable work, complete source code means all the source code for all modules
it contains, plus any associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system
on which the executable runs, unless that component itself accompanies the executable.
</p><p> If distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the same place
counts as distribution of the source code, even though third parties are not compelled to
copy the source along with the object code.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817830"></a>Section 4
</h3></div></div></div><p> You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the
Program is void, and will automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this License will not have their
licenses terminated so long as such parties remain in full compliance.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817848"></a>Section 5
</h3></div></div></div><p> You are not required to accept this License, since you have not signed it. However, nothing
else grants you permission to modify or distribute the Program or its derivative works.
These actions are prohibited by law if you do not accept this License. Therefore, by modifying
or distributing the Program (or any work based on the Program), you indicate your acceptance
of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817866"></a>Section 6
</h3></div></div></div><p> Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify
the Program subject to these terms and conditions. You may not impose any further restrictions
on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
compliance by third parties to this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817884"></a>Section 7
</h3></div></div></div><p> If, as a consequence of a court judgment or allegation of patent infringement or for any other
reason (not limited to patent issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot distribute so as to satisfy simultaneously
your obligations under this License and any other pertinent obligations, then as a consequence
you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or
indirectly through you, then the only way you could satisfy both it and this License would be
to refrain entirely from distribution of the Program.
</p><p> If any portion of this section is held invalid or unenforceable under any particular circumstance,
the balance of the section is intended to apply and the section as a whole is intended to apply
in other circumstances.
</p><p> It is not the purpose of this section to induce you to infringe any patents or other property
right claims or to contest validity of any such claims; this section has the sole purpose of
protecting the integrity of the free software distribution system, which is implemented by public
license practices. Many people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that system; it is up
to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
</p><p> This section is intended to make thoroughly clear what is believed to be a consequence of the
rest of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817934"></a>Section 8
</h3></div></div></div><p> If the distribution and/or use of the Program is restricted in certain countries either by patents
or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such case, this License
incorporates the limitation as if written in the body of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817952"></a>Section 9
</h3></div></div></div><p> The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ
in detail to address new problems or concerns.
</p><p> Each version is given a distinguishing version number. If the Program specifies a version number of
this License which applies to it and "any later version", you have the option of following the terms
and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817985"></a>Section 10
</h3></div></div></div><p> If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted
by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all
derivatives of our free software and of promoting the sharing and reuse of software generally.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2818003"></a>Section 11 NO WARRANTY
</h3></div></div></div><p> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2818024"></a>Section 12
</h3></div></div></div><p> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
</p><p>END OF TERMS AND CONDITIONS
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apc.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apc.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apcs03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix C. GNU General Public License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> How to Apply These Terms to Your New Programs
</td></tr></table></div></body></html>

60
doc/html/apcs03.html
View File

@ -1,60 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>How to Apply These Terms to Your New Programs</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="apc.html" title="Appendix C. GNU General Public License"><link rel="prev" href="apcs02.html" title="TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION"><link rel="next" href="apd.html" title="Appendix D. License for Scintilla and SciTE"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">How to Apply These Terms to Your New Programs
</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apcs02.html">Prev</a> </td><th width="60%" align="center">Appendix C. GNU General Public License</th><td width="20%" align="right"> <a accesskey="n" href="apd.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818049"></a>How to Apply These Terms to Your New Programs
</h2></div></div></div><p>
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
</p><p>
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
</p><p>
&lt;one line to give the program's name and a brief idea of what it does.&gt;
Copyright (C) &lt;year&gt; &lt;name of author&gt;
</p><p>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
</p><p>
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
</p><p>
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
</p><p>
Also add information on how to contact you by electronic and paper mail.
</p><p>
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
</p><p>
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
</p><p>
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
</p><p>
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
</p><p>
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
</p><p>
&lt;signature of Ty Coon&gt;, 1 April 1989
Ty Coon, President of Vice
</p><p>
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apcs02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apc.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apd.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix D. License for Scintilla and SciTE</td></tr></table></div></body></html>

62
doc/html/apd.html
View File

@ -1,62 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix D. GNU General Public License</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="apc.html" title="Appendix C. Compile time options"><link rel="next" href="apds02.html" title="TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix D. GNU General Public License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apc.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="apds02.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="geany-gpl"></a>GNU General Public License</h1></div><div><p class="releaseinfo"> Version 2, June 1991</p></div><div><p class="copyright">Copyright © 1989, 1991 Free Software Foundation, Inc.</p></div><div><div class="legalnotice"><a name="id2816760"></a><p>
</p><div class="address"><p>Free Software Foundation, Inc.<br>
  <span class="street">59 Temple Place, Suite 330</span>,<br>
  <span class="city">Boston</span>,<br>
  <span class="state">MA</span><br>
  <span class="postcode">02111-1307</span><br>
  <span class="country">USA</span><br>
</p></div><p>.
</p><p> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
</p></div></div><div><p class="pubdate">Version 2, June 1991</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="apd.html#id2817418">Preamble</a></span></dt><dt><span class="sect1"><a href="apds02.html">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</a></span></dt><dd><dl><dt><span class="sect2"><a href="apds02.html#id2817524">Section 0</a></span></dt><dt><span class="sect2"><a href="apds02.html#sect1">Section 1</a></span></dt><dt><span class="sect2"><a href="apds02.html#sect2">Section 2</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817711">Section 3
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817812">Section 4
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817830">Section 5
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817848">Section 6
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817866">Section 7
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817916">Section 8
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817934">Section 9
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817967">Section 10
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2817985">Section 11 NO WARRANTY
</a></span></dt><dt><span class="sect2"><a href="apds02.html#id2818006">Section 12
</a></span></dt></dl></dd><dt><span class="sect1"><a href="apds03.html">How to Apply These Terms to Your New Programs
</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2817418"></a>Preamble</h2></div></div></div><p> The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public License is
intended to guarantee your freedom to share and change
free software - to make sure the software is free for all its users.
This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit
to using it. (Some other Free Software Foundation software is covered
by the GNU Library General Public License instead.) You can apply it
to your programs, too.
</p><p> When we speak of free software, we are referring to freedom, not price.
Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free software (and charge for this
service if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
</p><p> To protect your rights, we need to make restrictions that forbid anyone
to deny you these rights or to ask you to surrender the rights. These
restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it.
</p><p> For example, if you distribute copies of such a program, whether gratis or
for a fee, you must give the recipients all the rights that you have. You
must make sure that they, too, receive or can get the source code. And you
must show them these terms so they know their rights.
</p><p> We protect your rights with two steps:
</p><div class="orderedlist"><ol type="1"><li><p> copyright the software, and
</p></li><li><p> offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
</p></li></ol></div><p>
</p><p> Also, for each author's protection and ours, we want to make certain that
everyone understands that there is no warranty for this free software. If
the software is modified by someone else and passed on, we want its
recipients to know that what they have is not the original, so that any
problems introduced by others will not reflect on the original authors'
reputations.
</p><p> Finally, any free program is threatened constantly by software patents.
We wish to avoid the danger that redistributors of a free program will
individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be
licensed for everyone's free use or not licensed at all.
</p><p> The precise terms and conditions for copying, distribution and modification
follow.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apc.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="apds02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix C. Compile time options </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</td></tr></table></div></body></html>

172
doc/html/apds02.html
View File

@ -1,172 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="apd.html" title="Appendix D. GNU General Public License"><link rel="prev" href="apd.html" title="Appendix D. GNU General Public License"><link rel="next" href="apds03.html" title="How to Apply These Terms to Your New Programs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apd.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU General Public License</th><td width="20%" align="right"> <a accesskey="n" href="apds03.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2817518"></a>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817524"></a>Section 0</h3></div></div></div><p> This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms
of this General Public License. The "Program", below, refers to any such
program or work, and a
“<span class="quote">work based on the Program
</span>” means either
the Program or any derivative work under copyright law: that is to say, a
work containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter, translation
is included without limitation in the term
“<span class="quote">modification
</span>”.) Each licensee is addressed as “<span class="quote">you</span>”.
</p><p> Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sect1"></a>Section 1</h3></div></div></div><p> You may copy and distribute verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License
along with the Program.
</p><p> You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sect2"></a>Section 2</h3></div></div></div><p> You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifications
or work under the terms of
<a href="apds02.html#sect1" title="Section 1">Section 1</a> above, provided
that you also meet all of these conditions:
</p><div class="orderedlist"><ol type="1"><li><p> You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.
</p></li><li><p> You must cause any work that you distribute or publish, that in whole or
in part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this License.
</p></li><li><p> If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying
that you provide a warranty) and that users may redistribute the program
under these conditions, and telling the user how to view a copy of this
License.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Exception:
</h3><p> If the Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print an
announcement.)
</p></div><p>
</p></li></ol></div><p>
</p><p> These requirements apply to the modified work as a whole. If identifiable sections
of that work are not derived from the Program, and can be reasonably considered
independent and separate works in themselves, then this License, and its terms,
do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.
</p><p> Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to control
the distribution of derivative or collective works based on the Program.
</p><p> In addition, mere aggregation of another work not based on the Program with the Program
(or with a work based on the Program) on a volume of a storage or distribution medium
does not bring the other work under the scope of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817711"></a>Section 3
</h3></div></div></div><p> You may copy and distribute the Program (or a work based on it, under
<a href="apds02.html#sect2" title="Section 2">Section 2</a> in object code or executable form under the terms of
<a href="apds02.html#sect1" title="Section 1">Sections 1</a> and
<a href="apds02.html#sect2" title="Section 2">2</a> above provided that you also do one of the following:
</p><div class="orderedlist"><ol type="1"><li><p> Accompany it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
</p></li><li><p> Accompany it with a written offer, valid for at least three years, to give any
third party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code,
to be distributed under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
</p></li><li><p> Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommercial
distribution and only if you received the program in object code or executable form
with such an offer, in accord with Subsection b above.)
</p></li></ol></div><p>
</p><p> The source code for a work means the preferred form of the work for making modifications
to it. For an executable work, complete source code means all the source code for all modules
it contains, plus any associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system
on which the executable runs, unless that component itself accompanies the executable.
</p><p> If distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the same place
counts as distribution of the source code, even though third parties are not compelled to
copy the source along with the object code.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817812"></a>Section 4
</h3></div></div></div><p> You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the
Program is void, and will automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this License will not have their
licenses terminated so long as such parties remain in full compliance.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817830"></a>Section 5
</h3></div></div></div><p> You are not required to accept this License, since you have not signed it. However, nothing
else grants you permission to modify or distribute the Program or its derivative works.
These actions are prohibited by law if you do not accept this License. Therefore, by modifying
or distributing the Program (or any work based on the Program), you indicate your acceptance
of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817848"></a>Section 6
</h3></div></div></div><p> Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify
the Program subject to these terms and conditions. You may not impose any further restrictions
on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
compliance by third parties to this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817866"></a>Section 7
</h3></div></div></div><p> If, as a consequence of a court judgment or allegation of patent infringement or for any other
reason (not limited to patent issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot distribute so as to satisfy simultaneously
your obligations under this License and any other pertinent obligations, then as a consequence
you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or
indirectly through you, then the only way you could satisfy both it and this License would be
to refrain entirely from distribution of the Program.
</p><p> If any portion of this section is held invalid or unenforceable under any particular circumstance,
the balance of the section is intended to apply and the section as a whole is intended to apply
in other circumstances.
</p><p> It is not the purpose of this section to induce you to infringe any patents or other property
right claims or to contest validity of any such claims; this section has the sole purpose of
protecting the integrity of the free software distribution system, which is implemented by public
license practices. Many people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that system; it is up
to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
</p><p> This section is intended to make thoroughly clear what is believed to be a consequence of the
rest of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817916"></a>Section 8
</h3></div></div></div><p> If the distribution and/or use of the Program is restricted in certain countries either by patents
or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such case, this License
incorporates the limitation as if written in the body of this License.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817934"></a>Section 9
</h3></div></div></div><p> The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ
in detail to address new problems or concerns.
</p><p> Each version is given a distinguishing version number. If the Program specifies a version number of
this License which applies to it and "any later version", you have the option of following the terms
and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817967"></a>Section 10
</h3></div></div></div><p> If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted
by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all
derivatives of our free software and of promoting the sharing and reuse of software generally.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2817985"></a>Section 11 NO WARRANTY
</h3></div></div></div><p> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2818006"></a>Section 12
</h3></div></div></div><p> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
</p><p>END OF TERMS AND CONDITIONS
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apd.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apd.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apds03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix D. GNU General Public License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> How to Apply These Terms to Your New Programs
</td></tr></table></div></body></html>

60
doc/html/apds03.html
View File

@ -1,60 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>How to Apply These Terms to Your New Programs</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="apd.html" title="Appendix D. GNU General Public License"><link rel="prev" href="apds02.html" title="TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION"><link rel="next" href="ape.html" title="Appendix E. License for Scintilla and SciTE"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">How to Apply These Terms to Your New Programs
</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apds02.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU General Public License</th><td width="20%" align="right"> <a accesskey="n" href="ape.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818031"></a>How to Apply These Terms to Your New Programs
</h2></div></div></div><p>
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
</p><p>
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
</p><p>
&lt;one line to give the program's name and a brief idea of what it does.&gt;
Copyright (C) &lt;year&gt; &lt;name of author&gt;
</p><p>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
</p><p>
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
</p><p>
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
</p><p>
Also add information on how to contact you by electronic and paper mail.
</p><p>
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
</p><p>
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
</p><p>
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
</p><p>
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
</p><p>
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
</p><p>
&lt;signature of Ty Coon&gt;, 1 April 1989
Ty Coon, President of Vice
</p><p>
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apds02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apd.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ape.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix E. License for Scintilla and SciTE</td></tr></table></div></body></html>

12
doc/html/ape.html
View File

@ -1,12 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix E. License for Scintilla and SciTE</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="apds03.html" title="How to Apply These Terms to Your New Programs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix E. License for Scintilla and SciTE</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apds03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="scintilla-license"></a>Appendix E. License for Scintilla and SciTE</h2></div></div></div><p>Copyright 1998-2003 by Neil Hodgson &lt;neilh@scintilla.org&gt;</p><p>All Rights Reserved</p><p>Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright
notice and this permission notice appear in supporting documentation.
</p><p>NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL NEIL HODGSON
BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apds03.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">How to Apply These Terms to Your New Programs
 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>

16
doc/html/ch01.html
View File

@ -1,16 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 1.  Introduction</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="index.html" title="Geany 0.11"><link rel="next" href="ch01s02.html" title="About this document"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. 
Introduction
</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch01s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter 1. 
Introduction
</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch01.html#id2800224">About Geany</a></span></dt><dt><span class="section"><a href="ch01s02.html">About this document</a></span></dt><dt><span class="section"><a href="ch01s03.html">Where to get it</a></span></dt><dt><span class="section"><a href="ch01s04.html">License</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800224"></a>About Geany</h2></div></div></div><p>
<span class="application">Geany</span> is a small and lightweight Integrated Development Environment.
It was developed to provide a small and fast IDE, which has only a few dependencies from other
packages. Another goal was to be as independent as possible from a special Desktop Environment
like KDE or GNOME, so <span class="application">Geany</span> only requires the GTK2 toolkit
and therefore you only need the GTK2 runtime libraries installed to run it.
</p><p>
The basic features of <span class="application">Geany</span> are:
</p><div class="itemizedlist"><ul type="disc"><li><p>Syntax highlighting</p></li><li><p>Code completion</p></li><li><p>Auto completion of often-used constructs like "if", "for" and "while"</p></li><li><p>Auto completion of XML and HTML tags</p></li><li><p>Call tips</p></li><li><p>Many supported filetypes including C, Java, PHP, HTML, Python, Perl, Pascal, and others</p></li><li><p>Tag/Symbol lists</p></li></ul></div><p>
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch01s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
Geany 0.11
 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> About this document</td></tr></table></div></body></html>

8
doc/html/ch01s02.html
View File

@ -1,8 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>About this document</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch01.html" title="Chapter 1.  Introduction"><link rel="prev" href="ch01.html" title="Chapter 1.  Introduction"><link rel="next" href="ch01s03.html" title="Where to get it"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">About this document</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
Introduction
</th><td width="20%" align="right"> <a accesskey="n" href="ch01s03.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2762083"></a>About this document</h2></div></div></div><p>
This documentation is available in various formats like HTML, text and PDF. The latest version is
always available at <a href="http://geany.uvena.de" target="_top">http://geany.uvena.de</a>.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. 
Introduction
 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Where to get it</td></tr></table></div></body></html>

6
doc/html/ch01s03.html
View File

@ -1,6 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Where to get it</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch01.html" title="Chapter 1.  Introduction"><link rel="prev" href="ch01s02.html" title="About this document"><link rel="next" href="ch01s04.html" title="License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Where to get it</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
Introduction
</th><td width="20%" align="right"> <a accesskey="n" href="ch01s04.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2762150"></a>Where to get it</h2></div></div></div><p>
You can obtain <span class="application">Geany</span> from <a href="http://geany.uvena.de" target="_top">http://geany.uvena.de</a>
or perhaps from your distributor.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">About this document </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> License</td></tr></table></div></body></html>

13
doc/html/ch01s04.html
View File

@ -1,13 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>License</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch01.html" title="Chapter 1.  Introduction"><link rel="prev" href="ch01s03.html" title="Where to get it"><link rel="next" href="ch02.html" title="Chapter 2.  Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
Introduction
</th><td width="20%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2762175"></a>License</h2></div></div></div><p>
<span class="application">Geany</span> is distributed under the terms of the GNU General Public License as published
by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
A copy of this license can be found in the file COPYING included with the source code of this
program or see <a href="apd.html" title="Appendix D. GNU General Public License">Appendix D, <i>GNU General Public License</i></a>.
</p><p>
The included Scintilla library (found in the subdirectory scintilla/) has its own
license, which can be found in the appendix (see <a href="ape.html" title="Appendix E. License for Scintilla and SciTE">Appendix E, <i>License for Scintilla and SciTE</i></a>).
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Where to get it </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. 
Installation
</td></tr></table></div></body></html>

13
doc/html/ch02.html
View File

@ -1,13 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 2.  Installation</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="ch01s04.html" title="License"><link rel="next" href="ch02s02.html" title="Source compilation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. 
Installation
</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter 2. 
Installation
</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch02.html#id2762369">Requirements</a></span></dt><dt><span class="section"><a href="ch02s02.html">Source compilation</a></span></dt><dt><span class="section"><a href="ch02s03.html">Binary packages</a></span></dt><dd><dl><dt><span class="section"><a href="ch02s03.html#id2762327">Fedora</a></span></dt><dt><span class="section"><a href="ch02s03.html#id2762675">Debian</a></span></dt><dt><span class="section"><a href="ch02s03.html#id2762700">SuSE</a></span></dt><dt><span class="section"><a href="ch02s03.html#id2762711">Gentoo</a></span></dt></dl></dd></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2762369"></a>Requirements</h2></div></div></div><p>
For compiling <span class="application">Geany</span> yourself, you will need the GTK (&gt;= 2.6.0)
libraries and header files. You will also need the Pango, Glib and ATK libraries and header files.
All these files are available at <a href="http://www.gtk.org" target="_top">http://www.gtk.org</a>.
</p><p>
Furthermore you need, of course, a C compiler and the Make tool; a C++ compiler is
also required for the included Scintilla library. The GNU versions of these tools are
recommended.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Source compilation</td></tr></table></div></body></html>

28
doc/html/ch02s02.html
View File

@ -1,28 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Source compilation</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch02.html" title="Chapter 2.  Installation"><link rel="prev" href="ch02.html" title="Chapter 2.  Installation"><link rel="next" href="ch02s03.html" title="Binary packages"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Source compilation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02.html">Prev</a> </td><th width="60%" align="center">Chapter 2. 
Installation
</th><td width="20%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="source_compilation"></a>Source compilation</h2></div></div></div><p>
Compiling <span class="application">Geany</span> is quite easy. The following should do it:
</p><pre class="screen">
<code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">./configure</strong></span></code></strong>
<code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">make</strong></span></code></strong>
<code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">make</strong></span> install</code></strong></pre><p>
</p><p>
The configure script supports several common options, for a detailed list, type
</p><pre class="screen">
<code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">./configure</strong></span> --help</code></strong></pre><p>
There also some compile time options which can be found in <code class="filename">src/geany.h</code>.
Please see <a href="apc.html" title="Appendix C. Compile time options">Appendix C, <i>Compile time options</i></a> for more information.
</p><p>
In the case that your system lacks dynamic linking loader support, you probably want
to pass the option --disable-vte to the configure script. This prevents compiling
<span class="application">Geany</span> with dynamic linking loader support to automatically load
<code class="filename">libvte.so.4</code> if available.
</p><p><span class="application">Geany</span> has been successfully compiled and tested under Debian 3.1 Sarge, Debian 4.0 Etch,
Fedora Core 3/4/5, LinuxFromScratch and FreeBSD 6.0. It also compiles under
<span class="trademark">Microsoft Windows</span>™.
</p><p>
If there are any errors during compilation, check your build environment and try to find the error,
otherwise contact the author at <code class="email">&lt;<a href="mailto:enrico.troeger@uvena.de">enrico.troeger@uvena.de</a>&gt;</code>.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. 
Installation
 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Binary packages</td></tr></table></div></body></html>

17
doc/html/ch02s03.html
View File

@ -1,17 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Binary packages</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch02.html" title="Chapter 2.  Installation"><link rel="prev" href="ch02s02.html" title="Source compilation"><link rel="next" href="ch03.html" title="Chapter 3. Usage"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Binary packages</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s02.html">Prev</a> </td><th width="60%" align="center">Chapter 2. 
Installation
</th><td width="20%" align="right"> <a accesskey="n" href="ch03.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="binary_packages"></a>Binary packages</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2762327"></a>Fedora</h3></div></div></div><p>
You can use the Fedora Core 4 repository from
<a href="http://naturidentisch.de/packages/fc4/" target="_top">http://naturidentisch.de/packages/fc4/</a>.
</p><p>
You can also use the Fedora Core 5 repository from
<a href="http://naturidentisch.de/packages/fc5/" target="_top">http://naturidentisch.de/packages/fc5/</a>.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2762675"></a>Debian</h3></div></div></div><p>
<span class="application">Geany</span> is available through the official Debian archives.
</p><p>
<span><strong class="command">apt-get install geany</strong></span>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2762700"></a>SuSE</h3></div></div></div><p>
Packages for SuSE are not yet available.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2762711"></a>Gentoo</h3></div></div></div><p>
An ebuild for Gentoo can be found on <a href="https://bugs.gentoo.org/show_bug.cgi?id=114815" target="_top">http://bugs.gentoo.de</a>.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Source compilation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Usage</td></tr></table></div></body></html>

16
doc/html/ch03.html
View File

File diff suppressed because one or more lines are too long

35
doc/html/ch03s02.html
View File

@ -1,35 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Command line options</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03.html" title="Chapter 3. Usage"><link rel="next" href="ch03s03.html" title="General"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Command line options</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s03.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="clo"></a>Command line options</h2></div></div></div><p>
</p><div class="table"><a name="id2762848"></a><p class="title"><b>Table 3.1. Command line Options</b></p><div class="table-contents"><table summary="Command line Options" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Short option</th><th>Long option</th><th>Function</th></tr></thead><tbody><tr><td> </td><td>--column</td><td>Set initial column number for the first opened file.
</td></tr><tr><td>-c dir_name</td><td>--config=directory_name</td><td>Use an alternate configuration directory. Default
configuration directory is <code class="filename">~/.geany/</code>
and there resides <code class="filename">geany.conf</code> and
other configuration files.
</td></tr><tr><td>-d</td><td>--debug</td><td>Run <span class="application">Geany</span> in debug mode, which
means being verbose and printing lots of information.
</td></tr><tr><td>-i</td><td>--new-instance</td><td>Do not open files in a running instance, force opening a
new instance. Only available if <span class="application">Geany</span>
was compiled with support for Sockets.
</td></tr><tr><td>-l</td><td>--line</td><td>Set initial line number for the first opened file.
</td></tr><tr><td>-m</td><td>--no-msgwin</td><td>Do not show the message window. Use this option if you do not
need compiler messages or VTE support.
</td></tr><tr><td>-n</td><td>--no-ctags</td><td>Do not load auto completion and call tip data.
Use this option if you do not want to use them.
</td></tr><tr><td>-s</td><td>--no-session</td><td>Don't load the previous session's files.
</td></tr><tr><td>-t</td><td>--no-terminal</td><td>Do not load terminal support. Use this option if you do not
want to load the virtual terminal emulator widget at startup.
If you do not have <code class="filename">libvte.so.4</code> installed,
then terminal-support is automatically disabled. Only available
if <span class="application">Geany</span> was compiled with support
for VTE.
</td></tr><tr><td> </td><td>--vte-lib</td><td>Specify explicitly the path including filename or only the filename
to the VTE library, e.g. <code class="filename">/usr/lib/libvte.so</code> or
<code class="filename">libvte.so</code>. This option is only needed when the
autodetection does not work. Only available if
<span class="application">Geany</span> was compiled with support for VTE.
</td></tr><tr><td>-v</td><td>--version</td><td>Show version information and exit.</td></tr><tr><td>-?</td><td>--help</td><td>Show help information and exit.</td></tr><tr><td> </td><td>[files ...]</td><td>Open all given files at startup. This option causes
<span class="application">Geany</span> to ignore loading stored
files from the last session (if enabled).
</td></tr></tbody></table></div></div><p><br class="table-break">
<span class="application">Geany</span> supports all generic GTK options, a list is
available on the help screen.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Usage </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> General</td></tr></table></div></body></html>

87
doc/html/ch03s03.html
View File

@ -1,87 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>General</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s02.html" title="Command line options"><link rel="next" href="ch03s04.html" title="Character sets and Unicode Byte-Order-Mark (BOM)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">General</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s02.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s04.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="general"></a>General</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="general_startup"></a>Startup</h3></div></div></div><p>
At startup, <span class="application">Geany</span> loads all files from the last time
<span class="application">Geany</span> was launched. You can disable this feature in the
preferences dialog(see <a href="ch03s08.html#prefs_gen" title="Figure 3.4. General tab in preferences dialog">Figure 3.4, “General tab in preferences dialog”</a>). If you specify some files on
the command line, only these files will be opened, but you can find the files from the
last session in the file menu under the "Recent files" item. By default this contains
the last 10 recently opened files. You can change the amount of recently opened
files in the preferences dialog.
</p><p>
You can start several instances of <span class="application">Geany</span>, but only
the first will load files from the last session. To run a second instance of
<span class="application">Geany</span>, do not specify any filenames on the
command-line, or disable opening files in a running instance using the
appropriate command line option.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="general_instance"></a>Opening files from the command-line in a running instance</h3></div></div></div><p>
<span class="application">Geany</span> detects an already running instance of itself
and opens files from the command-line in the already running instance.
So, <span class="application">Geany</span> can be used to view and edit files by
opening them from other programs such as a file manager. If you do not like
this for some reason, you can disable using the first instance by using the
appropriate command line option - see <a href="ch03s02.html" title="Command line options">the section called “Command line options”</a>.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="general_vte"></a>Virtual terminal emulator widget (VTE)</h3></div></div></div><p>
If you have installed <code class="filename">libvte.so</code> in your system, it is loaded
automatically by <span class="application">Geany</span>, and you will have a terminal widget
in the notebook at the bottom.
</p><p>
If <span class="application">Geany</span> cannot find <code class="filename">libvte.so</code> at
startup, the terminal widget will not be loaded. So there is no need to install the
package containing this file in order to run <span class="application">Geany</span>.
Additionally, you can disable the use of the terminal widget by command line option,
for more information see <a href="ch03s02.html" title="Command line options">the section called “Command line options”</a>.
</p><p>
You can use this terminal (from now on called VTE) nearly as an usual terminal program
like xterm. There is basic clipboard support. You can paste the contents
of the clipboard by pressing the right mouse button to open the popup menu and
choosing Paste.
To copy text from the VTE, just select the desired text and then press the
right mouse button and choose Copy from the popup menu.
On systems running the X Window System you can paste the last selected text by
pressing the middle mouse button in the VTE (on 2-button mice,
the middle button can often be simulated by pressing both mouse buttons together).
</p><p>
In the preferences dialog you can specify a shell which should be started in the
VTE. To make the specified shell a login shell just use the appropriate command
line options for the shell. These options should be found in the manual page of
the shell. For zsh and bash you can use the argument <code class="literal">--login</code>.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p><span class="application">Geany</span> tries to load <code class="filename">libvte.so</code>.
If this fails, it tries to load <code class="filename">libvte.so.4</code>. If this
fails too, you should check whether you installed libvte correctly. Again,
<span class="application">Geany</span> also runs without this library.
</p><p>
It could be, that the library is called something else than
<code class="filename">libvte.so.4</code> (e.g. on FreeBSD 6.0 it is called
<code class="filename">libvte.so.8</code>). So please set a link to the correct file (as root).
</p><pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code><span><strong class="command">ln -s /usr/lib/libvte.so.X /usr/lib/libvte.so.4</strong></span></code></strong></pre><p>
Obviously, you have to adjust the paths and set X to the number of your
<code class="filename">libvte.so</code>.
</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="general_userstyles"></a>Defining own widget styles using .gtkrc-2.0</h3></div></div></div><p>
You can define your widget style for many of <span class="application">Geany</span>'s
GUI parts. To do this, just edit your <code class="filename">.gtkrc-2.0</code> (usually
found in your home directory on UNIX-like systems and in the etc subdirectory
of your <span class="application">Geany</span> installation on Windows).
</p><p>
To get a defined style get noticed by <span class="application">Geany</span> you must
it assign to one of <span class="application">Geany</span>'s widgets. To do so,
use the following line:
</p><p>
<span><strong class="command">widget "Geany*" style "geany_style"</strong></span>
</p><p>
This would assign your already defined style "geany_style" to all
<span class="application">Geany</span> widgets. You can also assign styles only to
specific widgets. At the moment you can use the following widgets:
</p><div class="orderedlist"><ol type="1"><li><p>GeanyMainWindow</p></li><li><p>GeanyEditMenu</p></li><li><p>GeanyToolbarMenu</p></li><li><p>GeanyDialog</p></li><li><p>GeanyDialogPrefs</p></li><li><p>GeanyDialogProject</p></li><li><p>GeanyDialogSearch</p></li></ol></div><p>
</p><p>Example of a simple .gtkrc-2.0:
</p><pre class="programlisting">style "geanyStyle"
{
font_name="Sans 12"
}
widget "GeanyMainWindow" style "geanyStyle"
style "geanyStyle"
{
font_name="Sans 10"
}
widget "GeanyPrefsDialog" style "geanyStyle"
</pre><p>
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Command line options </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Character sets and Unicode Byte-Order-Mark (BOM)</td></tr></table></div></body></html>

60
doc/html/ch03s04.html
View File

@ -1,60 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Character sets and Unicode Byte-Order-Mark (BOM)</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s03.html" title="General"><link rel="next" href="ch03s05.html" title="Editing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Character sets and Unicode Byte-Order-Mark (BOM)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s03.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s05.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="charset"></a>Character sets and Unicode Byte-Order-Mark (BOM)</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2810138"></a>Using character sets</h3></div></div></div><p>
<span class="application">Geany</span> provides support for detecting and converting
character sets. So you can open and save files in different character sets and
even can convert a file from a character set to another one.
To do this, <span class="application">Geany</span> uses the character conversion
capabilities of the GLib.
</p><p>
Only text files are supported, i.e. opening files which contain NUL-bytes may
fail. <span class="application">Geany</span> will try to open the file anyway but it
is likely that the file will be truncated because it can only opened up to the
first occurrence of the first NUL-byte. All characters after this position are
lost and are not written when you save the file.
</p><p>
<span class="application">Geany</span> tries to detect the encoding of a file while
opening it. It might be that the encoding of a file cannot be detected correctly
so you have to set manually the encoding of the file in order to display it
correctly. You can this in the file open dialog by selecting an encoding in the
drop down box or by reloading the file with the file menu item "Reload as".
The auto detection works well for most encodings but there are also some encodings
known where auto detection has its problems. Auto detecting the encoding of a file
is not easy and sometimes an encoding might be detected not correctly.
</p><p>
There are different ways to use different encodings in <span class="application">Geany</span>:
</p><div class="orderedlist"><ol type="1"><li><p>Using the file open dialog</p><p>This opens the file with the encoding specified in the encoding
drop down box. If the encoding is set to "Detect from file"
auto detection will be used. If the encoding is set to
"Without encoding (None)" the file will be opened without any
character conversion and <span class="application">Geany</span> will
not try to auto detect the encoding(see below for more information).
</p></li><li><p>Using the "Reload as" menu item</p><p>This item reloads the current file with the specified encoding.
It can help if you opened a file and found out that a wrong
encoding was used.
</p></li><li><p>Using the "Set encoding" menu item</p><p>In contrary to the above two options, this will not change or
reload the current file unless you save it. It is useful when
you want to change the encoding of the file.</p></li></ol></div><p>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2810280"></a>Special encoding "None"</h3></div></div></div><p>
There is a special encoding "None" which is actually no real encoding. It is
useful when you know that Geany cannot auto detect the encoding of a file and
it is not displayed correctly. Especially when the file contains NUL-bytes this
can be useful to skip auto detection and open the file properly at least until
the occurrence of the first NUL-byte. Using this encoding opens the file as it
is without any character conversion.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2810298"></a>Unicode Byte-Order-Mark (BOM)</h3></div></div></div><p>
Furthermore, <span class="application">Geany</span> detects an Unicode Byte Order Mark
(see <a href="http://en.wikipedia.org/wiki/Byte_Order_Mark" target="_top">
<em class="citetitle">http://en.wikipedia.org/wiki/Byte_Order_Mark</em>
</a> for details). Of course, this feature is only available if the opened file
is in an unicode encoding. The Byte Order Mark helps to detect the encoding of a
file, e.g. whether it is UTF-16LE or UTF-16BE and so on. On Unix-like systems using
a Byte Order Mark could cause some problems, e.g. the gcc stops with stray errors,
PHP does not parse a script containing a BOM and script files starting with a
she-bang maybe cannot be started.
In the status bar you can easily see whether the file starts with a BOM or not.
If you want to set a BOM for a file or if you want to remove it from a file, just
use the document menu and toggle the checkbox.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
If you are unsure what a BOM is or if you do not understand where to use it,
then it is not important for you and you can safely ignore it.
</p></div><p>
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">General </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Editing</td></tr></table></div></body></html>

85
doc/html/ch03s05.html
View File

@ -1,85 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Editing</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s04.html" title="Character sets and Unicode Byte-Order-Mark (BOM)"><link rel="next" href="ch03s06.html" title="Search, replace and go to"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Editing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s04.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s06.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="editing"></a>Editing</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="editing_text_dnd"></a>Drag and drop of text</h3></div></div></div><p>
If you drag selected text in the editor widget of
<span class="application">Geany</span> the text is moved to the position where the
mouse pointer is when releasing the mouse button. Holding Control when releasing
the mouse button will copy the text instead. This behaviour was
changed in <span class="application">Geany</span> 0.11 - before the selected text
was copied to the new position.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="editing_indentation"></a>Auto indentation</h3></div></div></div><p>
<span class="application">Geany</span> knows three types of auto indentation:
None, Basic and Advanced.
</p><div class="variablelist"><p class="title"><b>Auto indentation types</b></p><dl><dt><span class="term">None</span></dt><dd><p>
Disables auto indentation completely.
</p></dd><dt><span class="term">Basic</span></dt><dd><p>
Adds the same amount of whitespace on a new line as on the last line.
</p></dd><dt><span class="term">Advanced</span></dt><dd><p>
Does the same as Basic but also indents curly brackets and adds a tabulator
character (or spaces) on a new line after an opening '{' brace.
</p></dd></dl></div><p>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="editing_cc"></a>Construct completion</h3></div></div></div><p>
Built-in construct completion is available for C-like languages. By default the
<span><strong class="keycap">Tab</strong></span> key is used straight after typing the construct keyword.
</p><p>
Example: <code class="literal">for</code>&lt;TAB&gt;
</p><p>
typed into a C file expands to:
</p><p>
</p><div class="literallayout"><p><code class="literal">for (i = 0; i &lt; ; i++)<br>
{<br>
<br>
}<br>
</code></p></div><p>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="editing_bookmarks"></a>Bookmarks</h3></div></div></div><p>
Geany provides a handy bookmarking feature that lets you mark one or more lines in a document, and
return the cursor to them using a key combination.
</p><p>
To place a mark on a line, either left-mouse-click in the left margin of the editor window, or else
use Ctrl-m. Either way, this will produce a small green plus symbol in the margin. You can have as
many marks in a document as you like. Click again (or use Ctrl-m again) to remove the bookmark.
To remove all the marks in a given document, use "Remove Markers" in the Document menu.
</p><p>
To navigate down your document, jumping from one mark to the next, use Ctrl-. (control period).
To go in the opposite direction on the page, use Ctrl-, (control comma). Using the bookmarking
feature together with the commands to switch from one editor tab to another (Ctrl-PgUp/PgDn and
Ctrl-Tab) provides a particularly fast way to navigate around multiple files.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="editing_definable_commands"></a>Send text through definable commands</h3></div></div></div><p>
You can define several custom commands in <span class="application">Geany</span> and
send the current selection to one of these commands. The output of the command
will be used to replace the current selection. So, it is possible to use text
formatting tools with Geany in a general way.
The selected text will be sent to the standard input of the executed command,
so the command should be able to read from it and it should print all results
to its standard output which will be read by <span class="application">Geany</span>.
To help finding errors in executing the command, the output of the program's
standard error will be printed on <span class="application">Geany</span>'s standard
output.
</p><p>
To add a custom command, just go to the Set Custom Commands dialog in the
Format sub menu of the Edit and Popup menu. Then click on Add to get a new
text entry and type the command. You can also specify some command line options.
To delete a command, just clear the text entry and press Ok. It will be deleted
automatically.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="editing_context_actions"></a>Context actions</h3></div></div></div><p>
You can execute a specified command on the current word near the cursor
position or an available selection and this word is passed as an argument
to this command. It can be used for example to open some API documentation
in a browser window or open any other external program. To do this,
there is an menu entry in the popup menu of the editor widget and also a
keyboard shortcut(see <a href="ch03s12.html" title="Keybindings">the section called “Keybindings”</a>).
</p><p>
The command can be specified in the preferences dialog and additionally for
each filetype (see "context_action_cmd" in <a href="ch04.html#filetypes_format" title="Format">the section called “Format”</a>).
At executing, the filetype specific command is used if available otherwise the
command specified in the preferences dialog is executed.
</p><p>
The passed word can be referred with the wildcard "%s" everywhere in the
command, before executing it will be replaced by the current word.
For example, the command to open the PHP API documentation would be:
</p><p>
<span><strong class="command">firefox "http://www.php.net/%s"</strong></span>
</p><p>
when executing the command, the %s is substituted by the word near the
cursor position or by the current selection. If the cursor is at the word
"echo", a browser window will open(assumed your browser is called firefox)
and it will open the address: http://www.php.net/echo.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Character sets and Unicode Byte-Order-Mark (BOM) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Search, replace and go to</td></tr></table></div></body></html>

132
doc/html/ch03s06.html
View File

@ -1,132 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Search, replace and go to</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s05.html" title="Editing"><link rel="next" href="ch03s07.html" title="Tags"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Search, replace and go to</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s05.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s07.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="search"></a>Search, replace and go to</h2></div></div></div><p>
This section describes search-related commands from the Search menu and
the editor window's popup menu:
</p><p>
</p><div class="itemizedlist"><ul type="disc"><li><p>Find</p></li><li><p>Find usage *</p></li><li><p>Find in files</p></li><li><p>Replace</p></li><li><p>Go to tag definition *</p></li><li><p>Go to tag declaration *</p></li><li><p>Go to line</p></li></ul></div><p>
</p><p>
* These items are available from the editor window's popup menu, or by
using a keyboard shortcut (see <a href="ch03s12.html" title="Keybindings">the section called “Keybindings”</a>).
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="search_find"></a>Find</h3></div></div></div><p>
The Find dialog is used for finding text in one or more open documents.
</p><p>
</p><div class="figure"><a name="id2810752"></a><p class="title"><b>Figure 3.1. Find dialog</b></p><div class="figure-contents"><div><img src="images/find_dialog.png" alt="Find dialog"></div></div></div><p><br class="figure-break">
</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="search_matchingoptions"></a>Matching options</h4></div></div></div><p>
The syntax for the <span class="emphasis"><em>Use regular expressions</em></span> option is shown in
<a href="ch03s06.html#regexp" title="Table 3.2. Regular expressions">Table 3.2, “Regular expressions”</a>.
</p><p>
The <span class="emphasis"><em>Use escape sequences</em></span> option will transform
any escaped characters into their UTF-8 equivalent. For example,
<code class="literal">\t</code> will be transformed into a tab character. Other
recognised symbols are:
<code class="literal">\\</code>, <code class="literal">\n</code>, <code class="literal">\r</code>,
<code class="literal">\uXXXX</code> (Unicode chararacters).
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2810833"></a>Find all</h4></div></div></div><p>
To find all matches, click on the <span class="emphasis"><em>Find All</em></span> expander.
This will reveal several options:
</p><div class="itemizedlist"><ul type="disc"><li><p>In Document</p></li><li><p>In Session</p></li><li><p>Mark</p></li></ul></div><p>
<span class="emphasis"><em>Find All In Document</em></span> will show a list of matching lines
in the current document in the Messages tab of the Message Window.
<span class="emphasis"><em>Find All In Session</em></span> does the same for all open documents.
</p><p>
<span class="emphasis"><em>Mark</em></span> will set markers for all matching lines in the
current document, if the Markers margin is visible.
If not, the background colour of matching lines will be highlighted.
Markers and highlighting can be removed by selecting the
<span class="emphasis"><em>Remove Markers</em></span> command from the
Document menu.
</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2810892"></a>Find usage</h3></div></div></div><p>
Find usage searches all open files. It is similar to the
<span class="emphasis"><em>Find All In Session</em></span> Find dialog command.
</p><p>
If there is a selection, then it is used
as the search text; otherwise the current word is used.
The current word is either taken from the word nearest the edit cursor, or
the word underneath the popup menu click position when the popup menu is
used.
The search results are shown in the Messages tab of the Message Window.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="search_fif"></a>Find in files</h3></div></div></div><p>
Find in files is a more powerful version of Find usage that searches all files
in a certain directory using the Grep tool. The Grep tool must be correctly set
in Preferences to the path of the system's Grep utility.
GNU Grep is recommended.
</p><p>
</p><div class="figure"><a name="id2810936"></a><p class="title"><b>Figure 3.2. Find in files dialog</b></p><div class="figure-contents"><div><img src="images/find_in_files_dialog.png" alt="Find in files dialog"></div></div></div><p><br class="figure-break">
</p><p>
The <span class="emphasis"><em>Extra options</em></span> field is used to pass any additional
arguments to the <code class="literal">grep</code> tool.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2810965"></a>Filtering out version control files</h4></div></div></div><p>
When using the <span class="emphasis"><em>Recurse in subfolders</em></span> option with a
directory that's under version control, you can set the
<span class="emphasis"><em>Extra options</em></span> field to use <code class="literal">grep</code>'s
<code class="literal">--exclude</code> flag to filter out filenames.
</p><p>
SVN Example: <code class="literal">--exclude=*.svn-base</code>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
The GNU Grep project added support for excluding directories,
using the <code class="literal">--exclude-dir</code> flag.
At the time of writing (April 2007) this is unreleased outside
of version control.
Check your Grep manual to see if your version supports it.
</p><p>
Example: <code class="literal">--exclude-dir=.* --exclude-dir=CVS</code>
</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="search_replace"></a>Replace</h3></div></div></div><p>
The Replace dialog is used for replacing text in one or more open documents.
</p><p>
</p><div class="figure"><a name="id2811050"></a><p class="title"><b>Figure 3.3. Replace dialog</b></p><div class="figure-contents"><div><img src="images/replace_dialog.png" alt="Replace dialog"></div></div></div><p><br class="figure-break">
</p><p>
The Replace dialog has the same options for matching text as the Find
dialog. See <a href="ch03s06.html#search_matchingoptions" title="Matching options">the section called “Matching options”</a>.
</p><p>
The <span class="emphasis"><em>Use regular expressions</em></span> option applies both to the
search string and
to the replacement text; for the latter back references can be used -
see the entry for '\n' in <a href="ch03s06.html#regexp" title="Table 3.2. Regular expressions">Table 3.2, “Regular expressions”</a>.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2811092"></a>Replace all</h4></div></div></div><p>
To replace several matches, click on the <span class="emphasis"><em>Replace All</em></span>
expander. This will reveal several options:
</p><div class="itemizedlist"><ul type="disc"><li><p>In Document</p></li><li><p>In Session</p></li><li><p>In Selection</p></li></ul></div><p>
<span class="emphasis"><em>Replace All In Document</em></span> will replace all matching text
in the current document.
<span class="emphasis"><em>Replace All In Session</em></span> does the same for all open documents.
<span class="emphasis"><em>Replace All In Selection</em></span> will replace all matching text
in the current selection of the current document.
</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="search_gototag"></a>Go to tag definition</h3></div></div></div><p>
If the current word is the name of a tag definition (like a function body)
and the file containing the tag definition is open, this command will
switch to that file and go to the corresponding line number.
The current word is either taken from the word nearest the edit cursor, or
the word underneath the popup menu click position when the popup menu is
used.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2811169"></a>Go to tag declaration</h3></div></div></div><p>
Like Go to tag definition, but for a forward declaration such as a
function prototype or <code class="literal">extern</code> declaration instead
of a function body.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2811187"></a>Go to line</h3></div></div></div><p>
Go to a particular line number in the current file.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2811198"></a>Regular expressions</h3></div></div></div><p>
You can use regular expressions in the Find and Replace dialogs by
selecting the <span class="emphasis"><em>Use regular expressions</em></span> check box.
The syntax is POSIX-like, as described below in <a href="ch03s06.html#regexp" title="Table 3.2. Regular expressions">Table 3.2, “Regular expressions”</a>.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
Searching backwards with regular expressions is not supported.
</p></div><p>
</p><p>
</p><div class="table"><a name="regexp"></a><p class="title"><b>Table 3.2. Regular expressions</b></p><div class="table-contents"><table summary="Regular expressions" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col></colgroup><thead><tr><th colspan="2" align="left">
In a regular expression, the following characters are interpreted:
</th></tr></thead><tbody><tr><td>.</td><td>Matches any character.</td></tr><tr><td>(</td><td>This marks the start of a region for tagging a match.</td></tr><tr><td>)</td><td>This marks the end of a tagged region.</td></tr><tr><td>\n</td><td>Where n is 1 through 9 refers to the first through ninth tagged region
when replacing. For example, if the search string was Fred([1-9])XXX
and the replace string was Sam\1YYY, when applied to Fred2XXX this would
generate Sam2YYY.
</td></tr><tr><td>\&lt;</td><td>This matches the start of a word.</td></tr><tr><td>\&gt;</td><td>This matches the end of a word.</td></tr><tr><td>\x</td><td>This allows you to use a character x that would otherwise have a special
meaning. For example, \[ would be interpreted as [ and not as the start
of a character set. Use \\ for a literal backslash.
</td></tr><tr><td>[...]</td><td>This indicates a set of characters, for example, [abc] means any of the
characters a, b or c. You can also use ranges, for example [a-z] for any
lower case character.
</td></tr><tr><td>[^...]</td><td>The complement of the characters in the set. For example, [^A-Za-z] means
any character except an alphabetic character.
</td></tr><tr><td>^</td><td>This matches the start of a line (unless used inside a set, see above).</td></tr><tr><td>$</td><td>This matches the end of a line.</td></tr><tr><td>*</td><td>This matches 0 or more times. For example, Sa*m matches Sm, Sam, Saam, Saaam and so on.</td></tr><tr><td>+</td><td>This matches 1 or more times. For example, Sa+m matches Sam, Saam, Saaam and so on.</td></tr></tbody></table></div></div><p><br class="table-break">
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Partial POSIX compatibility</h3><p>
Note that the POSIX '?' regular expression character for optional matching
is not supported by the Find and Replace dialogs.
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s07.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Editing </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Tags</td></tr></table></div></body></html>

77
doc/html/ch03s07.html
View File

@ -1,77 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Tags</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s06.html" title="Search, replace and go to"><link rel="next" href="ch03s08.html" title="Preferences"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Tags</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s06.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s08.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tags"></a>Tags</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2811464"></a>Workspace tags</h3></div></div></div><p>
Tags for each document are parsed whenever a file is loaded or saved. These are
shown in the Symbol list in the Sidebar. These tags are also used for autocompletion
and calltips in other documents open in the current session.
</p><p>
The <span class="emphasis"><em>Go to Tag</em></span> commands can be used with all workspace tags.
See <a href="ch03s06.html#search_gototag" title="Go to tag definition">the section called “Go to tag definition”</a>.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="tags_global"></a>Global tags</h3></div></div></div><p>
Global tags are used to provide autocompletion and calltips without having to open
the corresponding source files. This is intended for library APIs, as the tags file
only has to be updated when you upgrade the library.
</p><p>
You can load a custom global tags file in two ways:
</p><div class="itemizedlist"><ul type="disc"><li><p>Using the <span class="emphasis"><em>Load Tags</em></span> command in the File menu.
</p></li><li><p>By creating a directory <code class="filename">~/.geany/tags</code>,
and moving or symlinking the tags files there before starting
<span class="application">Geany</span>.
</p></li></ul></div><p>
</p><p>
You can either download these files or generate your own.
They have the format:
</p><p>
<code class="filename">libraryname.lang_ext.tags</code>
</p><p>
<span class="emphasis"><em>lang_ext</em></span> is one of the extensions set for the filetype
associated with the tags. See <a href="ch04s02.html" title="Filetype extensions">the section called “Filetype extensions”</a> for more
information.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2811571"></a>Default global tags files</h4></div></div></div><p>
For some languages, a list of global tags is loaded when the corresponding filetype
is first used. Currently these are for:
</p><div class="itemizedlist"><ul type="disc"><li><p>C - GTK+ and GLib</p></li><li><p>Pascal</p></li><li><p>PHP</p></li><li><p>HTML - <code class="literal">&amp;symbol;</code> completion, e.g.
for ampersand, copyright, etc.</p></li><li><p>LaTeX</p></li></ul></div><p>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="tags_generating"></a>Generating a global tags file</h4></div></div></div><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Filetypes support</h3><p>
Currently this is not yet supported for Pascal, PHP and LaTeX filetypes.
</p></div><p>
</p><p>
You can generate your own global tags files by parsing a list of source files.
The command is:
</p><p>
geany -g &lt;Tag File&gt; &lt;File list&gt;
</p><p>
</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Tag File</em></span> should be in the format described
earlier - see <a href="ch03s07.html#tags_global" title="Global tags">the section called “Global tags”</a>.</p></li><li><p><span class="emphasis"><em>File list</em></span> is a list of filenames, each with
a full path (unless you are generating C/C++ tags and have set the CFLAGS
environment variable appropriately).</p></li></ul></div><p>
</p><p>
Example for the wxD library for the D programming language:
</p><pre class="programlisting">geany -g wxd.d.tags /home/username/wxd/wx/*.d</pre><p>
</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2811688"></a>Generating C/C++ tag files</h5></div></div></div><p>
For C/C++ tag files, <code class="filename">gcc</code> and <code class="filename">grep</code> are
required, so that header files can be preprocessed to include
any other headers they depend upon.
</p><p>
For C/C++ files, the environment variable CFLAGS should be set with appropriate
<code class="literal">-I/path</code> include paths.
The following example works with the <code class="filename">bash</code> shell, generating
tags for the GnomeUI library:
</p><pre class="programlisting">CFLAGS=`pkg-config --cflags libgnomeui-2.0` geany -g gnomeui.c.tags
/usr/include/libgnomeui-2.0/gnome.h</pre><p>
</p><p>
You can adapt this command to use CFLAGS and header files appropriate for
whichever libraries you want.
</p><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Replacing the default C/C++ tags file</h3><p>
<span class="application">Geany</span> currently uses a default global tags file
<code class="filename">global.tags</code>
for C and C++, commonly installed in <code class="filename">/usr/share/geany</code>. This
file can be replaced with one containing tags parsed from a different set of
header files. When <span class="application">Geany</span> is next started, your custom
tags file will be loaded instead of the default <code class="filename">global.tags</code>.
You should keep a copy of the generated
tags file because it will get overwritten when upgrading
<span class="application">Geany</span>.
</p><p>This is a temporary solution - in later versions this will be unnecessary.
</p></div><p>
</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s06.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s08.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Search, replace and go to </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Preferences</td></tr></table></div></body></html>

48
doc/html/ch03s08.html
View File

@ -1,48 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Preferences</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s07.html" title="Tags"><link rel="next" href="ch03s09.html" title="Project Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Preferences</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s07.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s09.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="prefs"></a>Preferences</h2></div></div></div><p>
You may adjust Geany's settings using the Edit --&gt; Preferences dialog. Any
changes you make there can be applied by hitting either the Apply or the Ok
button. These settings will persist between Geany sessions. Note that most
settings here have descriptive popup bubble help -- just hover the mouse
over the item in question to get help on it.
</p><p>
You may also adjust some View settings (under the View menu) that persist
between Geany sessions. The settings under the Document menu, however, are
only for the current document and revert to defaults when restarting Geany.
</p><p>
Note, in the paragraphs that follow, the text describing a dialog tab
(if present) comes after the screenshot of that tab.
</p><p>
</p><p>
</p><div class="figure"><a name="prefs_gen"></a><p class="title"><b>Figure 3.4. General tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_gen.png" alt="General tab in preferences dialog"></div></div></div><p><br class="figure-break">
<span class="emphasis"><em>The "Context Activation" setting needs to be documented.</em></span>
</p><p>
</p><div class="figure"><a name="id2811878"></a><p class="title"><b>Figure 3.5. Interface tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_interface.png" alt="Interface tab in preferences dialog"></div></div></div><p><br class="figure-break">
The open files list and the editor tabs are two different ways to switch
between documents using the mouse. When you hit the key combination to
move between tabs, the order is determined by the tab order, not alphabetical
as shown in the open files list (regardless whether or not editor tabs are
visible).
</p><p>
</p><div class="figure"><a name="id2811901"></a><p class="title"><b>Figure 3.6. Toolbar tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_toolbar.png" alt="Toolbar tab in preferences dialog"></div></div></div><p><br class="figure-break">
</p><p>
</p><div class="figure"><a name="id2811918"></a><p class="title"><b>Figure 3.7. Files tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_files.png" alt="Files tab in preferences dialog"></div></div></div><p><br class="figure-break">
</p><p>
</p><div class="figure"><a name="id2811935"></a><p class="title"><b>Figure 3.8. Editor tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_edit.png" alt="Editor tab in preferences dialog"></div></div></div><p><br class="figure-break">
Line wrapping refers to the display of the text in the editor. Currently,
there is no setting to have Geany automatically insert newlines into your
document while you type.
</p><p>
</p><div class="figure"><a name="id2811956"></a><p class="title"><b>Figure 3.9. Tools tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_tools.png" alt="Tools tab in preferences dialog"></div></div></div><p><br class="figure-break">
</p><p>
</p><div class="figure"><a name="prefs_templ"></a><p class="title"><b>Figure 3.10. Template tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_templ.png" alt="Template tab in preferences dialog"></div></div></div><p><br class="figure-break">
</p><p>
</p><div class="figure"><a name="prefs_keys"></a><p class="title"><b>Figure 3.11. Keybinding tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_keys.png" alt="Keybinding tab in preferences dialog"></div></div></div><p><br class="figure-break">
There are some handy commands in here that are not, by default, bound to a key
combination, and may in fact not even be available as a menu item (for example, the
very handy "Hide and show all additional widgets").
</p><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>For more information see <a href="ch03s12.html" title="Keybindings">the section called “Keybindings”</a>.</p></div><p>
</p><div class="figure"><a name="prefs_vte"></a><p class="title"><b>Figure 3.12. VTE tab in preferences dialog</b></p><div class="figure-contents"><div><img src="images/pref_dialog_vte.png" alt="VTE tab in preferences dialog"></div></div></div><p><br class="figure-break">
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s07.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s09.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Tags </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Project Management</td></tr></table></div></body></html>

40
doc/html/ch03s09.html
View File

@ -1,40 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Project Management</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s08.html" title="Preferences"><link rel="next" href="ch03s10.html" title="Build system"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Project Management</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s08.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s10.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="project_management"></a>Project Management</h2></div></div></div><p>
Project Management is optional in <span class="application">Geany</span>.
Currently it can be used for:
</p><div class="itemizedlist"><ul type="disc"><li><p>Running <span class="emphasis"><em>Make</em></span> from the project's base
directory.</p></li><li><p>Setting a custom <span class="emphasis"><em>Run</em></span> command specific to
the project.</p></li></ul></div><p>
</p><p>
As long as a project is open, the Make and Run commands will use the project's
settings, instead of the defaults. These will be used whichever document is
currently displayed.
</p><p>
The current project's settings are saved when it is closed, or when
<span class="application">Geany</span> is shutdown.
When restarting <span class="application">Geany</span>, the previously opened project file
that was in use at the end of the last session will be reopened.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812116"></a>New Project</h3></div></div></div><p>
To create a new project, fill in the <span class="emphasis"><em>Name</em></span> field. By default
this will setup a new project file <code class="filename">~/projects/name.geany</code>.
Usually it's best to store all your project files in the same directory
(they are independent of any source directory trees).
</p><p>
The <span class="emphasis"><em>Base path</em></span> text field is setup to use
<code class="filename">~/projects/name</code>. This can safely be set to any existing path
- it will not touch the file structure contained in it.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812155"></a>Project Properties</h3></div></div></div><p>
You can set an optional description for the project, but it is not used elsewhere by
<span class="application">Geany</span>.
</p><p>
The <span class="emphasis"><em>Base path</em></span> field is used as the directory to run the
Make command in.
</p><p>
The <span class="emphasis"><em>Run</em></span> command overrides the default run command. You can
set this to the executable or main script file for the project, and append any
command-line arguments.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812191"></a>Close Project</h3></div></div></div><p>
Project file settings are saved when the project is closed.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812202"></a>Open Project</h3></div></div></div><p>
The <span class="emphasis"><em>Open</em></span> command displays a standard file chooser, starting
in <code class="filename">~/projects</code>.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s08.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Preferences </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Build system</td></tr></table></div></body></html>

102
doc/html/ch03s10.html
View File

@ -1,102 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Build system</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s09.html" title="Project Management"><link rel="next" href="ch03s11.html" title="Printing support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Build system</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s09.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s11.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="build_system"></a>Build system</h2></div></div></div><p>
<span class="application">Geany</span> has an integrated build system.
Firstly this means that the current source file will be saved before
it is processed. This is for convenience so that you don't need to keep saving
small changes to the current file before building.
</p><p>
Secondly the output for Compile, Build and Make actions will be captured
in the Compiler notebook tab of the messages window (assuming you have it visible).
If there are any warnings or errors with line numbers shown in the Compiler output tab,
you can double click on them and <span class="application">Geany</span> will switch to
the relevant source file (if it is open) and mark the line number so the problem
can be corrected. <span class="application">Geany</span> will also set indicators for
warnings or errors with line numbers.
</p><p>
Depending on the current file's filetype, the Build menu will contain the following
items:
</p><div class="itemizedlist"><ul type="disc"><li><p>Compile</p></li><li><p>Build</p></li><li><p>Make all</p></li><li><p>Make custom target</p></li><li><p>Make object</p></li><li><p>Execute</p></li><li><p>Set Includes and Arguments</p></li></ul></div><p>
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812310"></a>Compile</h3></div></div></div><p>
The Compile command has different uses for different kinds of files.
</p><p>
For compilable languages such as C and C++, the Compile command is setup
to compile the current source file into a binary object file.
</p><p>
Java source files will be compiled to class file bytecode.
Interpreted languages such as Perl, Python, Ruby will
compile to bytecode if the language supports it, or will run a syntax check,
or failing that will run the file in its language interpreter.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812335"></a>Build</h3></div></div></div><p>
For compilable languages such as C and C++, the Build command will link the
current source file's equivalent object file into an executable. If the object
file does not exist, the source will be compiled and linked in one step,
producing just the executable binary.
</p><p>
Interpreted languages do not use the Build command.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812354"></a>Make all</h3></div></div></div><p>
This effectively runs "make all" in the same directory as the current file.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
For each of the Make commands, The Make tool path must be correctly set
in the Tools tab of the Preferences dialog.
</p></div><p>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812373"></a>Make custom target</h3></div></div></div><p>
This is similar to running 'Make all' but you will be prompted
for the make target name to be passed to the Make tool. For example,
typing 'clean' in the dialog prompt will run "make clean".
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812386"></a>Make object</h3></div></div></div><p>
Make object will run "make current_file.o" in the same directory as the current
file, using its prefix for 'current_file'. It is useful for compiling just the
current file without building the whole project.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812400"></a>Execute</h3></div></div></div><p>
Execute will run the corresponding executable file, shell script or interpreted
script in a terminal window. Note that the Terminal tool path must be correctly
set in the Tools tab of the Preferences dialog - you can use any terminal
program that runs a Bourne compatible shell and accept the "-e" command line
argument to start a command.
</p><p>
After your program or script has finished executing, you will be prompted to
press the return key. This allows you to review any text output from the program
before the terminal window is closed.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812423"></a>Stopping running processes</h3></div></div></div><p>
When there is a running program, the Run button in the
toolbar becomes a stop button and you can stop the current action. This works
by sending a signal to the process (and its child process(es)) to stop the
process. The used signal is SIGQUIT.
</p><p>
Depending on the process you started it might occur that the process cannot be
stopped. This can happen when the process creates more than one child process.
Therefore stopping any make actions is not possible because make creates child
processes and these child processes creates again child process. There might be
some other programs which cannot be stopped correctly. Xterm is known to work
properly. If you are using "Terminal" (the terminal program of Xfce), you
should add the command line option "--disable-server" otherwise the started
process cannot be stopped. Just add this option in the preferences dialog on
the Tools tab in the terminal field.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812465"></a>Set Includes and Arguments</h3></div></div></div><p>
By default the Compile and Build commands invoke the compiler and linker with
only the basic arguments needed by all programs.
Using Set Includes and Arguments you can add any include
paths and compile flags for the compiler, any library names and paths for the
linker, and any arguments you want to use when running Execute.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
If you are using the Build command to compile and link in one step, you will need
to set both the compiler arguments and the linker arguments in the linker
command setting.
</p></div><p>
These settings are not saved when <span class="application">Geany</span> is shut
down. See below for how to set permanent arguments.
</p><p>
If you need complex settings for your build system, or several different
settings, then writing a Makefile and using the Make commands is recommended.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812506"></a>Indicators</h3></div></div></div><p>
Indicators are red squiggly underlines which are used to highlight errors which
occured while compiling the current file. So you can easily see where your code
failed to compile. To remove the indicators, just click on
"Remove all indicators" in the document file menu.
</p><p>
If you do not like this feature, you can disable it in the preferences dialog.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2812526"></a>File type configuration settings</h3></div></div></div><p>
You can set the commands to run for compiling, building or executing
by opening the relevant <code class="filename">filetypes.*</code> configuration file,
and checking the [build_settings] section. See <a href="ch04.html#filetypes" title="Filetype definition files">the section called “Filetype definition files”</a> for more
information.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s09.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s11.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Project Management </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Printing support</td></tr></table></div></body></html>

20
doc/html/ch03s11.html
View File

@ -1,20 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Printing support</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s10.html" title="Build system"><link rel="next" href="ch03s12.html" title="Keybindings"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Printing support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s10.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch03s12.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="printing"></a>Printing support</h2></div></div></div><p>
<span class="application">Geany</span> has basic printing support. This means you can
print a file by passing the filename of the current file to a command which actually
prints the file. However, the printed document contains no syntax highlighting.
You can adjust the command to which the filename is passed in the preferences dialog.
The default command is:
</p><pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">lpr</strong></span> %f</code></strong></pre><p>
%f will be substituted by the filename of the current file.
<span class="application">Geany</span> will not show errors from the command itself, so
you should make sure that it works before(e.g. by trying to execute it from the
command line).
</p><p>
A nicer example, which I prefer is:
</p><pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">a2ps</strong></span> -1 --medium=A4 -o - %f | xfprint4</code></strong></pre><p>
But this depends on a2ps and xfprint4. As a replacement for xfprint4, gtklp or similar
programs can be used.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
The printing support of <span class="application">Geany</span> will be improved in the
future. With GTK 2.10, better printing (including syntax highlighting) will be possible.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s10.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s12.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Build system </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Keybindings</td></tr></table></div></body></html>

73
doc/html/ch03s12.html
View File

@ -1,73 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Keybindings</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch03.html" title="Chapter 3. Usage"><link rel="prev" href="ch03s11.html" title="Printing support"><link rel="next" href="ch04.html" title="Chapter 4. Configuration files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Keybindings</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s11.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Usage</th><td width="20%" align="right"> <a accesskey="n" href="ch04.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="keybindings"></a>Keybindings</h2></div></div></div><p>
<span class="application">Geany</span> supports the default keyboard shortcuts for the
Scintilla editing widget. For a list of these commands, see
<a href="apb.html" title="Appendix B. Scintilla keyboard commands">Appendix B, <i>Scintilla keyboard commands</i></a>.
The Scintilla keyboard shortcuts will be overridden by any custom keybindings
with the same keyboard shortcut.
</p><p>
For all actions listed below you can define your own keybindings. Open the Preferences
dialog, select the desired action and click on change. In the opening dialog you can
press any key combination you want and it will be saved when you press OK.
You can define only one key combination for one action.
</p><p>
Some of the default key combinations cannot be changed, e.g. menu_new or menu_open.
These are set by GTK and should be kept, but you can still add other key
combinations for these actions. For example to execute menu_open by default
<span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">O</strong></span> is set, but you can
also define <span><strong class="keycap">Alt</strong></span>-<span><strong class="keycap">O</strong></span>, so that the
file open dialog is shown by pressing either
<span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">O</strong></span> or
<span><strong class="keycap">Alt</strong></span>-<span><strong class="keycap">O</strong></span>.
</p><p>
The following table lists all customizable keyboard shortcuts.
</p><p>
</p><div class="table"><a name="id2812755"></a><p class="title"><b>Table 3.3. Keybindings action table</b></p><div class="table-contents"><table summary="Keybindings action table" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col></colgroup><thead><tr><th>Action</th><th>Description</th></tr></thead><tbody><tr><td colspan="2" align="left">Menu items</td></tr><tr><td>New</td><td>Creates a new file.</td></tr><tr><td>Open</td><td>Opens a file.</td></tr><tr><td>Save</td><td>Saves the current file.</td></tr><tr><td>Save As</td><td>Saves the current file under a new name.</td></tr><tr><td>Save all</td><td>Saves all open files.</td></tr><tr><td>Close all</td><td>Closes all open files.</td></tr><tr><td>Close</td><td>Closes the current file.</td></tr><tr><td>Reload file</td><td>Reloads the current file. All unsaved changes will be lost.
</td></tr><tr><td>Print</td><td>Prints the current file.</td></tr><tr><td>Undo</td><td>Undoes the last action.</td></tr><tr><td>Redo</td><td>Redoes the last action.</td></tr><tr><td>Select all</td><td>Makes a selection of all text in the current document.
</td></tr><tr><td>Insert date</td><td>Inserts a customisable date.</td></tr><tr><td>Preferences</td><td>Opens preferences dialog.</td></tr><tr><td>Find Next</td><td>Finds next result.</td></tr><tr><td>Find Previous</td><td>Finds previous result.</td></tr><tr><td>Replace</td><td>Opens the Replace dialog.</td></tr><tr><td>Find in files</td><td>Opens the Find in files dialog.</td></tr><tr><td>Next message</td><td>Jumps to the line with the next message from the last call
to Find usage.</td></tr><tr><td>Go to line</td><td>Opens the Go to line dialog.</td></tr><tr><td>Show Colour Chooser</td><td>Opens the Colour Chooser dialog.</td></tr><tr><td>Fullscreen</td><td>Switches to fullscreen mode.</td></tr><tr><td>Toggle Messages Window</td><td>Toggles the message window (status and compiler messages)
on and off.
</td></tr><tr><td>Toggle Sidebar</td><td>Shows or hides the sidebar.</td></tr><tr><td>Toggle all additional widgets</td><td>Hide and show all additional widgets like the notebook tabs,
the toolbar, the messages window and the statusbar.</td></tr><tr><td>Zoom In</td><td>Zooms in the text</td></tr><tr><td>Zoom Out</td><td>Zooms out the text</td></tr><tr><td>Replace tabs by space</td><td>Replaces all tabs with the right amount of spaces.</td></tr><tr><td>Fold all</td><td>Folds all contractible code blocks.</td></tr><tr><td>Unfold all</td><td>Unfolds all contracted code blocks.</td></tr><tr><td colspan="2" align="left">Build options</td></tr><tr><td>Compile</td><td>Compiles the current file.</td></tr><tr><td>Build</td><td>Builds (compiles if necessary and links) the current file.
</td></tr><tr><td>Make all</td><td>Builds the current file with the Make tool.</td></tr><tr><td>Make custom target</td><td>Builds the current file with the Make tool and a given target.
</td></tr><tr><td>Make object</td><td>Compiles the current file with the Make tool.
</td></tr><tr><td>Next error</td><td>Jumps to the line with the next error from the last build
process.
</td></tr><tr><td>Run</td><td>Executes the current file in a terminal emulation.</td></tr><tr><td>Run (alternative command)</td><td>Executes the current file in a terminal emulation.</td></tr><tr><td>Build options</td><td>Opens the build options dialog.</td></tr><tr><td colspan="2" align="left">Miscellaneous</td></tr><tr><td>Reload symbol list</td><td>Reloads the tag/symbol list.</td></tr><tr><td>Switch to Editor</td><td>Switches to editor widget.</td></tr><tr><td>Switch to Scribble</td><td>Switches to scribble widget.</td></tr><tr><td>Switch to VTE</td><td>Switches to VTE widget.</td></tr><tr><td>Switch to Search Bar</td><td>Switches to the search bar in the toolbar (if visible).</td></tr><tr><td>Switch to left document</td><td>Switches to the previous open document.</td></tr><tr><td>Switch to right document</td><td>Switches to the next open document.</td></tr><tr><td>Switch to last used document</td><td>Switches to the previously selected open document.</td></tr><tr><td colspan="2" align="left">Editing operations</td></tr><tr><td>Convert selection to lower case</td><td>Converts the current selection to lower case.</td></tr><tr><td>Convert selection to upper case</td><td>Converts the current selection to upper case.</td></tr><tr><td>Duplicate line or selection</td><td>Duplicates the current line or selection.</td></tr><tr><td>Comment line</td><td>Comments current line or selection.</td></tr><tr><td>Uncomment line</td><td>Uncomments current line or selection.</td></tr><tr><td>Toggle line commentation</td><td>Comments a line if it is not commented or removes a comment
if the line is commented.</td></tr><tr><td>Increase indent</td><td>Indents the current line or selection by one tabulator.</td></tr><tr><td>Decrease indent</td><td>Removes one tabulator from the indentation of the current
line or selection.</td></tr><tr><td>Goto matching brace</td><td>If the cursor is ahead or behind a brace, then it is moved to
the brace which belongs to the current one. If this keyboard
shortcut is pressed again, the cursor is moved back to the
first brace.</td></tr><tr><td>Toggle marker</td><td>Set a marker on the current line, or clear the marker if there
already is one.</td></tr><tr><td>Goto next marker</td><td>Goto the next marker in the current document.</td></tr><tr><td>Goto previous marker</td><td>Goto the previous marker in the current document.</td></tr><tr><td>Complete word</td><td>Shows auto completion list.</td></tr><tr><td>Show calltip</td><td>Shows call tips for the current function or method.</td></tr><tr><td>Show macro list</td><td>Shows a list of available macros and
variables in the workspace.
</td></tr><tr><td>Complete construct</td><td>If you type a construct like <code class="literal">if</code> or
<code class="literal">for</code> and press this key, it
will be completed with a matching template.
</td></tr><tr><td>Suppress construct completion</td><td>If you type a construct like <code class="literal">if</code> or
<code class="literal">for</code> and press this key, it
will not be completed, and a space or tab will be inserted,
depending on what the construct completion keybinding is set to.
For example, if you have set the
construct completion keybinding to <code class="literal">space</code>,
then setting this to <code class="literal">Shift+space</code> will
prevent construct completion and insert a space.
</td></tr><tr><td>Select current word</td><td>Selects the current word under the cursor.
</td></tr><tr><td>Insert alternative whitespace</td><td>Inserts a tabulator character when spaces should be used for
indentation and inserts space characters of the amount of a
tabulator width when tabulators should be used for
indentation.
</td></tr><tr><td>Find Usage</td><td>Finds all occurrences of the current word (near the keyboard
cursor) or selection and displays them in the messages window.
</td></tr><tr><td>Go to tag definition</td><td>Jump to the definition of the current word (near the
keyboard cursor). If the definition cannot be found (e.g. the
relevant file is not open) <span class="application">Geany</span>
will beep and do nothing. See <a href="ch03s06.html#search_gototag" title="Go to tag definition">the section called “Go to tag definition”</a>.
</td></tr><tr><td>Go to tag declaration</td><td>Jump to the declaration of the current word (near the
keyboard cursor). If the declaration cannot be found (e.g. the
relevant file is not open) <span class="application">Geany</span>
will beep and do nothing. See <a href="ch03s06.html#search_gototag" title="Go to tag definition">the section called “Go to tag definition”</a>.
</td></tr><tr><td>Context Action</td><td>Executes a command and passes the current word (near the
cursor postion) or selection as an argument. See
<a href="ch03s05.html#editing_context_actions" title="Context actions">the section called “Context actions”</a>.
</td></tr></tbody></table></div></div><p><br class="table-break">
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s11.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Printing support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Configuration files</td></tr></table></div></body></html>

203
doc/html/ch04.html
View File

@ -1,203 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 4. Configuration files</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="index.html" title="Geany 0.11"><link rel="prev" href="ch03s12.html" title="Keybindings"><link rel="next" href="ch04s02.html" title="Filetype extensions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Configuration files</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s12.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch04s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="config_files"></a>Chapter 4. Configuration files</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch04.html#filetypes">Filetype definition files</a></span></dt><dd><dl><dt><span class="section"><a href="ch04.html#filetypes_format">Format</a></span></dt><dt><span class="section"><a href="ch04.html#filetypes_common">Special file filetypes.common</a></span></dt></dl></dd><dt><span class="section"><a href="ch04s02.html">Filetype extensions</a></span></dt><dt><span class="section"><a href="ch04s03.html">Templates</a></span></dt><dd><dl><dt><span class="section"><a href="ch04s03.html#id2814807">Template metadata</a></span></dt><dt><span class="section"><a href="ch04s03.html#id2814839">Filetype templates</a></span></dt><dt><span class="section"><a href="ch04s03.html#id2814943">Customizing templates</a></span></dt></dl></dd></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="filetypes"></a>Filetype definition files</h2></div></div></div><p>
All colour definitions and other filetype specific settings are stored in the
filetype definition files. Those settings are colours for syntax highlighting,
general settings like comment characters or word delimiter characters as well as
compiler and linker settings.
</p><p>
The system-wide configuration files can be found in
<code class="filename">$prefix/share/geany</code> and are called
<code class="filename">filetypes.$ext</code>, where $prefix is the path where
<span class="application">Geany</span> is installed (commonly
<code class="filename">/usr/local</code>) and $ext is the name of the filetype.
For every filetype there is a corresponding definition file. There is one exception:
<code class="filename">filetypes.common</code> - this file is for general settings, which
are not specific to a certain filetype. It is not recommended to edit the
system-wide files, because they will be overridden when
<span class="application">Geany</span> is updated.
</p><p>
To change the settings, copy a file from <code class="filename">$prefix/share/geany</code>
to the subdirectory <code class="filename">filedefs</code> in your configuration directory
(usually <code class="filename">~/.geany/</code>).
</p><p>
For example:
</p><pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">cp /usr/local/share/geany/filetypes.c /home/username/.geany/filedefs/</strong></span></code></strong></pre><p>
Then you can edit the file and the changes are also available after an update of
<span class="application">Geany</span> because they reside in your configuration
directory. Alternatively, you can create a file
<code class="filename">~/.geany/filedefs/filetypes.X</code> and add only these settings you
want to change. All missing settings will be read from the corresponding global
definition file in <code class="filename">$prefix/share/geany</code>.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="filetypes_format"></a>Format</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2813862"></a>[styling] Section</h4></div></div></div><p>
In this section the colours for syntax highlighting are defined.
The format is always:
<code class="constant">key=forground_colour;background_colour;bold;italic</code>
</p><p>
Colours have to be specified as RGB hex values prefixed by 0x. For
example red is 0xff0000, blue is 0x0000ff. The values are case-insensitive,
but it is a good idea to use small letters. Bold and italic are flags and
should only be "true" or "false". If their value is something other than
"true" or "false", "false" is assumed.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2813887"></a>[keywords] Section</h4></div></div></div><p>
This section contains keys for different keyword lists specific to the
filetype. Some filetypes do not support keywords, so adding a new key will
not work. You can only add or remove keywords to/from an existing list.
</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>The keywords list must be in one line without line ending
characters.</p></div><p>
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2813907"></a>[settings] Section</h4></div></div></div><p>
</p><div class="table"><a name="id2813915"></a><p class="title"><b>Table 4.1. General settings</b></p><div class="table-contents"><table summary="General settings" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Key</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>wordchars</td><td>
These characters define word boundaries when
making selections and searching using word matching
options.
</td><td>(look at system filetypes.* files)</td></tr><tr><td>comment_open</td><td>A character or string which is used to comment code.
If you want to use multiline comments, also set
comment_close, otherwise leave it empty.
</td><td>comment_open=/*</td></tr><tr><td>comment_close</td><td>If multiline comments are used, this is the character
or string to close the comment.
</td><td>comment_close=*/</td></tr><tr><td>comment_use_indent</td><td>Set this to false if a comment character or string
should start at column 0 of a line. If set to true
it uses any indentation of the line.
<div class="example"><a name="id2814014"></a><p class="title"><b>Example 4.1. Comment indentation</b></p><div class="example-contents"><p>
comment_use_indent=true would generate this if a line
is commented (e.g. with
<span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">D</strong></span>)
</p><pre class="programlisting"> #command_example();</pre><p>
comment_use_indent=false would generate this if a line
is commented (e.g. with
<span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">D</strong></span>)
</p><pre class="programlisting"># command_example();</pre><p>
</p></div></div><p><br class="example-break"></p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
This setting only works for single line comments
(like '//', '#' or ';').
</p></div>
</td><td>comment_use_indent=true</td></tr><tr><td>context_action_cmd</td><td><p>
A command which can be executed on a certain word or
the current selection. Example usage: Open the API
documentation for the current function call at the
cursor position. The command can be set for every
filetype or if not set, a global command will be used.
The command itself can be specified without the full
path, then it is searched in $PATH. But for security
reasons, it is recommended to specify the full path
to the command. The wildcard %s will be replaced
by the current word at the cursor position or by
the current selection.
</p>
<p>
Hint: for PHP files the following could be quite
useful:
<span class="emphasis"><em>
context_action_cmd=firefox "http://www.php.net/%s"
</em></span>
</p>
</td><td>context_action_cmd=devhelp -s "%s"</td></tr></tbody></table></div></div><p><br class="table-break">
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2814121"></a>[build_settings] Section</h4></div></div></div><p>
</p><div class="table"><a name="id2814129"></a><p class="title"><b>Table 4.2. Build settings</b></p><div class="table-contents"><table summary="Build settings" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Key</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>compiler</td><td>
This item specifies the command to compile source code
files. But it is also possible to use it with
interpreted languages like Perl or Python. With these
filetypes you can use this option as a kind of syntax
parser, which sends output to the compiler message
window.
<p>You should quote the filename to also support
filenames with spaces. The following wildcards for
filenames are available:
</p>
<p>
</p><div class="itemizedlist"><ul type="disc"><li><p>
%f - complete filename without path
</p></li><li><p>
%e - filename without path and without extension
</p></li></ul></div><p>
</p>
</td><td>compiler=gcc -Wall -c "%f"</td></tr><tr><td>linker</td><td>This item specifies the command to link the file.
If the file is not already compiled, it will be
compiled while linking. The -o option is
automatically added by
<span class="application">Geany</span>. This item works
well with GNU gcc, but may be problematic with other
compilers (esp. with the linker).
</td><td>linker=gcc -Wall "%f"</td></tr><tr><td>run_cmd</td><td>Use this item to execute your file. It has to have been
built already.
Use the %e wildcard to have only the name of
the executable (i.e. without extension) or use the %f
wildcard if you need the complete filename, e.g.
for shell scripts.
</td><td>run_cmd="./%e"</td></tr></tbody></table></div></div><p><br class="table-break">
</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="filetypes_common"></a>Special file filetypes.common</h3></div></div></div><p>There is a special filetype definition file called
<code class="filename">filetypes.common</code>. This file defines some general
non-filetype-specific settings.
</p><p>
</p><div class="table"><a name="id2814282"></a><p class="title"><b>Table 4.3. General settings</b></p><div class="table-contents"><table summary="General settings" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Key</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>default</td><td>This is the default style. It is used for styling files
without a filetype set.
</td><td>default=0x000000;0xffffff;false;false</td></tr><tr><td>selection</td><td>
The style for colouring selected text.
The format is:
<div class="itemizedlist"><ul type="disc"><li><p>Foreground colour</p></li><li><p>Background colour</p></li><li><p>Use foreground colour</p></li><li><p>Use background colour</p></li></ul></div>
The colours are only set if the 3rd or 4th argument is true.
When the colours are not overridden, the default is a dark
grey background with syntax highlighted foreground text.
</td><td>selection=0xc0c0c0;0x00007F;true;true</td></tr><tr><td>brace_good</td><td>The style for brace highlighting when a
matching brace was found.
</td><td>brace_good=0xff0000;0xFFFFFF;true;false</td></tr><tr><td>brace_bad</td><td>The style for brace highlighting when no
matching brace was found.
</td><td>brace_bad=0x0000ff;0xFFFFFF;true;false</td></tr><tr><td>caret</td><td>The style for colouring the caret(the blinking cursor).
Only the first argument is interpreted.
</td><td>caret=0x000000;0x0;false;false</td></tr><tr><td>caret_width</td><td>The width for the caret(the blinking cursor).
Only the first argument is interpreted. The width is
specified in pixels with a maximum of three pixel.
Use the width 0 to make the caret invisible.
</td><td>caret=1;0;false;false</td></tr><tr><td>current_line</td><td>The style for colouring the background of the current
line. Only the second and third arguments are interpreted.
The second argument is the background colour.
Use the third argument to enable or disable background
highlighting for the current line (has to be true/false).
</td><td>current_line=0x0;0xe5e5e5;true;false</td></tr><tr><td>indent_guide</td><td>The style for colouring the indentation guides.
Only the first and second arguments are interpreted.
</td><td>indent_guide=0xc0c0c0;0xffffff;false;false</td></tr><tr><td>white_space</td><td>The style for colouring the white space if it is shown.
The first both arguments define the foreground and
background colours, the third argument sets whether to use
the defined foreground colour or to use the colour
defined by each filetype for the white space.
The fourth argument defines whether to use the background
colour.
</td><td>white_space=0xc0c0c0;0xffffff;true;true</td></tr><tr><td>folding_style</td><td>The style of folding icons. Only first and second
arguments are used.
<p>
Valid values for the first argument are:
</p><div class="itemizedlist"><ul type="disc"><li><p>
1 - for boxes
</p></li><li><p>
2 - for circles
</p></li></ul></div><p>
</p>
<p>
Valid values for the second argument are:
</p><div class="itemizedlist"><ul type="disc"><li><p>
1 - for straight lines
</p></li><li><p>
2 - for curved lines
</p></li></ul></div><p>
</p>
</td><td>folding_style=1;1;false;false</td></tr><tr><td>folding_horiz_line</td><td>Draw a thin horizontal line at the line where text is
folded. Only first argument is used.
<p>
Valid values for the first argument are:
</p><div class="itemizedlist"><ul type="disc"><li><p>
0 - disable, do not draw a line
</p></li><li><p>
1 - draw the line above folded text
</p></li><li><p>
2 - draw the line below folded text
</p></li></ul></div><p>
</p>
</td><td>folding_horiz_line=0;0;false;false</td></tr><tr><td>invert_all</td><td>Whether to invert all defined colours. This is useful
if you like a dark background colour(e.g. black) and do
not want to change every single line. Please note, at
time of writing this was only tested with the C syntax
highlighting.
<p>Only first argument is interpreted. Set it to 1 to
invert all colours.
</p>
</td><td>invert_all=0;0;false;false</td></tr></tbody></table></div></div><p><br class="table-break">
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s12.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch04s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Keybindings </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Filetype extensions</td></tr></table></div></body></html>

27
doc/html/ch04s02.html
View File

@ -1,27 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Filetype extensions</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch04.html" title="Chapter 4. Configuration files"><link rel="prev" href="ch04.html" title="Chapter 4. Configuration files"><link rel="next" href="ch04s03.html" title="Templates"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Filetype extensions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuration files</th><td width="20%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="filetype_extensions"></a>Filetype extensions</h2></div></div></div><p>
You can override the default extensions that <span class="application">Geany</span> uses
for each filetype using the <code class="filename">filetype_extensions.conf</code> file.
</p><p>
To override the system-wide configuration file,
copy it from <code class="filename">$prefix/share/geany</code> to your
configuration directory, usually <code class="filename">~/.geany/</code>.
$prefix is the path where
<span class="application">Geany</span> is installed (commonly
<code class="filename">/usr/local</code>).
</p><p>
For example:
</p><pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code><span><strong class="command">cp /usr/local/share/geany/filetype_extensions.conf /home/username/.geany/</strong></span></code></strong></pre><p>
</p><p>
Then edit it and remove all the lines for filetype extensions that you
do not want to override. The remaining lines can be edited after the
<code class="literal">=</code> sign, using a semi-colon separated list of patterns
which should be matched for that filetype.
</p><p>
For example, to set the filetype extensions for Make, the
<code class="filename">/home/username/.geany/filetype_extensions.conf</code>
file should look like:
</p><div class="literallayout"><p><code class="literal"><br>
[Extensions]<br>
Make=Makefile*;*.mk;Buildfile;<br>
</code></p></div><p>
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Configuration files </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Templates</td></tr></table></div></body></html>

78
doc/html/ch04s03.html
View File

@ -1,78 +0,0 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Templates</title><link rel="stylesheet" href="geany.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Geany 0.11"><link rel="up" href="ch04.html" title="Chapter 4. Configuration files"><link rel="prev" href="ch04s02.html" title="Filetype extensions"><link rel="next" href="apa.html" title="Appendix A. Contributing to this document"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Templates</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s02.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuration files</th><td width="20%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="templates"></a>Templates</h2></div></div></div><p>
<span class="application">Geany</span> supports the following templates:
</p><div class="itemizedlist"><ul type="disc"><li><p>ChangeLog entry</p></li><li><p>File header</p></li><li><p>Function description</p></li><li><p>Short GPL notice</p></li><li><p>Short BSD notice</p></li><li><p>Filetype template</p></li></ul></div><p>
To use these templates, just open the Edit menu or open the
popup menu by right-clicking in the editor widget, and choose "Insert Comments" and
insert templates as you want.
</p><p>
Some templates (like File header or ChangeLog entry) will always be inserted at the
top of the file.
</p><p>
To insert a function description, the cursor must be inside of the function, so that
the function name can be determined automatically. The description will be positioned
correctly one line above the function, just check it out. If the cursor is not inside
of a function or the function name cannot be determined, you cannot insert a function
description.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814807"></a>Template metadata</h3></div></div></div><p>
Metadata can be used with all templates, but by default user set metadata is only
used for the ChangeLog and File header templates.
</p><p>
In the configuration dialog you can find a tab "Templates"
(see <a href="ch03s08.html#prefs_templ" title="Figure 3.10. Template tab in preferences dialog">Figure 3.10, “Template tab in preferences dialog”</a>). You can define the default values which
will be inserted in the templates. You should restart <span class="application">Geany</span>
after making changes, because they are only read at startup.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814839"></a>Filetype templates</h3></div></div></div><p>
Filetype templates are templates used as the basis of a new file. To use them, choose
the <span class="emphasis"><em>New (with Template)</em></span> menu item from the
<span class="emphasis"><em>File</em></span> menu.
</p><p>
By default, templates are created for some filetypes. Other filetype templates can be
added by creating the appropriate template file and restarting
<span class="application">Geany</span>. You can also edit the default filetype templates.
</p><p>
Filetype template files are read from the <code class="filename">~/.geany/templates</code>
directory, and are named '<code class="filename">filetype.</code>'
followed by the filetype name, e.g. <code class="filename">filetype.python</code>,
<code class="filename">filetype.sh</code>. If you are unsure about the filetype name extensions,
they are the same as the filetype configuration file extensions, commonly installed
in <code class="filename">/usr/share/geany</code>, with the prefix
'<code class="filename">filetypes.</code>'.
</p><p>
The file's contents are just the text to place in the document, except for the
optional <code class="literal">{fileheader}</code> template wildcard. This can be placed anywhere,
but is usually on the first line of the file, followed by a blank line.
</p><p>
There is also a template file <code class="filename">template.none</code> which is used when
the <span class="emphasis"><em>New</em></span> command is used without a filetype. This is empty by
default.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2814943"></a>Customizing templates</h3></div></div></div><p>
Each template can be customized to your needs. The templates are stored in the
<code class="filename">~/.geany/templates/</code> directory (see <a href="ch03s02.html" title="Command line options">the section called “Command line options”</a>
for further information about the configuration directory). Just open the desired
template with an editor (ideally <span class="application">Geany</span> ;-) ) and edit
the template to your needs. There are some wildcards which will be automatically
replaced by <span class="application">Geany</span> at startup.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2814982"></a>Template wildcards</h4></div></div></div><p>
All wildcards must be enclosed by "{" and "}", e.g. {date}.
</p><p>
</p><div class="table"><a name="id2814994"></a><p class="title"><b>Table 4.4. Template wildcards</b></p><div class="table-contents"><table summary="Template wildcards" cellspacing="0" cellpadding="4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Wildcard</th><th>Description</th><th>Available in following templates</th></tr></thead><tbody><tr><td>developer</td><td>The name of the developer.</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>initial</td><td>The developer's initials, e.g. "ET" for
Enrico Tröger or "JFD" for John Foobar Doe.</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>mail</td><td>The email address of the developer.</td><td>file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>company</td><td>The company the developer is working for.</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>year</td><td>The current year in the format: YYYY</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>version</td><td>The initial version of a new file.</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>date</td><td>The current date in the format: YYYY-MM-DD</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>untitled</td><td>The string "untitled" (this will be translated to your locale),
used in filetype templates</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>geanyversion</td><td>The actual <span class="application">Geany</span> version,
e.g. "Geany 0.11"
</td><td>filetypes, file header, function description, ChangeLog entry,
bsd, gpl</td></tr><tr><td>datetime</td><td>The current date and time in the format: DD.MM.YYYY HH:mm:ss ZZZZ</td><td>file header, function description</td></tr><tr><td>filename</td><td>The filename of the current file. Only available for the file header template.</td><td>file header</td></tr><tr><td>gpl</td><td>This wildcard inserts a short GPL notice.</td><td>file header</td></tr><tr><td>bsd</td><td>This wildcard inserts a short BSD licence notice.</td><td>file header</td></tr><tr><td>functionname</td><td>The function name of the function at the cursor position.
This wildcard will only be replaced in the function
description template.</td><td>function description</td></tr><tr><td>fileheader</td><td>The file header template.
This wildcard will only be replaced in filetype
templates.</td><td>filetypes</td></tr></tbody></table></div></div><p><br class="table-break">
If you need any other wildcards or a special date/time format, please email the
author <code class="email">&lt;<a href="mailto:enrico.troeger@uvena.de">enrico.troeger@uvena.de</a>&gt;</code>.
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Filetype extensions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix A. Contributing to this document</td></tr></table></div></body></html>

97
doc/html/geany.css
View File

@ -1,97 +0,0 @@
body address
{
line-height: 1.3;
margin: .6em 0;
}
body blockquote
{
margin-top: .75em;
line-height: 1.5;
margin-bottom: .75em;
}
html body
{
margin: 1em 2% 1em 2%;
line-height: 1.2;
background-color: #ffffff;
}
body pre
{
margin: .75em 0;
line-height: 1.3;
color: #4f3f3f;
font-weight: bold;
}
body div
{
margin: 0;
}
dl
{
margin: .4em 0;
line-height: 1.2;
}
.legalnotice
{
font-size: small;
}
h1,h2,h3,h4,h5,h6,
div.example p b,
.question,
div.table p b,
div.procedure p b
{
color: #990000;
}
.option
{
color: #0000ca;
font-weight: bold;
}
.parameter
{
color: #007a00;
font-weight: bold;
}
a
{
color: #000000;
}
a:hover
{
color: #3c3c3c;
border-bottom: 1px solid #dc0000;
}
hr
{
background-color: #9c9c9c;
border-style: none;
height: 1px;
}
li
{
list-style-type: square;
}
.programlisting, .screen
{
background-color: #F8F9FD;
border-color: #907777;
border-width: 1px;
border-style: solid;
padding: 0.5em;
}

29
doc/html/index.html
View File

File diff suppressed because one or more lines are too long

8
doc/make_webable.sh
View File

@ -1,8 +0,0 @@
#!/bin/sh
# this converts the UTF-8 string in the Content-Type meta tag in all
# html files to lower case, otherwise some browsers
# (e.g. Mozilla Firefox) have problems to detect the right encoding
# if it is put through a webserver
sed -i 's/charset=UTF-8/charset=utf-8/g' html/*.html

185
doc/scikeybinding.docbook
View File

@ -1,185 +0,0 @@
<appendixinfo>
<title>Scintilla keyboard commands</title>
<pubdate>20 June 2006</pubdate>
<copyright>
<year>1998, 2006</year>
<holder>Neil Hodgson &lt;neilh@scintilla.org&gt;</holder>
</copyright>
<legalnotice>
<para>
This appendix is distributed under the terms of the License for
Scintilla and SciTE.
A copy of this license can be found in the file scintilla/License.txt
included with the source code of this
program and in the
appendix of this document.
See <xref linkend="scintilla-license"/>.
</para>
</legalnotice>
</appendixinfo>
<title>Scintilla keyboard commands</title>
<sect1>
<title>
Keyboard commands
</title>
<para>
<!-- Scintilla release 1.70, 20 June 2006 -->
Keyboard commands for Scintilla mostly follow common Windows and GTK+ conventions.
All move keys (arrows, page up/down, home and end)
allows to extend or reduce the stream selection when holding the Shift key,
and the rectangular selection when holding the Shift and Alt keys.
Some keys may not be available with some national keyboards or because
they are taken by the system such as by a window manager on GTK+.
Keyboard equivalents of menu commands are listed in the menus.
Some less common commands with no menu equivalent are:
</para>
<para>
<table frame="all">
<title>Scintilla keyboard commands</title>
<tgroup cols="2">
<?dbhtml cellpadding="4" ?>
<?dbhtml cellspacing="0" ?>
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
<spanspec spanname="hspan" namest="col1" nameend="col2" align="center"/>
<thead>
<row>
<entry>Action</entry>
<entry>Shortcut key</entry>
</row>
</thead>
<tbody>
<row>
<entry>Magnify text size.</entry><entry>Ctrl+Keypad+</entry>
</row>
<row>
<entry>Reduce text size.</entry><entry>Ctrl+Keypad-</entry>
</row>
<row>
<entry>Restore text size to normal.</entry><entry>Ctrl+Keypad/</entry>
</row>
<!--
<row>
<entry>Cycle through recent files.</entry><entry>Ctrl+Tab</entry>
</row>
-->
<row>
<entry>Indent block.</entry><entry>Tab</entry>
</row>
<row>
<entry>Dedent block.</entry><entry>Shift+Tab</entry>
</row>
<row>
<entry>Delete to start of word.</entry><entry>Ctrl+BackSpace</entry>
</row>
<row>
<entry>Delete to end of word.</entry><entry>Ctrl+Delete</entry>
</row>
<row>
<entry>Delete to start of line.</entry><entry>Ctrl+Shift+BackSpace</entry>
</row>
<row>
<entry>Delete to end of line.</entry><entry>Ctrl+Shift+Delete</entry>
</row>
<row>
<entry>Go to start of document.</entry><entry>Ctrl+Home</entry>
</row>
<row>
<entry>Extend selection to start of document.</entry><entry>Ctrl+Shift+Home</entry>
</row>
<row>
<entry>Go to start of display line.</entry><entry>Alt+Home</entry>
</row>
<row>
<entry>Extend selection to start of display line.</entry><entry>Alt+Shift+Home</entry>
</row>
<row>
<entry>Go to end of document.</entry><entry>Ctrl+End</entry>
</row>
<row>
<entry>Extend selection to end of document.</entry><entry>Ctrl+Shift+End</entry>
</row>
<row>
<entry>Go to end of display line.</entry><entry>Alt+End</entry>
</row>
<row>
<entry>Extend selection to end of display line.</entry><entry>Alt+Shift+End</entry>
</row>
<!--
<row>
<entry>Expand or contract a fold point.</entry><entry>Ctrl+Keypad*</entry>
</row>
<row>
<entry>Create or delete a bookmark.</entry><entry>Ctrl+F2</entry>
</row>
<row>
<entry>Go to next bookmark.</entry><entry>F2</entry>
</row>
<row>
<entry>Select to next bookmark.</entry><entry>Alt+F2</entry>
</row>
<row>
<entry>Find selection.</entry><entry>Ctrl+F3</entry>
</row>
<row>
<entry>Find selection backwards.</entry><entry>Ctrl+Shift+F3</entry>
</row>
-->
<row>
<entry>Scroll up.</entry><entry>Ctrl+Up</entry>
</row>
<row>
<entry>Scroll down.</entry><entry>Ctrl+Down</entry>
</row>
<row>
<entry>Line cut.</entry><entry>Ctrl+L</entry>
</row>
<row>
<entry>Line copy.</entry><entry>Ctrl+Shift+T</entry>
</row>
<row>
<entry>Line delete.</entry><entry>Ctrl+Shift+L</entry>
</row>
<row>
<entry>Line transpose with previous.</entry><entry>Ctrl+T</entry>
</row>
<row>
<entry>Selection duplicate.</entry><entry>Ctrl+D</entry>
</row>
<!--
<row>
<entry>Find matching preprocessor conditional, skipping nested ones.</entry><entry>Ctrl+K</entry>
</row>
<row>
<entry>Select to matching preprocessor conditional.</entry><entry>Ctrl+Shift+K</entry>
</row>
<row>
<entry>Find matching preprocessor conditional backwards, skipping nested ones.</entry><entry>Ctrl+J</entry>
</row>
<row>
<entry>Select to matching preprocessor conditional backwards.</entry><entry>Ctrl+Shift+J</entry>
</row>
-->
<row>
<entry>Previous paragraph. Shift extends selection.</entry><entry>Ctrl+[</entry>
</row>
<row>
<entry>Next paragraph. Shift extends selection.</entry><entry>Ctrl+]</entry>
</row>
<row>
<entry>Previous word. Shift extends selection.</entry><entry>Ctrl+Left</entry>
</row>
<row>
<entry>Next word. Shift extends selection.</entry><entry>Ctrl+Right</entry>
</row>
<row>
<entry>Previous word part. Shift extends selection</entry><entry>Ctrl+/</entry>
</row>
<row>
<entry>Next word part. Shift extends selection.</entry><entry>Ctrl+\</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</sect1>