vindarel
vindarel
What brings the performance hit is printing the data. This works fine: (setf *res* (dexador:get "https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=Microsoft"))
and my feedback: - use a shorter package name? (or more fun :p ) - in run-git or the download functions: no need of more error handling? (network error, the...
> eval-when […] it's most like a cache for ql packages for auto-completion. then a simple variable not instantiated, to check with `boundp`? (to differentiate with NIL) This seems nicer...
> I'm using it as a constant basically (not really a constant, but is not meant to change), it should get populated when compiling, which given the rate of update...
Hi, thanks for bringing a workforce to this task. > 3. where should I start IMO you cant start right away by writing content to Lem's website. There is a...
Do you notice a performance hit or even a lag when you run M-x commands (or do anything really)? I did and found a workaround: https://github.com/lem-project/lem/issues/1092
Hello, do you confirm that the same key combinations work in the SDL2 version? On my side: I can type characters with AltGr in ncurses and the GUI. AltGr-a =>...
- **breaking change** for vi-mode users: `lem-vi-mode:*command-keymap*` was renamed to `lem-vi-mode:*normal-keymap*`. - The SDL2 implementation implemented graphical-text-buffer and its drawing methods. This is a buffer that can mix the drawing...
see also https://github.com/fstamour/breeze/ It currently has a lossless parser (keeps comments) and helpers: insert a defpackage, insert a test, etc (https://github.com/fstamour/breeze/blob/master/tests/refactor.lisp not proper refactoring yet).
FWIW, a fuzzy matcher for strings: https://github.com/vindarel/fuzzy-match this was extracted from Next/Nyxt. It uses some string matching algorithm, with more manual selection to get a "natural" result. Some benchmarking and...