howard/hamacs
howard/hamacs
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Argh ...

Browse source 
My attempt at making a gnarly banner function more readable by
creating lexical functions with `cl-flet` to pass to `mapconcat` was
thwarted! Who would have thunk that `mapconcat' couldn't access a
symbol reference to a function created by `cl-flet*'!?
This commit is contained in:
Howard Abrams 2022-09-28 22:36:30 -07:00
parent 3724a7decb
commit d5e30ec98f
1 changed files with 14 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
ha-eshell.org
View file

@ -587,15 +587,22 @@ Whenever I open a shell, I instinctively type =ls= … so why not do that automa
(format padded (cond
((string-match image-rx file) (propertize file 'face '(:foreground "light pink")))
((string-match code-rx file) (propertize file 'face '(:foreground "DarkSeaGreen1")))
;; ((string-match docs-rx file) (propertize file 'face '(:foreground "LightYellow1")))
((file-directory-p file) (propertize file 'face '(:foreground "SteelBlue")))
(t file)))))
(process-line
(files)
(mapconcat 'process-file files "• ")))
(concat
(mapconcat 'process-line (seq-partition files columns) "\n")
"\n\n"))))
;; This nasty little function was an attempt to make
;; things readable, but who would have thunk that
;; `mapconcat' couldn't access a symbol reference to a
;; function created by `cl-flet*'!?
(process-files
(table)
(mapconcat (lambda (line) (mapconcat
(lambda (file) (process-file file))
line
"• "))
table
"\n")))
(concat (process-files (seq-partition files columns)) "\n\n"))))
#+end_src
* Shell Windows
Now that I often need to quickly pop into remote systems to run a shell or commands, I create helper functions to create those buffer windows. Each begin with =eshell-=: