Jack

The command `echo ~` also seems to go poorly when GCALWAYS enabled -- if GCPROTECT is on, it results in a segfault; if not, `echo ~` literally echoes `~` (expected...

Another potential design for readline-history primitive(s) would be to have just one `$&history` primitive with several "subcommands". For example: - `$&history log $cmd` - `$&history setfile $file` - `$&history setpos...

> As for `$&sethistory`, it is necessary unless you create a `$&readhistory` primitive for readline's sake. Oops, I missed that. Good catch. > There are definitely more history operations that...

(Sorry, trying to clean up some old branches, I took this one out as well. Restored.)

Hmm, those are interesting ideas -- I'd never thought about the idea that with enough runtime support, it could be possible to change the shell's idea of true/false. I'm not...

Okay, as soon as I filed this it stopped happening. I'm gonna leave this open for now to see if I can figure out how to get it to start...

Aha, I'm getting repros again! Yay! The failures all happen while trying to produce `y.tab.o`. I notice in the Makefile there is no config line referring to dependencies of `y.tab.o`...

Here's my best guess right now as to what's going on: `make` doesn't know that a single `yacc` invocation produces both `y.tab.c` and `y.tab.h`. So what happens is, if `make`...

It would be valuable to add `-Wconversion` as well, but fixing all the warnings caused by `-Wconversion` is a whole task in itself (and, I suspect, causes a dizzying diff).

A thought that has just occurred to me, relevant for exception-based exit-on-false: Should false-exiting commands also cause an exception inside an exception handler? For example, if the following script is...