Michał "phoe" Herda
Michał "phoe" Herda
Fixed by remapping `C-Backspace` to `sp-backward-delete-word`.
Actually *not* fixed. Issuing `(define-key smartparens-mode-map (kbd "") 'sp-backward-delete-word)` in IELM and hitting `C-backspace` several times causes erratic behavior, as the kill ring is seemingly cycled over.
Compile-time is probably overkill - Slynk compiles fine without Unicode, it needs Unicode only at runtime. ```lisp (eval-when (:compile-toplevel :load-toplevel :execute) (require "comm")) ;;; The default LW character element type...
By "overkill" I meant that sly does not require being compiled with the default character type set to `character` whatsoever.
Won't modifying the arguments to `w-o-t-s` below work better here? ```lisp (with-output-to-string (*standard-output* nil ;; Explicitly setting output type for LispWorks ;; as it diverges from the CL specification here....
> So it seems `(stream-element-type *standard-output*)` is not setf'able? Yes, http://www.lispworks.com/documentation/HyperSpec/Body/f_stm_el.htm does not mention that `s-e-t` is an accessor. ``` 3: ((SUBFUNCTION 1 (METHOD STREAM:STREAM-WRITE-STRING (SLYNK-GRAY::SLY-OUTPUT-STREAM T)))) ``` We need...
This one is clearly not enough then, e.g. if we still get `[error printing frame]` in the debugger then whatever string streams the debugger uses still need patching. I have...
OK, will try to do that when I notice people talking about Sly. My personal IRC setup is irssi inside tmux running on a VPS, and it works pretty flawlessly...
Nonetheless, some kind of filesystem support is required for compliance with the ANSI CL standard.
> What I am concerned about: will existing links break? This is a valid concern. Links to the Lisp Cookbook are already everywhere, from search engines through Stack Overflow to...