yew VS lib-os

It's possible, but you can observe how much trouble it can be in opsys , which doesn't depend on any C headers or do any grovelling. You may be suprised the amount of syscall instability papered over by libc.

org-view: https://github.com/nibbula/yew/blob/ea624f08ec235cf12536323c68a9805d9e668f3d/tools/view-org.lisp

I have plans to develop a shell that handles both POSIX shell script and common-lips, likely by simply passing the s-expressions to a REPL such as sbcl, but as I am very new to common-lisp I know that I will not having something fully working anytime soon, I am okay with that all is fun in learning right? I have, however, been hankering to find a new shell recently that can at least provide me with the basics of what I plan to create, a simple shell that can handle POSIX scripting and common-lisp interactively. For this I did some research and read this blog post. I have looked around at different dual shells and found that shcl and yew seem to be the most promising for my temporary use until my own shell is ready. My question here is, has anyone used either of these extensively? I am not expecting something that can give me what zsh does, I only use it for syntax highlighting anyway lol, but rather if either of these shells would be on par, interactively, with something like ksh (the shell I am most use too) i.e. basic tab completion, customizable prompt and anything else is a bonus. Does anyone here have experiences with stress testing either of these shells?

And a lot more. Knee deep in documentation, but still finishing my other stuff first.

I have been taking the time to learn more Common Lisp lately and only have a question about how to use a certain part of asdf. I am working on a library called lib-os; essentially think of it as a UIOP with some conceptual changes and more features. First let me just say, my code runs fines that is not the issue. I have loaded each function in, it all works as expected (except detect-os which I am still working!). The issue I am having is with loading order of my code inside of ASDF. Currently I am having an issue where I need to pull some code from my implementation.lisp file to use in my kernel.lisp, (featurep ()) to be specific. For awhile the aforementioned function was inside of kernel.lisp, but once I decided to start porting some features from UIOP I moved it into the other file to keep the code related to checking CL stuff in one place. The issue is that now when I run (asdf:load-system "os") it throws a warning saying it is cutting unreachable code from all of the os-p functions, i.e. all of the functions that call (feature-p). I am confused as to why this is because I have implementation.lisp not only loading before kernel.lisp, but also listed as a depends-on for it. I have searched around, but cannot figure out what I am missing. Additionally, and this is slightly off-topic, how does one make a function callable at compile-time? setenv-if-not-p was a macro, but ASDF kept saying I need to make (getenv) callable at compile-time. Apologise for taking up so much of this subreddits time! You all, and a friend, have helped me learn a lot and I have been able to work on this because of it!