Kurtis Rader

@sneyx123 Also, if you're inclined to try and debug problems you'll find the `DPRINTF()`, `DPRINT_NV()`, `DPRINT_NR()` and `DPRINT_VT()` macros useful . See the bottom of the *config_ast.h.in* module.

@sneyx123 FWIW, I also tried to install `fish` which is my preferred interactive shell. It builds but fails to run with lots of errors starting with being unable to figure...

> There is some funny "{" "}" nesting if the "#ifdef" is true : Note that we do not define `_ast_fltmax_double` so the block of code predicated on that symbol...

FWIW, the `wcstoutf32s()` function did not exist in the ksh93u+ release. It is present in the ksh93v- code but is used in exactly one place. The same place that still...

Not only does `wcstooutf32s()` not exist in the last stable release: ksh93u+. The function that calls it, `sh_fmtstr(),` does not exist in that release.

There is only one use of `tvgettime()`: in `tvtouch()`. And `tvtouch()` is only used one place: `hist_touch()`. We're probably better off eliminating that (indirect) use of `tvgettime()` rather than adding...

Thanks, @McDutchie. I had answered most of my question(s) after opening this issue when it occurred to me to carefully read the ksh(1) man page. Nonetheless, your comment was helpful....

Also, the `builtin` documentation in the ksh(1) man page says: > Special built-ins cannot be bound to a pathname or deleted. Which means you can't create a dynamically loaded plugin...

Gah! I also meant to include this text from the "Built-in Commands" section of the ksh(1) man page in my previous comment: ``` Commands that are preceded by one or...

Point number one in my previous comment, from the ksh documentation, is obviously misleading if not outright wrong. Using a ksh93u+ binary: ``` $ /bin/ksh KSH PROMPT:1: x=y . /dev/stdin...