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.
Verify that the CONFIG file contains all configurations from the DEFCONFIG file. When the verification fails, raise an error with the mismatching keys and their values.
This function can modify a given DEFCONFIG (or .config) file by adding, changing or removing the list of strings in CONFIGS. This allows customization of Kconfig based projects like the kernel Linux or the bootloader 'Das U-Boot'.
These are examples for CONFIGS to add, change or remove configurations to/from DEFCONFIG:
'("CONFIG_A=\"a\"" "CONFIG_B=0" "CONFIG_C=y" "CONFIG_D=m" "CONFIG_E=" "# CONFIG_G is not set" ;; For convenience this abbreviation can be used for not set configurations. "CONFIG_F")
Instead of a list, CONFIGS can be a string with one configuration per line.
Build the given package, applying all of PHASES in order, with a Linux kernel in attendance.
Generate an image, possibly standalone, which contains all DEPENDENCIES, placing the result in IMAGE.image. Link in any asd files from DEPENDENCY-PREFIXES to ensure references to those libraries are retained.
If a `lib' output exists, build things there. Otherwise use `out'.
Generates a system which can be used by asdf to produce an image or program inside the current directory. The image or program will contain DEPENDENCIES.
Generates an entry point program from the list of lisp statements ENTRY-PROGRAM for SYSTEM within the current directory.
Use a lisp implementation to test the TEST-SYSTEMS using asdf.
Replace simple lisp forms that the guile writer escapes, for example by replacing ##p# with #p. Should only be used to replace truly simple forms which are not nested.
Use LISP to generate an executable, whose TYPE can be 'asdf:image-op or 'asdf:program-op. The latter will always be standalone. Depends on having created a "SYSTEM-exec" system which contains the entry program.
Replace invalid characters in STR with a hyphen.
Generate an executable program containing all DEPENDENCIES, and which will execute ENTRY-PROGRAM. The result is placed in PROGRAM. When executed, it will run ENTRY-PROGRAM, a list of Common Lisp expressions in which `arguments' has been bound to the command-line arguments which were passed. Link in any asd files from DEPENDENCY-PREFIXES to ensure references to those libraries are retained.
Evaluate PROGRAM with a given LISP implementation.
Use a lisp implementation to compile the SYSTEMS using asdf.
Read the name of a mod from MOD.CONF. If MOD.CONF does not have a name field and NOT-FOUND is #false, raise an error. If NOT-FOUND is TRUE, call NOT-FOUND instead.