Pascal J. Bourguignon

> We noticed the same issue (wrong header being included, even though its path was not being included, its parent path was) on ceedling 0.32. > ceedling 0.31 does not...

Here is a minimal project demonstrating the problem. See the README.org in the archive. [ceedling-bug-order-header.tar.bz2.zip](https://github.com/ThrowTheSwitch/Ceedling/files/11868139/ceedling-bug-order-header.tar.bz2.zip)

Nope. 5|| is explicitly rejected as syntax for potential numbers by https://www.lispworks.com/documentation/lw61/CLHS/Body/02_caaa.htm This is to stay consistent with things like 5|x| or 5|2| which must both be interpreted as symbols....

> A few passages, including the one that I have already cited earlier from CLHS 2.3.1.1.1, suggest that escape characters should be part of the token. Here's another passage that...

Actually, these tools are compiled separately for different architectures, and libexec is a symlinl: ``` /Applications/Emacs.app/Contents/MacOS/libexec -> libexec-x86_64-10_11/ ``` but it points to the bad directory on arm. Fat executables...

It was chatgpt-shell that was failing on it, when it started a process "hexl". I have a exec-path with a lot of additionnal directories, and ineed, with libexec-arm64-11, so it...

> If you open your terminal and type `which hexl` does it print anything (that is, do you have `hexl` somewhere if your normal shell `PATH`)? > > I took...

Thanks, I'll check my paths. Also, since we can install it by just dragging Emacs.app somwhere. And it could be installed on a network file system and used simultaneously by...

Also, it would be nice if rebuilding would not overwrite the binaries used to rebuild.

You mention LW 8.0.1 Personal, so perhaps you’re only interested in implementation specific behavior, but note that a dot in a pathname component is NOT conforming. Even lower case is...