# Org Pelican Literate Document

Posted by Beetle B. on Thu 19 December 2019

.

## Variables

These variables need to be defined:

(setq opel-output-dir-name "orgpelican")
(setq opel-page-dir "/home/me/blog/content/pages/orgpelican")
(setq opel-article-dir "/home/me/blog/content/articles/orgpelican")
(setq opel-tmp-file "/tmp/file.org")
(setq opel-no-export "noexport")


## All Definitions

Here are all the function definitions.

<<license>>
<<get-node-text-def>>
<<get-tags-def>>
<<get-property-def>>
<<build-level-regexp>>

<<get-title-string>>
<<get-date-string>>
<<get-tags-string>>
<<get-body-string>>
<<get-newcommands-string>>
<<transform-image>>
<<get-status-string>>

<<make-post>>
<<convert-post-to-rst>>
<<remove-math-directive>>
<<fix-example-blocks>>
<<write-rst-to-file>>

<<list-files>>
<<delete-files>>
<<custom-id-mapping>>
<<write-files-to-rst>>

opel-write-files-to-rst


;; Copyright (C) 2019 Mueen Nawaz

;; This software is being released with the GNU Public License, quoted
;; below.

;; Version 3, 29 June 2007

;; 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.

;; of works, such as semiconductor masks.

;; “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
;; 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,
;; 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
;; 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
;;     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
;;     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

;; “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

;; 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

;;     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
;; paragraph of section 11).

;; However, if you cease all violation of this License, then your
;; provisionally, unless and until the copyright holder explicitly and
;; copyright holder fails to notify you of the violation by some
;; reasonable means prior to 60 days after the cessation.

;; 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

;; 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
;; 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.

;; permissions. However, no additional obligations are imposed on any
;; 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) <year>  <name of author>

;;     This program is free software: you can redistribute it and/or modify
;;     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) <year>  <name of author>
;;     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

;; 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


## Get the Tags of a Node

(mapcar (lambda (tag) (replace-regexp-in-string "_" " " tag)) tags)

(defun opel-get-tags ()
"Get all tags of a heading."
(let ((tags (org-entry-get (point) "ALLTAGS" t)))
(when tags
(setq tags (split-string tags ":" t)) ; Make a list of tags.
<<replace-underscore-with-space>>)))


## Get the Headline of a Node

(defun opel-get-headline ()


## Get the Property of a Node

(defun opel-get-property (prop-name)
"Get a property of a node."
(org-entry-get (point) prop-name t))


## Get the Body of a Node

This gets the body of a node and all subtrees, sans the metadata.

Now in the master org file, our post could be buried deep inside some hierarchy. In the temporary org file, though, we need this post to be at the top level. The code snippet below will promote headlines until the first subchild becomes a top level node.

(defun opel-build-level-regexp (level)
"Build the regular expression to match the number of stars in a heading."
(mapconcat #'identity (cons "^" (make-list level "\\*")) ""))

(defun opel-get-node-text (&optional position)
"Gets the text of the node and all subnodes under the point or at the specified position."
(save-excursion
(when position (goto-char position))
(save-restriction
(org-narrow-to-subtree)
(org-end-of-meta-data)
(replace-regexp-in-string (opel-build-level-regexp (org-current-level)) ""
(buffer-substring-no-properties (point) (point-max))))))


## Get the Body of All Nodes That Have a Property

We want to know which nodes in the org document are Pelican posts. So we traverse all of them looking for a particular property.

Reddit’s alphapapa suggested I use org-get-entry, but I couldn’t get it to play nice with org-element-map. Instead I used John Kitchin’s solution:

There is one problem with this solution, though. I’m not sure what the behavior would be if you have a Pelican node nested within a Pelican node. I don’t know if org-element-map will guarantee going over the top level node first, and even if it does, I suspect it will also traverse the inner node.

I also check that none of the tags is set to prevent exporting.

(defun opel-get-all-pelican-nodes ()
"Return a list of text of all the Pelican nodes."
(save-excursion
(when
(seq-every-p (lambda (tag) (not (equal (downcase tag) opel-no-export)))
(opel-get-tags))
(opel-get-node-text)))))))

opel-get-all-pelican-nodes


## Get All Metadata of All Nodes That Have a Property

The code snippet below will extract the date, tags, etc of a post.

(defun opel-get-all-pelican-nodes-metadata ()
"Return a list of metadata of all the Pelican nodes."
(save-excursion
(when (org-entry-get (point) "PELICAN_TYPE" nil)
(date (opel-get-property "PELICAN_DATE"))
(type (opel-get-property "PELICAN_TYPE"))
(status (opel-get-property "TODO"))
(tags (opel-get-tags))
(custom-id (opel-get-property "CUSTOM_ID"))
(body (opel-get-node-text)))
((title ,title)
(date ,date)
(type ,type)
(tags ,tags)
(status ,status)
(custom-id ,custom-id)
(body ,body))))))))


This seems to work, but why do I get only one result? Shouldn’t PELICANTYPE be inherited by all the children? Does org-element-property not respect inheritance? Or do I have property inheritance turned off?

Yup - I have it turned off. This will be a problem if I ever turn it on. Is there an alternative?

Yup - I switched to org-entry-get where I can control inheritance. Should be robust.

## Construct Post

### Construct Title

(defun opel-make-post-title (post-metadata)
"Make the title of the post."
(format "#+TITLE: %s" (car (alist-get 'title post-metadata))))


#### Test It

<<all-definitions>>

(opel-make-post-title (car opel-posts))


### Construct Date

We would like to use Org’s date capabilities. This means an extra square bracket at each end of the string. Let’s remove those.

(substring date 1 -1)

(defun opel-make-post-date (post-metadata)
"Make the date of the post."
(let ((date (car (alist-get 'date post-metadata))))
(when date
(format "#+DATE: %s" <<remove-square-brackets-from-date-string>>))))

opel-make-post-date


### Construct Status

(defun opel-make-post-status (post-metadata)
"Make the status of the post."
(let ((status (car (alist-get 'status post-metadata))))
(if status
(format ":status: %s" (downcase status))
":status: draft")))


### Construct Tags

Tags are represented as a list. This will make them into a space delimited string.

(defun opel-make-post-tags (post-metadata)
"Make the tags of the post."
(let* ((tag-list (car (alist-get 'tags post-metadata)))
(tags (mapconcat 'identity tag-list ", ")))
(if tag-list
(format ":tags: %s" tags)
"")))


### Construct Body

(defun opel-make-post-body (post-metadata)
"Make the body of the post."
(let ((body (car (alist-get 'body post-metadata))))
(format "%s"

opel-make-post-body


#### Replace Images

An image of the form:

#+BEGIN_EXPORT rst
.. image:: {static}/images/path/image.png
:target: {static}/images/path/image.png
:width:  200px

#+END_EXPORT


will be replaced with:

#+BEGIN_EXPORT rst
.. image:: {static}/images/path/image.png
:target: {static}/images/path/image.png
:width: 200px
#+END_EXPORT


The assumption is that:

1. The user does not specify a description for the link. This is purely an inline link.
2. The master org file is in the parent directory of images.
3. The images directory is where all the images go, and is in the STATIC_PATHS variable in the pelicanconf.py file.

I don’t recall if CAPTION is needed, but width is not.

"\$$#\\+width: \\(.*?\$$\n\\)?#\\+CAPTION:\$$.*?\$$\n\$\\[file:\$$.*?\$$\$\\]"

(defun opel-transform-image-link (text)
"Convert an image link to its rst equivalent."
(save-match-data
(let ((text-list (split-string text "\n"))
(width-text nil))
(when (= (length text-list) 3)
(setq width-text (substring (car text-list) 8))
(setq text-list (cdr text-list)))
(let* ((caption-text (car text-list))
(caption (substring caption-text 10))
(if width-text
(format "\n\n#+BEGIN_EXPORT rst\n.. image:: {static}/%s\n   :target: {static}/%s\n   :alt: %s\n   :width: %s \n\n#+END_EXPORT\n\n" link link caption width-text)
(format "\n\n#+BEGIN_EXPORT rst\n.. image:: {static}/%s\n   :target: {static}/%s\n   :alt: %s\n\n#+END_EXPORT\n\n" link link caption))))))

opel-transform-image-link


### Construct LaTeX newcommand Formulae

Org mode has this nice capability where if I have the following in an org file:

#+LATEX_HEADER: \newcommand{..}{..}


then I can use the new command I’ve defined and Org mode will render it when I try to render any formula using the new command. So I’d like to make use of this while authoring articles.

But this is in my master org file. How do I get it into the individual org file?

I noticed that if I put a #+LATEX_HEADER in the individual org file, pandoc will not treat it appropriately when converting to rst. Or rather, it will treat it too appropriately and mark it as LaTeX which I believe Pelican ignores.


I tried this, and got a new problem: When showing the summaries on the main page, the summary shows all these \newcommand statements. If I have a bunch of them, the summary doesn’t show anything of my actual content!

Finally I decided to put it in the header under a display:none style. I do this by creating a metadata field called newcommands and dump the LaTeX in there. My HTML template looks for this and populates it.

I have to say of all the features I put in here, this gave me the biggest headaches.

There is one major downside to my solution: We will have every newcommand in every article - even ones that don’t involve math. This means MathJax in every article. This is a poor solution, but it does the job and I don’t want to overengineer.

The code is below. A word about all the backslashes. I’m going to put this into its own org file under an EXPORT block. Then pandoc exports it to rst. Then Pelican handles it. It seems Pelican doesn’t escape the backslash when converting to HTML. So I need to ensure every backslash is escaped.

Believe it or not, the Elisp code is simply stating that one should replace one backslash with two. Even though the code has 4 and 8. Elisp is annoying that way.

(defun opel-filter-newcommand (element)
"Given an Org keyword, filter for LATEX_HEADERs with newcommand. Then replace a backslash with two backslashes."
(let ((key (org-element-property :key element))
(value (org-element-property :value element)))
(string-match-p "newcommand" value))
(replace-regexp-in-string "\\\\" "\\\\\\\\" value))))

(defun opel-get-newcommands ()
"Return a list of all the \newcommand statements I have as
(org-element-map (org-element-parse-buffer 'element) 'keyword
#'opel-filter-newcommand))

(defun opel-make-newcommands ()
(format ":newcommands: %s"
(mapconcat (lambda (x) (format "\\\$$%s\\\$$" x)) (opel-get-newcommands) "")))


### Construct the Whole Post

(defun opel-make-post (post-metadata)
"Create the full text of a post."
(format
"%s\n%s\n#+BEGIN_EXPORT rst\n%s\n%s\n%s\n\n#+END_EXPORT\n\n%s\n"
title date tags status newcommands body)))


### Convert Post to Restructured Text

I will use Pandoc for this.

pandoc -s -f org -t rst

(defun opel-convert-post-to-rst (post-string filename)
"Convert the string of the post to restructured text."
(with-temp-file filename
(insert post-string))
(shell-command-to-string (format "<<pandoc-command>> %s" filename)))


### Clean Up Math Directives

When your post has mathematics in it, pandoc will insert the following after the metadata:

.. role:: math(raw)
:format: html latex
..


But there’s a problem with this. Since I put the tags and status metadata as an export block, pandoc will insert the LaTeX directive before the tags and status metadata. So you end up with:

======
Title
======

:Date:   2018-09-30 Sun

.. role:: math(raw)
:format: html latex
..

:tags: jeddah, jeddahtrip
:status: hidden

Rest of content


Now I don’t know if this leads to an invalid rst file, but Pelican doesn’t handle that well - it doesn’t see the status or tags.

I’ve noticed that if I delete the directive text, it still renders mathematics just fine. I know I have a render_math plugin - I wonder if that is helping? In any case, I want to just delete the text.

(defun opel-remove-math-directive (s)
(replace-regexp-in-string
".. role:: math(raw)\n   :format: html latex\n..\n"
""
s))


### Clean Up “example” Code

Perhaps my version of pandoc is old, but it suffers from two problems.

1. It converts BEGIN_EXAMPLE blocks into code blocks with language example.
2. It converts random stuff like RESULTS blocks to code blocks with the language example.

In both cases, Pygments fails.

(defun opel-fix-example-blocks (s)
(replace-regexp-in-string
".. code::"
".. code::"
s))


## Write Post to File

I have two choices: The functional approach would be to construct all the posts, and then write them one by one to a file. For a large .org file, this may consume too much RAM, and also has the down side of not writing anything if one post is malformed. Instead, I’ll construct and write before proceeding to the next post.

There is a lazy library, but for now I’ll minimize the dependencies.

(defun opel-write-post-to-file (post-string filename)
"Write a post (in rst) to file."
(with-temp-file filename
(insert post-string)))


## Write All Posts To Files

### Find Files in Directory

Return the full path of all files, conveniently omitting “.” and “..”, and anything else that is a directory.

(defun opel-list-files (directory)
"List all files in a directory."
(seq-filter
#'file-regular-p
(directory-files directory t)))


### Delete All Files In Directory

(defun opel-delete-files (file-list)
"Delete all files in the list."
(mapc #'delete-file file-list))


### Write All Posts To rst Files

So the method for internal links is to use the CUSTOMID property. In Org Mode, a link of the type:

$\[#ref-to-other-headline][link text]]  will link to the node whose CUSTOM_ID property is ref-to-other-headline. To solve this problem, I go through all the posts that have a CUSTOM_ID property set, and make that the keys of an association list. The corresponding value is the index of the post (where it is in the list). Later, I convert all links to link to rst#.rst where # is the index of the post being linked to. First, make a mapping from custom-id to the index and the type. We need to know if what we’re linking to is an article or a page. (defun opel-construct-customid-mapping (posts-metadata) "Create a mapping from custom-id to the index and post type." (let ((custom-ids) (types) (indices (number-sequence 0 (length posts-metadata))) (mapping '())) (setq custom-ids (mapcar (lambda (post) (car (alist-get 'custom-id post))) posts-metadata)) (setq types (mapcar (lambda (post) (car (alist-get 'type post))) posts-metadata)) (mapcar* #'list custom-ids indices types)))  (defun opel-sub-internal-link-with-text (matched-text mapping) "Convert \[\[#blah][text]] to the appropriate link for Pelican." ;; matched-text is the matched text. I could not figure out a way to ;; use capture and have the function return the value based on ;; captured data, so I had to do some parsing on my own. ;; Split on ][. The left side will then be the custom-id, beginning ;; with [[. The right side will be the link text, ending in ]]. ;; Also, I need the ~save-match-data~ because apparently ;; ~split-string~ messes up the match information. I spent hours ;; debugging this. (let* ((splitted (save-match-data (split-string matched-text "\$\$"))) (custom-id (substring (car splitted) 3)) ; Omit the first \[\[# (link-text (substring (car (cdr splitted)) 0 -2)) ; Omit the ending ]] (index (car (cdr (assoc custom-id mapping)))) (type (car (cdr (cdr (assoc custom-id mapping)))))) ;; I need to know the type to know whether to link to a page or an article. (format "[[file:{filename}/%ss/%s/rst%d.rst][%s]]" type opel-output-dir-name index link-text))) (defun opel-sub-internal-link-wo-text (matched-text mapping) "Convert \[\[#blah]] to the appropriate link for Pelican." (let* ((custom-id (substring (car splitted) 2 -2)) (index (car (cdr (assoc custom-id mapping)))) (type (car (cdr (cdr (assoc custom-id mapping)))))) (format "[[file:{filename}/%ss/%s/rst%d.rst]]" type opel-output-dir-name index)))  Below is the regular expression to match the long link style: "\\[\\[#.*?\$\$.*?\$\\]"


Below is the regular expression to match the short link style:

"\$\\[#\$$[^$]*?\$$\\]\\]"

(defun opel-fix-internal-links (post-text custom-id mapping)
"Convert internal links to point to the appropriate rst file."
(let ((index (car (cdr (assoc custom-id mapping)))))
(when index
(setq post-text
(replace-regexp-in-string
post-text nil 't))
(setq post-text
(replace-regexp-in-string
post-text nil t)))
post-text))

(defun opel-write-files-to-rst (posts-metadata)
"Create a rst file per post and put it in the output directory."
(opel-delete-files (opel-list-files opel-page-dir))
(opel-delete-files (opel-list-files opel-article-dir))
(let ((counter 0)
(basename "rst")
(filename)
(let ((type (downcase (car (alist-get 'type post-metadata))))
(directory nil)
(cond ((equal type "page") (setq directory opel-page-dir))
((equal type "article") (setq directory opel-article-dir)))
(if directory
(progn
(setq filename (format "%s%d.rst" basename counter))
(setq filename (concat (file-name-as-directory directory) filename))
(setq post (opel-fix-internal-links post custom-id mapping))
(opel-write-post-to-file
(opel-fix-example-blocks
(opel-remove-math-directive
(opel-convert-post-to-rst post opel-tmp-file)))
filename)
(setq counter (1+ counter)))
(error "Could not determine the type of the post. Is PELICAN_TYPE set?"))))))

<<all-definitions>>

(defun opel-export ()
"Export all posts."
(interactive)
`