Next: Introduction [Contents][Index]
*rcirc log*Next: Requirements, Previous: rcirc logging in SQLite, Up: rcirc logging in SQLite [Contents][Index]
rcirc is a default, simple IRC client in Emacs. rcirc can be enabled to
log the IRC chats, it logs to files.
This minor mode, when activated, diverts the rcirc logs to a SQLite database.
It also comes with some functionality to query the SQLite database.
Next: Installation and activation, Previous: Introduction, Up: rcirc logging in SQLite [Contents][Index]
rcirc-sqlite relies on the capability of Emacs to work together
with SQLite. It makes use of the variable rcirc-log-time-format,
which is introduced in Emacs version 30.1.
To use rcirc-sqlite:
rcirc-log-time-format.
Next: Customization, Previous: Requirements, Up: rcirc logging in SQLite [Contents][Index]
Next: Activation, Up: Installation and activation [Contents][Index]
Next: Manual installation, Up: Installation [Contents][Index]
The GNU ELPA package name is: rcirc-sqlite.
To install the package:
M-x package-refresh-contents
M-x package-install
and search for rcirc-sqlite.
Or use use-package:
(use-package rcirc-sqlite
:ensure t
:config
(add-hook 'rcirc-mode-hook #'rcirc-sqlite-log-mode))
Previous: Install from GNU ELPA, Up: Installation [Contents][Index]
Create a directory for the package.
mkdir ~/.emacs.d/manualpackages
Add this directory as a load path to your init file:
(add-to-list 'load-path "~/.emacs.d/manualpackages")
Re-evaluate your init file or restart Emacs, whatever you prefer.
Requirements describes the requirements.
Previous: Installation, Up: Installation and activation [Contents][Index]
Activates or deactivates rcirc-sqlite.
Issue the command rcirc-sqlite-log-mode to manually start
rcirc-sqlite. This command toggles between activation
and deactivation of rcirc-sqlite.
To start rcirc-sqlite automatically when rcirc
is started, add the following to your init file:
(require 'rcirc-sqlite) (add-hook 'rcirc-mode-hook #'rcirc-sqlite-log-mode)
While rcirc-sqlite is activated, rcirc will no longer
write the logs to files, until rcirc-sqlite is deactivated.
Deactivate rcirc-sqlite using the command
rcirc-sqlite-log-mode again.
The logging must be enabled in rcirc.
To do this, add for example the following to your init file:
(setq rcirc-log-flag t)
Next: Commands, Previous: Installation and activation, Up: rcirc logging in SQLite [Contents][Index]
To customize rcirc-sqlite run M-x customize-group rcirc-sqlite,
or use (setopt ...) in your init file, like /.emacs.
For example:
(setopt rcirc-sqlite-rows 100)
The user may customize the following options.
The file in which SQLite stores the database.
The file in which SQLite stores the database can be customized.
The default file is ricirc-log.db, located in the default Emacs directory (e.g., ~/.emacs.d/ricirc-log.db).
Set this option to use a different file.
The format for the date and time in the buffer *rcirc log*.
The variable rcirc-sqlite-time-format describes the date and
time format which is used when displaying the chat messages.
This variable only influences how the date and time is formatted
in the buffer *rcirc log*.
The default format is %Y-%m-%d %H:%M.
Set this option to use a different time format in the buffer
*rcirc log*.
The default maximum number of rows when viewing logs.
The variable rcirc-sqlite-rows describes the maximum number
of rows to display when viewing the chat logs.
This only affects when viewing the chat logs. Search results are always shown unabridged.
View the logs describes the command to view the logs.
The default value is 200 rows.
Set this option to change the default number of lines.
The default column width of the channel column in the buffer
*rcirc log*.
The variable rcirc-sqlite-channel-column-width describes the
default width of the column that displays the channel names.
The default value is 40 chars.
Change this option to let the channel names be shown in a smaller or
wider column in the buffer *rcirc log*.
The buffer *rcirc log* has more information on this buffer.
The register to store messages.
The variable rcirc-sqlite-register assigns the register
to store chat messages in.
The user selects a message from the list of messages in the
buffer *rcirc log*.
Depending on the command, the chat message either overwrites
the current contents of the register, or is appended to it.
Collect one or more messages in a register
The default register is r.
Change this option when you have assigned this register for a different use.
Next: The buffer *rcirc log*, Previous: Customization, Up: rcirc logging in SQLite [Contents][Index]
Next: View the logs, Up: Commands [Contents][Index]
M-x rcirc-sqlite-view-log: display the logs.
M-x rcirc-sqlite-text-search: perform full text search in the logs.
M-x rcirc-sqlite-logs-from-nick: display the logs from a specific nick.
M-x rcirc-sqlite-stats: displays some stats.
These commands result in logs displayed in the buffer *rcirc
log*. In that buffer you can use the key bindings for more actions.
These actions are described in the sections:
The stats view offer some drill-down options and can be a good starting point to explore your logs.
Next: Full text search and load the result in a buffer, Previous: Summery of the commands, Up: Commands [Contents][Index]
Display the logs in a new buffer.
Issue the command M-x rcirc-sqlite-view-log to view the logs
of a specific channel. Default this command shows the last 200
lines. This number can be changed by setting the variable
rcirc-sqlite-rows.
This command prompts the user for the channel and provides a list
of available channels. Choose a channel using completion.
Choose the option All channels to show the last 200 lines of the
chat log of all channels.
Next, the user is prompted to choose a time range, using
completion. When a range is chosen, the last 200 lines the chat log
from that range are shown. Choose the option Anytime or the
last 90, 60, 30, or 7 days to get the most recent 200 lines.
The buffer *rcirc log* displays the chat logs.
This function has three optional arguments, unlimited,
offset, and limit.
unlimited
When non nil, rcirc-sqlite-view-log will show all
log lines in the database of the channel.
offset and limit
Use offset and limit to select a number of lines from
the log lines in the database of the channel.
Next: Toggle display of the server in the channel name, Previous: View the logs, Up: Commands [Contents][Index]
Perform full text search.
Issue the command M-x rcirc-sqlite-text-search to perform
full text search in the logs.
When this command is issued:
When a channel is chosen, the search is performed within the
chat logs of that specific channel. Choose All channels to
search independent of the channel.
When a time range is chosen, the search is performed within the
chat messages that were send during the chosen range. When
Anytime is chosen, no filtering on date/time takes place.
When a nick is chosen, the search is performed within the
chats send by a specific nick. Choose All nicks to search
independent of the sender.
The search string is used to do a full text search in the SQLite
database. When the search string is foo, chat messages
containing the word foo will be found, but chat messages
containing the word foobar will not be found.
To search for both foo and foobar, use the search
string foo*.
Likewise, to search for URLs, use something like "http*"
to search for "http://" as well as for "https://".
For more formatting of the search see the chapter
Full-text Query Syntax of the SQLite documentation (see
https://www.sqlite.org/fts5.html).
The buffer *rcirc log* displays the search results.
Next: Change the selected logs in the log-buffer, Previous: Full text search and load the result in a buffer, Up: Commands [Contents][Index]
The buffer *rcirc log* shows the results from the latest query.
To suprress the display of the server name in the channel name, use the key (.
To activate the display of the server name in the channel name, use the key ).
Next: Copy a message to the kill-ring, Previous: Toggle display of the server in the channel name, Up: Commands [Contents][Index]
The buffer *rcirc log* shows the results from the latest query.
Move the point on this buffer up or down to select a chat message.
Use one of the key bindings to change the selected logs.
Next: Change the view to a specific day and the next day, Up: Change the selected logs in the log-buffer [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-single-day’ with the key RET or mouse button 1.
The command switches the view to the logs with the same channel and the same date as the selected chat message.
This can be useful to get some context around a specific search result.
Next: Change the view to a specific day and the previous day, Previous: Change the view to a specific day, Up: Change the selected logs in the log-buffer [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-next-day’ with the key >.
The command switches the view to the logs with the same channel and the same date and the next day as the selected chat message.
Next: Change the view to a specific day and the next days, Previous: Change the view to a specific day and the next day, Up: Change the selected logs in the log-buffer [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-previous-day’ with the key ^.
The command switches the view to the logs with the same channel and the same date and the previous day as the selected chat message.
Next: Change the view to a specific day and a specific nick, Previous: Change the view to a specific day and the previous day, Up: Change the selected logs in the log-buffer [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-all-next-days’ with the key a.
The command switches the view to the logs with the same channel and the same date or later as the selected chat message.
Previous: Change the view to a specific day and the next days, Up: Change the selected logs in the log-buffer [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-single-nick’ with the key <.
The command switches the view to the logs with the same channel, the same nick, and the same date as the selected chat message.
Next: Collect one or more messages in a register, Previous: Change the selected logs in the log-buffer, Up: Commands [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-kill-insert’ with the key c to insert the selected message in the kill-ring.
This command copies the chat message with a some markup, fit to use in e.g., org mode.
Next: Logs from a specific nick, Previous: Copy a message to the kill-ring, Up: Commands [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-register-insert’ with the key R to insert the selected message in a register. This overwrites the current contents of the register.
Activate the command ‘rcirc-sqlite-register-append’ with the key r to append the selected message to a register.
The commands insert the chat message with a some markup, fit to use in e.g., org mode.
The default register that is used for this is register ‘r’. Change the default register by setting the variable ‘rcirc-sqlite-register’ to a different register.
You can insert the contents of the register into any buffer with ‘insert-register’ (‘C-x r i <register>’). For the default register ‘r’ this is: ‘C-x r i r’.
Whatever you store in a register remains there until you store something else in that register, or until you close Emacs.
See Registers in Emacs manual
Explore the logs, for example with the search option, and start collecting messages.
Store the first message of your interest with the command ‘rcirc-sqlite-register-insert’ (key: R), overwriting anything that was in this register.
Search for the next message of your interest, and issue the command ‘rcirc-sqlite-register-append’ (key: r).
Repeat appending until done.
Open a note, for example in denote, org, or org-roam, and insert your collected chat messages with ‘insert-register’ (‘C-x r i <register>’).
Next: Browse URL in the message, Previous: Collect one or more messages in a register, Up: Commands [Contents][Index]
Display the logs from a specific nick
Issue the command rcirc-sqlite-logs-from-nick to request the
logs of a specific nick.
The user is prompted to select a nick, using completion.
Next, the user is prompted to select a time range, using completion. The options are:
When the option Anytime is chosen, no filtering takes
place.
When the latest 90, 60, 30, or 7 days is chosen, the logs from that time range are shown.
The option manually select range prompts the user to select a
start and a end of a time range, using the org date picker. Use the
org calendar commands to select a date and time.
Next: Stats, Previous: Logs from a specific nick, Up: Commands [Contents][Index]
Move the point in the buffer *rcirc log* up or down to select a
chat message.
Activate the command ‘rcirc-sqlite-browse-url-from-message’ with the key b to browse to the first URL in the selected message.
Previous: Browse URL in the message, Up: Commands [Contents][Index]
Create overview with some stats
Issue the command M-x rcirc-sqlite-stats to get an overview
of the number of rows (messages) in the database.
The user is prompted for a nick. Choose a nick through completion.
When a nick is chosen, the buffer *rcirc log* is opened and
lists each channel with one or more chat messages from that nick,
together with the number of chat messages from that nick.
When All nicks is chosen, the buffer shows the row count
for each channel in the database.
When Nicks per channel is chosen, the buffer shows for
each channel the number of unique nicks.
When Channels per nick is chosen, the buffer shows for
each nick the number of channels with messages from this nick.
Drill-down to more details
Use drill-down in the buffer showing the stats. This will show more details.
The drill-down options make the command rcirc-sqlite-stats
a nice starting point to explore your logs.
Create overview of the number of rows per month.
Issue the command M-x rcirc-sqlite-stats-per-month to get an
overview of the number of rows (messages) in the database, summerized
per month.
Drill down to the number of rows summerized per day of the selected month, and from there drill down to all messages of the selected day.
Next: Inner workings, Previous: Commands, Up: rcirc logging in SQLite [Contents][Index]
*rcirc log*The buffer *rcirc log* is used to show the output of the
database queries. This buffer uses a derived mode from the
tabulated-list-mode.
Suprress the display of the server name in the channel name with the key (, or activate the display of the server name with the key ).
Move up and down in this buffer to select a chat message. Then you can use the following key bindings to activate some commands.
rcirc-sqlite-single-dayrcirc-sqlite-next-dayrcirc-sqlite-previous-dayrcirc-sqlite-all-next-daysrcirc-sqlite-browse-url-from-messagercirc-sqlite-single-nickrcirc-sqlite-kill-insertrcirc-sqlite-register-insertrcirc-sqlite-register-appendFor a description of these commands, see the following chapters.
Change the selected logs in the log-buffer
Copy a message to the kill-ring
Collect one or more messages in a register
The default key bindings of the
tabulated-list-mode are also available in this buffer.
Some examples of these key bindings:
Sort) ¶Sort the buffer according to the values of the column of point.
Use a numeric prefix argument n to sort the buffer according to the values of the n-th column from point. Repeat to sort in the alternate order (ascending or descending).
Widen the current column by n (the prefix numeric argument) characters,
Narrow the current column by n (the prefix numeric argument) characters.
Scroll the buffer up.
Scroll the buffer down.
Move down one screen line (next line).
Move up one screen line (previous line).
Close the buffer.
Next: Database schema, Previous: The buffer *rcirc log*, Up: rcirc logging in SQLite [Contents][Index]
rcirc caches the IRC messages in a list, and periodically
writes the contents of this cache to the log files.
rcirc-sqlite collects the contents of this cache.
rcirc-sqlite overrides the rcirc-function
rcirc-log-write with the rcirc-sqlite-function
rcirc-sqlite-store-log for this.
To be able to easy parse the timestamp, rcirc-sqlite changes
the rcirc-log-time-format. It does this by advising around the
rcirc-function rcirc-log.
Up: Inner workings [Contents][Index]
There is some delay between the arrival of chat messages in the chat buffer and the storage of the logs in the database.
rcirc uses the auto-save functionality to trigger the flushing
of the cache to the log file. Hence, the storage of the chat logs to
the SQLite database by rcirc-sqlite is also triggered by the
auto-save functionality.
Next: GNU Free Documentation License, Previous: Inner workings, Up: rcirc logging in SQLite [Contents][Index]
The SQLite database is created at the first time rcirc-sqlite
flushes the cache. The SQLite database is populated with a virtual
table, using the SQLite FTS5 Extension. The schema of this table has
the following fields.
rcirc uses to
determine the log file. This format is
[email protected], for example
#[email protected].
Next: Command and Function Index, Previous: Database schema, Up: rcirc logging in SQLite [Contents][Index]
Copyright © 2000,2001,2002,2024 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, 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.
Next: Variable Index, Previous: GNU Free Documentation License, Up: rcirc logging in SQLite [Contents][Index]
| Jump to: | R S |
|---|
| Jump to: | R S |
|---|
Next: Key bindings, Previous: Command and Function Index, Up: rcirc logging in SQLite [Contents][Index]
| Jump to: | R |
|---|
| Jump to: | R |
|---|
Previous: Variable Index, Up: rcirc logging in SQLite [Contents][Index]
| Jump to: | (
)
<
>
^
{
}
A B C M N P Q R S |
|---|
| Jump to: | (
)
<
>
^
{
}
A B C M N P Q R S |
|---|