[elpa] externals/mct 310cc42 01/70: Initial commit

[ELPA Syncer]

branch: externals/mct
commit 310cc421516a5a4fc270e7974992855be1c5c073
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Initial commit
---
 .gitignore      |   3 +
 COPYING         | 674 +++++++++++++++++++++++++++++++++++++++
 README.org      | 880 +++++++++++++++++++++++++++++++++++++++++++++++++++
 doclicense.texi | 505 +++++++++++++++++++++++++++++
 mct.el          | 778 +++++++++++++++++++++++++++++++++++++++++++++
 mct.info        | 964 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 mct.texi        | 473 +++++++++++++++++++++++++++
 7 files changed, 4277 insertions(+)

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..cb62d01
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,3 @@
+*.elc
+*-autoloads.el
+*-pkg.el
diff --git a/COPYING b/COPYING
new file mode 100644
index 0000000..89d9142
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 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.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  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
+them 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 prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  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.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  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, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  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
+state 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) 2021  Protesilaos Stavrou
+
+    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 3 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, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) 2021  Protesilaos Stavrou
+    This program 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, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU 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 Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.
diff --git a/README.org b/README.org
new file mode 100644
index 0000000..7161335
--- /dev/null
+++ b/README.org
@@ -0,0 +1,880 @@
+#+title: Minibuffer and Completions in Tandem (mct.el)
+#+author: Protesilaos Stavrou
+#+email: info@protesilaos.com
+#+language: en
+#+options: ':t toc:nil author:t email:t num:t
+#+startup: content
+
+#+macro: stable-version 0.1.0
+#+macro: release-date 2021-10-22
+#+macro: development-version 0.2.0-dev
+#+macro: file @@texinfo:@file{@@$1@@texinfo:}@@
+#+macro: space @@texinfo:@: @@
+#+macro: kbd @@texinfo:@kbd{@@$1@@texinfo:}@@
+
+#+export_file_name: mct.texi
+
+#+texinfo_filename: mct.info
+#+texinfo_dir_category: Emacs misc features
+#+texinfo_dir_title: Minibuffer and Completions in Tandem: (mct)
+#+texinfo_dir_desc: Enhancement of the default minibuffer completion
+#+texinfo_header: @set MAINTAINERSITE @uref{https://protesilaos.com,maintainer 
webpage}
+#+texinfo_header: @set MAINTAINER Protesilaos Stavrou
+#+texinfo_header: @set MAINTAINEREMAIL @email{info@protesilaos.com}
+#+texinfo_header: @set MAINTAINERCONTACT 
@uref{mailto:info@protesilaos.com,contact the maintainer}
+
+#+texinfo: @insertcopying
+
+This manual, written by Protesilaos Stavrou, describes the customization
+options for =mct.el=, and provides every other piece of information
+pertinent to it.
+
+The documentation furnished herein corresponds to stable version
+{{{stable-version}}}, released on {{{release-date}}}.  Any reference to a newer
+feature which does not yet form part of the latest tagged commit, is
+explicitly marked as such.
+
+Current development target is {{{development-version}}}.
+
+#+toc: headlines 8 insert TOC here, with eight headline levels
+
+* COPYING
+:PROPERTIES:
+:COPYING: t
+:CUSTOM_ID: h:efc32d6b-9405-4f3c-9560-3229b3ce3866
+:END:
+
+Copyright (C) 2021  Free Software Foundation, Inc.
+
+#+begin_quote
+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.”
+#+end_quote
+
+* Overview of mct.el
+:PROPERTIES:
+:CUSTOM_ID: h:ba224631-618c-4e52-b373-e46970cb2242
+:END:
+#+cindex: Overview of features
+#+findex: mct-choose-completion-number
+#+vindex: mct-minimum-input
+#+vindex: mct-live-update-delay
+#+vindex: mct-completion-blocklist
+#+vindex: mct-completion-passlist
+#+vindex: mct-hide-completion-mode-line
+#+vindex: mct-remove-shadowed-file-name
+#+vindex: mct-apply-completion-stripes
+#+vindex: mct-stripe
+
+Minibuffer and Completions in Tandem, also known as "MCT", "Mct", =mct=,
+or =mct.el=, is a package that enhances the default minibuffer and
+=*Completions*= buffer of Emacs 28 (or higher) so that they work together
+as part of a unified framework.  The idea is to make the presentation
+and overall functionality be consistent with other popular, vertically
+aligned completion UIs while leveraging built-in functionality.
+
+The main feature set that unifies the minibuffer and the =*Completions*=
+buffer consists of commands that cycle between the two, making it seem
+like they are part of a contiguous space 
([[#h:884d6702-8666-4d89-87a2-7d74843653f3][Basic usage]]).
+
+MCT tries to find a middle ground between the frugal defaults and the
+more opinionated completion UIs.  This is most evident in its approach
+on how to present completion candidates.  Instead of showing them
+outright or only displaying them on demand, MCT implements a minimum
+input threshold as well as a slight delay before it pops up the
+=*Completions*= buffer and starts updating it to respond to user input.
+
+Customisation options control the input threshold (~mct-minimum-input~)
+and the delay between live updates (~mct-live-update-delay~).  Similarly,
+a blocklist and a passlist for commands are on offer:
+
++ The blocklist (~mct-completion-blocklist~) disables the live-updating
+  functionality for the commands specified therein.
+
++ The passlist (~mct-completion-passlist~) always shows the Completions'
+  buffer for the designated command without accounting for the minimum
+  input threshold.
+
+Other customisations:
+
++ ~mct-hide-completion-mode-line~ to hide the mode line of the
+  =*Completions*= buffer.  This removes the separation between it and the
+  minibuffer, further contributing to the idea of a unified space
+  between the two.
+
++ ~mct-remove-shadowed-file-name~ to clear shadowed file names when
+  ~file-name-shadow-mode~ is enabled.  This means that in prompts that use
+  file paths (such as ~find-file~) when you start in, say, =~/Git/mct.el=
+  and type =~/= the previous file path is removed and only the new one is
+  inserted.  Whereas the default is to keep the original file name
+  visible yet "shadowed" by a different colour.
+
++ ~mct-show-completion-line-numbers~ to always display line numbers in the
+  Completions' buffer.  This can be helpful to get a sense of the length
+  of the completion candidates' list.  Though note that line numbers are
+  displayed ephemerally while using the ~mct-choose-completion-number~
+  command, which is bound to =M-g M-g= in either the minibuffer or the
+  =*Completions*= buffer.
+
++ ~mct-apply-completion-stripes~ applies alternative background colours in
+  the Completions' buffer.  This is only tested with the =modus-themes=
+  and will only work nicely if the main background is pure black or
+  white---other themes would need to add support for the faces we define
+  or, at least, users must modify the ~mct-stripe~ face.
+
+* Basic usage
+:PROPERTIES:
+:CUSTOM_ID: h:884d6702-8666-4d89-87a2-7d74843653f3
+:END:
+
+** Cyclic behaviour
+:PROPERTIES:
+:CUSTOM_ID: h:68c61a76-1d64-4f62-a77a-52e7b66a68fe
+:END:
+#+cindex: Cyclic behaviour
+#+findex: mct-switch-to-completions-top
+#+findex: mct-switch-to-completions-bottom
+#+findex: mct-previous-completion-or-mini
+#+findex: mct-next-completion-or-mini
+#+findex: mct-list-completions-toggle
+
+When ~mct-mode~ is enabled, some new keymaps are activated which add
+commands for cycling between the minibuffer and the completions.
+Suppose the following standard layout:
+
+#+begin_example
+-----------------
+|               |
+|               |
+|               |
+|  Buffer       |
+|               |
+|               |
+|               |
+-----------------
+-----------------
+|               |
+|  Completions  |
+|               |
+-----------------
+-----------------
+|  Minibuffer   |
+-----------------
+#+end_example
+
+When inside the minibuffer, pressing =C-n= (or down arrow) takes you to
+the top of the completions, while =C-p= (or up arrow) moves to the bottom.
+The commands are ~mct-switch-to-completions-top~ for the former and
+~mct-switch-to-completions-bottom~ for the latter.  If the =*Completions*=
+are not shown, then the buffer pops up automatically and point moves to
+the given position.
+
+Similarly, while inside the =*Completions*= buffer, =C-p= (or up arrow) at
+the top of the buffer switches to the minibuffer, while =C-n= (or down
+arrow) at the bottom of the buffer also goes to the minibuffer.  If
+point is anywhere else inside the buffer, those key bindings perform a
+regular line motion.  The commands are ~mct-previous-completion-or-mini~
+and ~mct-next-completion-or-mini~.
+
+The display of the =*Completions*= can be toggled at any time from inside
+the minibuffer with =C-l= (mnemonic is "[l]ist completions" and the
+command is ~mct-list-completions-toggle~).
+
+** Selecting candidates
+:PROPERTIES:
+:CUSTOM_ID: h:bb445062-2e39-4082-a868-2123bfb793cc
+:END:
+#+cindex: Candidate selection
+#+findex: mct-edit-completion
+
+There are several ways to select a completion candidate.
+
+1. Suppose that you are typing =mod= with the intent to select the
+   =modus-themes.el= buffer.  To complete the first candidate follow up
+   =mod= with the =TAB= key.  This is how you would do it with the default
+   minibuffer.  If done fast enough, no completions will be shown
+   (depending on your minimum input threshold and the live-update
+   delay).
+
+2. Upon cycling through the completions, type =RET= to select the
+   candidate at point and exit the minibuffer.  This works for all types
+   of completion prompts.
+
+3. For certain contexts where selecting a candidate does not necessarily
+   mean that the process has to be finalised (e.g. when using ~find-file~)
+   selection in the =*Completions*= buffer can be done with =TAB= which
+   completes the item at point but does not exit the minibuffer.  The
+   command is instead renewed to update the list of completions with the
+   new candidates.
+
+4. Select a candidate by its line number by typing =M-g M-g= in either the
+   minibuffer or the =*Completions*= buffer.  This calls the command
+   ~mct-choose-completion-number~ which internally enables line numbers
+   and always makes the completions' buffer visible.
+
+5. In prompts that allow the selection of multiple candidates
+   (internally via the ~completing-read-multiple~ function) a =[CRM]= label
+   is added to the text of the prompt.  The user thus knows that
+   pressing =M-RET= in the =*Completions*= will append the candidate at
+   point to the list of selections and keep the completions available so
+   that another item may be selected.  Any of the aforementioned
+   applicable methods can confirm the final selection.  If, say, you
+   want to pick a total of three candidates, do =M-RET= for the first two
+   and =RET= for the last one.  In contexts that are not CRM-powered, the
+   =M-RET= has the same effect as =RET=.
+
+   NOTE 2021-10-22: this assumes the ~crm-separator~ to be constant (the
+   comma =,= character) but some commands ~let~ bind it to something else,
+   so the behaviour does not work as expected.  One such case is
+   ~org-set-tags-command~ which uses =:= as a separator.
+
+7. Type =M-e= (~mct-edit-completion~) in the completions' buffer to place
+   the current candidate in the minibuffer, without exiting the session.
+   This allows you to edit the text before confirming it.
+
+* Installation
+:PROPERTIES:
+:CUSTOM_ID: h:1b501ed4-f16c-4118-9a4a-7a5e29143077
+:END:
+
+MCT is not in any package archive for the time being, though I plan to
+submit it to GNU ELPA (as such, any non-trivial patches require
+copyright assignment to the Free Software Foundation).  Users can rely
+on =straight.el=, =quelpa=, or equivalent to fetch the source.  Below are
+the essentials for those who prefer the manual method.
+
+Assuming your Emacs files are found in =~/.emacs.d/=, execute the
+following commands in a shell prompt:
+
+#+begin_src sh
+cd ~/.emacs.d
+
+# Create a directory for manually-installed packages
+mkdir manual-packages
+
+# Go to the new directory
+cd manual-packages
+
+# Clone this repo and name it "mct"
+git clone https://gitlab.com/protesilaos/mct.el.git mct
+#+end_src
+
+Finally, in your =init.el= (or equivalent) evaluate this:
+
+#+begin_src emacs-lisp
+;; Make Elisp files in that directory available to the user.
+(add-to-list 'load-path "~/.emacs.d/manual-packages/")
+#+end_src
+
+Everything is in place to set up the package.
+
+* Sample setup
+:PROPERTIES:
+:CUSTOM_ID: h:318ba6f8-2909-44b0-9bed-558552722667
+:END:
+#+cindex: Sample configuration
+
+Minimal setup:
+
+#+begin_src emacs-lisp
+(require 'mct)
+(mct-mode 1)
+#+end_src
+
+And with more options:
+
+#+begin_src emacs-lisp
+(require 'mct)
+
+(setq mct-remove-shadowed-file-names t) ; works when `file-name-shadow-mode' 
is enabled
+(setq mct-hide-completion-mode-line t)
+(setq mct-show-completion-line-numbers nil)
+(setq mct-apply-completion-stripes t)
+(setq mct-minimum-input 3)
+(setq mct-live-update-delay 0.6)
+
+;; NOTE: `mct-completion-blocklist' can be used for commands with lots
+;; of candidates, depending also on how low `mct-minimum-input' is.
+;; With the settings shown here this is not required, otherwise I would
+;; use something like this:
+;;
+;; (setq mct-completion-blocklist
+;;       '( describe-symbol describe-function describe-variable
+;;          execute-extended-command insert-char))
+(setq mct-completion-blocklist nil)
+
+;; This is for commands that should always pop up the completions'
+;; buffer.  It circumvents the default method of waiting for some user
+;; input (see `mct-minimum-input') before displaying and updating the
+;; completions' buffer.
+(setq mct-completion-passlist
+      '(imenu
+        Info-goto-node
+        Info-index
+        Info-menu
+        vc-retrieve-tag))
+
+(mct-mode 1)
+#+end_src
+
+Other useful extras from the Emacs source code:
+
+#+begin_src emacs-lisp
+(setq enable-recursive-minibuffers t)
+(setq minibuffer-eldef-shorten-default t)
+
+(file-name-shadow-mode 1)
+(minibuffer-depth-indicate-mode 1)
+(minibuffer-electric-default-mode 1)
+#+end_src
+
+* Keymaps
+:PROPERTIES:
+:CUSTOM_ID: h:b3178edd-f340-444c-8426-fe84f23ac9ea
+:END:
+#+cindex: Keymaps
+#+vindex: mct-completion-list-mode-map
+#+vindex: mct-minibuffer-local-completion-map
+#+vindex: mct-minibuffer-local-filename-completion-map
+
+MCT defines its own keymaps, which extend those that are active in the
+minibuffer and the =*Completions*= buffer, respectively:
+
++ ~mct-completion-list-mode-map~
++ ~mct-minibuffer-local-completion-map~
++ ~mct-minibuffer-local-filename-completion-map~
+
+You can invoke ~describe-keymap~ to learn more about them.
+
+If you want to edit any key bindings, do it in those keymaps, not in
+those they extend and override (the names of the original ones are the
+same as above, minus the =mct-= prefix).
+
+* Extensions
+:PROPERTIES:
+:CUSTOM_ID: h:03227254-d467-4147-b8cf-2fe05a2e279b
+:END:
+#+cindex: Extra packages
+
+MCT only tweaks the default minibuffer.  To get more out of it, consider
+these exceptionally well-crafted extras:
+
++ =consult= :: Adds several commands that make interacting with the
+  minibuffer more powerful.  There also are several packages that build
+  on it, such as =consult-dir=.
++ =embark= :: Provides configurable contextual actions for completions and
+  many other constructs inside buffers.
++ =marginalia= :: Displays informative annotations for all known types of
+  completion candidates.
++ =orderless= :: A completion style that matches a variety of patterns
+  (regexp, flex, initialism, etc.) regardless of the order they appear
+  in.
+
+* Alternatives
+:PROPERTIES:
+:CUSTOM_ID: h:c9ddedea-e279-4233-94dc-f8d32367a954
+:END:
+#+cindex: Alternatives to MCT
+
+The only alternative I have used that is conceptually close to MCT is
+=vertico=.  Vertico is a more mature and feature-rich package, while its
+maintainer, Daniel Mendler, is an accomplished programmer.  Whereas MCT
+is mostly an excuse to practice my Elisp skills.
+
+* GNU Free Documentation License
+:PROPERTIES:
+:APPENDIX: t
+:CUSTOM_ID: h:2d84e73e-c143-43b5-b388-a6765da974ea
+:END:
+
+#+texinfo: @include doclicense.texi
+
+#+begin_export html
+<pre>
+
+                GNU Free Documentation License
+                 Version 1.3, 3 November 2008
+
+
+ Copyright (C) 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.
+
+0. PREAMBLE
+
+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.
+
+
+1. APPLICABILITY AND DEFINITIONS
+
+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.
+
+2. VERBATIM COPYING
+
+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.
+
+
+3. COPYING IN QUANTITY
+
+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.
+
+
+4. MODIFICATIONS
+
+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:
+
+A. Use in the Title Page (and on the covers, if any) a title distinct
+   from that of the Document, and from those of previous versions
+   (which should, if there were any, be listed in the History section
+   of the Document).  You may use the same title as a previous version
+   if the original publisher of that version gives permission.
+B. List on the Title Page, as authors, one or more persons or entities
+   responsible for authorship of the modifications in the Modified
+   Version, together with at least five of the principal authors of the
+   Document (all of its principal authors, if it has fewer than five),
+   unless they release you from this requirement.
+C. State on the Title page the name of the publisher of the
+   Modified Version, as the publisher.
+D. Preserve all the copyright notices of the Document.
+E. Add an appropriate copyright notice for your modifications
+   adjacent to the other copyright notices.
+F. Include, immediately after the copyright notices, a license notice
+   giving the public permission to use the Modified Version under the
+   terms of this License, in the form shown in the Addendum below.
+G. Preserve in that license notice the full lists of Invariant Sections
+   and required Cover Texts given in the Document's license notice.
+H. Include an unaltered copy of this License.
+I. Preserve the section Entitled "History", Preserve its Title, and add
+   to it an item stating at least the title, year, new authors, and
+   publisher of the Modified Version as given on the Title Page.  If
+   there is no section Entitled "History" in the Document, create one
+   stating the title, year, authors, and publisher of the Document as
+   given on its Title Page, then add an item describing the Modified
+   Version as stated in the previous sentence.
+J. Preserve the network location, if any, given in the Document for
+   public access to a Transparent copy of the Document, and likewise
+   the network locations given in the Document for previous versions
+   it was based on.  These may be placed in the "History" section.
+   You may omit a network location for a work that was published at
+   least four years before the Document itself, or if the original
+   publisher of the version it refers to gives permission.
+K. For any section Entitled "Acknowledgements" or "Dedications",
+   Preserve the Title of the section, and preserve in the section all
+   the substance and tone of each of the contributor acknowledgements
+   and/or dedications given therein.
+L. Preserve all the Invariant Sections of the Document,
+   unaltered in their text and in their titles.  Section numbers
+   or the equivalent are not considered part of the section titles.
+M. Delete any section Entitled "Endorsements".  Such a section
+   may not be included in the Modified Version.
+N. Do not retitle any existing section to be Entitled "Endorsements"
+   or to conflict in title with any Invariant Section.
+O. Preserve any Warranty Disclaimers.
+
+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.
+
+
+5. COMBINING DOCUMENTS
+
+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".
+
+
+6. COLLECTIONS OF DOCUMENTS
+
+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.
+
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+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.
+
+
+8. TRANSLATION
+
+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.
+
+
+9. TERMINATION
+
+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.
+
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+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.
+
+11. RELICENSING
+
+"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.
+
+
+ADDENDUM: How to use this License for your documents
+
+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.
+</pre>
+#+end_export
+
+#+html: <!--
+
+* Indices
+:PROPERTIES:
+:CUSTOM_ID: h:0325b677-0b1b-426e-a5d5-ddc225fde6fa
+:END:
+
+** Function index
+:PROPERTIES:
+:INDEX: fn
+:CUSTOM_ID: h:40430725-fd7f-47ac-9a29-913942e84a57
+:END:
+
+** Variable index
+:PROPERTIES:
+:INDEX: vr
+:CUSTOM_ID: h:91f3c207-8149-4f9a-89cf-b8726e4e4415
+:END:
+
+** Concept index
+:PROPERTIES:
+:INDEX: cp
+:CUSTOM_ID: h:2b11517a-b67f-494f-b111-1c6195e8a2fc
+:END:
+
+#+html: -->
diff --git a/doclicense.texi b/doclicense.texi
new file mode 100644
index 0000000..eaf3da0
--- /dev/null
+++ b/doclicense.texi
@@ -0,0 +1,505 @@
+@c The GNU Free Documentation License.
+@center Version 1.3, 3 November 2008
+
+@c This file is intended to be included within another document,
+@c hence no sectioning command or @node.
+
+@display
+Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, 
Inc.
+@uref{https://fsf.org/}
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+@end display
+
+@enumerate 0
+@item
+PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document @dfn{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.
+
+@item
+APPLICABILITY AND DEFINITIONS
+
+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, La@TeX{} 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.
+
+@item
+VERBATIM COPYING
+
+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.
+
+@item
+COPYING IN QUANTITY
+
+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.
+
+@item
+MODIFICATIONS
+
+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:
+
+@enumerate A
+@item
+Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document).  You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
+@item
+List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
+@item
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
+@item
+Preserve all the copyright notices of the Document.
+
+@item
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
+@item
+Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
+@item
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's license notice.
+
+@item
+Include an unaltered copy of this License.
+
+@item
+Preserve the section Entitled ``History'', Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page.  If
+there is no section Entitled ``History'' in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
+@item
+Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on.  These may be placed in the ``History'' section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
+@item
+For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
+@item
+Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles.  Section numbers
+or the equivalent are not considered part of the section titles.
+
+@item
+Delete any section Entitled ``Endorsements''.  Such a section
+may not be included in the Modified Version.
+
+@item
+Do not retitle any existing section to be Entitled ``Endorsements'' or
+to conflict in title with any Invariant Section.
+
+@item
+Preserve any Warranty Disclaimers.
+@end enumerate
+
+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.
+
+@item
+COMBINING DOCUMENTS
+
+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.''
+
+@item
+COLLECTIONS OF DOCUMENTS
+
+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.
+
+@item
+AGGREGATION WITH INDEPENDENT WORKS
+
+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.
+
+@item
+TRANSLATION
+
+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.
+
+@item
+TERMINATION
+
+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.
+
+@item
+FUTURE REVISIONS OF THIS LICENSE
+
+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
+@uref{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.
+
+@item
+RELICENSING
+
+``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.
+
+@end enumerate
+
+@page
+@heading ADDENDUM: How to use this License for your documents
+
+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:
+
+@smallexample
+@group
+  Copyright (C)  @var{year}  @var{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''.
+@end group
+@end smallexample
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the ``with@dots{}Texts.''@: line with this:
+
+@smallexample
+@group
+    with the Invariant Sections being @var{list their titles}, with
+    the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
+    being @var{list}.
+@end group
+@end smallexample
+
+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.
+
+@c Local Variables:
+@c ispell-local-pdict: "ispell-dict"
+@c End:
diff --git a/mct.el b/mct.el
new file mode 100644
index 0000000..cc1f246
--- /dev/null
+++ b/mct.el
@@ -0,0 +1,778 @@
+;;; mct.el --- Minibuffer and Completions in Tandem -*- lexical-binding: t -*-
+
+;; Copyright (C) 2021  Free Software Foundation, Inc.
+
+;; Author: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://gitlab.com/protesilaos/mct.el
+;; Version: 0.1.0
+;; Package-Requires: ((emacs "28.1"))
+
+;; This file is NOT part of GNU Emacs.
+
+;; 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 3 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, see <https://www.gnu.org/licenses/>.
+
+;;; Commentary:
+;;
+;; MCT enhances the default Emacs completion.  It makes the minibuffer
+;; and Completions' buffer work together and look like a vertical
+;; completion UI.
+;;
+;; Read the documentation for basic usage and configuration.
+
+;;; Code:
+
+;;;; General utilities
+
+(defgroup mct ()
+  "Extensions for the minibuffer."
+  :group 'minibuffer)
+
+(defcustom mct-completion-windows-regexp
+  "\\`\\*Completions.*\\*\\'"
+  "Regexp to match window names with completion candidates.
+Used by `mct--get-completion-window'."
+  :type 'string
+  :group 'mct)
+
+(defcustom mct-remove-shadowed-file-names nil
+  "Delete shadowed parts of file names.
+
+For example, if the user types ~/ after a long path name,
+everything preceding the ~/ is removed so the interactive
+selection process starts again from the user's $HOME.
+
+Only works when variable `file-name-shadow-mode' is non-nil."
+  :type 'boolean
+  :group 'mct)
+
+(defcustom mct-hide-completion-mode-line nil
+  "Do not show a mode line in the Completions' buffer."
+  :type 'boolean
+  :group 'mct)
+
+(defcustom mct-show-completion-line-numbers nil
+  "Display line numbers in the Completions' buffer."
+  :type 'boolean
+  :group 'mct)
+
+(defcustom mct-apply-completion-stripes nil
+  "Display alternating backgrounds the Completions' buffer."
+  :type 'boolean
+  :group 'mct)
+
+(defcustom mct-minimum-input 3
+  "Live update completions when input is >= N.
+
+Setting this to a value greater than 1 can help reduce the total
+number of candidates that are being computed."
+  :type 'natnum
+  :group 'mct)
+
+(defcustom mct-live-update-delay 0.3
+  "Delay in seconds before updating the Completions' buffer.
+
+Set this to 0 to disable the delay."
+  :type 'number
+  :group 'mct)
+
+(defcustom mct-completion-blocklist nil
+  "Commands that do not do live updating of completions.
+
+A less drastic measure is to set `mct-minimum-input'
+to an appropriate value.
+
+The Completions' buffer can still be accessed with commands that
+place it in a window (such as `mct-list-completions-toggle',
+`mct-switch-to-completions-top')."
+  :type '(repeat symbol)
+  :group 'mct)
+
+(defcustom mct-completion-passlist nil
+  "Commands that do live updating of completions from the start.
+
+This means that they ignore `mct-minimum-input' and
+the inherent constraint of updating the Completions' buffer only
+upon user input.  Furthermore, they also bypass any possible
+delay introduced by `mct-live-update-delay'."
+  :type '(repeat symbol)
+  :group 'mct)
+
+;;;; Basic helper functions
+
+;; Copied from icomplete.el
+(defun mct--field-beg ()
+  "Determine beginning of completion."
+  (if (window-minibuffer-p)
+      (minibuffer-prompt-end)
+    (nth 0 completion-in-region--data)))
+
+;; Copied from icomplete.el
+(defun mct--field-end ()
+  "Determine end of completion."
+  (if (window-minibuffer-p)
+      (point-max)
+    (nth 1 completion-in-region--data)))
+
+;; Copied from icomplete.el
+(defun mct--completion-category ()
+  "Return completion category."
+  (let* ((beg (mct--field-beg))
+         (md (when (window-minibuffer-p) (completion--field-metadata beg))))
+    (alist-get 'category (cdr md))))
+
+;;;; Basics of intersection between minibuffer and Completions' buffer
+
+(defface mct-hl-line
+  '((default :extend t)
+    (((class color) (min-colors 88) (background light))
+     :background "#b0d8ff" :foreground "#000000")
+    (((class color) (min-colors 88) (background dark))
+     :background "#103265" :foreground "#ffffff")
+    (t :inherit highlight))
+  "Face for current line in the completions' buffer."
+  :group 'mct)
+
+(defface mct-line-number
+  '((default :inherit default)
+    (((class color) (min-colors 88) (background light))
+     :background "#f2eff3" :foreground "#252525")
+    (((class color) (min-colors 88) (background dark))
+     :background "#151823" :foreground "#dddddd")
+    (t :inverse-video t))
+  "Face for line numbers in the completions' buffer."
+  :group 'mct)
+
+(defface mct-line-number-current-line
+  '((default :inherit default)
+    (((class color) (min-colors 88) (background light))
+     :background "#8ac7ff" :foreground "#000000")
+    (((class color) (min-colors 88) (background dark))
+     :background "#142a79" :foreground "#ffffff")
+    (t :inverse-video t))
+  "Face for current line number in the completions' buffer."
+  :group 'mct)
+
+(declare-function display-line-numbers-mode "display-line-numbers")
+(declare-function face-remap-remove-relative "face-remap" (cookie))
+
+(defun mct--display-line-numbers ()
+  "Set up line numbers for the completions' buffer.
+Add this to `completion-list-mode-hook'."
+  (when (and (derived-mode-p 'completion-list-mode)
+             mct-show-completion-line-numbers)
+    (face-remap-add-relative 'line-number 'mct-line-number)
+    (face-remap-add-relative 'line-number-current-line
+                             'mct-line-number-current-line)
+    (display-line-numbers-mode 1)))
+
+(defun mct--hl-line ()
+  "Set up line highlighting for the completions' buffer.
+Add this to `completion-list-mode-hook'."
+  (when (derived-mode-p 'completion-list-mode)
+    (face-remap-add-relative 'hl-line 'mct-hl-line)
+    (hl-line-mode 1)))
+
+;; Thanks to Omar Antolín Camarena for recommending the use of
+;; `cursor-sensor-functions' and the concomitant hook with
+;; `cursor-censor-mode' instead of the dirty hacks I had before to
+;; prevent the cursor from moving to that position where no completion
+;; candidates could be found at point (e.g. it would break `embark-act'
+;; as it could not read the topmost candidate when point was at the
+;; beginning of the line, unless the point was moved forward).
+(defun mct--clean-completions ()
+  "Keep only completion candidates in the Completions."
+  (with-current-buffer standard-output
+    (let ((inhibit-read-only t))
+      (goto-char (point-min))
+      (delete-region (point-at-bol) (1+ (point-at-eol)))
+      (insert (propertize " "
+                          'cursor-sensor-functions
+                          (list
+                           (lambda (_win prev dir)
+                             (when (eq dir 'entered)
+                               (goto-char prev))))))
+      (put-text-property (point-min) (point) 'invisible t))))
+
+(defun mct--fit-completions-window ()
+  "Fit Completions' buffer to its window."
+  (setq-local window-resize-pixelwise t)
+  (fit-window-to-buffer (get-buffer-window "*Completions*")
+                        (floor (frame-height) 2) 1))
+
+(defun mct--input-string ()
+  "Return the contents of the minibuffer as a string."
+  (buffer-substring-no-properties (minibuffer-prompt-end) (point-max)))
+
+(defun mct--minimum-input ()
+  "Test for minimum requisite input for live completions.
+See `mct-minimum-input'."
+  (>= (length (mct--input-string)) mct-minimum-input))
+
+;;;;; Live-updating Completions' buffer
+
+;; Adapted from Omar Antolín Camarena's live-completions library:
+;; <https://github.com/oantolin/live-completions>.
+(defun mct--live-completions (&rest _)
+  "Update the *Completions* buffer.
+Meant to be added to `after-change-functions'."
+  (when (minibufferp) ; skip if we've exited already
+    (let ((while-no-input-ignore-events '(selection-request)))
+      (while-no-input
+        (if (mct--minimum-input)
+            (condition-case nil
+                (save-match-data
+                  (save-excursion
+                    (goto-char (point-max))
+                    (let ((inhibit-message t)
+                          ;; don't ring the bell in 
`minibuffer-completion-help'
+                          ;; when <= 1 completion exists.
+                          (ring-bell-function #'ignore))
+                      (minibuffer-completion-help)
+                      (mct--fit-completions-window))))
+              (quit (abort-recursive-edit)))
+          (minibuffer-hide-completions))))))
+
+(defun mct--live-completions-timer (&rest _)
+  "Update Completions with `mct-live-update-delay'."
+  (let ((delay mct-live-update-delay))
+    (when (>= delay 0)
+      (run-with-idle-timer delay nil #'mct--live-completions))))
+
+(defun mct--setup-completions ()
+  "Set up the completions' buffer."
+  (cond
+   ((member this-command mct-completion-passlist)
+    (setq-local mct-minimum-input 0)
+    (setq-local mct-live-update-delay 0)
+    (save-excursion (minibuffer-completion-help))
+    (mct--fit-completions-window)
+    (add-hook 'after-change-functions #'mct--live-completions nil t))
+   ((unless (member this-command mct-completion-blocklist)
+      (add-hook 'after-change-functions #'mct--live-completions-timer nil 
t)))))
+
+;;;;; Alternating backgrounds (else "stripes")
+
+;; Based on `stripes.el' (maintained by Štěpán Němec) and the
+;; `embark-collect-zebra-minor-mode' from Omar Antolín Camarena's
+;; Embark:
+;;
+;; 1. <https://gitlab.com/stepnem/stripes-el>
+;; 2. <https://github.com/oantolin/embark>
+(defface mct-stripe
+  '((default :extend t)
+    (((class color) (min-colors 88) (background light))
+     :background "#f0f0f0")
+    (((class color) (min-colors 88) (background dark))
+     :background "#191a1b"))
+  "Face for alternating backgrounds in the Completions' buffer."
+  :group 'mct)
+
+(defun mct--remove-stripes ()
+  "Remove `mct-stripe' overlays."
+  (remove-overlays nil nil 'face 'mct-stripe))
+
+(defun mct--add-stripes ()
+  "Overlay alternate rows with the `mct-stripe' face."
+  (when (derived-mode-p 'completion-list-mode)
+    (mct--remove-stripes)
+    (save-excursion
+      (goto-char (point-min))
+      (when (overlays-at (point)) (forward-line))
+      (while (not (eobp))
+        (condition-case nil
+            (forward-line 1)
+          (user-error (goto-char (point-max))))
+        (unless (eobp)
+          (let ((pt (point))
+                (overlay))
+            (condition-case nil
+                (forward-line 1)
+              (user-error (goto-char (point-max))))
+            ;; We set the overlay this way and give it a low priority so
+            ;; that `hl-line-mode' and/or the active region can override
+            ;; it.
+            (setq overlay (make-overlay pt (point)))
+            (overlay-put overlay 'face 'mct-stripe)
+            (overlay-put overlay 'priority -100)))))))
+  
+;;;; Commands and helper functions
+
+;;;;; Focus minibuffer and/or show completions
+
+;;;###autoload
+(defun mct-focus-minibuffer ()
+  "Focus the active minibuffer."
+  (interactive nil mct-mode)
+  (when-let ((mini (active-minibuffer-window)))
+    (select-window mini)))
+
+(defun mct--get-completion-window ()
+  "Find a live window showing completion candidates."
+  (get-window-with-predicate
+   (lambda (window)
+     (string-match-p
+      mct-completion-windows-regexp
+      (buffer-name (window-buffer window))))))
+
+;;;###autoload
+(defun mct-focus-mini-or-completions ()
+  "Focus the active minibuffer or the completions' window.
+
+If both the minibuffer and the Completions are present, this
+command will first move per invocation to the former, then the
+latter, and then continue to switch between the two.
+
+The continuous switch is essentially the same as running
+`mct-focus-minibuffer' and `switch-to-completions' in
+succession.
+
+What constitutes a completions' window is ultimately determined
+by `mct-completion-windows-regexp'."
+  (interactive nil mct-mode)
+  (let* ((mini (active-minibuffer-window))
+         (completions (mct--get-completion-window)))
+    (cond
+     ((and mini (not (minibufferp)))
+      (select-window mini nil))
+     ((and completions (not (eq (selected-window) completions)))
+      (select-window completions nil)))))
+
+;;;###autoload
+(defun mct-list-completions-toggle ()
+  "Toggle the presentation of the completions' buffer."
+  (interactive nil mct-mode)
+  (if (get-buffer-window "*Completions*" 0)
+      (minibuffer-hide-completions)
+    (save-excursion (minibuffer-completion-help))
+    (mct--fit-completions-window)))
+
+;;;;; Commands for file completion
+
+;; Adaptation of `icomplete-fido-backward-updir'.
+(defun mct-backward-updir ()
+  "Delete char before point or go up a directory."
+  (interactive nil mct-mode)
+  (if (and (eq (char-before) ?/)
+           (eq (mct--completion-category) 'file))
+      (save-excursion
+        (goto-char (1- (point)))
+        (when (search-backward "/" (minibuffer-prompt-end) t)
+          (delete-region (1+ (point)) (point-max))))
+    (call-interactively 'backward-delete-char)))
+
+;;;;; Cyclic motions between minibuffer and completions' buffer
+
+(defun mct--switch-to-completions ()
+  "Subroutine for switching to the completions' buffer."
+  (unless (get-buffer-window "*Completions*" 0)
+    (save-excursion (minibuffer-completion-help)))
+  (switch-to-completions)
+  (mct--fit-completions-window))
+
+(defun mct-switch-to-completions-top ()
+  "Switch to the top of the completions' buffer."
+  (interactive nil mct-mode)
+  (mct--switch-to-completions)
+  (goto-char (point-min))
+  (next-completion 1))
+
+(defun mct-switch-to-completions-bottom ()
+  "Switch to the bottom of the completions' buffer."
+  (interactive nil mct-mode)
+  (mct--switch-to-completions)
+  (goto-char (point-max))
+  (next-completion -1)
+  (goto-char (point-at-bol))
+  (recenter
+   (- -1
+      (min (max 0 scroll-margin)
+           (truncate (/ (window-body-height) 4.0))))
+   t))
+
+(defun mct-next-completion-or-mini (&optional arg)
+  "Move to the next completion or switch to the minibuffer.
+This performs a regular motion for optional ARG lines, but when
+point can no longer move in that direction it switches to the
+minibuffer."
+  (interactive "p" mct-mode)
+  (if (or (eobp)
+          (eq (point-max)
+              (save-excursion (forward-line 1) (point))))
+      (mct-focus-minibuffer)
+    (next-completion (or arg 1)))
+  (setq this-command 'next-line))
+
+(defun mct-previous-completion-or-mini (&optional arg)
+  "Move to the next completion or switch to the minibuffer.
+This performs a regular motion for optional ARG lines, but when
+point can no longer move in that direction it switches to the
+minibuffer."
+  (interactive "p" mct-mode)
+  (let ((num (when (and (numberp arg) (> arg 0)) (* -1 arg))))
+    (if (or (bobp)
+            (and (save-excursion ; NOTE 2021-07-23: This `and' is for Emacs28 
group titles
+                   (next-completion -1)
+                   (eq (line-number-at-pos) 1))
+                 (not
+                  (save-excursion
+                    (next-completion -1)
+                    (get-text-property (point) 'completion--string))))
+            (eq (point) (1+ (point-min)))) ; see hack in 
`mct--clean-completions'
+        (mct-focus-minibuffer)
+      (next-completion (or num 1)))))
+
+;;;;; Candidate selection
+
+(defun mct-choose-completion-exit ()
+  "Run `choose-completion' in the Completions buffer and exit."
+  (interactive nil mct-mode)
+  (when (and (derived-mode-p 'completion-list-mode)
+             (active-minibuffer-window))
+    (choose-completion)
+    (minibuffer-force-complete-and-exit)))
+
+(defvar display-line-numbers-mode)
+
+(defun mct--line-completion (n)
+  "Select completion on Nth line."
+  (with-current-buffer "*Completions*"
+    (goto-char (point-min))
+    (forward-line (1- n))
+    (choose-completion)))
+
+(defun mct--line-bounds (n)
+  "Test if Nth line is in the buffer."
+  (with-current-buffer "*Completions*"
+    (let ((bounds (count-lines (point-min) (point-max))))
+      (unless (<= n bounds)
+        (user-error "%d is not within the buffer bounds (%d)" n bounds)))))
+
+(defun mct-goto-line ()
+  "Go to line N in the Completions' buffer."
+  (interactive nil mct-mode)
+  (let ((n (read-number "Line number: ")))
+    (mct--line-bounds n)
+    (select-window (mct--get-completion-window))
+    (mct--line-completion n)))
+
+(defun mct--line-number-selection ()
+  "Show line numbers and select one of them."
+  (with-current-buffer "*Completions*"
+    (let ((mct-show-completion-line-numbers t))
+      (if display-line-numbers-mode
+          (mct-goto-line)
+        (unwind-protect
+            (progn
+              (mct--display-line-numbers)
+              (mct-goto-line))
+          (display-line-numbers-mode -1))))))
+
+(defun mct-choose-completion-number ()
+  "Select completion candidate on line number with completion.
+
+If the Completions' buffer is not visible, it is displayed.  Line
+numbers are shown there for the duration of the operation (unless
+`mct-show-completion-line-numbers' is non-nil, in which case they
+are always visible).
+
+This command can be invoked from either the minibuffer or the
+Completions' buffer."
+  (interactive nil mct-mode)
+  (let ((mct-remove-shadowed-file-names t)
+        (mct-live-update-delay most-positive-fixnum)
+        (enable-recursive-minibuffers t))
+    (unless (get-buffer-window "*Completions*" 0)
+      (save-excursion (minibuffer-completion-help))
+      (mct--fit-completions-window))
+    (if (or (and (derived-mode-p 'completion-list-mode)
+                 (active-minibuffer-window))
+            (and (minibufferp)
+                 (mct--get-completion-window)))
+        (mct--line-number-selection))
+    (user-error "Only use this inside the minibuffer or the Completions")))
+
+(defvar crm-completion-table)
+
+(defun mct-choose-completion-dwim ()
+  "Append to minibuffer when at `completing-read-multiple' prompt.
+Otherwise behave like `mct-choose-completion-exit'."
+  (interactive nil mct-mode)
+  (when (and (derived-mode-p 'completion-list-mode)
+             (active-minibuffer-window))
+    (choose-completion)
+    (with-current-buffer (window-buffer (active-minibuffer-window))
+      (unless (eq (mct--completion-category) 'file)
+        (minibuffer-force-complete))
+      (when crm-completion-table
+        ;; FIXME 2021-10-22: How to deal with commands that let-bind the
+        ;; crm-separator?  For example: `org-set-tags-command'.
+        (insert ",")
+        (let ((inhibit-message t))
+          (switch-to-completions))))))
+
+(defun mct-edit-completion ()
+  "Edit the candidate from the Completions in the minibuffer."
+  (interactive nil mct-mode)
+  (let (string)
+    ;; BUG 2021-07-26: When we use `mct-list-completions-toggle'
+    ;; the first line is active even without switching to the
+    ;; Completions' buffer, so the user would expect that this command
+    ;; would capture the candidate at that point.  It does not.
+    ;;
+    ;; If we focus the Completions' buffer at least once, then
+    ;; everything works as expected.
+    (when (or (and (minibufferp)
+                   (get-buffer-window "*Completions*" 0))
+              (and (derived-mode-p 'completion-list-mode)
+                   (active-minibuffer-window)))
+      (with-current-buffer "*Completions*"
+        (setq string (get-text-property (point) 'completion--string)))
+      (if string
+          (progn
+            (select-window (active-minibuffer-window) nil)
+            (delete-region (minibuffer-prompt-end) (point-max))
+            (insert string))
+        (user-error "Could not find completion at point")))))
+
+;;;;; Miscellaneous commands
+
+;; This is needed to circumvent `mct--clean-completions' with regard to
+;; `cursor-sensor-functions'.
+(defun mct-beginning-of-buffer ()
+  "Go to the top of the Completions buffer."
+  (interactive nil mct-mode)
+  (goto-char (1+ (point-min))))
+
+(defun mct-keyboard-quit-dwim ()
+  "Control the exit behaviour for completions' buffers.
+
+If in a completions' buffer and unless the region is active, run
+`abort-recursive-edit'.  Otherwise run `keyboard-quit'.
+
+If the region is active, deactivate it.  A second invocation of
+this command is then required to abort the session."
+  (interactive nil mct-mode)
+  (when (derived-mode-p 'completion-list-mode)
+    (if (use-region-p)
+        (keyboard-quit)
+      (abort-recursive-edit))))
+
+;;;; Global minor mode setup
+
+;;;;; Stylistic tweaks and refinements
+
+;; Thanks to Omar Antolín Camarena for providing the messageless and
+;; stealthily.  Source: <https://github.com/oantolin/emacs-config>.
+(defun mct--messageless (fn &rest args)
+  "Set `minibuffer-message-timeout' to 0.
+Meant as advice around minibuffer completion FN with ARGS."
+  (let ((minibuffer-message-timeout 0))
+    (apply fn args)))
+
+;; Copied from Daniel Mendler's `vertico' library:
+;; <https://github.com/minad/vertico>.
+(defun mct--crm-indicator (args)
+  "Add prompt indicator to `completing-read-multiple' filter ARGS."
+  (cons (concat "[CRM] " (car args)) (cdr args)))
+
+;; Adapted from Omar Antolín Camarena's live-completions library:
+;; <https://github.com/oantolin/live-completions>.
+(defun mct--honor-inhibit-message (fn &rest args)
+  "Skip applying FN to ARGS if `inhibit-message' is t.
+Meant as `:around' advice for `minibuffer-message', which does
+not honor minibuffer message."
+  (unless inhibit-message
+    (apply fn args)))
+
+;; Note that this solves bug#45686:
+;; <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45686>
+(defun mct--stealthily (fn &rest args)
+  "Prevent minibuffer default from counting as a modification.
+Meant as advice for FN `minibuf-eldef-setup-minibuffer' with rest
+ARGS."
+  (let ((inhibit-modification-hooks t))
+    (apply fn args)))
+
+(defun mct--setup-completions-styles ()
+  "Set up variables for default completions."
+  (when mct-hide-completion-mode-line
+    (setq-local mode-line-format nil))
+  (if mct-apply-completion-stripes
+      (mct--add-stripes)
+    (mct--remove-stripes)))
+
+(defun mct--truncate-lines-silently ()
+  "Toggle line truncation without printing messages."
+  (let ((inhibit-message t))
+    (toggle-truncate-lines t)))
+
+;;;;; Shadowed path
+
+;; Adapted from icomplete.el
+(defun mct--shadow-filenames (&rest _)
+  "Hide shadowed file names."
+  (let ((saved-point (point)))
+    (when (and
+           mct-remove-shadowed-file-names
+           (eq (mct--completion-category) 'file)
+           rfn-eshadow-overlay (overlay-buffer rfn-eshadow-overlay)
+           (eq this-command 'self-insert-command)
+           (= saved-point (mct--field-end))
+           (or (>= (- (point) (overlay-end rfn-eshadow-overlay)) 2)
+               (eq ?/ (char-before (- (point) 2)))))
+      (delete-region (overlay-start rfn-eshadow-overlay)
+                     (overlay-end rfn-eshadow-overlay)))))
+
+(defun mct--setup-shadow-files ()
+  "Set up shadowed file name deletion.
+To be assigned to `minibuffer-setup-hook'."
+  (add-hook 'after-change-functions #'mct--shadow-filenames nil t))
+
+;;;;; Keymaps
+
+(defvar mct-completion-list-mode-map
+  (let ((map (make-sparse-keymap)))
+    (define-key map (kbd "<tab>") #'choose-completion)
+    (define-key map (kbd "M-v") #'scroll-down-command)
+    (define-key map (kbd "M-g M-g") #'mct-choose-completion-number)
+    (define-key map (kbd "M-e") #'mct-edit-completion)
+    (define-key map (kbd "C-g") #'mct-keyboard-quit-dwim)
+    (define-key map (kbd "C-n") #'mct-next-completion-or-mini)
+    (define-key map (kbd "n") #'mct-next-completion-or-mini)
+    (define-key map (kbd "<down>") #'mct-next-completion-or-mini)
+    (define-key map (kbd "C-p") #'mct-previous-completion-or-mini)
+    (define-key map (kbd "p") #'mct-previous-completion-or-mini)
+    (define-key map (kbd "<up>") #'mct-previous-completion-or-mini)
+    (define-key map (kbd "<return>") #'mct-choose-completion-exit)
+    (define-key map (kbd "<M-return>") #'mct-choose-completion-dwim)
+    (define-key map (kbd "M-<") #'mct-beginning-of-buffer)
+    map)
+  "Derivative of `completion-list-mode-map'.")
+
+(defvar mct-minibuffer-local-completion-map
+  (let ((map (make-sparse-keymap)))
+    (define-key map (kbd "C-j") #'exit-minibuffer)
+    (define-key map (kbd "<tab>") #'minibuffer-force-complete)
+    (define-key map (kbd "M-g M-g") #'mct-choose-completion-number)
+    (define-key map (kbd "M-e") #'mct-edit-completion)
+    (define-key map (kbd "C-n") #'mct-switch-to-completions-top)
+    (define-key map (kbd "<down>") #'mct-switch-to-completions-top)
+    (define-key map (kbd "C-p") #'mct-switch-to-completions-bottom)
+    (define-key map (kbd "<up>") #'mct-switch-to-completions-bottom)
+    (define-key map (kbd "C-l") #'mct-list-completions-toggle)
+    map)
+  "Derivative of `minibuffer-local-completion-map'.")
+
+(defvar mct-minibuffer-local-filename-completion-map
+  (let ((map (make-sparse-keymap)))
+    (define-key map (kbd "<backspace>") #'mct-backward-updir)
+    map)
+  "Derivative of `minibuffer-local-filename-completion-map'.")
+
+(defun mct--completion-list-mode-map ()
+  "Hook to `completion-setup-hook'."
+  (use-local-map
+   (make-composed-keymap mct-completion-list-mode-map
+                         (current-local-map))))
+
+(defun mct--minibuffer-local-completion-map ()
+  "Hook to `minibuffer-setup-hook'."
+  (use-local-map
+   (make-composed-keymap mct-minibuffer-local-completion-map
+                         (current-local-map))))
+
+(defun mct--minibuffer-local-filename-completion-map ()
+  "Hook to `minibuffer-setup-hook'."
+  (use-local-map
+   (make-composed-keymap mct-minibuffer-local-filename-completion-map
+                         (current-local-map))))
+
+;;;;; mct-mode declaration
+
+(declare-function minibuf-eldef-setup-minibuffer "minibuf-eldef")
+
+(defvar mct--resize-mini-windows nil)
+(defvar mct--completion-show-help nil)
+(defvar mct--completion-auto-help nil)
+(defvar mct--completions-format nil)
+(defvar mct--completions-detailed nil)
+
+;;;###autoload
+(define-minor-mode mct-mode
+  "Set up opinionated default completion UI."
+  :global t
+  :group 'mct
+  (if mct-mode
+      (progn
+        (setq mct--resize-mini-windows resize-mini-windows
+              mct--completion-show-help completion-show-help
+              mct--completion-auto-help completion-auto-help
+              mct--completions-format completions-format
+              mct--completions-detailed completions-detailed)
+        (setq resize-mini-windows t
+              completion-show-help nil
+              completion-auto-help t
+              completions-format 'one-column
+              completions-detailed t)
+        (let ((hook 'minibuffer-setup-hook))
+          (add-hook hook #'mct--setup-completions)
+          (add-hook hook #'mct--minibuffer-local-completion-map)
+          (add-hook hook #'mct--minibuffer-local-filename-completion-map)
+          (add-hook hook #'mct--setup-shadow-files))
+        (let ((hook 'completion-list-mode-hook))
+          (add-hook hook #'mct--setup-completions-styles)
+          (add-hook hook #'mct--completion-list-mode-map)
+          (add-hook hook #'mct--truncate-lines-silently)
+          (add-hook hook #'mct--hl-line)
+          (add-hook hook #'mct--display-line-numbers)
+          (add-hook hook #'cursor-sensor-mode))
+        (add-hook 'completion-setup-hook #'mct--clean-completions)
+        (dolist (fn '(exit-minibuffer
+                      choose-completion
+                      minibuffer-force-complete
+                      minibuffer-complete-and-exit
+                      minibuffer-force-complete-and-exit))
+          (advice-add fn :around #'mct--messageless))
+        (advice-add #'completing-read-multiple :filter-args 
#'mct--crm-indicator)
+        (advice-add #'minibuffer-message :around #'mct--honor-inhibit-message)
+        (advice-add #'minibuf-eldef-setup-minibuffer :around 
#'mct--stealthily))
+    (setq resize-mini-windows mct--resize-mini-windows
+          completion-show-help mct--completion-show-help
+          completion-auto-help mct--completion-auto-help
+          completions-format mct--completions-format
+          completions-detailed mct--completions-detailed)
+    (let ((hook 'minibuffer-setup-hook))
+      (remove-hook hook #'mct--setup-completions)
+      (remove-hook hook #'mct--minibuffer-local-completion-map)
+      (remove-hook hook #'mct--minibuffer-local-filename-completion-map))
+    (let ((hook 'completion-list-mode-hook))
+      (remove-hook hook #'mct--setup-completions-styles)
+      (remove-hook hook #'mct--completion-list-mode-map)
+      (remove-hook hook #'mct--truncate-lines-silently)
+      (remove-hook hook #'mct--hl-line)
+      (remove-hook hook #'mct--display-line-numbers)
+      (remove-hook hook #'cursor-sensor-mode))
+    (remove-hook 'completion-setup-hook #'mct--clean-completions)
+    (dolist (fn '(exit-minibuffer
+                  choose-completion
+                  minibuffer-force-complete
+                  minibuffer-complete-and-exit
+                  minibuffer-force-complete-and-exit))
+      (advice-remove fn #'mct--messageless))
+    (advice-remove #'completing-read-multiple #'mct--crm-indicator)
+    (advice-remove #'minibuffer-message #'mct--honor-inhibit-message)
+    (advice-remove #'minibuf-eldef-setup-minibuffer #'mct--stealthily)))
+
+(provide 'mct)
+;;; mct.el ends here
diff --git a/mct.info b/mct.info
new file mode 100644
index 0000000..6787d86
--- /dev/null
+++ b/mct.info
@@ -0,0 +1,964 @@
+This is mct.info, produced by makeinfo version 6.8 from mct.texi.
+
+Copyright (C) 2021 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.”
+
+INFO-DIR-SECTION Emacs misc features
+START-INFO-DIR-ENTRY
+* Minibuffer and Completions in Tandem: (mct). Enhancement of the default 
minibuffer completion.
+END-INFO-DIR-ENTRY
+
+
+File: mct.info,  Node: Top,  Next: Overview of mctel,  Up: (dir)
+
+Minibuffer and Completions in Tandem (mct.el)
+*********************************************
+
+Copyright (C) 2021 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 Protesilaos Stavrou, describes the
+customization options for ‘mct.el’, and provides every other piece of
+information pertinent to it.
+
+   The documentation furnished herein corresponds to stable version
+0.1.0, released on 2021-10-22.  Any reference to a newer feature which
+does not yet form part of the latest tagged commit, is explicitly marked
+as such.
+
+   Current development target is 0.2.0-dev.
+
+* Menu:
+
+* Overview of mct.el: Overview of mctel.
+* Basic usage::
+* Installation::
+* Sample setup::
+* Keymaps::
+* Extensions::
+* Alternatives::
+* GNU Free Documentation License::
+* Indices::
+
+— The Detailed Node Listing —
+
+Basic usage
+
+* Cyclic behaviour::
+* Selecting candidates::
+
+Indices
+
+* Function index::
+* Variable index::
+* Concept index::
+
+
+
+File: mct.info,  Node: Overview of mctel,  Next: Basic usage,  Prev: Top,  Up: 
Top
+
+1 Overview of mct.el
+********************
+
+Minibuffer and Completions in Tandem, also known as “MCT”, “Mct”, ‘mct’,
+or ‘mct.el’, is a package that enhances the default minibuffer and
+‘*Completions*’ buffer of Emacs 28 (or higher) so that they work
+together as part of a unified framework.  The idea is to make the
+presentation and overall functionality be consistent with other popular,
+vertically aligned completion UIs while leveraging built-in
+functionality.
+
+   The main feature set that unifies the minibuffer and the
+‘*Completions*’ buffer consists of commands that cycle between the two,
+making it seem like they are part of a contiguous space (*note Basic
+usage::).
+
+   MCT tries to find a middle ground between the frugal defaults and the
+more opinionated completion UIs.  This is most evident in its approach
+on how to present completion candidates.  Instead of showing them
+outright or only displaying them on demand, MCT implements a minimum
+input threshold as well as a slight delay before it pops up the
+‘*Completions*’ buffer and starts updating it to respond to user input.
+
+   Customisation options control the input threshold
+(‘mct-minimum-input’) and the delay between live updates
+(‘mct-live-update-delay’).  Similarly, a blocklist and a passlist for
+commands are on offer:
+
+   • The blocklist (‘mct-completion-blocklist’) disables the
+     live-updating functionality for the commands specified therein.
+
+   • The passlist (‘mct-completion-passlist’) always shows the
+     Completions’ buffer for the designated command without accounting
+     for the minimum input threshold.
+
+   Other customisations:
+
+   • ‘mct-hide-completion-mode-line’ to hide the mode line of the
+     ‘*Completions*’ buffer.  This removes the separation between it and
+     the minibuffer, further contributing to the idea of a unified space
+     between the two.
+
+   • ‘mct-remove-shadowed-file-name’ to clear shadowed file names when
+     ‘file-name-shadow-mode’ is enabled.  This means that in prompts
+     that use file paths (such as ‘find-file’) when you start in, say,
+     ‘~/Git/mct.el’ and type ‘~/’ the previous file path is removed and
+     only the new one is inserted.  Whereas the default is to keep the
+     original file name visible yet “shadowed” by a different colour.
+
+   • ‘mct-show-completion-line-numbers’ to always display line numbers
+     in the Completions’ buffer.  This can be helpful to get a sense of
+     the length of the completion candidates’ list.  Though note that
+     line numbers are displayed ephemerally while using the
+     ‘mct-choose-completion-number’ command, which is bound to ‘M-g M-g’
+     in either the minibuffer or the ‘*Completions*’ buffer.
+
+   • ‘mct-apply-completion-stripes’ applies alternative background
+     colours in the Completions’ buffer.  This is only tested with the
+     ‘modus-themes’ and will only work nicely if the main background is
+     pure black or white—other themes would need to add support for the
+     faces we define or, at least, users must modify the ‘mct-stripe’
+     face.
+
+
+File: mct.info,  Node: Basic usage,  Next: Installation,  Prev: Overview of 
mctel,  Up: Top
+
+2 Basic usage
+*************
+
+* Menu:
+
+* Cyclic behaviour::
+* Selecting candidates::
+
+
+File: mct.info,  Node: Cyclic behaviour,  Next: Selecting candidates,  Up: 
Basic usage
+
+2.1 Cyclic behaviour
+====================
+
+When ‘mct-mode’ is enabled, some new keymaps are activated which add
+commands for cycling between the minibuffer and the completions.
+Suppose the following standard layout:
+
+     -----------------
+     |               |
+     |               |
+     |               |
+     |  Buffer       |
+     |               |
+     |               |
+     |               |
+     -----------------
+     -----------------
+     |               |
+     |  Completions  |
+     |               |
+     -----------------
+     -----------------
+     |  Minibuffer   |
+     -----------------
+
+   When inside the minibuffer, pressing ‘C-n’ (or down arrow) takes you
+to the top of the completions, while ‘C-p’ (or up arrow) moves to the
+bottom.  The commands are ‘mct-switch-to-completions-top’ for the former
+and ‘mct-switch-to-completions-bottom’ for the latter.  If the
+‘*Completions*’ are not shown, then the buffer pops up automatically and
+point moves to the given position.
+
+   Similarly, while inside the ‘*Completions*’ buffer, ‘C-p’ (or up
+arrow) at the top of the buffer switches to the minibuffer, while ‘C-n’
+(or down arrow) at the bottom of the buffer also goes to the minibuffer.
+If point is anywhere else inside the buffer, those key bindings perform
+a regular line motion.  The commands are
+‘mct-previous-completion-or-mini’ and ‘mct-next-completion-or-mini’.
+
+   The display of the ‘*Completions*’ can be toggled at any time from
+inside the minibuffer with ‘C-l’ (mnemonic is “[l]ist completions” and
+the command is ‘mct-list-completions-toggle’).
+
+
+File: mct.info,  Node: Selecting candidates,  Prev: Cyclic behaviour,  Up: 
Basic usage
+
+2.2 Selecting candidates
+========================
+
+There are several ways to select a completion candidate.
+
+  1. Suppose that you are typing ‘mod’ with the intent to select the
+     ‘modus-themes.el’ buffer.  To complete the first candidate follow
+     up ‘mod’ with the ‘TAB’ key.  This is how you would do it with the
+     default minibuffer.  If done fast enough, no completions will be
+     shown (depending on your minimum input threshold and the
+     live-update delay).
+
+  2. Upon cycling through the completions, type ‘RET’ to select the
+     candidate at point and exit the minibuffer.  This works for all
+     types of completion prompts.
+
+  3. For certain contexts where selecting a candidate does not
+     necessarily mean that the process has to be finalised (e.g.  when
+     using ‘find-file’) selection in the ‘*Completions*’ buffer can be
+     done with ‘TAB’ which completes the item at point but does not exit
+     the minibuffer.  The command is instead renewed to update the list
+     of completions with the new candidates.
+
+  4. Select a candidate by its line number by typing ‘M-g M-g’ in either
+     the minibuffer or the ‘*Completions*’ buffer.  This calls the
+     command ‘mct-choose-completion-number’ which internally enables
+     line numbers and always makes the completions’ buffer visible.
+
+  5. In prompts that allow the selection of multiple candidates
+     (internally via the ‘completing-read-multiple’ function) a ‘[CRM]’
+     label is added to the text of the prompt.  The user thus knows that
+     pressing ‘M-RET’ in the ‘*Completions*’ will append the candidate
+     at point to the list of selections and keep the completions
+     available so that another item may be selected.  Any of the
+     aforementioned applicable methods can confirm the final selection.
+     If, say, you want to pick a total of three candidates, do ‘M-RET’
+     for the first two and ‘RET’ for the last one.  In contexts that are
+     not CRM-powered, the ‘M-RET’ has the same effect as ‘RET’.
+
+     NOTE 2021-10-22: this assumes the ‘crm-separator’ to be constant
+     (the comma ‘,’ character) but some commands ‘let’ bind it to
+     something else, so the behaviour does not work as expected.  One
+     such case is ‘org-set-tags-command’ which uses ‘:’ as a separator.
+
+  6. Type ‘M-e’ (‘mct-edit-completion’) in the completions’ buffer to
+     place the current candidate in the minibuffer, without exiting the
+     session.  This allows you to edit the text before confirming it.
+
+
+File: mct.info,  Node: Installation,  Next: Sample setup,  Prev: Basic usage,  
Up: Top
+
+3 Installation
+**************
+
+MCT is not in any package archive for the time being, though I plan to
+submit it to GNU ELPA (as such, any non-trivial patches require
+copyright assignment to the Free Software Foundation).  Users can rely
+on ‘straight.el’, ‘quelpa’, or equivalent to fetch the source.  Below
+are the essentials for those who prefer the manual method.
+
+   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 and name it "mct"
+     git clone https://gitlab.com/protesilaos/mct.el.git mct
+
+   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/")
+
+   Everything is in place to set up the package.
+
+
+File: mct.info,  Node: Sample setup,  Next: Keymaps,  Prev: Installation,  Up: 
Top
+
+4 Sample setup
+**************
+
+Minimal setup:
+
+     (require 'mct)
+     (mct-mode 1)
+
+   And with more options:
+
+     (require 'mct)
+
+     (setq mct-remove-shadowed-file-names t) ; works when 
`file-name-shadow-mode' is enabled
+     (setq mct-hide-completion-mode-line t)
+     (setq mct-show-completion-line-numbers nil)
+     (setq mct-apply-completion-stripes t)
+     (setq mct-minimum-input 3)
+     (setq mct-live-update-delay 0.6)
+
+     ;; NOTE: `mct-completion-blocklist' can be used for commands with lots
+     ;; of candidates, depending also on how low `mct-minimum-input' is.
+     ;; With the settings shown here this is not required, otherwise I would
+     ;; use something like this:
+     ;;
+     ;; (setq mct-completion-blocklist
+     ;;       '( describe-symbol describe-function describe-variable
+     ;;          execute-extended-command insert-char))
+     (setq mct-completion-blocklist nil)
+
+     ;; This is for commands that should always pop up the completions'
+     ;; buffer.  It circumvents the default method of waiting for some user
+     ;; input (see `mct-minimum-input') before displaying and updating the
+     ;; completions' buffer.
+     (setq mct-completion-passlist
+           '(imenu
+             Info-goto-node
+             Info-index
+             Info-menu
+             vc-retrieve-tag))
+
+     (mct-mode 1)
+
+   Other useful extras from the Emacs source code:
+
+     (setq enable-recursive-minibuffers t)
+     (setq minibuffer-eldef-shorten-default t)
+
+     (file-name-shadow-mode 1)
+     (minibuffer-depth-indicate-mode 1)
+     (minibuffer-electric-default-mode 1)
+
+
+File: mct.info,  Node: Keymaps,  Next: Extensions,  Prev: Sample setup,  Up: 
Top
+
+5 Keymaps
+*********
+
+MCT defines its own keymaps, which extend those that are active in the
+minibuffer and the ‘*Completions*’ buffer, respectively:
+
+   • ‘mct-completion-list-mode-map’
+   • ‘mct-minibuffer-local-completion-map’
+   • ‘mct-minibuffer-local-filename-completion-map’
+
+   You can invoke ‘describe-keymap’ to learn more about them.
+
+   If you want to edit any key bindings, do it in those keymaps, not in
+those they extend and override (the names of the original ones are the
+same as above, minus the ‘mct-’ prefix).
+
+
+File: mct.info,  Node: Extensions,  Next: Alternatives,  Prev: Keymaps,  Up: 
Top
+
+6 Extensions
+************
+
+MCT only tweaks the default minibuffer.  To get more out of it, consider
+these exceptionally well-crafted extras:
+
+‘consult’
+     Adds several commands that make interacting with the minibuffer
+     more powerful.  There also are several packages that build on it,
+     such as ‘consult-dir’.
+‘embark’
+     Provides configurable contextual actions for completions and many
+     other constructs inside buffers.
+‘marginalia’
+     Displays informative annotations for all known types of completion
+     candidates.
+‘orderless’
+     A completion style that matches a variety of patterns (regexp,
+     flex, initialism, etc.)  regardless of the order they appear in.
+
+
+File: mct.info,  Node: Alternatives,  Next: GNU Free Documentation License,  
Prev: Extensions,  Up: Top
+
+7 Alternatives
+**************
+
+The only alternative I have used that is conceptually close to MCT is
+‘vertico’.  Vertico is a more mature and feature-rich package, while its
+maintainer, Daniel Mendler, is an accomplished programmer.  Whereas MCT
+is mostly an excuse to practice my Elisp skills.
+
+
+File: mct.info,  Node: GNU Free Documentation License,  Next: Indices,  Prev: 
Alternatives,  Up: Top
+
+Appendix A GNU Free Documentation License
+*****************************************
+
+                     Version 1.3, 3 November 2008
+
+     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.
+
+  0. PREAMBLE
+
+     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.
+
+  1. APPLICABILITY AND DEFINITIONS
+
+     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.
+
+  2. VERBATIM COPYING
+
+     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.
+
+  3. COPYING IN QUANTITY
+
+     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.
+
+  4. MODIFICATIONS
+
+     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:
+
+       A. Use in the Title Page (and on the covers, if any) a title
+          distinct from that of the Document, and from those of previous
+          versions (which should, if there were any, be listed in the
+          History section of the Document).  You may use the same title
+          as a previous version if the original publisher of that
+          version gives permission.
+
+       B. List on the Title Page, as authors, one or more persons or
+          entities responsible for authorship of the modifications in
+          the Modified Version, together with at least five of the
+          principal authors of the Document (all of its principal
+          authors, if it has fewer than five), unless they release you
+          from this requirement.
+
+       C. State on the Title page the name of the publisher of the
+          Modified Version, as the publisher.
+
+       D. Preserve all the copyright notices of the Document.
+
+       E. Add an appropriate copyright notice for your modifications
+          adjacent to the other copyright notices.
+
+       F. Include, immediately after the copyright notices, a license
+          notice giving the public permission to use the Modified
+          Version under the terms of this License, in the form shown in
+          the Addendum below.
+
+       G. Preserve in that license notice the full lists of Invariant
+          Sections and required Cover Texts given in the Document’s
+          license notice.
+
+       H. Include an unaltered copy of this License.
+
+       I. Preserve the section Entitled “History”, Preserve its Title,
+          and add to it an item stating at least the title, year, new
+          authors, and publisher of the Modified Version as given on the
+          Title Page.  If there is no section Entitled “History” in the
+          Document, create one stating the title, year, authors, and
+          publisher of the Document as given on its Title Page, then add
+          an item describing the Modified Version as stated in the
+          previous sentence.
+
+       J. Preserve the network location, if any, given in the Document
+          for public access to a Transparent copy of the Document, and
+          likewise the network locations given in the Document for
+          previous versions it was based on.  These may be placed in the
+          “History” section.  You may omit a network location for a work
+          that was published at least four years before the Document
+          itself, or if the original publisher of the version it refers
+          to gives permission.
+
+       K. For any section Entitled “Acknowledgements” or “Dedications”,
+          Preserve the Title of the section, and preserve in the section
+          all the substance and tone of each of the contributor
+          acknowledgements and/or dedications given therein.
+
+       L. Preserve all the Invariant Sections of the Document, unaltered
+          in their text and in their titles.  Section numbers or the
+          equivalent are not considered part of the section titles.
+
+       M. Delete any section Entitled “Endorsements”.  Such a section
+          may not be included in the Modified Version.
+
+       N. Do not retitle any existing section to be Entitled
+          “Endorsements” or to conflict in title with any Invariant
+          Section.
+
+       O. Preserve any Warranty Disclaimers.
+
+     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.
+
+  5. COMBINING DOCUMENTS
+
+     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.”
+
+  6. COLLECTIONS OF DOCUMENTS
+
+     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.
+
+  7. AGGREGATION WITH INDEPENDENT WORKS
+
+     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.
+
+  8. TRANSLATION
+
+     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.
+
+  9. TERMINATION
+
+     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.
+
+  10. FUTURE REVISIONS OF THIS LICENSE
+
+     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.
+
+  11. RELICENSING
+
+     “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.
+
+ADDENDUM: How to use this License for your documents
+====================================================
+
+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.
+
+
+File: mct.info,  Node: Indices,  Prev: GNU Free Documentation License,  Up: Top
+
+B Indices
+*********
+
+* Menu:
+
+* Function index::
+* Variable index::
+* Concept index::
+
+
+File: mct.info,  Node: Function index,  Next: Variable index,  Up: Indices
+
+B.1 Function index
+==================
+
+[index]
+* Menu:
+
+* mct-choose-completion-number:          Overview of mctel.     (line 6)
+* mct-edit-completion:                   Selecting candidates.  (line 6)
+* mct-list-completions-toggle:           Cyclic behaviour.      (line 6)
+* mct-next-completion-or-mini:           Cyclic behaviour.      (line 6)
+* mct-previous-completion-or-mini:       Cyclic behaviour.      (line 6)
+* mct-switch-to-completions-bottom:      Cyclic behaviour.      (line 6)
+* mct-switch-to-completions-top:         Cyclic behaviour.      (line 6)
+
+
+File: mct.info,  Node: Variable index,  Next: Concept index,  Prev: Function 
index,  Up: Indices
+
+B.2 Variable index
+==================
+
+[index]
+* Menu:
+
+* mct-apply-completion-stripes:          Overview of mctel.     (line 6)
+* mct-completion-blocklist:              Overview of mctel.     (line 6)
+* mct-completion-list-mode-map:          Keymaps.               (line 6)
+* mct-completion-passlist:               Overview of mctel.     (line 6)
+* mct-hide-completion-mode-line:         Overview of mctel.     (line 6)
+* mct-live-update-delay:                 Overview of mctel.     (line 6)
+* mct-minibuffer-local-completion-map:   Keymaps.               (line 6)
+* mct-minibuffer-local-filename-completion-map: Keymaps.        (line 6)
+* mct-minimum-input:                     Overview of mctel.     (line 6)
+* mct-remove-shadowed-file-name:         Overview of mctel.     (line 6)
+* mct-stripe:                            Overview of mctel.     (line 6)
+
+
+File: mct.info,  Node: Concept index,  Prev: Variable index,  Up: Indices
+
+B.3 Concept index
+=================
+
+[index]
+* Menu:
+
+* Alternatives to MCT:                   Alternatives.          (line 6)
+* Candidate selection:                   Selecting candidates.  (line 6)
+* Cyclic behaviour:                      Cyclic behaviour.      (line 6)
+* Extra packages:                        Extensions.            (line 6)
+* Keymaps:                               Keymaps.               (line 6)
+* Overview of features:                  Overview of mctel.     (line 6)
+* Sample configuration:                  Sample setup.          (line 6)
+
+
+
+Tag Table:
+Node: Top865
+Node: Overview of mctel2436
+Node: Basic usage5705
+Node: Cyclic behaviour5885
+Node: Selecting candidates7616
+Node: Installation10322
+Node: Sample setup11407
+Node: Keymaps13089
+Node: Extensions13733
+Node: Alternatives14528
+Node: GNU Free Documentation License14935
+Node: Indices40286
+Node: Function index40456
+Node: Variable index41106
+Node: Concept index42070
+
+End Tag Table
+
+
+Local Variables:
+coding: utf-8
+End:
diff --git a/mct.texi b/mct.texi
new file mode 100644
index 0000000..c1a498d
--- /dev/null
+++ b/mct.texi
@@ -0,0 +1,473 @@
+\input texinfo    @c -*- texinfo -*-
+@c %**start of header
+@setfilename mct.info
+@settitle Minibuffer and Completions in Tandem (mct.el)
+@documentencoding UTF-8
+@documentlanguage en
+@set MAINTAINERSITE @uref{https://protesilaos.com,maintainer webpage}
+@set MAINTAINER Protesilaos Stavrou
+@set MAINTAINEREMAIL @email{info@protesilaos.com}
+@set MAINTAINERCONTACT @uref{mailto:info@protesilaos.com,contact the 
maintainer}
+@c %**end of header
+
+@copying
+Copyright (C) 2021  Free Software Foundation, Inc.
+
+@quotation
+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.”
+
+@end quotation
+@end copying
+
+@dircategory Emacs misc features
+@direntry
+* Minibuffer and Completions in Tandem: (mct). Enhancement of the default 
minibuffer completion.
+@end direntry
+
+@finalout
+@titlepage
+@title Minibuffer and Completions in Tandem (mct.el)
+@author Protesilaos Stavrou (@email{info@@protesilaos.com})
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+@end titlepage
+
+@ifnottex
+@node Top
+@top Minibuffer and Completions in Tandem (mct.el)
+
+@insertcopying
+
+This manual, written by Protesilaos Stavrou, describes the customization
+options for @samp{mct.el}, and provides every other piece of information
+pertinent to it.
+
+The documentation furnished herein corresponds to stable version
+0.1.0, released on 2021-10-22.  Any reference to a newer
+feature which does not yet form part of the latest tagged commit, is
+explicitly marked as such.
+
+Current development target is 0.2.0-dev.
+
+@end ifnottex
+
+@menu
+* Overview of mct.el: Overview of mctel. 
+* Basic usage::
+* Installation::
+* Sample setup::
+* Keymaps::
+* Extensions::
+* Alternatives::
+* GNU Free Documentation License::
+* Indices::
+
+@detailmenu
+--- The Detailed Node Listing ---
+
+Basic usage
+
+* Cyclic behaviour::
+* Selecting candidates::
+
+Indices
+
+* Function index::
+* Variable index::
+* Concept index::
+
+@end detailmenu
+@end menu
+
+@node Overview of mctel
+@chapter Overview of mct.el
+
+@cindex Overview of features
+@findex mct-choose-completion-number
+@vindex mct-minimum-input
+@vindex mct-live-update-delay
+@vindex mct-completion-blocklist
+@vindex mct-completion-passlist
+@vindex mct-hide-completion-mode-line
+@vindex mct-remove-shadowed-file-name
+@vindex mct-apply-completion-stripes
+@vindex mct-stripe
+
+Minibuffer and Completions in Tandem, also known as ``MCT'', ``Mct'', 
@samp{mct},
+or @samp{mct.el}, is a package that enhances the default minibuffer and
+@samp{*Completions*} buffer of Emacs 28 (or higher) so that they work together
+as part of a unified framework.  The idea is to make the presentation
+and overall functionality be consistent with other popular, vertically
+aligned completion UIs while leveraging built-in functionality.
+
+The main feature set that unifies the minibuffer and the @samp{*Completions*}
+buffer consists of commands that cycle between the two, making it seem
+like they are part of a contiguous space (@ref{Basic usage}).
+
+MCT tries to find a middle ground between the frugal defaults and the
+more opinionated completion UIs.  This is most evident in its approach
+on how to present completion candidates.  Instead of showing them
+outright or only displaying them on demand, MCT implements a minimum
+input threshold as well as a slight delay before it pops up the
+@samp{*Completions*} buffer and starts updating it to respond to user input.
+
+Customisation options control the input threshold (@code{mct-minimum-input})
+and the delay between live updates (@code{mct-live-update-delay}).  Similarly,
+a blocklist and a passlist for commands are on offer:
+
+@itemize
+@item
+The blocklist (@code{mct-completion-blocklist}) disables the live-updating
+functionality for the commands specified therein.
+
+@item
+The passlist (@code{mct-completion-passlist}) always shows the Completions'
+buffer for the designated command without accounting for the minimum
+input threshold.
+@end itemize
+
+Other customisations:
+
+@itemize
+@item
+@code{mct-hide-completion-mode-line} to hide the mode line of the
+@samp{*Completions*} buffer.  This removes the separation between it and the
+minibuffer, further contributing to the idea of a unified space
+between the two.
+
+@item
+@code{mct-remove-shadowed-file-name} to clear shadowed file names when
+@code{file-name-shadow-mode} is enabled.  This means that in prompts that use
+file paths (such as @code{find-file}) when you start in, say, 
@samp{~/Git/mct.el}
+and type @samp{~/} the previous file path is removed and only the new one is
+inserted.  Whereas the default is to keep the original file name
+visible yet ``shadowed'' by a different colour.
+
+@item
+@code{mct-show-completion-line-numbers} to always display line numbers in the
+Completions' buffer.  This can be helpful to get a sense of the length
+of the completion candidates' list.  Though note that line numbers are
+displayed ephemerally while using the @code{mct-choose-completion-number}
+command, which is bound to @samp{M-g M-g} in either the minibuffer or the
+@samp{*Completions*} buffer.
+
+@item
+@code{mct-apply-completion-stripes} applies alternative background colours in
+the Completions' buffer.  This is only tested with the @samp{modus-themes}
+and will only work nicely if the main background is pure black or
+white---other themes would need to add support for the faces we define
+or, at least, users must modify the @code{mct-stripe} face.
+@end itemize
+
+@node Basic usage
+@chapter Basic usage
+
+@menu
+* Cyclic behaviour::
+* Selecting candidates::
+@end menu
+
+@node Cyclic behaviour
+@section Cyclic behaviour
+
+@cindex Cyclic behaviour
+@findex mct-switch-to-completions-top
+@findex mct-switch-to-completions-bottom
+@findex mct-previous-completion-or-mini
+@findex mct-next-completion-or-mini
+@findex mct-list-completions-toggle
+
+When @code{mct-mode} is enabled, some new keymaps are activated which add
+commands for cycling between the minibuffer and the completions.
+Suppose the following standard layout:
+
+@example
+-----------------
+|               |
+|               |
+|               |
+|  Buffer       |
+|               |
+|               |
+|               |
+-----------------
+-----------------
+|               |
+|  Completions  |
+|               |
+-----------------
+-----------------
+|  Minibuffer   |
+-----------------
+@end example
+
+When inside the minibuffer, pressing @samp{C-n} (or down arrow) takes you to
+the top of the completions, while @samp{C-p} (or up arrow) moves to the bottom.
+The commands are @code{mct-switch-to-completions-top} for the former and
+@code{mct-switch-to-completions-bottom} for the latter.  If the 
@samp{*Completions*}
+are not shown, then the buffer pops up automatically and point moves to
+the given position.
+
+Similarly, while inside the @samp{*Completions*} buffer, @samp{C-p} (or up 
arrow) at
+the top of the buffer switches to the minibuffer, while @samp{C-n} (or down
+arrow) at the bottom of the buffer also goes to the minibuffer.  If
+point is anywhere else inside the buffer, those key bindings perform a
+regular line motion.  The commands are @code{mct-previous-completion-or-mini}
+and @code{mct-next-completion-or-mini}.
+
+The display of the @samp{*Completions*} can be toggled at any time from inside
+the minibuffer with @samp{C-l} (mnemonic is ``[l]ist completions'' and the
+command is @code{mct-list-completions-toggle}).
+
+@node Selecting candidates
+@section Selecting candidates
+
+@cindex Candidate selection
+@findex mct-edit-completion
+
+There are several ways to select a completion candidate.
+
+@enumerate
+@item
+Suppose that you are typing @samp{mod} with the intent to select the
+@samp{modus-themes.el} buffer.  To complete the first candidate follow up
+@samp{mod} with the @samp{TAB} key.  This is how you would do it with the 
default
+minibuffer.  If done fast enough, no completions will be shown
+(depending on your minimum input threshold and the live-update
+delay).
+
+@item
+Upon cycling through the completions, type @samp{RET} to select the
+candidate at point and exit the minibuffer.  This works for all types
+of completion prompts.
+
+@item
+For certain contexts where selecting a candidate does not necessarily
+mean that the process has to be finalised (e.g. when using @code{find-file})
+selection in the @samp{*Completions*} buffer can be done with @samp{TAB} which
+completes the item at point but does not exit the minibuffer.  The
+command is instead renewed to update the list of completions with the
+new candidates.
+
+@item
+Select a candidate by its line number by typing @samp{M-g M-g} in either the
+minibuffer or the @samp{*Completions*} buffer.  This calls the command
+@code{mct-choose-completion-number} which internally enables line numbers
+and always makes the completions' buffer visible.
+
+@item
+In prompts that allow the selection of multiple candidates
+(internally via the @code{completing-read-multiple} function) a @samp{[CRM]} 
label
+is added to the text of the prompt.  The user thus knows that
+pressing @samp{M-RET} in the @samp{*Completions*} will append the candidate at
+point to the list of selections and keep the completions available so
+that another item may be selected.  Any of the aforementioned
+applicable methods can confirm the final selection.  If, say, you
+want to pick a total of three candidates, do @samp{M-RET} for the first two
+and @samp{RET} for the last one.  In contexts that are not CRM-powered, the
+@samp{M-RET} has the same effect as @samp{RET}.
+
+NOTE 2021-10-22: this assumes the @code{crm-separator} to be constant (the
+comma @samp{,} character) but some commands @code{let} bind it to something 
else,
+so the behaviour does not work as expected.  One such case is
+@code{org-set-tags-command} which uses @samp{:} as a separator.
+
+@item
+Type @samp{M-e} (@code{mct-edit-completion}) in the completions' buffer to 
place
+the current candidate in the minibuffer, without exiting the session.
+This allows you to edit the text before confirming it.
+@end enumerate
+
+@node Installation
+@chapter Installation
+
+MCT is not in any package archive for the time being, though I plan to
+submit it to GNU ELPA (as such, any non-trivial patches require
+copyright assignment to the Free Software Foundation).  Users can rely
+on @samp{straight.el}, @samp{quelpa}, or equivalent to fetch the source.  
Below are
+the essentials for those who prefer the manual method.
+
+Assuming your Emacs files are found in @samp{~/.emacs.d/}, execute the
+following commands in a shell prompt:
+
+@example
+cd ~/.emacs.d
+
+# Create a directory for manually-installed packages
+mkdir manual-packages
+
+# Go to the new directory
+cd manual-packages
+
+# Clone this repo and name it "mct"
+git clone https://gitlab.com/protesilaos/mct.el.git mct
+@end example
+
+Finally, in your @samp{init.el} (or equivalent) evaluate this:
+
+@lisp
+;; Make Elisp files in that directory available to the user.
+(add-to-list 'load-path "~/.emacs.d/manual-packages/")
+@end lisp
+
+Everything is in place to set up the package.
+
+@node Sample setup
+@chapter Sample setup
+
+@cindex Sample configuration
+
+Minimal setup:
+
+@lisp
+(require 'mct)
+(mct-mode 1)
+@end lisp
+
+And with more options:
+
+@lisp
+(require 'mct)
+
+(setq mct-remove-shadowed-file-names t) ; works when `file-name-shadow-mode' 
is enabled
+(setq mct-hide-completion-mode-line t)
+(setq mct-show-completion-line-numbers nil)
+(setq mct-apply-completion-stripes t)
+(setq mct-minimum-input 3)
+(setq mct-live-update-delay 0.6)
+
+;; NOTE: `mct-completion-blocklist' can be used for commands with lots
+;; of candidates, depending also on how low `mct-minimum-input' is.
+;; With the settings shown here this is not required, otherwise I would
+;; use something like this:
+;;
+;; (setq mct-completion-blocklist
+;;       '( describe-symbol describe-function describe-variable
+;;          execute-extended-command insert-char))
+(setq mct-completion-blocklist nil)
+
+;; This is for commands that should always pop up the completions'
+;; buffer.  It circumvents the default method of waiting for some user
+;; input (see `mct-minimum-input') before displaying and updating the
+;; completions' buffer.
+(setq mct-completion-passlist
+      '(imenu
+        Info-goto-node
+        Info-index
+        Info-menu
+        vc-retrieve-tag))
+
+(mct-mode 1)
+@end lisp
+
+Other useful extras from the Emacs source code:
+
+@lisp
+(setq enable-recursive-minibuffers t)
+(setq minibuffer-eldef-shorten-default t)
+
+(file-name-shadow-mode 1)
+(minibuffer-depth-indicate-mode 1)
+(minibuffer-electric-default-mode 1)
+@end lisp
+
+@node Keymaps
+@chapter Keymaps
+
+@cindex Keymaps
+@vindex mct-completion-list-mode-map
+@vindex mct-minibuffer-local-completion-map
+@vindex mct-minibuffer-local-filename-completion-map
+
+MCT defines its own keymaps, which extend those that are active in the
+minibuffer and the @samp{*Completions*} buffer, respectively:
+
+@itemize
+@item
+@code{mct-completion-list-mode-map}
+@item
+@code{mct-minibuffer-local-completion-map}
+@item
+@code{mct-minibuffer-local-filename-completion-map}
+@end itemize
+
+You can invoke @code{describe-keymap} to learn more about them.
+
+If you want to edit any key bindings, do it in those keymaps, not in
+those they extend and override (the names of the original ones are the
+same as above, minus the @samp{mct-} prefix).
+
+@node Extensions
+@chapter Extensions
+
+@cindex Extra packages
+
+MCT only tweaks the default minibuffer.  To get more out of it, consider
+these exceptionally well-crafted extras:
+
+@table @asis
+@item @samp{consult}
+Adds several commands that make interacting with the
+minibuffer more powerful.  There also are several packages that build
+on it, such as @samp{consult-dir}.
+@item @samp{embark}
+Provides configurable contextual actions for completions and
+many other constructs inside buffers.
+@item @samp{marginalia}
+Displays informative annotations for all known types of
+completion candidates.
+@item @samp{orderless}
+A completion style that matches a variety of patterns
+(regexp, flex, initialism, etc.) regardless of the order they appear
+in.
+@end table
+
+@node Alternatives
+@chapter Alternatives
+
+@cindex Alternatives to MCT
+
+The only alternative I have used that is conceptually close to MCT is
+@samp{vertico}.  Vertico is a more mature and feature-rich package, while its
+maintainer, Daniel Mendler, is an accomplished programmer.  Whereas MCT
+is mostly an excuse to practice my Elisp skills.
+
+@node GNU Free Documentation License
+@appendix GNU Free Documentation License
+
+@include doclicense.texi
+
+@node Indices
+@chapter Indices
+
+@menu
+* Function index::
+* Variable index::
+* Concept index::
+@end menu
+
+@node Function index
+@section Function index
+
+@printindex fn
+
+@node Variable index
+@section Variable index
+
+@printindex vr
+
+@node Concept index
+@section Concept index
+
+@printindex cp
+
+@bye
\ No newline at end of file