Copyright (C) 2024-2025 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with the Front-Cover Texts being “A GNU Manual,” and with the Back-Cover Texts as in (a) below. A copy of the license is included in the section entitled “GNU Free Documentation License.”
(a) The FSF’s Back-Cover Text is: “You have the freedom to copy and modify this GNU manual.”
This manual, written by Lucas Quintana, describes the customization
options for the Emacs package called denote-search (or
‘denote-search.el’), and provides every other piece of information
pertinent to it.
The documentation furnished herein corresponds to stable version 1.0.3, released on 2025-03-02.
Next: Motivation, Previous: denote-search: a simple search utility for Denote, Up: denote-search: a simple search utility for Denote [Index]
This package provides a simple search utility for the excellent
denote program, the simple-to-use, focused-in-scope, and effective
note-taking tool for Emacs (see (denote)Top).
denote-search allows you to search for a regular expression in the
contents of your notes. Once the results are populated, you are
presented with a buffer from which you can refine the search (that is,
search in the matched files), jump to a certain file using imenu,
exclude certain files from the search, or search only certain files.
All commands provided by Xref are available as well (see
(emacs)Xref).
denote-search approach has several advantages over similar tools
(consult-grep, consult-notes, grep, and so on):
denote-search-files-referenced-in-region. That is great
for metanotes, shell outputs of ‘ls’, and more.
denote-search-marked-dired-files.
helm,
vertico+consult, etc.).
denote-search doesn’t rely on any external package other
than Denote.
grep, it allows excluding (or including only) certain files
on-demand, without command-line gimmicks.
Furthermore, denote-search has a small and simple codebase. It is
designed to do one thing and one thing only: to search in your notes.
Next: Points of entry, Previous: Overview, Up: denote-search: a simple search utility for Denote [Index]
I wrote denote-search because I needed a simple tool to search my
personal knowledge database, which of course is managed with Denote.
Available options, such as consult-notes, almost always used the
minibuffer to display results. Which is fine, it works, but it is
sort of annoying on small screens. In fact, I hacked the first
version of denote-search on Emacs for Android, in a time where I
didn’t have a laptop with me. Don’t take those things as granted,
trust me.
I was mainly inspired by Howm1, a really great note-taking tool,
also made for Emacs. It has a life-changing approach to notes: it
doesn’t matter where do you store your information as long as you can
retrieve it later. “Write fragmentarily and read collectively”, that
is. Howm has thus powerful search facilities built-in, some of which
(filtering and excluding/including files) I reimplemented in
denote-search. I’m very happy now ^_^
Next: Navigating the search results, Previous: Motivation, Up: denote-search: a simple search utility for Denote [Index]
The main point of entry of this package is the denote-search
command. This command will prompt for a string. You should input a
valid regular expression, as understood by the tool which will
actually perform the search. Which program that is depends on the
value of xref-search-program, and its arguments are taken from
xref-search-program-alist. Note that denote-search is really just
a wrapper for Xref, albeit an useful one, so anything related to the
actual search results is the matter (for bad or for good) of that
library and/or the program it calls.
Once the (synchronous) search is over, a new buffer populated with the results, if any, will be made current. On that buffer, the user will be able to perform several potentially useful actions, including filtering the output (see filtering the search results) and searching in the matched files (see focused search).
History is available when searching. Press M-p
(previous-history-element) to view past queries.
There are two additional commands that can start a search:
denote-search-marked-dired-files and
denote-search-files-referenced-in-region. They allow searching a
restricted subset of files and are described in the next sections.
The command denote-search-marked-dired-files acts just like
denote-search, but it restricts the search to the files marked in
current Dired buffer (see (emacs)Marks vs Flags). This is useful if you only
want to search some files, though depending on the case maybe you’d
be better served by our built-in filtering capabilities; see
filtering the search results.
This works well in tandem with the Denote command denote-sort-dired,
which produces a Dired buffer with files matching a regexp. So,
generating that buffer and then pressing t (dired-toggle-marks)
will enable you to use denote-search-marked-dired-files to search on
those files. Again, using the filtering functionality available for
the results buffer should suit you better, but you have options.
Previous: Searching in marked Dired files, Up: Points of entry [Index]
The command denote-search-files-referenced-in-region may seem odd at
first, but it’s probably the most useful one. It allows you to search
in a set of notes referenced in a buffer. What does that means?
Well, it means that any buffer can serve as the source for the set of
files to search for; you just need Denote IDs written somewhere, and
the command will recognize them as files and search in them.
But let’s look at an example. Probably, you already have a note with a section that resembles this:
* See also - An amazing note - Another amazing note - Yet another amazing note
Those notes are links and are highlighted as such, so internally they look like this:
* See also - [[denote:20231205T202124][An amazing note]] - [[denote:20230720T154224][Another amazing note]] - [[denote:20230719T194132][Yet another amazing note]]
That 20231205T202124 bit is the Denote ID. That’s the only thing
our command needs to recognize a note. So, you just need to select
the section (with the mouse or C-SPC, whichever you like the most)
and call denote-search-files-referenced-in-region. It will prompt
for a regexp just like denote-search, but it will only search the
files selected.
This is useful for searching in notes linked in Org dynamic blocks
(first mark the block with org-babel-mark-block), or for searching
something in linked notes in general (first mark the whole buffer with
mark-whole-buffer, bound to C-x h).
This works everywhere. If you had notes with the exact same IDs as the ones depicted previously, you could select them in this very same Info buffer (assuming you are reading this in Emacs) and search something in them right away.
As the Denote ID is included in file names, you can also use this
command on Dired, on a shell output of ls from async-shell-command,
and so on. It’s on those cases where you can grasp how powerful the
Denote file-naming scheme is.
Next: Focused search, Previous: Navigating the search results, Up: denote-search: a simple search utility for Denote [Index]
On the results buffer, you can press x
(denote-search-exclude-files) to exclude certain files from the
search. The command will prompt for a regular expression. Once
given, the last search query will be re-run, but excluding all the
files that match the regular expression given. For instance, you can
input ‘_philosophy’ to exclude all the notes with the “philosophy”
keyword. Or you can input ‘-emacs’ to exclude all the notes that have
“emacs” in their title. Or you can input ‘org$’ to exclude Org files.
And so on.
You can press i (denote-search-only-include-files) for the
opposite operation; it will prompt for a regular expression, and then
re-run the search, but only on the files matched by the regular
expression given.
These commands always act as if the files matched by the last search
were all the Denote files in existence. This has a great advantage;
you can chain them in any way you want. You can, for example, press
i and input ‘_emacs’, and then press x and input ‘_philosophy’.
The resulting buffer will have all the notes which have the keyword
“emacs” but not the keyword “philosophy”, and will then display the
matches for the search query you made originally only for those
specific files. You can of course keep filtering further.
To “break the chain” and start a totally new search, you can simply
call denote-search, which is bound to s in the results buffer for
convenience.
It’s possible that you don’t want to start a new search, but rather to search something on the curated file list you got. See focused search.
Filtering by keywords is such a common operation that two special
commands exist just for that: X
(denote-search-exclude-files-with-keywords) and I
(denote-search-only-include-files-with-keywords). They are
equivalent to calling its regular counterparts and issuing a word with
a leading underscore; however, they also offer completion for
available keywords (using denote-keywords, so its actual behaviour
is governed by the variables denote-infer-keywords and
denote-known-keywords). But the main advantage is that they allow
issuing multiple keywords at once, separated by commas (or whatever
the value of crm-separator is, which should be a comma).
History is available when filtering. Press M-p
(previous-history-element) to view past queries. This history is
kept separately from that available when searching. In the case of
keyword filtering, history is shared with other Denote keyword
prompts.
To get rid of all filters, just type G
(denote-search-clean-all-filters). This simply re-runs the last
search on the full set of Denote files. Note that this differs from
g (revert-buffer), which re-runs the last search on the same set
of files (i.e. with filters applied).
Next: Editing files, Previous: Filtering the search results, Up: denote-search: a simple search utility for Denote [Index]
A “focused search” is a search which is run against a set of files matched by a previous search. There are many use-cases for this, including searching for a note that you know has two or three very specific words, probably on different lines.
On the results buffer, press f (denote-search-refine) to start a
focused search. The command will prompt for a regular expression.
Once given, it will be searched in the files matched by the last
search. The buffer will be properly updated and will show the matches
found.
Note that this feature, combined with the filtering capabilities offered by this package (see filtering the search results), can be very powerful.
Let’s look at a complex example, which would be nearly impossible with other tools: search for all the mentions of “quantum mechanics” in notes with the “science” keyword, without the “personal” keyword, and which mention “Maxwell” somewhere in the text. The procedure is as follows:
There it is, a really complex task is done in four straightforward steps. And all without external and platform-specific programs such as xapian!
Next: Customization, Previous: Focused search, Up: denote-search: a simple search utility for Denote [Index]
denote-search is designed only for finding information in your
knowledge database, not for changing it. You can open the files (with
RET, n or otherwise) and edit them as usual.
There’s a special editing feature offered by Xref, though. You can
press r (xref-query-replace-in-results) to replace the search
query (naturally as a regular expression) in the files matched; the
interface is similar to that of query-replace-regexp. This works in
the files then displayed in the results buffer, so you can filter and
fine-grain as usual to come with the replace command you wish. Maybe
replace all the occurences of “Vim” with “Emacs” in notes with the
keyword “programming” but not in notes with the keyword “personal”,
and only in files which mention “GNU”? The sky is the limit!
Next: Working with silos, Previous: Editing files, Up: denote-search: a simple search utility for Denote [Index]
Although denote-search is designed to be simple and require no
special configuration, some options are available.
Next: Other options, Up: Customization [Index]
By default, denote-search uses the pretty title found in the
front-matter to format note headings in the results buffer. This is
pleasent to the eye and shouldn’t impact performance (the bottleneck
is always the search itself).
You can change how headings are formatted by customizing the
denote-search-format-heading-function variable. It must be set to a
function which takes a single argument, the file path, and returns the
desired string for the heading.
By default, denote-search-extract-title is used, which produces the
aforementioned behaviour. If it fails to find a suitable title for a
note, it uses the value of denote-search-untitled-string. You can
customize that, as well.
This package also offers an alternative function, called
denote-search-format-heading-with-keywords. If used as the heading
formatter, it adds keywords to the file title. This isn’t the default
merely to not clutter the view, but many users may prefer it.
You can write custom functions to display pretty much everything you want in the headings. Just keep in mind that the function is called for every single matched file, so for large collection of notes, it can indeed impact performance if you use complex code.
Previous: Format of headings, Up: Customization [Index]
You can customize the name of the buffer where results are put using
the variable denote-search-buffer-name.
By default, the results buffer has a header line which displays
information about the search and a short help string. Once you know
the commands by heart, you can set the variable
denote-search-help-string to nil or a void string to disable the
help.
Next: Installation, Previous: Customization, Up: denote-search: a simple search utility for Denote [Index]
If silos (see (denote)denote#Maintain separate directory silos for notes) are
set up correctly (that is, with a ‘.dir-locals.el’ file that sets a
value for denote-directory), then denote-search should correctly
search in the contents of the silo when inside of it, without
additional configuration.
Next: Sample configuration, Previous: Working with silos, Up: denote-search: a simple search utility for Denote [Index]
Next: VC installation, Up: Installation [Index]
The package is available as denote-search. Simply do:
M-x package-refresh-contents M-x package-install
And search for it.
Next: Manual installation, Previous: GNU ELPA package, Up: Installation [Index]
You can install the package from source by evaluating the following code:
(package-vc-install '(denote-search :url "https://github.com/lmq-10/denote-search" :doc "README.org"))
Alternatively, you can use the :vc keyword from use-package.
Previous: VC installation, Up: Installation [Index]
Assuming your Emacs files are found in ‘~/.emacs.d/’, execute the following commands in a shell prompt:
cd ~/.emacs.d # Create a directory for manually-installed packages mkdir manual-packages # Go to the new directory cd manual-packages # Clone this repo, naming it "denote-search" git clone https://github.com/lmq-10/denote-search denote-search
Finally, in your ‘init.el’ (or equivalent) evaluate this:
;; Make Elisp files in that directory available to the user. (add-to-list 'load-path "~/.emacs.d/manual-packages/denote-search")
Everything is in place to set up the package.
Next: Troubleshooting, Previous: Installation, Up: denote-search: a simple search utility for Denote [Index]
(use-package denote-search
:ensure t
:bind
;; Customize keybindings to your liking
(("C-c s s" . denote-search)
("C-c s d" . denote-search-marked-dired-files)
("C-c s r" . denote-search-files-referenced-in-region))
:custom
;; Disable help string (set it once you learn the commands)
;; (denote-search-help-string "")
;; Display keywords in results buffer
(denote-search-format-heading-function #'denote-search-format-heading-with-keywords))
Next: Acknowledgements, Previous: Sample configuration, Up: denote-search: a simple search utility for Denote [Index]
Fixes for some common issues.
Up: Troubleshooting [Index]
Search is not managed by denote-search, but rather by xref. Check
the value of xref-search-program. Changing it to ‘ripgrep’ (after
installing it of course) can improve the speed.
Next: GNU Free Documentation License, Previous: Troubleshooting, Up: denote-search: a simple search utility for Denote [Index]
denote-search, just like Denote itself, is meant to be a collective
effort. Every bit of help matters.
Lucas Quintana.
Grant Rettke, Philip Kaludercic.
If denote-search exists it’s because Protesilaos Stavrou developed
the incredible Denote package. Please consider donating to him.3
I also want to thank Richard Stallman (creator of GNU Emacs), Po Lu
(who ported it to Android, allowing me to write the first version of
denote-search) and Hiraoka Kazuyuki (author of Howm, from which this
package borrows some ideas). This wouldn’t be possible without them,
either.
Next: Indices, Previous: Acknowledgements, Up: denote-search: a simple search utility for Denote [Index]
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. https://fsf.org/ 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.
The “publisher” means any person or entity that distributes copies of the Document to the public.
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 under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.
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 https://www.gnu.org/licenses/.
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. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Document.
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site.
“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.
“Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document.
An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.
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.3 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.
Previous: GNU Free Documentation License, Up: denote-search: a simple search utility for Denote [Index]
Next: Variable index, Up: Indices [Index]
| Jump to: | D |
|---|
| Jump to: | D |
|---|
Next: Concept index, Previous: Function index, Up: Indices [Index]
| Jump to: | D |
|---|
| Jump to: | D |
|---|
Previous: Variable index, Up: Indices [Index]
https://kaorahi.github.io/howm/
You’ll probably bind denote-search to something comfortable, see Sample configuration