This file documents Freetalk version 4.1. Freetalk is a freely available console based Jabber client-cum-bot powered by GNU Guile, GNU Readline and Loudmouth.
|• Overview:||These are features of Freetalk|
|• Invoking:||Command line arguments|
|• Commands:||List of Freetalk commands|
|• Customization:||Customizing Freetalk|
|• Tips and Tricks:||Cool tips and tricks|
Extension Developer Guide (Advanced)
|• Extension language:||About an extension language|
|• Procedures:||Freetalk exported Scheme primitives|
|• Hooks:||Freetalk exported Scheme hooks|
|• Learning further:||Guile and Scheme URLs|
|• Authors:||Freetalk contributors|
|• URLs:||Downloads, GIT|
|• Guidelines for submitting a patch:|
|• Portability:||Porting Freetalk|
|• Concept Index:|
|• Command Index:|
|• Procedure Index:|
Freetalk is a freely available console based Jabber client-cum-bot. It has many features, but to highlight,
historyfeature records all your conversions in ~/.freetalk/history/login-id/buddy-name.
Invoking Freetalk at command prompt is very simple. The following are the possible command-line arguments supported,
|• connect:||Connect to jabber server.|
|• disconnect:||Disconnect from the present server.|
|• server:||Specify the server to connect.|
|• jid:||Specify the jabber Id to connect.|
|• add:||Add Buddies in your buddy list.|
|• allow:||Allow a buddy to see your status.|
|• deny:||Deny permission to a buddy to see your status.|
|• quit:||quit Freetalk.|
|• restart:||restart Freetalk.|
|• prompt:||sets the prompt.|
|• pipe:||send the output of command as message.|
|• port:||set server port for next connect command.|
|• shell:||run or escape to shell.|
|• date:||date command.|
|• who:||view buddy list.|
|• whoami:||display current account info.|
|• version:||displays freetalk version information.|
|• logout:||same as disconnect.|
|• history:||display history page one by one.|
|• load:||load an extension file.|
|• setup:||setup a fresh ~/.freetalk|
|• login:||interactive to jabber server blocking.|
|• help:||displays help for all the commands.|
|• repl:||command used for debugging.|
|• urlview:||handle URL’s in message archives.|
|• freetalk:||check whether a buddy is using freetalk.|
|• greet:||IRC style greeting message.|
|• burst:||explode chars in the message.|
|• burst-of-romance:||simulate multiple hand-made kisses.|
|• broadcast:||broadcast a message to all the roster.|
|• proxyserver:||specify proxyserver for next connect.|
|• proxyport:||specify proxyport for next connect.|
Connect to the configured jabber server (see
~\/~ /connect Connecting... ~\/~
If server is not configured, it displays an error message and stops
~\/~ /connect Server not set ~\/~
Disconnect from the currently connected server.
~\/~ /disconnect Disconnected from server. Reason (0): User request ~\/~
Specify the servername which you want to connect, or display the currently set server.
~\/~ /server Current server: ~\/~ /server jabber.org ~\/~ /server Current server: jabber.org ~\/~
Specify the Jabber ID which you want to use, or display the currently set Jabber ID.
~\/~ /jid Current JID: ~\/~ /jid email@example.com ~\/~ /jid Current JID: firstname.lastname@example.org
This command is meant to be used when changing accounts and quick logins.
This command sends a buddy add request to user@domain into your buddy list.
~\/~ /add email@example.com ~\/~
Allow the user to see (“subscribe to”) your status. Note that this command does not add the user to your buddy list; if you must do that, use /add.
~\/~ /allow firstname.lastname@example.org
Deny the user permission to see (“subscribe to”) your status.
~\/~ /deny email@example.com
Quits Freetalk with a banner.
~\/~ /quit shell$
This command restarts Freetalk.
~\/~ /restart Loading dictionary [/usr/share/dict/words]...  words Jabber ID:
This command sets the prompt with specified type
~\/~ /prompt ~qp~ ~qp~
Pipe the output of command to buddy. options are passed to command.
~\/~> /pipe firstname.lastname@example.org ls -alh ~\/~>
/port command sets the specified TCP port to be used for the next
~\/~> /port 995 ~\/~>
/shell command executes the specified command with its
args. With no arguments,
/shell escapes to shell. You can
also chat with shell as if shell is your buddy. Just type
~\/~> /shell ls -lh /tmp total 12k drwxr-xr-x 3 root root 4.0k Jan 1 00:53 emacs-terminfo -rw-r--r-- 1 root root 1 Jan 1 05:04 emacsOdVut8 drwx------ 2 root root 4.0k Jan 1 00:13 xdvi7GIKqr ~\/~> /sh press C-d to return to freetalk $ rm -f /tmp/xdvi7GIKqr C-d RET ~\/~>
This command displays the system date. Try ‘--help’ for complete list of arguments.
This command displays the buddy list as well as their current buddy status.
~\/~ /who * email@example.com (friend) * firstname.lastname@example.org -> [Away] (on metarnity leave) ... ... ~\/~
Sets or displays your current status. Optionally also sets the resource priority.
~\/~ /status online Using Freetalk ~\/~ /status Current status: online Using Freetalk ~\/~ /status away/5 ~\/~
This command displays the currently logged in buddy info.
~\/~ /whoami ~\/~ /whoami Jabber ID: email@example.com Jabber Server: jabber.org Status: hacking ~\/~
This command displays the version information of the installed freetalk package.
~\/~ /version freetalk (Freetalk) 4.1 Copyright (C) 2005-2014 FreeTalk Core Team … ~\/~
This command works same as /disconnect but looks more meaningfull.
~\/~ /logout Disconnected from server, reason(0): User request ~\/~
This command displays paginated history with BUDDY. If BUDDY is not specified, it displays paginated history of only the current session.
~\/~ /history firstname.lastname@example.org Prints the history of messages with email@example.com paginated by
less. ~\/~ /history Prints this history of messages of the current session. ~\/~
This command loads the Scheme Extension file and executes it. SCM is the extension Scheme file written in Guile. This command helps for the better customization of the software.
SCM is first looked for in the current directory, followed by ~/.freetalk/extensions followed by the global prefix/share/freetalk/extensions.
SCM can also be an absolute path.
~\/~ /load beep.scm ~\/~
This command prepares a fresh ~/.freetalk directory with backing up the older one.
~\/~> /setup '/root/.freetalk' -> '/root/.freetalk-backup-0' Creating fresh state /root/.freetalk NOTE: Archived previous state to /root/.freetalk-backup-0 !!! ~\/~>
This command is the better interactive login than the normal login. This command should be followed by /disconnect if you are logged in.
~\/~ /login Jabber ID: firstname.lastname@example.org Password: Enable TLS/SSL (Y/N)? [Y]: y Port : 443 Connecting... ~\/~
This command prints help information on freetalk-command commands interatively in a sorted way.If no argument in given it prints the help for all the commands.
~\/~ /help /history /history - /history [BUDDY] Display history page by page ~\/~
This command helps in debugging. Invokes the guile interpreter resulting in the better debugging of the freetalk Scheme extension.
~\/~ /repl guile>(define ft-get-jid "email@example.com")
This command helps in viewing URL’s in the message archive or message coming from a particular BUDDY.More precisely this command catches URL or URL’s in the message and launches the browser to open the URL.
~\/~ /urlview firstname.lastname@example.org friend: https://www.gnu.org/software/freetalk/ ~\/~
This command helps in checking whether the other BUDDY is using freetalk or not.
~\/~ /freetalk email@example.com Yes firstname.lastname@example.org is using freetalk. ~\/~
Send IRC style greeting message to your BUDDY.
Example: email@example.com> /greet firstname.lastname@example.org On the other side email@example.com gets a message ``sssssssssssccccccrrrrrreeeeeeeeaaaaaaammmmmm''.
Explode MESSAGE in to multiple charactest (IRC style greeting) and send it to BUDDY.
Example: firstname.lastname@example.org> /burst email@example.com harsha On the other side firstname.lastname@example.org gets a message ``sssssssssssccccccrrrrrreeeeeeeeaaaaaaammmmmm''.
Send COUNT number of MESSAGE to BUDDY with random delays in between. This command is useful to simulate multiple hand-made kisses.
Example: email@example.com> /burst firstname.lastname@example.org 45 :-*
Send MESSAGE to all the buddies
Example: email@example.com> /broadcast "Hello All, I am back"
Specify the proxyservername which you want to connect, or display the currently set proxyserver.
~\/~ /proxyserver Current ProxyServer: ~\/~ /proxyserver tc.vip.org ~\/~ /proxyserver Current ProxyServer: tc.vip.org ~\/~
/proxyport command sets the specified TCP proxyport to be used
for the next
/connect or display the currently set proxyport
~\/~ /proxyport Current Port (8080 = default): 0 ~\/~ ~\/~ /proxyport 8080 ~\/~ /proxyport Current Port (8080 = default): 8080
freetalk can be customized to a great extent using Guile interface. User can herself/himself customize or extend new features in freetalk using Scheme as extension language. Most of the features are already written in Scheme.
|• freetalk.scm:||startup configuration file|
|• init.scm:||system wide initialization|
|• Default Scheme extensions:||default Scheme extensions|
If you want to extend freetalk yourself, you can further explore freetalk Extension Developer Guide. (see Extension language)
Freetalk loads the startup options from ~/.freetalk/freetalk.scm. Right from custom settings like username, password … to complete Scheme programming can be done in this file.
;; Sample ~/.freetalk/freetalk.scm ;; It sets connection parameters and tries to connect on ;; starting freetalk (and (strings=? (ft-get-jid) "") (ft-set-jid! "firstname.lastname@example.org") (ft-set-password! "f00b4r") (ft-set-sslconn! 1) (ft-set-server! "jabber.org") ;; Proxy support (ft-set-proxyserver! "your.proxy.org") (ft-set-proxyport! "8080"))
All entries in this file freetalk.scm are optional.How ever there is no limit of cutomizing this file using Guile Interface. (see Extension language)
All system wide policy settings and extensions are loaded through init.scm. By default you can find init.scm at /usr/share/freetalk/extensions/. To override this system wide init.scm file, copy it to ~/.freetalk/extensions/init.scm. You must be aware of what you are doing, before you mess up anything here.
(see Extension language)
Most of the freetalk features are available through Scheme extensions. To override these extensions, copy them from /usr/share/freetalk/extensions/ to ~/.freetalk/extensions/ and edit them.
(see Extension language)
You are free to use complete Readline keys inside freetalk. Frequently used Readline keys inside freetalk are,
|delete char backwards||C-h|
|delete word backwards||C-w|
|kill line backwards||C-u|
If you want to do further stunts, jump to Readline manual, See Readline in Readline.
An extension language is a programming language interpreter offered by an application program, so that users can write macros or even full-fledged programs to extend the original application. Extension languages have a C interface (it is usually C, but it could be any other compiled language), and can be given access to the C data structures. Likewise, there are C routines to access the extension language data structures.
This uses GNU extension language - Guile (which can stand for _GNU Ubiquitous Intelligent Language Extension_). Guile started out as an embeddable Scheme interpreter, and has rapidly evolved into a kitchen-sink package including a standalone Scheme interpreter, an embeddable Scheme interpreter, several graphics options, other languages that can be used along with Scheme (for now just _ctax_ and _Tcl_), and hooks for much more.
Freetalk avoids sharing of variables between C and Scheme environment. Everything is done through primitive procedures for clarity and control.
The following are the list of freetalk procedures that are exported to Scheme. Now you are able to call the procedures from Scheme that are written in C.
|• General procedures:||General Scheme primitives|
|• Configuration procedures:||Configuration Scheme primitives|
|• Hook related procedures:||Hook related Scheme primitives|
|• Utility procedures:||Utility Scheme primitives|
Loads and evaluates filepath.scm from mentioned path or from ~/.freetalk/extensions/ or from /usr/share/freetalk/extensions/.
Adds buddy into your contact list.
Gets jabberid from the console.
(and (string=? (ft-get-jid) "") …)
Set defaultid as the Jabber ID to be used on the next connect.
Gets the status of the connection from the server. 0 - Not connected. 1 - Connected, Not authenticated. 2 - Authenticated. (usable for IM)
Gets the currently set password.
(and (string=? (ft-get-password) …)
Get the servername configured for the next connection.
(and (string=? (ft-get-server) "") …)
Set the value such that login is in SSL mode or not.
Set the value such that login is in TLS mode or not.
Sends message to the buddy.
(ft-send-message "email@example.com" "had breakfast? or was it lunch?")
Prints the message in the console. Unlike the
primitive, this procedure takes care of printing message
asynchronously keeping the readline state as-is.
(ft-display ("I am proud of freetalk"))
Binds CTRL+ given char to arbitrary scm command. Allows for displaying roster or whatever by just pressing a key even during composition of new messages, keeping the readline state as-is.
(ft-bind-to-ctrl-key #\a "(/who \"all\")")
Makes the calling procedure return immediately after running the hooks.
These are general purpose utility procedures written completly in Scheme.
Through Hooks facility Freetalk lets you steal its control at various important junctures during execution.
Hook procedure is called with buddy and message as arguments on every send message operation.
Hook procedure is called with buddy and message as arguments on every receive message operation.
Hook procedure is called with buddy, message and timestamp recieve the presence.
The following are the URLs where you can find useful manuals for Guile and Scheme.
We believe in Software Freedom and Ethics, the GNU’s way.
You are welcome to send bug reports about freetalk to firstname.lastname@example.org. The bugs that you think are of the interest to the public (i.e. more people should be informed about them) can be Cc-ed to the above mailing lists.
Before actually submitting a bug report, please try to follow a few simple guidelines.
Send your specific queries to email@example.com
Since freetalk uses GNU Autoconf for building and configuring, and avoids using ‘special’ ultra–mega–cool features of any particular Unix, it should compile (and work) on all common Unix flavors.
Various freetalk versions have been compiled and tested under GNU/Linux. However freetalk can be easily ported to any POSIX complaint platform with Guile and Readline ports. If you compile it on an architecture not listed here, please let us know so that we can update it. (see URLs)
|• Freetalk License:|
|• Freetalk Documentation License:|
Freetalk licensed under GNU General Public License v3 or later.
Copyright © 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
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.
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.
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.
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.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
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.
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.
The precise terms and conditions for copying, distribution and modification follow.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
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.
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.
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.
one line to give the program's name and a brief idea of what it does. Copyright (C) yyyy name of author 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. 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. 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.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy 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.
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.
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:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice
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.
Freetalk documentation licensed under GNU Free Documentation License 1.2 or later.
Copyright © 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.
A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.
You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.”
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document 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.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation 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. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (C) year your name. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being list their titles, with the Front-Cover Texts being list, and with the Back-Cover Texts being list.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.
|Jump to:||A C E F G I O P R S|
|Command line arguments:||Invoking|
|Extension language:||Extension language|
|FDL, GNU Free Documentation License:||Freetalk Documentation License|
|Overriding extensions:||Default Scheme extensions|
|Readline in freetalk:||Tips and Tricks|
|Submitting patches:||Guidelines for submitting a patch|
|Jump to:||A C E F G I O P R S|
|Jump to:||A B C D F G H J L P Q R S U V W|
|Jump to:||A B C D F G H J L P Q R S U V W|
|Hook related procedures|
When you press TAB twice at freetalk prompt you can see all the possible commands and buddy names.
Info awaiting coming soon....
utility procedures are loaded through /DATADIR/freetalk/extensions/ and you are free to hack for cool undocumented procedures