vindarel
Good idea. Something like ```lisp (defun ensure (s &key start end wrapped-in) (cond (wrapped-in (ensure-wrapped-in wrapped-in s)) ((and start end) (ensure-start start (ensure-end end s))) (start (ensure-start start s)) (end...
re. naming, I now tend to `ensure-prefix/suffix`, along with `(ensure s :prefix … :suffix …)` @kilianmh thoughts?
Alright, thanks, let's name them properly and merge quick, I have code using these functions now! > ```lisp > (ensure-prefix "abc" "c3235") ;=> "abc3235" > ``` but this is too...
I wouldn't add these changes. I don't find the grammar stuff self-explanatory enough. I think we should rather understand what's missing from the existing function, and add meaningful key arguments....
The format directives: `~` plus a newline allows to format the format string with newlines, but to not have newlines in the result. `~@` is similar, we can also indent...
`split`, `rsplit` and `split-omit-nulls` with a `:regex` key argument is probably useful, although I didn't encounter the need. An example I can think of: ```lisp (str:split "[0-9]+" "some987stupid123string" :regex t)...
thanks for doing it! May it serve you well for advent of code ;)
I would warn about this move. Org-mode is _poorly_ supported by Github (for example, we can't inline html, so we can't have images with custom size and height, and it...
ah, you make a point, thanks for sharing.
@lewisl I just tried: use `C-x C-f` to open a file, but give it the name of a new file. This creates a buffer with the given name, the file...