How to programmatically re-write your Elisp code with ‘el-search’ and ‘el-search-refactor’ (Or) How to De-‘dash’, De-‘s’ and De-‘f’ your Elisp Libraries
How to programmatically re-write your Elisp code with ‘el-search’ and ‘el-search-refactor’ (Or) How to De-‘dash’, De-‘s’ and De-‘f’ your Elisp Libraries
A Challenge: De-‘dash’ and De-‘s’ an Elisp snippet Down below you see an Emacs Lisp code which uses dash, and s libraries. You are tasked with de-‘dash’-ing and de-‘s’-ing this code so that it no l…
This looks neat but... does el-search-refactor actually exist? I am not able to find it anywhere.
This looks neat but… does el-search-refactor actually exist? I am not able to find it anywhere.
It is right there in the article. Here it is https://raw.githubusercontent.com/emacksnotes/emacsnotes.wordpress.com/master/el-search-refactor/el-search-refactor.el or https://github.com/emacksnotes/emacsnotes.wordpress.com/tree/master/el-search-refactor
Thanks, I see it now. I guess the use of that little link icon instead of the normal text anchor threw me.
Is there an actual reason to de-magnar your libraries? The main reason I use them is they provide some concise approaches to common operations. I get that later emacs have introduced similar functions but I try and maintain support for as wide a range of emacs versions add possible.
I guess it depends on whether you want to have less dependencies and support more Emacs versions, for the opposite.
If I am supplying functions for others, I generally like to keep the dependencies low, just use standard libraries built into Emacs, so I think this could be helpful.