Enter the query into the form above.
API method:
GET /api/symbols?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.
Return the requisites of PATHS, including PATHS---i.e., their closures (all its references, recursively).
Return the list of live store paths---i.e., store paths still referenced, and thus not subject to being garbage-collected.
Return the SHA256 hash of the nar serialization of PATH as a bytevector.
Export the store paths listed in PATHS to PORT, in topological order, signing them if SIGN? is true. When RECURSIVE? is true, export the closure of PATHS---i.e., PATHS and all their dependencies.
START, PROGRESS, and FINISH are used to track progress of the data transfer. START is a one-argument that is passed the list of store items that will be transferred; it returns values that are then used as the initial state threaded through PROGRESS calls. PROGRESS is passed the store item about to be sent, along with the values previously return by START or by PROGRESS itself. FINISH is called when the last store item has been called.
Return the store path whose hash part is HASH-PART (a nix-base32 string). Return the empty string if no such path exists.
Return #t if binary substitutes are available for PATH, and #f otherwise.
Return the name of FILE once interned in the store. Use NAME as its store name, or the basename of FILE if NAME is omitted.
When RECURSIVE? is true, the contents of FILE are added recursively; if FILE designates a flat file and RECURSIVE? is true, its contents are added, and its permission bits are kept.
When RECURSIVE? is true, call (SELECT? FILE STAT) for each directory entry, where FILE is the entry's absolute file name and STAT is the result of 'lstat'; exclude entries for which SELECT? does not return true.
Verify the integrity of the store and return false if errors remain, and true otherwise. When REPAIR? is true, repair any missing or altered store items by substituting them (this typically requires root privileges because it is not an atomic operation.) When CHECK-CONTENTS? is true, check the contents of store items; this can take a lot of time.
Add the contents of FILE-NAME under BASENAME to the store and return its store file name. When RECURSIVE? is false, FILE-NAME must designate a regular file--not a directory nor a symlink. When RECURSIVE? is true and FILE-NAME designates a directory, the contents of FILE-NAME are added recursively; if FILE-NAME designates a flat file and RECURSIVE? is true, its contents are added, and its permission bits are kept. HASH-ALGO must be a string such as "sha256".
When RECURSIVE? is true, call (SELECT? FILE STAT) for each directory entry, where FILE is the entry's absolute file name and STAT is the result of 'lstat'; exclude entries for which SELECT? does not return true.
Return the list of valid "derivers" of PATH---i.e., all the .drv present in the store that have PATH among their outputs.