emacs-load-relative-1.3.1/0000755000175000017500000000000013474465145015201 5ustar dogslegdogslegemacs-load-relative-1.3.1/NEWS0000644000175000017500000000000013474465145015666 0ustar dogslegdogslegemacs-load-relative-1.3.1/COPYING0000644000175000017500000010451313474465145016240 0ustar dogslegdogsleg GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. 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. Copyright (C) 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 . 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: Copyright (C) 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 . 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 . emacs-load-relative-1.3.1/INSTALL0000644000175000017500000002361413474465145016240 0ustar dogslegdogslegInstallation Instructions ************************* Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. Basic Installation ================== Briefly, the shell commands `./configure && make' should configure, and build this package. If that succeeds `make install' will install the package. However on some systems you may need root privileges, you may have use `sudo make install' or perhaps `su root' beforehand. Generic Information =================== The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It also creates a shell script `config.status' that you can run in the future to recreate the current configuration, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). The configure script can also use an optional file (typically called `config.cache' and enabled with `--cache-file=config.cache' or simply `-C') that saves the results of its tests to speed up reconfiguring. Caching is disabled by default to prevent problems with accidental use of stale cache files. If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If you are using the cache, and at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.ac' is used to create `configure' by a program called `autoconf'. You need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. Running `configure' might take a while. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package. 3. Optionally, type `make check' to run any self-tests that come with the package, generally using the just-built uninstalled binaries. 4. Type `make install' to install the programs and any data files and documentation. When installing into a prefix owned by root, it is recommended that the package be configured and built as a regular user, and only the `make install' phase executed with root privileges. 5. You can remove the compiled Emacs Lisp files and other derived files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution. 6. You can also type `make uninstall' to remove the installed files again. 7. We don't provide `make distcheck' right now, but perhaps someday we will. This is by used by developers to test that all other targets like `make install' and `make uninstall' work correctly. This target is generally not run by end users. Options ===================== Run `./configure --help' for details on the pertinent environment variables. You can give `configure' initial values for configuration parameters by setting variables in the command line or in the environment. Here is an example: ./configure CC=c99 EMACS=/usr/bin/emacs23-x *Note Defining Variables::, for more details. Installation Names ================== By default, `make install' installs the package's emacs files under `/usr/local/share/emacs/site-lisp', You can specify an installation prefix other than `/usr/local/emacs/site-lisp' by giving `configure' the option `--with-site-lisp=PREFIX', where PREFIX must be an absolute file name. The most portable way to affect installation locations is to pass the correct locations to `configure'; however, many packages provide one or both of the following shortcuts of passing variable assignments to the `make install' command line to change installation locations without having to reconfigure or recompile. The first method involves providing an override variable for each affected directory. For example, `make install prefix=/alternate/directory' will choose an alternate location for all directory configuration variables that were expressed in terms of `${prefix}'. Any directories that were specified during `configure', but not in terms of `${prefix}', must each be overridden at install time for the entire installation to be relocated. The approach of makefile variable overrides for each directory variable is required by the GNU Coding Standards, and ideally causes no recompilation. However, some platforms have known limitations with the semantics of shared libraries that end up requiring recompilation when using this method, particularly noticeable in packages that use GNU Libtool. The second method involves providing the `DESTDIR' variable. For example, `make install DESTDIR=/alternate/directory' will prepend `/alternate/directory' before all installation names. The approach of `DESTDIR' overrides is not required by the GNU Coding Standards, and does not work on platforms that have drive letters. On the other hand, it does better at avoiding recompilation issues, and works well even when some directory options were not specified in terms of `${prefix}' at `configure' time. Optional Features ================= If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The `README' should mention any `--enable-' and `--with-' options that the package recognizes. For packages that use the X Window System, `configure' can usually find the X include and library files automatically, but if it doesn't, you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations. Some packages offer the ability to configure how verbose the execution of `make' will be. For these packages, running `./configure --enable-silent-rules' sets the default to minimal output, which can be overridden with `make V=1'; while running `./configure --disable-silent-rules' sets the default to verbose, which can be overridden with `make V=0'. Sharing Defaults ================ If you want to set default values for `configure' scripts to share, you can create a site shell script called `config.site' that gives default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. Defining Variables ================== Variables not defined in a site shell script can be set in the environment passed to `configure'. However, some packages may run configure again during the build, and the customized values of these variables may be lost. In order to avoid this problem, you should set them in the `configure' command line, using `VAR=value'. For example: ./configure EMACS=/usr/bin/emacs23-x causes the specified `/usr/bin/emacs23-x' to be used as the Emacs program to use. Unfortunately, this technique does not work for `CONFIG_SHELL' due to an Autoconf bug. Until the bug is fixed you can use this workaround: CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash `configure' Invocation ====================== `configure' recognizes the following options to control how it operates. `--help' `-h' Print a summary of all of the options to `configure', and exit. `--help=short' `--help=recursive' Print a summary of the options unique to this package's `configure', and exit. The `short' variant lists options used only in the top level, while the `recursive' variant lists options also present in any nested packages. `--version' `-V' Print the version of Autoconf used to generate the `configure' script, and exit. `--cache-file=FILE' Enable the cache: use and save the results of the tests in FILE, traditionally `config.cache'. FILE defaults to `/dev/null' to disable caching. `--config-cache' `-C' Alias for `--cache-file=config.cache'. `--quiet' `--silent' `-q' Do not print messages saying which checks are being made. To suppress all normal output, redirect it to `/dev/null' (any error messages will still be shown). `--srcdir=DIR' Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. `--prefix=DIR' Use DIR as the installation prefix. *note Installation Names:: for more details, including other options available for fine-tuning the installation locations. `--no-create' `-n' Run the configure checks, but stop before creating any output files. `configure' also accepts some other, not widely useful, options. Run `configure --help' for more details. emacs-load-relative-1.3.1/README.md0000644000175000017500000000752613474465145016472 0ustar dogslegdogsleg[![Build Status](https://travis-ci.org/rocky/emacs-load-relative.png)](https://travis-ci.org/rocky/emacs-load-relative) # Emacs multi-file develop/run-from-of-source routines The rational behind module is to be able to write small Emacs functions or modules in a larger multi-file Emacs package and facilitate running from the source tree without having to "install" the code or fiddle with evil *load-path*'s. See my [NYC Lisp talk](https://github.com/rocky/emacs-load-relative/wiki/NYC-Lisp-talk) for more background on this. ## Contents ## * [\__FILE__](https://github.com/rocky/emacs-load-relative#file) * [load-relative](https://github.com/rocky/emacs-load-relative#load-relative) * [require-relative](https://github.com/rocky/emacs-load-relative#require-relative-require-relative-list) * [provide-me](https://github.com/rocky/emacs-load-relative#provide-me) The latest version is at http://github.com/rocky/emacs-load-relative ## \__FILE__ \__FILE__ returns the file name that that the calling program is running. If you are *eval*'ing a buffer then the file name of that buffer is used. The name was selected to be analogous to the name used in C, Perl, and Ruby. For an common example of using this, see [How to Insert Demo Code into an Emacs Lisp Module](https://github.com/rocky/emacs-load-relative/wiki/How-to-Insert-Demo-Code-into-an-Emacs-Lisp-Module). ## load-relative *load-relative* loads an Emacs Lisp file relative to another (presumably currently running) Emacs Lisp file. For example suppose you have Emacs Lisp files `foo.el` and `bar.el` in the same directory. To load Emacs Lisp file `bar.el` from inside Emacs lisp file `foo.el`: ```lisp (require 'load-relative) (load-relative "baz") ``` That *load-relative* line could above have also been written as: ```lisp (load-relative "./baz") ``` or: ```lisp (load-relative "baz.el") # if you want to exclude any byte-compiled files ``` ## require-relative, require-relative-list Use *require-relative* if you want to *require* the file instead of *load*'ing it: ```lisp (require-relative "baz") ``` or: ```lisp (require-relative "./baz") ``` The above not only does a *require* on `'baz`, but makes sure you get that from the same file as you would have if you had issued *load_relative*. Use *require-relative-list* when you have a list of files you want to *require*. To *require-relative* them in one shot: ```lisp (require-relative-list '("dbgr-init" "dbgr-fringe")) ``` ## provide-me The macro *provide-me* saves you the trouble of adding a symbol after *provide*, by using the file basename (without directory or file extension) as the name of the thing you want to provide. Using this forces the *provide* names to be the same as the filename, but I consider that a good thing. *provide-me* also takes an optional string which will be prepended to the provide name. This is useful if you have a multi-file package and want the files to be prefaced with the name of the package. Assume your package *foo* and contains simply file `foo.el`. Then adding: ```lisp (provide-me) ``` inside that file is the same thing as writing: ```lisp (provide 'foo) ``` Now suppose `foo.el` is part of a larger package called *bar*. Then if you write: ```lisp (provide-me "bar-") ``` this is the same as writing: ```lisp (provide 'bar-foo) ``` ## find-file-noselect-relative The function *find-file-noselect-relative* provides a way of accessing resources which are located relative to the currently running Emacs lisp file. This is probably most useful when running Emacs as a scripting engine for batch processing or with tests cases. ```lisp (find-file-noselect-relative "README.md") ``` ## with-relative-file The macro *with-relative-file* runs in a buffer with the contents of the given relative file. ```lisp (with-relative-file "README.md" (buffer-substring)) ``` emacs-load-relative-1.3.1/.travis.yml0000644000175000017500000000055013474465145017312 0ustar dogslegdogsleglanguage: emacs-lisp install: - if [ "$EMACS" = 'emacs24' ]; then sudo add-apt-repository -y ppa:cassou/emacs && sudo apt-get -qq update && sudo apt-get -qq -f install && sudo apt-get -qq install emacs24 emacs24-el; fi env: - EMACS=emacs24 # run the tests script: - /bin/bash ./autogen.sh && cd test && make check emacs-load-relative-1.3.1/ChangeLog0000644000175000017500000001356613474465145016766 0ustar dogslegdogsleg2010-09-30 rocky * .gitignore: git Administrivia. 2010-09-30 rocky Merge branch 'master' of github.com:rocky/emacs-load-relative Conflicts: .gitignore 2010-09-30 rocky * .gitignore, COPYING, Makefile.am, README, configure.ac: Administrivia. Add COPYING, update README and .gitignore, bump version number. 2010-08-17 R. Bernstein * INSTALL: Customize more for emacs. 2010-08-13 R. Bernstein * .gitignore, INSTALL: Make INSTALL less generic and more specific to Emacs 2010-07-25 rocky * AUTHORS, Makefile.am, configure.ac, load-relative.el: Add Emacs Lisp Code Archive (ELCA) meta-comments. 2010-03-08 rocky Merge branch 'master' of git@github.com:rocky/emacs-load-relative 2010-03-08 rocky * .gitignore: elisp-comp is now in the repository 2009-12-18 rocky * .gitignore, autogen.sh, elisp-comp: Don't overwrigte elisp-comp. 2009-12-18 rocky * autogen.sh: Add --enable-maintainer-mode to configure when running autogen.sh 2009-12-14 rocky Merge branch 'master' of git@github.com:rocky/emacs-load-relative 2009-12-13 rocky * test/behave.el, test/test-load.el, test/test-require-list.el: Remove local behave.el in favor of new installed package test-unit. 2009-12-13 rocky * .gitignore, ChangeLog, Makefile.am, configure.ac: Administrivia. 2009-12-13 rocky Merge branch 'master' of git@github.com:rocky/emacs-load-relative 2009-12-13 rocky * configure.ac: Fix package name typo. 2009-12-13 rocky * Makefile.am: Include textile README in distribution tarball 2009-12-12 rocky * README.textile: Reformat without line breaks 2009-12-12 rocky * README.md, README.textile: Try textile for readme 2009-12-12 rocky * README.md, README.redcloth: Try using .md extension for doc. 2009-11-29 rocky * test/behave.el: Add assert-raises. 2009-11-25 rocky * test/behave.el: behave.el: fix incorrect initialization on *behave-total-assertions*. 2009-11-24 rocky * test/behave.el: Show number of assertions run. 2009-11-22 rocky * load-relative.el: Add provision for getting __FILE__ when we are byte compiling. 2009-11-22 rocky * load-relative.el, test/require-file2.el, test/require-file3.el, test/test-load.el: Add optional prefix to require-relative, require-relative and provide-me which will add that prefix to the feature name. 2009-11-22 rocky * test/test-load.el: Minimal test of provide-me. 2009-11-22 rocky * load-relative.el: Doc string fix. 2009-11-21 rocky * Makefile.am, README, README.redcloth: Turn README back into text. Add special redcloth version. 2009-11-21 rocky * README, README.markup: Nope changing the name made things worse. 2009-11-21 rocky * README, README.markup: See if changing the name from README to README.markup gives github a clue 2009-11-21 rocky * README, load-relative.el: load-relative.el: Add provide-me and make GPL v3. README: expand and turn into red-cloth markup. 2009-11-19 R. Bernstein * test/test-load.el: Another test of (__FILE__). Make test-load more eval-current'able. 2009-11-19 R. Bernstein * test/test-load.el: Add first __FILE__ test. 2009-11-17 R. Bernstein * load-relative.el: Bug: was not require-relative when not at compile time. 2009-11-15 rocky * load-relative.el: Working towards a more perfect __FILE__. Perhaps I am flailing here. Need much better tests. 2009-11-15 rocky * Makefile.am, load-relative.el, test/test-require-list.el: Add macro to handle relative requires using a list. And use this list eval-when-compile to remove the undefined function messages in byte-compilation. 2009-11-13 rocky * load-relative.el: Go over __FILE__ test ordering and more comments to as to why we do what we do. 2009-11-13 rocky * load-relative.el: Update __FILE__ docstring comment. 2009-11-13 rocky * load-relative.el: Also try #$ - "the name of this file as a string". Thanks due to grischka for the suggestion. 2009-11-13 rocky * test/require-file1.el: Used in testing require-relative 2009-11-13 rocky * load-relative.el, test/load-file2.el, test/test-load.el: load-relative.el: Use current-load-list to get loaded/eval'd file name. It is perhaps is the most reliable but also the most low-level and it is an undocumented API. Update doc strings to record what we now understand. Allow an optional symbol -- just in case. Update tests. 2009-11-12 rocky * test/behave.el, test/test-load.el: test-load.el: add a require-relative test behave.el: sync up with emacs-dbgr - one bug removed. 2009-11-12 rocky * load-relative.el: Add require-relative. 2009-11-12 rocky Merge branch 'master' of git@github.com:rocky/emacs-load-relative Conflicts: load-relative.el 2009-11-12 rocky * load-relative.el, test/test-load.el: Add require-relative. 2009-11-10 R. Bernstein * load-relative.el, test/behave.el, test/test-load.el: test-load.el: I think we need to expand the filename before calling load. behave.el: reduce dependency on spec part. 2009-11-09 rocky * load-relative.el, test/load-file1.el, test/test-load.el: Allow load-relative to accept a list of strings of files to load. 2009-11-09 rocky * Relative loads for Emacs Lisp files. Adds functions __FILE__ and load-relative. emacs-load-relative-1.3.1/copyright_exceptions0000644000175000017500000000000013474465145021363 0ustar dogslegdogslegemacs-load-relative-1.3.1/configure.ac0000644000175000017500000000140113474465145017463 0ustar dogslegdogslegAC_INIT(emacs-load-relative, 1.3.1,) AC_CONFIG_SRCDIR(load-relative.el) AM_INIT_AUTOMAKE([foreign]) AM_MAINTAINER_MODE AM_MISSING_PROG(GIT2CL, git2cl, $missing_dir) AC_PATH_PROG(EMACS, emacs, no) AC_ARG_WITH(emacs, AC_HELP_STRING([--with-emacs], [location of emacs program]), EMACS=$withval) if test x$EMACS != xno ; then $EMACS -batch -q -no-site-file -eval \ '(if (< emacs-major-version 23) (progn (error "You need GNU Emacs 23 or better for this package.") (kill-emacs 1) ))' if test $? -ne 0 ; then EMACS=no fi fi ## ## Find out where to install the debugger emacs lisp files ## AM_PATH_LISPDIR AM_CONDITIONAL(INSTALL_EMACS_LISP, test "x$lispdir" != "x") AC_CONFIG_FILES([Makefile test/Makefile]) AC_OUTPUT emacs-load-relative-1.3.1/autogen.sh0000755000175000017500000000022413474465145017200 0ustar dogslegdogsleg#!/bin/sh autoreconf -vi && \ autoconf && { echo "Running configure with --enable-maintainer-mode $@" ./configure --enable-maintainer-mode $@ } emacs-load-relative-1.3.1/THANKS0000644000175000017500000000027213474465145016115 0ustar dogslegdogslegPhil Lord - Contribute find-file-noselect-relative, and with-relative-file Lars Anderson - Melpa packaging, among other things Stefan Monnier - Elisp guidance emacs-load-relative-1.3.1/Makefile.am0000644000175000017500000000263513474465145017243 0ustar dogslegdogsleglisp_files := $(wildcard *.el) lisp_LISP = $(lisp_files) PHONY=check check-short clean dist distclean test EXTRA_DIST = $(lisp_files) $(test_files) README.md GIT2CL ?= git2cl #: Run all tests check: $(test-files) $(MAKE) -C test check #: Run all tests with minimum verbosity check-short: $(MAKE) -C test check 2>&1 | ruby test/make-check-filter.rb #: same as check test: check #: same as check-short test-short: check-short #: Read this first. README: README.md ln -s README.md README if MAINTAINER_MODE CL = ChangeLog #: Create a log file from the individual commits via git2cl ChangeLog: git log --pretty --numstat --summary | $(GIT2CL) > $@ ACLOCAL_AMFLAGS=-I . endif CR_EXCEPTIONS=copyright_exceptions #: Check for GNU Copyrights. check_copyrights: @echo "Compute exceptions >$(CR_EXCEPTIONS)~" @export LANG=C; \ find . -name '.git' -prune -o -name '*.el' -print0 | \ xargs -0 grep -L 'Free Software Foundation, Inc' | \ grep -v '\(\.dir-locals\|.-\(pkg\|autoloads\)\)\.el$$'; \ find . -name '.git' -prune -o -name '*.el' -print | \ while read f; do \ fquoted="$$(echo $$f|tr '|' '_')"; \ sed -n -e '/[Cc]opyright.*, *[1-9][-0-9]*,\?$$/N' \ -e '/Free Software Foundation/d' \ -e "s|^\\(.*[Cc]opyright\\)|$$fquoted:\\1|p" \ "$$f"; \ done | sort >$(CR_EXCEPTIONS)~ diff -u "$(CR_EXCEPTIONS)" "$(CR_EXCEPTIONS)~" emacs-load-relative-1.3.1/install-from-git.sh0000755000175000017500000000517013474465145020733 0ustar dogslegdogsleg#!/bin/bash # This installs all realgud and its prerequisites. If you are lucky # you can just run this: # # bash ./install-from-git.sh # # However we do provide for some customization... # # 1. GIT PROTOCOL # =============== # # If your "git clone" can't handle the "http" protocol, you might be # able to use the "git" protocol. To do this set the GIT_PROTOCOL # variable like this: # # GIT_PROTOCOL=git sh ./install-from-git.sh # # 2. configure options (e.g --prefix) # ==================================== # If you want to customize configuration parameters, for example, # choose where to install, you can pass configure options to this # script. For example:# can pass configure options. # # sh ./install-from-git.sh --prefix=/tmp # # 3. TO "sudo" or not to "sudo"? # ============================== # If you are running as root on a *Nix-like box, then there's no problem. # # If you are not running as root, "sudo" might be invoked to install # code. On systems that don't have a "sudo" command but need # filesystem permission, then you get by with setting SUDO_CMD to "su root-c" # For example: # # SUDO_CMD='su root -c' sh ./install-from-git.sh # # If you have sufficient filesystem permission (which is often the # case on Windows or cygwin) then you might not need or want sudo. So # here, set SUDO_CMD to a blank: # # SUDO_CMD=' ' sh ./install-from-git.sh # # # To finish here is an invocation using all 3 above options: # GIT_PROTOCOL='git' SUDO_CMD=' ' sh ./install-from-git.sh --prefix=/tmp GIT_PROTOCOL=${GIT_PROTOCOL:-http} # Run and echo a command run_cmd() { echo "--- Running command: $@" $@ rc=$? echo "--- $@ exit status is $?" return $rc } # environment variable SUDO_CMD could be "sudo" or "su root -c" or " " # for don't need sudo if (( $(id -u) != 0)) ; then if [[ -z "$SUDO_CMD" ]] ; then need_sudo='sudo' if which $need_sudo >/dev/null 2>&1 ; then try_cmd='' else need_sudo='su root -c' try_cmd='su' fi else need_sudo="$SUDO_CMD" fi else need_sudo='' try_cmd='' fi for program in git make $need_sudo ; do if ! which $program >/dev/null 2>&1 ; then echo "Cant find program $program in $PATH" exit 1 fi done for pkg in emacs-{test-simple,load-relative} ; do echo '******************************************' echo Trying to install ${pkg}... echo '******************************************' run_cmd git clone ${GIT_PROTOCOL}://github.com/rocky/${pkg}.git (cd $pkg && \ run_cmd $SHELL ./autogen.sh && \ run_cmd ./configure $@ && \ run_cmd make && \ run_cmd make check && \ run_cmd $need_sudo make install ) done emacs-load-relative-1.3.1/common.mk0000644000175000017500000000017213474465145017022 0ustar dogslegdogslegshort: $(MAKE) 2>&1 >/dev/null | ruby $(top_srcdir)/make-check-filter.rb %.short: $(MAKE) $(@:.short=) 2>&1 >/dev/null emacs-load-relative-1.3.1/el-get-install.el0000644000175000017500000000743513474465145020355 0ustar dogslegdogsleg(eval-when-compile (defvar el-get-sources) ) (declare-function el-get-post-install 'el-get) (add-to-list 'load-path "~/.emacs.d/el-get/el-get") ;;; el-get-install.el --- installer for the lazy ;; ;; Copyright (C) 2010 Dimitri Fontaine ;; ;; Author: Dimitri Fontaine ;; URL: http://www.emacswiki.org/emacs/el-get.el ;; Created: 2010-06-17 ;; Keywords: emacs package elisp install elpa git git-svn bzr cvs apt-get fink http http-tar ;; Licence: WTFPL, grab your copy here: http://sam.zoy.org/wtfpl/ ;; ;; This file is NOT part of GNU Emacs. ;; ;; bootstrap your el-get installation, the goal is then to use el-get to ;; update el-get. ;; ;; So the idea is that you copy/paste this code into your *scratch* buffer, ;; hit C-j, and you have a working el-get. (let ((el-get-root (file-name-as-directory (or (bound-and-true-p el-get-dir) (concat (file-name-as-directory user-emacs-directory) "el-get"))))) (when (file-directory-p el-get-root) (add-to-list 'load-path el-get-root)) ;; try to require el-get, failure means we have to install it (unless (require 'el-get nil t) (unless (file-directory-p el-get-root) (make-directory el-get-root t)) (let* ((package "el-get") (buf (switch-to-buffer "*el-get bootstrap*")) (pdir (file-name-as-directory (concat el-get-root package))) (git (or (executable-find "git") (error "Unable to find `git'"))) (url (or (bound-and-true-p el-get-git-install-url) "http://github.com/dimitri/el-get.git")) (default-directory el-get-root) (process-connection-type nil) ; pipe, no pty (--no-progress) ;; First clone el-get (status (call-process git nil `(,buf t) t "--no-pager" "clone" "-v" url package))) (unless (zerop status) (error "Couldn't clone el-get from the Git repository: %s" url)) ;; switch branch if we have to (let* ((branch (cond ;; Check if a specific branch is requested ((bound-and-true-p el-get-install-branch)) ;; Check if master branch is requested ((boundp 'el-get-master-branch) "master") ;; Read the default branch from the el-get recipe ((plist-get (with-temp-buffer (insert-file-contents-literally (expand-file-name "recipes/el-get.rcp" pdir)) (read (current-buffer))) :branch)) ;; As a last resort, use the master branch ("master"))) (remote-branch (format "origin/%s" branch)) (default-directory pdir) (bstatus (if (string-equal branch "master") 0 (call-process git nil (list buf t) t "checkout" "-t" remote-branch)))) (unless (zerop bstatus) (error "Couldn't `git checkout -t %s`" branch))) (add-to-list 'load-path pdir) (load package) (let ((el-get-default-process-sync t) ; force sync operations for installer (el-get-verbose t)) ; let's see it all (el-get-post-install "el-get")) (with-current-buffer buf (goto-char (point-max)) (insert "\nCongrats, el-get is installed and ready to serve!"))))) (declare-function el-get 'el-get) ;; now either el-get is `require'd already, or have been `load'ed by the ;; el-get installer. (setq el-get-sources '(el-get ; el-get is self-hosting loc-changes ; loc marks in buffers load-relative ; load emacs lisp relative to emacs source test-simple ; simple test framework )) ;; install new packages and init already installed packages (el-get 'sync '(loc-changes list-utils load-relative test-simple)) emacs-load-relative-1.3.1/elisp-comp0000755000175000017500000000524613474465145017206 0ustar dogslegdogsleg#!/bin/sh # Copyright (C) 1995, 2000, 2003, 2004, 2005 Free Software Foundation, Inc. scriptversion=2009-11-26.09 # Franc,ois Pinard , 1995. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2, or (at your option) # any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. # As a special exception to the GNU General Public License, if you # distribute this file as part of a program that contains a # configuration script generated by Autoconf, you may include it under # the same distribution terms that you use for the rest of that program. # This file is maintained in Automake, please report # bugs to or send patches to # . case $1 in '') echo "$0: No files. Try \`$0 --help' for more information." 1>&2 exit 1; ;; -h | --h*) cat <<\EOF Usage: elisp-comp [--help] [--version] FILES... This script byte-compiles all `.el' files listed as FILES using GNU Emacs, and put the resulting `.elc' files into the current directory, so disregarding the original directories used in `.el' arguments. This script manages in such a way that all Emacs LISP files to be compiled are made visible between themselves, in the event they require or load-library one another. Report bugs to . EOF exit $? ;; -v | --v*) echo "elisp-comp $scriptversion" exit $? ;; esac if test -z "$EMACS" || test "$EMACS" = "t"; then # Value of "t" means we are running in a shell under Emacs. # Just assume Emacs is called "emacs". EMACS=emacs fi tempdir=. # Cleanup the temporary directory on exit. # trap 'ret=$?; rm -rf "$tempdir" && exit $ret' 0 trap 'ret=$?; rm -rf "./script" && exit $ret' 0 trap '(exit $?); exit' 1 2 13 15 ( cd $tempdir echo "(setq load-path (cons nil load-path))" > script $EMACS -batch -q -l script -f batch-byte-compile *.el || exit $? # mv *.elc .. ) || exit $? (exit 0); exit 0 # Local Variables: # mode: shell-script # sh-indentation: 2 # eval: (add-hook 'write-file-hooks 'time-stamp) # time-stamp-start: "scriptversion=" # time-stamp-format: "%:y-%02m-%02d.%02H" # time-stamp-end: "$" # End: emacs-load-relative-1.3.1/load-relative.el0000644000175000017500000002777113474465145020271 0ustar dogslegdogsleg;;; load-relative.el --- Relative file load (within a multi-file Emacs package) -*- lexical-binding: t -*- ;; Author: Rocky Bernstein ;; Version: 1.3.1 ;; Keywords: internal ;; URL: http://github.com/rocky/emacs-load-relative ;; Compatibility: GNU Emacs 23.x ;; Copyright (C) 2015-2019 Free Software Foundation, Inc ;; 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 ;; . ;;; Commentary: ;; Here we provide functions which facilitate writing multi-file Emacs ;; packages and facilitate running from the source tree without having ;; to "install" code or fiddle with evil `load-path'. See ;; https://github.com/rocky/emacs-load-relative/wiki/NYC-Lisp-talk for ;; the the rationale behind this. ;; ;; The functions we add are relative versions of `load', `require' and ;; `find-file-no-select' and versions which take list arguments. We also add a ;; `__FILE__' function and a `provide-me' macro. ;; The latest version of this code is at: ;; http://github.com/rocky/emacs-load-relative/ ;; `__FILE__' returns the file name that that the calling program is ;; running. If you are `eval''ing a buffer then the file name of that ;; buffer is used. The name was selected to be analogous to the name ;; used in C, Perl, Python, and Ruby. ;; `load-relative' loads an Emacs Lisp file relative to another ;; (presumably currently running) Emacs Lisp file. For example suppose ;; you have Emacs Lisp files "foo.el" and "bar.el" in the same ;; directory. To load "bar.el" from inside Emacs Lisp file "foo.el": ;; ;; (require 'load-relative) ;; (load-relative "baz") ;; ;; The above `load-relative' line could above have also been written as: ;; ;; (load-relative "./baz") ;; or: ;; (load-relative "baz.el") # if you want to exclude any byte-compiled files ;; ;; Use `require-relative' if you want to `require' the file instead of ;; `load'ing it: ;; ;; (require-relative "baz") ;; ;; or: ;; ;; (require-relative "./baz") ;; ;; The above not only does a `require' on 'baz', but makes sure you ;; get that from the same file as you would have if you had issued ;; `load_relative'. ;; ;; Use `require-relative-list' when you have a list of files you want ;; to `require'. To `require-relative' them all in one shot: ;; ;; (require-relative-list '("dbgr-init" "dbgr-fringe")) ;; ;; The macro `provide-me' saves you the trouble of adding a ;; symbol after `provide' using the file basename (without directory ;; or file extension) as the name of the thing you want to ;; provide. ;; ;; Using this constrains the `provide' name to be the same as ;; the filename, but I consider that a good thing. ;; ;; The function `find-file-noselect-relative' provides a way of accessing ;; resources which are located relative to the currently running Emacs Lisp ;; file. This is probably most useful when running Emacs as a scripting engine ;; for batch processing or with tests cases. For example, this form will find ;; the README file for this package. ;; ;; (find-file-noselect-relative "README.md") ;; ;; `find-file-noselect-relative' also takes wildcards, as does it's ;; non-relative namesake. ;; ;; The macro `with-relative-file' runs in a buffer with the contents of the ;; given relative file. ;; ;; (with-relative-file "README.md" ;; (buffer-substring)) ;; ;; This is easier if you care about the contents of the file, rather than ;; a buffer. ;;; Code: ;; Press C-x C-e at the end of the next line configure the program in ;; for building via "make" to get set up. ;; (compile (format "EMACSLOADPATH=:%s ./autogen.sh" ".")) ;; After that you can run: ;; (compile "make check") ;;;###autoload (defun __FILE__ (&optional symbol) "Return the string name of file/buffer that is currently begin executed. The first approach for getting this information is perhaps the most pervasive and reliable. But it the most low-level and not part of a public API, so it might change in future implementations. This method uses the name that is recorded by readevalloop of `lread.c' as the car of variable `current-load-list'. Failing that, we use `load-file-name' which should work in some subset of the same places that the first method works. However `load-file-name' will be nil for code that is eval'd. To cover those cases, we try function `buffer-file-name' which is initially correct, for eval'd code, but will change and may be wrong if the code sets or switches buffers after the initial execution. As a last resort, you can pass in SYMBOL which should be some symbol that has been previously defined if none of the above methods work we will use the file-name value find via `symbol-file'." ;; Not used right now: ;; Failing the above the next approach we try is to use the value of ;; $# - 'the name of this file as a string'. Although it doesn't ;; work for eval-like things, it has the advantage that this value ;; persists after loading or evaluating a file. So it would be ;; suitable if __FILE__ were called from inside a function. (cond ;; lread.c's readevalloop sets (car current-load-list) ;; via macro LOADHIST_ATTACH of lisp.h. At least in Emacs ;; 23.0.91 and this code goes back to '93. ((stringp (car-safe current-load-list)) (car current-load-list)) ;; load-like things. 'relative-file-expand' tests in ;; test/test-load.el indicates we should put this ahead of ;; $#. (load-file-name) ;; Pick up "name of this file as a string" which is set on ;; reading and persists. In contrast, load-file-name is set only ;; inside eval. As such, it won't work when not in the middle of ;; loading. ;; (#$) ;; eval-like things ((buffer-file-name)) ;; When byte compiling. FIXME: use a more thorough precondition like ;; byte-compile-file is somehwere in the backtrace or that ;; bytecomp-filename comes from that routine? ;; FIXME: `bytecomp-filename' doesn't exist any more (since Emacs-24.1). ((boundp 'bytecomp-filename) bytecomp-filename) (t (symbol-file symbol) ;; last resort ))) (defun autoload-relative (function-or-list file &optional docstring interactive type symbol) ;; FIXME: Docstring talks of FUNCTION but argname is `function-or-list'. "Autoload an Emacs Lisp file relative to Emacs Lisp code that is in the process of being loaded or eval'd. Define FUNCTION to autoload from FILE. FUNCTION is a symbol. FILE is a string to pass to `load'. DOCSTRING is documentation for the function. INTERACTIVE if non-nil says function can be called interactively. TYPE indicates the type of the object: nil or omitted says function is a function, `keymap' says function is really a keymap, and `macro' or t says function is really a macro. Third through fifth args give info about the real definition. They default to nil. If function is already defined other than as an autoload, this does nothing and returns nil. SYMBOL is the location of of the file of where that was defined (as given by `symbol-file' is used if other methods of finding __FILE__ don't work." (if (listp function-or-list) ;; FIXME: This looks broken: ;; - Shouldn't it iterate on `function-or-list' instead of `file'? ;; - Shouldn't the `autoload' take `function' rather than ;; `function-or-list' as argument? (mapc (lambda(_function) (autoload function-or-list (relative-expand-file-name file symbol) docstring interactive type)) file) (autoload function-or-list (relative-expand-file-name file symbol) docstring interactive type)) ) ;;;###autoload (defun find-file-noselect-relative (filename &optional nowarn rawfile wildcards) "Read relative FILENAME into a buffer and return the buffer. If a buffer exists visiting FILENAME, return that one, but verify that the file has not changed since visited or saved. The buffer is not selected, just returned to the caller. Optional second arg NOWARN non-nil means suppress any warning messages. Optional third arg RAWFILE non-nil means the file is read literally. Optional fourth arg WILDCARDS non-nil means do wildcard processing and visit all the matching files. When wildcards are actually used and expanded, return a list of buffers that are visiting the various files." (find-file-noselect (relative-expand-file-name filename) nowarn rawfile wildcards)) ;;;###autoload (defmacro with-relative-file (file &rest body) "Read the relative FILE into a temporary buffer and evaluate BODY in this buffer." (declare (indent 1) (debug t)) `(with-temp-buffer (insert-file-contents (relative-expand-file-name ,file)) ,@body)) ;;;###autoload (defun load-relative (file-or-list &optional symbol) "Load an Emacs Lisp file relative to Emacs Lisp code that is in the process of being loaded or eval'd. FILE-OR-LIST is either a string or a list of strings containing files that you want to loaded. If SYMBOL is given, the location of of the file of where that was defined (as given by `symbol-file' is used if other methods of finding __FILE__ don't work." (if (listp file-or-list) (mapcar (lambda(relative-file) (load (relative-expand-file-name relative-file symbol))) file-or-list) (load (relative-expand-file-name file-or-list symbol))) ) (defun relative-expand-file-name(relative-file &optional opt-file) "Expand RELATIVE-FILE relative to the Emacs Lisp code that is in the process of being loaded or eval'd. WARNING: it is best to run this function before any buffer-setting or buffer changing operations." (let ((file (or opt-file (__FILE__) default-directory)) (prefix)) (unless file ;; FIXME: Since default-directory should basically never be nil, this ;; should basically never trigger! (error "Can't expand __FILE__ here and no file name given")) (setq prefix (file-name-directory file)) (expand-file-name (concat prefix relative-file)))) ;;;###autoload (defun require-relative (relative-file &optional opt-file opt-prefix) "Run `require' on an Emacs Lisp file relative to the Emacs Lisp code that is in the process of being loaded or eval'd. The symbol used in require is the base file name (without directory or file extension) treated as a symbol. WARNING: it is best to to run this function before any buffer-setting or buffer changing operations." (let ((require-string-name (concat opt-prefix (file-name-sans-extension (file-name-nondirectory relative-file))))) (require (intern require-string-name) (relative-expand-file-name relative-file opt-file)))) ;;;###autoload (defmacro require-relative-list (list &optional opt-prefix) "Run `require-relative' on each name in LIST which should be a list of strings, each string being the relative name of file you want to run." `(eval-and-compile (dolist (rel-file ,list) (require-relative rel-file (__FILE__) ,opt-prefix)))) ;;;###autoload (defmacro provide-me ( &optional prefix ) "Call `provide' with the feature's symbol name made from source-code's file basename sans extension. For example if you write (provide-me) inside file ~/lisp/foo.el, this is the same as writing: (provide \\='foo). With a prefix, that prefix is prepended to the `provide' So in the previous example, if you write (provide-me \"bar-\") this is the same as writing (provide \\='bar-foo)." `(provide (intern (concat ,prefix (file-name-sans-extension (file-name-nondirectory (__FILE__))))))) (provide-me) ;;; load-relative.el ends here emacs-load-relative-1.3.1/AUTHORS0000644000175000017500000000004013474465145016243 0ustar dogslegdogslegRocky Bernstein (rocky@gnu.org) emacs-load-relative-1.3.1/test/0000755000175000017500000000000013474465145016160 5ustar dogslegdogslegemacs-load-relative-1.3.1/test/require-file1.el0000644000175000017500000000137413474465145021161 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (provide 'require-file1) emacs-load-relative-1.3.1/test/simple-test.el0000644000175000017500000003322413474465145020754 0ustar dogslegdogsleg;;; test-simple.el --- Simple Unit Test Framework for Emacs Lisp -*- lexical-binding: t -*- ;; Rewritten from Phil Hagelberg's behave.el by rocky ;; Copyright (C) 2015, 2016 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; URL: http://github.com/rocky/emacs-test-simple ;; Keywords: unit-test ;; Package-Requires: ((cl-lib "0")) ;; Version: 1.2.0 ;; 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 ;; . ;;; Commentary: ;; test-simple.el is: ;; ;; * Simple. No need for ;; - context macros, ;; - enclosing specifications, ;; - required test tags. ;; ;; But if you want, you still can enclose tests in a local scope, ;; add customized assert failure messages, or add summary messages ;; before a group of tests. ;; ;; * Accommodates both interactive and non-interactive use. ;; - For interactive use, one can use `eval-last-sexp', `eval-region', ;; and `eval-buffer'. One can `edebug' the code. ;; - For non-interactive use, run: ;; emacs --batch --no-site-file --no-splash --load ;; ;; Here is an example using gcd.el found in the examples directory. ;; ;; (require 'test-simple) ;; (test-simple-start) ;; Zero counters and start the stop watch. ;; ;; ;; Use (load-file) below because we want to always to read the source. ;; ;; Also, we don't want no stinking compiled source. ;; (assert-t (load-file "./gcd.el") ;; "Can't load gcd.el - are you in the right directory?" ) ;; ;; (note "degenerate cases") ;; ;; (assert-nil (gcd 5 -1) "using positive numbers") ;; (assert-nil (gcd -4 1) "using positive numbers, switched order") ;; (assert-raises error (gcd "a" 32) ;; "Passing a string value should raise an error") ;; ;; (note "GCD computations") ;; (assert-equal 1 (gcd 3 5) "gcd(3,5)") ;; (assert-equal 8 (gcd 8 32) "gcd(8,32)") ;; (end-tests) ;; Stop the clock and print a summary ;; ;; Edit (with Emacs of course) gcd-tests.el and run M-x eval-current-buffer ;; ;; You should see in buffer *test-simple*: ;; ;; gcd-tests.el ;; ...... ;; 0 failures in 6 assertions (0.002646 seconds) ;; ;; Now let us try from a command line: ;; ;; $ emacs --batch --no-site-file --no-splash --load gcd-tests.el ;; Loading /src/external-vcs/emacs-test-simple/example/gcd.el (source)... ;; *scratch* ;; ...... ;; 0 failures in 6 assertions (0.000723 seconds) ;;; To do: ;; FIXME: Namespace is all messed up! ;; Main issues: more expect predicates (require 'time-date) ;;; Code: (eval-when-compile (byte-compile-disable-warning 'cl-functions) ;; Somehow disabling cl-functions causes the erroneous message: ;; Warning: the function `reduce' might not be defined at runtime. ;; FIXME: isolate, fix and/or report back to Emacs developers a bug ;; (byte-compile-disable-warning 'unresolved) (require 'cl) ) (require 'cl) (defgroup test-simple nil "Simple Unit Test Framework for Emacs Lisp" :group 'lisp) (defcustom test-simple-runner-interface (if (fboundp 'bpr-spawn) 'bpr-spawn 'compile) "Function with one string argument when running tests non-interactively. Command line started with `emacs --batch' is passed as the argument. `bpr-spawn', which is in bpr package, is preferable because of no window popup. If bpr is not installed, fall back to `compile'." :type 'function :group 'test-simple) (defcustom test-simple-runner-key "C-x C-z" "Key to run non-interactive test after defining command line by `test-simple-run'." :type 'string :group 'test-simple) (defvar test-simple-debug-on-error nil "If non-nil raise an error on the first failure.") (defvar test-simple-verbosity 0 "The greater the number the more verbose output.") (defstruct test-info description ;; description of last group of tests (assert-count 0) ;; total number of assertions run (failure-count 0) ;; total number of failures seen (start-time (current-time)) ;; Time run started ) (defvar test-simple-info (make-test-info) "Variable to store testing information for a buffer.") (defun note (description &optional test-info) "Add a name to a group of tests." (if (getenv "USE_TAP") (test-simple-msg (format "# %s" description) 't) (if (> test-simple-verbosity 0) (test-simple-msg (concat "\n" description) 't)) (unless test-info (setq test-info test-simple-info)) (setf (test-info-description test-info) description) )) ;;;###autoload (defmacro test-simple-start (&optional test-start-msg) `(test-simple-clear nil (or ,test-start-msg (if (and (functionp '__FILE__) (__FILE__)) (file-name-nondirectory (__FILE__)) (buffer-name))) )) ;;;###autoload (defun test-simple-clear (&optional test-info test-start-msg) "Initialize and reset everything to run tests. You should run this before running any assertions. Running more than once clears out information from the previous run." (interactive) (unless test-info (unless test-simple-info (make-variable-buffer-local (defvar test-simple-info (make-test-info)))) (setq test-info test-simple-info)) (setf (test-info-description test-info) "none set") (setf (test-info-start-time test-info) (current-time)) (setf (test-info-assert-count test-info) 0) (setf (test-info-failure-count test-info) 0) (with-current-buffer (get-buffer-create "*test-simple*") (let ((old-read-only inhibit-read-only)) (setq inhibit-read-only 't) (delete-region (point-min) (point-max)) (if test-start-msg (insert (format "%s\n" test-start-msg))) (setq inhibit-read-only old-read-only))) (unless noninteractive (message "Test-Simple: test information cleared"))) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Assertion tests ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (defmacro assert-raises (error-condition body &optional fail-message) (let ((fail-message (or fail-message (format "assert-raises did not get expected %s" error-condition)))) (list 'condition-case nil (list 'progn body (list 'assert-t nil fail-message)) (list error-condition '(assert-t t))))) (defun assert-op (op expected actual &optional fail-message test-info) "Expectation is that ACTUAL should be equal to EXPECTED." (unless test-info (setq test-info test-simple-info)) (cl-incf (test-info-assert-count test-info)) (if (not (funcall op actual expected)) (let* ((fail-message (if fail-message (format "Message: %s" fail-message) "")) (expect-message (format "\n Expected: %S\n Got: %S" expected actual)) (test-info-mess (if (boundp 'test-info) (test-info-description test-info) "unset"))) (test-simple--add-failure (format "assert-%s" op) test-info-mess (concat fail-message expect-message))) (test-simple--ok-msg fail-message))) (defun assert-equal (expected actual &optional fail-message test-info) "Expectation is that ACTUAL should be equal to EXPECTED." (assert-op 'equal expected actual fail-message test-info)) (defun assert-eq (expected actual &optional fail-message test-info) "Expectation is that ACTUAL should be EQ to EXPECTED." (assert-op 'eql expected actual fail-message test-info)) (defun assert-eql (expected actual &optional fail-message test-info) "Expectation is that ACTUAL should be EQL to EXPECTED." (assert-op 'eql expected actual fail-message test-info)) (defun assert-matches (expected-regexp actual &optional fail-message test-info) "Expectation is that ACTUAL should match EXPECTED-REGEXP." (unless test-info (setq test-info test-simple-info)) (cl-incf (test-info-assert-count test-info)) (if (not (string-match expected-regexp actual)) (let* ((fail-message (if fail-message (format "\n\tMessage: %s" fail-message) "")) (expect-message (format "\tExpected Regexp: %s\n\tGot: %s" expected-regexp actual)) (test-info-mess (if (boundp 'test-info) (test-info-description test-info) "unset"))) (test-simple--add-failure "assert-equal" test-info-mess (concat expect-message fail-message))) (progn (test-simple-msg ".") t))) (defun assert-t (actual &optional fail-message test-info) "expectation is that ACTUAL is not nil." (assert-nil (not actual) fail-message test-info)) (defun assert-nil (actual &optional fail-message test-info) "expectation is that ACTUAL is nil. FAIL-MESSAGE is an optional additional message to be displayed." (unless test-info (setq test-info test-simple-info)) (cl-incf (test-info-assert-count test-info)) (if actual (let* ((fail-message (if fail-message (format "\n\tMessage: %s" fail-message) "")) (test-info-mess (if (boundp 'test-simple-info) (test-info-description test-simple-info) "unset"))) (test-simple--add-failure "assert-nil" test-info-mess fail-message test-info)) (test-simple--ok-msg fail-message))) (defun test-simple--add-failure (type test-info-msg fail-msg &optional test-info) (unless test-info (setq test-info test-simple-info)) (cl-incf (test-info-failure-count test-info)) (let ((failure-msg (format "\nDescription: %s, type %s\n%s" test-info-msg type fail-msg)) ) (save-excursion (test-simple--not-ok-msg fail-msg) (test-simple-msg failure-msg 't) (unless noninteractive (if test-simple-debug-on-error (signal 'test-simple-assert-failed failure-msg) ;;(message failure-msg) ))))) (defun end-tests (&optional test-info) "Give a tally of the tests run." (interactive) (unless test-info (setq test-info test-simple-info)) (test-simple-describe-failures test-info) (if noninteractive (progn (switch-to-buffer "*test-simple*") (message "%s" (buffer-substring (point-min) (point-max))) ) (switch-to-buffer-other-window "*test-simple*") )) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Reporting ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (defun test-simple-msg(msg &optional newline) (switch-to-buffer "*test-simple*") (let ((inhibit-read-only t)) (insert msg) (if newline (insert "\n")) (switch-to-buffer nil) )) (defun test-simple--ok-msg (fail-message &optional test-info) (unless test-info (setq test-info test-simple-info)) (let ((msg (if (getenv "USE_TAP") (if (equal fail-message "") (format "ok %d\n" (test-info-assert-count test-info)) (format "ok %d - %s\n" (test-info-assert-count test-info) fail-message)) "."))) (test-simple-msg msg)) 't) (defun test-simple--not-ok-msg (_fail-message &optional test-info) (unless test-info (setq test-info test-simple-info)) (let ((msg (if (getenv "USE_TAP") (format "not ok %d\n" (test-info-assert-count test-info)) "F"))) (test-simple-msg msg)) nil) (defun test-simple-summary-line(info) (let* ((failures (test-info-failure-count info)) (asserts (test-info-assert-count info)) (problems (concat (number-to-string failures) " failure" (unless (= 1 failures) "s"))) (tests (concat (number-to-string asserts) " assertion" (unless (= 1 asserts) "s"))) (elapsed-time (time-since (test-info-start-time info))) ) (if (getenv "USE_TAP") (format "1..%d" asserts) (format "\n%s in %s (%g seconds)" problems tests (float-time elapsed-time)) ))) (defun test-simple-describe-failures(&optional test-info) (unless test-info (setq test-info test-simple-info)) (goto-char (point-max)) (test-simple-msg (test-simple-summary-line test-info))) ;;;###autoload (defun test-simple-run (&rest command-line-formats) "Register command line to run tests non-interactively and bind key to run test. After calling this function, you can run test by key specified by `test-simple-runner-key'. It is preferable to write at the first line of test files as a comment, e.g, ;;;; (test-simple-run \"emacs -batch -L %s -l %s\" (file-name-directory (locate-library \"test-simple.elc\")) buffer-file-name) Calling this function interactively, COMMAND-LINE-FORMATS is set above." (interactive) (setq command-line-formats (or command-line-formats (list "emacs -batch -L %s -l %s" (file-name-directory (locate-library "test-simple.elc")) buffer-file-name))) (let ((func (lambda () (interactive) (funcall test-simple-runner-interface (apply 'format command-line-formats))))) (global-set-key (kbd test-simple-runner-key) func) (funcall func))) (defun test-simple-noninteractive-kill-emacs-hook () "Emacs exits abnormally when noninteractive test fails." (when (and noninteractive test-simple-info (<= 1 (test-info-failure-count test-simple-info))) (let (kill-emacs-hook) (kill-emacs 1)))) (when noninteractive (add-hook 'kill-emacs-hook 'test-simple-noninteractive-kill-emacs-hook)) (provide 'test-simple) ;;; test-simple.el ends here emacs-load-relative-1.3.1/test/load-file3.el0000644000175000017500000000140313474465145020417 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (setq loaded-file "load-file3") emacs-load-relative-1.3.1/test/load-file1.el0000644000175000017500000000143213474465145020417 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (setq loaded-file "load-file1") (setq loaded-file1 't) emacs-load-relative-1.3.1/test/test-file.el0000644000175000017500000000315213474465145020377 0ustar dogslegdogsleg;;; test-file.el --- Simple test for load-relative ;; Copyright (C) 2015 Free Software Foundation, Inc. ;; 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 GNU Emacs. If not, see . ;;; Commentary: ;;; Code: (load-file "../load-relative.el") (require 'ert) (ert-deftest test-name () (should ;; not sure how I can test the full path here because, well, I need to ;; resolve a relative path to do so... (equal "simple.txt" (let ((bf (find-file-noselect-relative "simple.txt"))) (kill-buffer bf) (file-name-nondirectory (buffer-file-name bf)))))) (ert-deftest test-contents () (should (equal "simple\n" (let* ((bf (find-file-noselect-relative "simple.txt")) (ct (with-current-buffer bf (buffer-string)))) (kill-buffer bf) ct)))) (ert-deftest test-contents-with-relative-file () (should (equal "simple\n" (with-relative-file "simple.txt" (buffer-string))))) (provide 'test-file) ;;; test-file.el ends here emacs-load-relative-1.3.1/test/simple.txt0000644000175000017500000000000713474465145020207 0ustar dogslegdogslegsimple emacs-load-relative-1.3.1/test/Makefile.am0000644000175000017500000000405313474465145020216 0ustar dogslegdogsleginclude $(top_srcdir)/common.mk PHONY=check test all check-elget test-elget help #: same thing as check all: check #: overall help on running the make targets help: @echo "The main function of this Makefile is to facilitate running tests." @echo @echo "To run all of the tests, use targets \"test\", \"check\" or \"check-short\"." @echo "For example:" @echo @echo " make check" @echo "or:" @echo " make check-short" @echo @echo "The -short target uses a filter written in Ruby to remove extreanous output." @echo @echo "To run a specific test like test-srcbuf.el, change \".el\" to" @echo "\".run\". For example:" @echo @echo " make test-srcbuf.run" @echo @echo "Tests can also be run via the Emacs el-get package and this loads dependent emacs " @echo "package, like load-relative. To do this, use targets, \"check-elget\"," @echo "\"test-elget\", or \"check-short-elget\"." @echo @echo "To run a specific test like test-srcbuf.el via el-get change \".el\"" @echo "to \".elrun\" For example:" @echo @echo " make test-srcbuf.elrun" #: same thing as "check" test: check test_files := $(wildcard test-*.el) CHECK_FILES = $(notdir $(test_files:.el=.run)) EL_GET_CHECK_FILES = $(notdir $(test_files:.el=.elrun)) #: Run all tests check: $(CHECK_FILES) #: Run all tests via el-get check-elget: (cd $(top_srcdir)/test && $(EMACS) --batch --no-site-file --no-splash --load ./install-pkgs.el --load test-load.el) #: Run all tests with minimum verbosity check-short: $(MAKE) check 2>&1 | ruby ./make-check-filter.rb #: Run all tests with minimum verbosity via el-get check-short-elget: $(MAKE) check-elget 2>&1 | ruby ./make-check-filter.rb test-%.run: (cd $(top_srcdir)/test && $(EMACS) --batch --no-site-file --no-splash --load $(@:.run=.el)) #: Run tests getting external Lisp dependencies test-%.elrun: (cd $(top_srcdir)/test && $(EMACS) --batch --no-site-file --no-splash --load ../el-get-install.el --load $(@:.elrun=.el)) # Whatever it is you want to do, it should be forwarded to the # to top-level directories # %: # $(MAKE) -C .. $@ emacs-load-relative-1.3.1/test/require-file2.el0000644000175000017500000000136613474465145021163 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (provide-me "my-") emacs-load-relative-1.3.1/test/test-require-list.el0000644000175000017500000000201113474465145022076 0ustar dogslegdogsleg;; Copyright (C) 2015, 2016 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (require 'cl) (load-file "./simple-test.el") (load-file "../load-relative.el") (test-simple-start) (if (featurep 'require-file1) (unload-feature 'require-file1)) (require-relative-list '("./require-file1")) (assert-t (featurep 'require-file1) "relative-relative-list") (end-tests) emacs-load-relative-1.3.1/test/make-check-filter.rb0000644000175000017500000000073113474465145021761 0ustar dogslegdogsleg#!/usr/bin/env ruby # Use this to cut out the crud from make check. # Use like this: # make check 2>&1 | ruby ../make-check-filter.rb # See Makefile.am pats = ["^(?:Loading", '(re)?make\[', "Making check in", "^Wrote", '\(cd \.\.', "make -C", "Test-Unit", "Fontifying", '\s*$', '##[<>]+$' ].join('|') + ')' # puts pats skip_re = /#{pats}/ while gets() next if $_ =~ skip_re puts $_ end emacs-load-relative-1.3.1/test/subdir/0000755000175000017500000000000013474465145017450 5ustar dogslegdogslegemacs-load-relative-1.3.1/test/subdir/Makefile0000644000175000017500000000021413474465145021105 0ustar dogslegdogsleg# Whatever it is you want to do, it should be forwarded to the # to top-level irectories PHONY=check all all: check %: $(MAKE) -C .. $@ emacs-load-relative-1.3.1/test/subdir/test-require-list-from-subdir.el0000644000175000017500000000222613474465145025625 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (require 'cl) (require 'test-unit) (load-file "../../load-relative.el") (test-unit-clear-contexts) (context "load-relative-list-from-subdir" (tag load-relative-list-from-subdir) (if (featurep 'require-file1) (unload-feature 'require-file1)) (specify "relative-relative-list" (require-relative-list '("../require-file1")) (assert-t (featurep 'require-file1)) ) ) (test-unit "load-relative-list-from-subdir") emacs-load-relative-1.3.1/test/load-file2.el0000644000175000017500000000140013474465145020413 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (load-relative "load-file3") emacs-load-relative-1.3.1/test/test-load.el0000644000175000017500000000564713474465145020412 0ustar dogslegdogsleg;; Copyright (C) 2015, 2016 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (require 'cl) (load-file "./simple-test.el") (load-file "../load-relative.el") (test-simple-start) ;; (setq tempbuf (generate-new-buffer "*cmdbuf-test*")) ;; (assert-nil ;; (with-current-buffer tempbuf ;; (insert "(__FILE__)\n") ;; (eval-current-buffer)) ;; (kill-buffer tempbuf) "(__FILE__) on temporary buffer") (assert-equal "test-load" (file-name-sans-extension (file-name-nondirectory (__FILE__))) "(__FILE__) on this running program" ) (dolist (file-name '("load-file1.el" "./load-file1.el" "../test/load-file1.el")) (assert-equal (expand-file-name file-name) (relative-expand-file-name file-name)) "relative-expand-filename" ) (note "Basic load-relative") (setq loaded-file nil) (assert-equal t (load-relative "load-file2")) (assert-equal "load-file3" loaded-file) (setq loaded-file nil) (setq loaded-file1 nil) (assert-equal '(t t) (load-relative '("load-file1" "load-file2") )) (assert-equal 't loaded-file1) (assert-equal "load-file3" loaded-file) (dolist (file-name '("load-file1.el" "./load-file1.el" "../test/load-file1.el")) (setq loaded-file nil) (assert-equal t (load-relative file-name) (format "load-relative with list file %s" loaded-file)) (assert-equal "load-file1" loaded-file (format "load-relative value with list file %s" loaded-file) )) (if (featurep 'require-file1 t) (unload-feature 'require-file1)) (require-relative "require-file1") (assert-t (featurep 'require-file1) "require-relative") (if (featurep 'require-file1 t) (unload-feature 'require-file1)) (require-relative-list '("require-file1" "require-file3")) (assert-t (and (featurep 'require-file1) (featurep 'require-file3)) "require-relative-list") (if (featurep 'my-require-file2 t) (unload-feature 'my-require-file2)) (require-relative-list '("require-file2") "my-") (assert-t (featurep 'my-require-file2) "require-relative-list with prefix") (if (featurep 'test-load t) (unload-feature 'test-load) "provide-me - no prefix") (provide-me) (assert-t (featurep 'test-load)) (if (featurep 'my-test-load t) (unload-feature 'my-test-load)) (provide-me "my-") (assert-t (featurep 'my-test-load) "provide-me - prefix") (end-tests) emacs-load-relative-1.3.1/test/require-file3.el0000644000175000017500000000137413474465145021163 0ustar dogslegdogsleg;; Copyright (C) 2015 Free Software Foundation, Inc ;; Author: Rocky Bernstein ;; 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 . (provide 'require-file3)