Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This package provides efficient vector-based hashtable implementation similar to .NET Generic Dictionary implementation (at the time of 2015). . See "Data.Vector.Hashtables" for documentation.
Render HTML in org-mode blocks.
This library enables the completion of C/C++ header file names using Company. To initialize it, just add it to `company-backends': (add-to-list company-backends company-c-headers) When you type an #include declaration within a supported major mode (see `company-c-headers-modes'), company-c-headers will search for header files within predefined search paths. company-c-headers can search "system" and "user" paths, depending on the type of #include declaration you type. You will probably want to customize the `company-c-headers-path-user and `company-c-headers-path-system variables for your specific needs.
A quail-based input method for the Ogham script (beith-luis-nion).
This library provides common desirable features using the Org interface for blocks and links: 0. A unified interface, the ‘defblock’ macro, for making new block and link types. 1. Colours: Regions of text and inline text can be coloured using 19 colours; easily extendable; below is an example. #+begin_red org /This/ *text* _is_ red! #+end_red 2. Multiple columns: Regions of text are exported into multiple side-by-side columns 3. Remarks: First-class visible editor comments 4. Details: Regions of text can be folded away in HTML 5. Badges: SVG badges have the pleasant syntax badge:key|value|colour|url|logo; only the first two are necessary. 6. Tooltips: Full access to Lisp documentation as tooltips, or any other documentation-backend, including user-defined entries; e.g., doc:thread-first retrives the documentation for thread-first and attachs it as a tooltip to the text in the HTML export and as a glossary entry in the LaTeX export 7. Various other blocks: Solution, org-demo, spoiler (“fill in the blanks”). This file has been tangled from a literate, org-mode, file; and so contains further examples demonstrating the special blocks it introduces. Full documentation can be found at https://alhassy.github.io/org-special-block-extras
This library implements the Org-mode back-end generic exporter for HTML Timeline. Installation ------------ Download the timeline scripts from https://squarechip.github.io/timeline/ Then copy the files relative to your html file.n The default (`org-timeline-source-url') is set to "modules/timeline/dist". Usage ----- To test it, run: M-x org-timeline-export-as-html in an Org mode buffer. See ox.el and ox-html.el for more details on how this exporter works.
This library provides common desirable “L”anguage “F”eatures: 0. A unifed interface for defining both variables and functions. LF-DEFINE. 1. A way to define typed, constrained, variables. LF-DEFINE. 2. A way to define type specifed functions. LF-DEFINE. 3. A macro to ease variable updates: (lf-define very-long-name (f it)) ≋ (setq very-long-name (f very-long-name)) 4. A more verbose, yet friendlier, alternative to SETF: LF-DEFINE. Minimal Working Example: (lf-define age 0 [(integerp it) (<= 0 it 100)]) (lf-define age 123) ;; ⇒ Error: Existing constraints for “age” violated! ;; “age” is not updated; it retains old value. (lf-define age 29) ;; OK, “age” is now 29. This file has been tangled from a literate, org-mode, file. There are numerous examples in tests.el.
This package provides access to an IEx shell buffer, optionally running a specific command (e.g. iex -S mix, iex -S mix phx.server, etc)
Terminal support for `company-quickhelp'.
This is the official Emacs mode for editing Julia programs.
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. This is a another exporter for org-mode that translates Org-mode file to beautiful PDF file EXAMPLE ORG FILE HEADER: #+title:Readme ox-notes #+author: Matthias David #+options: toc:nil #+ou:Zoom #+quand: 20/2/2021 #+projet: ox-minutes #+absent: C. Robert,T. tartanpion #+present: K. Soulet,I. Payet #+excuse:Sophie Fonsec,Karine Soulet #+logo: logo.png
Org mode export backend for exporting the document syntax tree to JSON. The main entry points are `ox-json-export-as-json and `ox-json-export-to-json'. It can also be used through the built-in export dispatcher through `org-export-dispatch'. Export options: :json-data-type-property (string) - This the name of a property added to all JSON objects in export to differentiate between structured data and ordinary key-value mappings. Its default value is "$$data_type". Setting to nil prevents the property being added altogether. :json-exporters - plist containing exporter functions for different data types. The keys appear in :json-property-types and can also be used with `ox-json-encode-with-type'. Functions are called with the value to be exported and the export info plist. Default values stored in `ox-json-default-type-exporters'. :json-property-types (plist) - Sets the types of properties of specific elements/objects. Nested set of plists - the top level is keyed by element type (see `org-element-type') and the second level by property name (used with `org-element-property'). Values in 2nd level are keys in the :json-exporters plist and are used to pick the function that will export the property value. Properties with a type of t will be encoded using `ox-json-encode-auto', but this sometimes can produce undesirable results. The "all" key contains the default property types for all element types. This option overrides the defaults set in `ox-json-default-property-types'. :json-strict (bool) - If true an error will be signaled when problems are encountered in exporting a data structure. If nil the data structure will be exported as an object containing an error message. Defaults to nil. :json-include-extra-properties (bool) - Whether to export node properties not listed in the :json-property-types option. If true these properties will be exported using `ox-json-encode-auto'.
M-x offlineimap We need comint for `comint-truncate-buffer
impatient-mode is a minor mode that publishes the live buffer through the local simple-httpd server under /imp/live/<buffer-name>/. To unpublish a buffer, toggle impatient-mode off. Start the simple-httpd server (`httpd-start') and visit /imp/ on the local server. There will be a listing of all the buffers that currently have impatient-mode enabled. This is likely to be found here: http://localhost:8080/imp/ Except for html-mode buffers, buffers will be prettied up with htmlize before being sent to clients. This can be toggled at any time with `imp-toggle-htmlize'. Because html-mode buffers are sent raw, you can use impatient-mode see your edits to an HTML document live! This is perhaps the primary motivation of this mode. To receive updates the browser issues a long poll on the client waiting for the buffer to change -- server push. The response happens in an `after-change-functions hook. Buffers that do not run these hooks will not be displayed live to clients.
This package contains extra functions for easy-kill/easy-mark: * easy-mark-word * easy-mark-sexp * easy-mark-to-char * easy-mark-up-to-char These are shorthand commands for easy-marking an aimed string at point. * easy-kill-er-expand * easy-kill-er-unexpand These work like `er/expand-region and `er/contract-region', respectively, using the functionality of the `expand-region package. It also provides the following easy-kill/easy-mark targets: * `buffer This selects the whole buffer. * `buffer-before-point * `buffer-after-point These work like vi's gg/G commands, respectively. * `backward-line-edge * `forward-line-edge The former is like vi's ^/0 commands, and the latter is just like that in the opposite direction. * `string-to-char-forward * `string-to-char-backward * `string-up-to-char-forward * `string-up-to-char-backward These work like vi's f/F/t/T commands, respectively. Experimental ace-jump integration into easy-kill is enabled by default. `ace-jump-*-mode can be invoked for selection when in easy-kill/easy-mark mode. You can disable this feature via a customize variable `easy-kill-ace-jump-enable-p'. Experimental multiple-cursors-mode support for easy-kill is enabled by default. `easy-kill and `easy-mark will mostly work in `multiple-cursors-mode'. Suggested settings are as follows: ;; Upgrade `mark-word and `mark-sexp with easy-mark ;; equivalents. (global-set-key (kbd "M-@") easy-mark-word) (global-set-key (kbd "C-M-@") easy-mark-sexp) ;; `easy-mark-to-char or `easy-mark-up-to-char could be a good ;; replacement for `zap-to-char'. (global-set-key [remap zap-to-char] easy-mark-to-char) ;; Integrate `expand-region functionality with easy-kill (define-key easy-kill-base-map (kbd "o") easy-kill-er-expand) (define-key easy-kill-base-map (kbd "i") easy-kill-er-unexpand) ;; Add the following tuples to `easy-kill-alist', preferrably by ;; using `customize-variable'. (add-to-list easy-kill-alist (?^ backward-line-edge "")) (add-to-list easy-kill-alist (?$ forward-line-edge "")) (add-to-list easy-kill-alist (?b buffer "")) (add-to-list easy-kill-alist (?< buffer-before-point "")) (add-to-list easy-kill-alist (?> buffer-after-point "")) (add-to-list easy-kill-alist (?f string-to-char-forward "")) (add-to-list easy-kill-alist (?F string-up-to-char-forward "")) (add-to-list easy-kill-alist (?t string-to-char-backward "")) (add-to-list easy-kill-alist (?T string-up-to-char-backward ""))
The I Ching or Book of Changes can be used as a divination method, pattern generator or fixed point for millennia of commentary & exegesis. This package provides methods for casting and describing hexagrams, querying the oracle, and finding patterns in randomness. The descriptions of hexagrams and their classification have been drawn from public domain sources, tradition and antiquity. Further details of usage along with reading & study material can be found in the README file.
Read the following for how to use the how-many function http://www.neverfriday.com/sweetfriday/2008/06/emacs-tip-word-counting-with-a.html The following site had a good idea on how to produce number of chars http://xahlee.org/emacs/elisp_count-region.html Inspired by http://750words.com ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Description: This is a major mode for the V programming language For more details, see the project page at https://github.com/damon-kwok/v-mode Installation: The simple way is to use package.el: M-x package-install v-mode Or, copy v-mode.el to some location in your Emacs load path. Then add "(require v-mode)" to your Emacs initialization (.emacs, init.el, or something). Example config: (require v-mode)
This package provides an Emacs interface to LeetCode allowing users to log in and solve problems of their choice using Emacs.
Verb is a package that allows you to organize and send HTTP requests from Emacs. See the project's README.md file for more details.
Adds 256 color handling to term/ansi-term by adding 247 customizable faces to ansi-term-color-vector and overriding term-handle-colors-array to handle additional escape sequences.
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.
`company-mode backend for `ledger-mode', `beancount-mode and similar plain-text accounting modes. Provides fuzzy completion for transactions, prices and other date prefixed entries. See Readme for detailed setup and usage description. Detailed Description -------------------- - Provides auto-completion based on words on current line - The words on the current line can be partial and in any order - The candidate entities are reverse sorted by location in file - Candidates are paragraphs starting with YYYY[-/]MM[-/]DD Minimal Setup ------------- (with-eval-after-load company (add-to-list company-backends company-ledger)) Use-Package Setup ----------------- (use-package company-ledger :ensure company :init (with-eval-after-load company (add-to-list company-backends company-ledger)))
org-brain implements a variant of concept mapping with org-mode, it is inspired by The Brain software (http://thebrain.com). An org-brain is a network of org-mode entries, where each entry is a file or a headline, and you can get a visual overview of the relationships between the entries: parents, children, siblings and friends. This visual overview can also be used to browse your entries. You can think of entries as nodes in a mind map, or pages in a wiki. All org files put into your `org-brain-path directory will be considered entries in your org-brain. Headlines with an ID property in your entry file(s) are also considered as entries. Use `org-brain-visualize to see the relationships between entries, quickly add parents/children/friends/pins to an entry, and open them for editing.