Tools for Home Assistant that work with GNU Emacs

Right now this is just auto completion support for entity names.

You either need to put the JSON contents of your Home Assistant's /api/states API output in a file (probably called api_states.txt in your config directory) or you need to populate a file hass-mode-secrets.el with your server name and an authentication token (gotten from HomeAssistant's UI).

If you do the former, you need to pass the name of the file to hass-setup-completion (possibly just by using a prefix-arg before calling the function interactively:

C-u M-x hass-setup-completion

Will prompt you for the filename that has the contents of /api/states from your server.

It's easier to just use hass-mode-secrets.el unless you have another reason to have api_states.txt lying around (I do, and I like this completion being able to work without the live server running, which is why I support the file version in addition to accessing via a live server)

The aim of this exporter to generate meeting minutes plain text that is convenient to send via email. - Unnecessary blank lines are removed from the final exported plain text. - Header decoration and section numbers done in the default ASCII exports is prevented. - Also TOC and author name are not exported. This is an ox-ascii derived backed for org exports. This backend effectively sets the `org-export-headline-levels to 0 and, `org-export-with-section-numbers', `org-export-with-author and `org-export-with-toc to nil time being for the exports. That is equivalent to manually putting the below in the org file: #+options: H:0 num:nil author:nil toc:nil This package has been tested to work with the latest version of org built from the master branch ( http://orgmode.org/cgit.cgi/org-mode.git ) as of Aug 10 2016. EXAMPLE ORG FILE: #+title: My notes * Heading 1 ** Sub heading *** More nesting - List item 1 - List item 2 - List item 3 * Heading 2 ** Sub heading - List item 1 - List item 2 - List item 3 *** More nesting MINUTES EXPORT: __________ MY NOTES __________ * Heading 1 + Sub heading - More nesting - List item 1 - List item 2 - List item 3 * Heading 2 + Sub heading - List item 1 - List item 2 - List item 3 - More nesting REQUIREMENTS: - Emacs 24 is required at minimum for lexical binding support. - Emacs 24.4 is required as ox-ascii got added to org-mode in that Emacs release.

Run Conway's Game of Life, in all windows, using the original window content as seed. In addition, when performing the animation, the original characters and the colors they have, are retained, resulting is a much more living result than when simply using, say, stars. By "seed", it means that the original content of the windows are seen as dots in the plane. All non-blank characters are seen as live dots. The Game of Life animation can be started as a screensaver, so that it starts automatically when Emacs has been idle for a while. By default, it stops after 1000 generations. Screenshot:  Usage: `gameoflife-animate -- Start the Game of Life animation. `gameoflife-screensaver-mode -- Run as a screensaver. The animation is started when Emacs has been idle for a while. About Conway's Game of Life: Conway's Game of Life is a simple simulation, originally developed in 1970, taking place in a two-dimentional grid -- think of it as an infinite chess board. A square can either be dead or alive. In each step in the simulation, the following rule applies: - A live square stays alive only if it has two or three neighbours. - A dead square is resurrected if it has exactly three neighburs. Personal reflection: I have noticed that sparse programming languages with a lot of highlighting, like C and C++, produde the most beautiful animations. More dense programming languages, like elisp, tend to "kill" many squares in the first generation, making them less suited for Game of Life seeds.

This file should not be confused with Rick Bielawski's cobol-mode.el (http://www.emacswiki.org/emacs/cobol-mode.el), which this mode attempts to supersede. This COBOL mode features syntax highlighting for most modern COBOL dialects, indentation, code skeletons, rulers and basic formatting functions. Highlighting changes with the code format, which can be specified using the M-x customize menu. Installation: To install cobol-mode.el, save it to your .emacs.d/ directory and add the following to your .emacs: (autoload cobol-mode "cobol-mode" "Major mode for highlighting COBOL files." t nil) To automatically load cobol-mode.el upon opening COBOL files, add this: (setq auto-mode-alist (append (("\\.cob\\'" . cobol-mode) ("\\.cbl\\'" . cobol-mode) ("\\.cpy\\'" . cobol-mode)) auto-mode-alist)) Finally, I strongly suggest installing auto-complete-mode, which makes typing long keywords and variable names a thing of the past. See https://github.com/auto-complete/auto-complete. Known bugs: * Switching source formats requires M-x customize settings to be changed, saved and cobol-mode to be unloaded then reloaded. * Copying-and-pasting content in fixed-format sometimes results in content being pasted in column 1 and spaces inserted in the middle of it. * The indentation code leaves a lot of trailing whitespace. * Periods on their own line are sometimes indented strangely. * String continuation does not work. Missing features: * Switch between dialect's reserved word lists via M-x customize (without unloading cobol-mode). * Allow users to modify easily reserved word lists. * Expand copybooks within a buffer. * String continuation (see above). * Allow users to modify start of program-name area.

Quickstart (require font-utils) (font-utils-exists-p "Courier") Explanation Font-utils is a collection of functions for working with fonts. This library has no user-level interface; it is only useful for programming in Emacs Lisp. The following functions are provided, most of which deal with font names rather than font objects: `font-utils-exists-p `font-utils-first-existing-font `font-utils-is-qualified-variant `font-utils-lenient-name-equal `font-utils-list-names `font-utils-name-from-xlfd `font-utils-normalize-name `font-utils-parse-name `font-utils-read-name The most generally useful of these is `font-utils-exists-p', which tests whether a font matching the given name is currently available for use. To use font-utils, place the font-utils.el library somewhere Emacs can find it, and add the following to your ~/.emacs file: (require font-utils) See Also M-x customize-group RET font-utils RET Notes Compatibility and Requirements GNU Emacs version 24.4-devel : yes, at the time of writing GNU Emacs version 24.3 : yes GNU Emacs version 23.3 : yes GNU Emacs version 22.3 and lower : no Uses if present: persistent-soft.el (Recommended) Bugs Behavior/echo messages are not sane when font-utils-use-memory-cache is nil, or pcache is not available. Checking for font availability is slow on most systems. Workaround: where supported, font information will be cached to disk. See customize for more. font-utils-exists-p only supports two styles of font name. This page http://www.gnu.org/software/emacs/manual/html_node/emacs/Fonts.html#Fonts describes four styles of font name. TODO Better support for disabling caching. Possibly return a font object instead of font-info vector from font-utils-exists-p. Test whether (find-font (font-spec :name "Name")) is faster than font-info. font-utils-create-fuzzy-matches is not exhaustive enough to catch many typos. ; License Simplified BSD License: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. This software is provided by Roland Walker "AS IS" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall Roland Walker or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of Roland Walker.

Edit distance between two strings

Documentation at https://melpa.org/#/defrepeater

Documentation at https://melpa.org/#/htmltagwrap

Documentation at https://melpa.org/#/markdownfmt

Documentation at https://melpa.org/#/bibretrieve

Documentation at https://melpa.org/#/geolocation

Documentation at https://melpa.org/#/minesweeper

Documentation at https://melpa.org/#/chronometer

Documentation at https://melpa.org/#/nand2tetris

Documentation at https://melpa.org/#/importmagic

Documentation at https://melpa.org/#/liquidmetal

Documentation at https://melpa.org/#/structurizr

Documentation at https://melpa.org/#/chembalance

Documentation at https://melpa.org/#/levenshtein

Documentation at https://melpa.org/#/workgroups2

Documentation at https://melpa.org/#/inflections

Documentation at https://melpa.org/#/keypression