11/14/2022 0 Comments Latex textify![]() The way I dealt with this was to take the generated HTML file and to search and replace the licensing information and URLs. It also hard-codes licensing information and URLs which are not appropriate for me. In addition I can't define an order on the way the API components are presented and consequently things jump around a-bit. #Latex textify code#It doesn't seem to like embedded HTML or markdown formatting in the lisp code comments, so the API descriptions appear somewhat 'flat'. The package does have its quirks/features. This package generates an HTML file with the API description based on embedded comments, which is exactly what I was looking for. One such package is Edi Weitz's documentation template. There are various lisp packages available which will pull out the source code comments for the public interface defined in the packages file. Javadoc style documentation, which can be generated from source code annotations would be ideal. Ideally you want the documentation and the code tightly integrated. I went through the code and made sure I documented the exported classes, methods and functions. The original documentation was generated 'by hand'. I want to be able to keep the documentation of cl-mongo current when I am adding new features to the package. The special keyword :all can be used to close all connections in the registry.Ĭontinue reading "Connections in CL-MONGO" This is useful if you want to use a different default connection, or want to change the parameters on an existing named connection.ĭefgeneric mongo-close ( name ) is used to close a connection. (defgeneric mongo-swap (left right) will swap two connections. If no connection with that name exists, a new connection will be created.ĭefun mongo-show () will show all connections currently in the registry. special variables.ĭefgeneric mongo (&key host port db name) gets the connection referred to by the :name keyword. The connection parameters used by the default connection for host, port and db are accessible through the mongo-default. Database calls in cl-mongo default to using the :default connection. Each connection is stored in a connection registry. In the new implementation each connection is referenced by a unique name. I revamped the way connections to a mongo database are handled in cl-mongo. Continue reading "Adding clojure to an existing slime setup in emacs" As it turns out, there 's currently a bit of incompatibility between clojure and the slime package, but it's minor and easy to work around. I"ll provide a few helpful links to get more information on slime and swank. I'm going to show how you too can use use the current cvs head for slime, and the current git repos for clojure, clojure-contrib and swank clojure to run clojure with slime and lisp. #Latex textify install#In addition, rather than hand things off to a tool like elpa, I'd like to install things myself, so I get to understand how the various pieces work together. As an alternative, you can start a swank server using either the swank plug-in for the leiningen build tool, or the swank plug-in for the maven build tool.Īll of this advice is good, but I've been using slime with sbcl and emacs for years and I don't want to start from scratch just to add clojure. The current recommended setup of emacs and slime with clojure is to have elpa handle all the dependencies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |