@Dennis: Are you sure you want to reserve ƁƇƊƑƓƘⱮƝƤƬƲȤɓƈɗƒɠɦƙɱɲƥʠɼʂƭʋȥ (or whatever they’ll be replaced by if that bit of the code page changes) for nilads?

@Lynn No, I want to use those glyphs for nilads, since those that are already assigned are nilads. For consistency, nothing more. I'll replace them with something else when I change the code page, so they can be used for quicks.

Maybe it would be a good idea to add certain input/output methods as command-line arguments. For example, l could split the input on newlines and join the output, separating by newlines.

I'm also thinking about a few ways to make Jelly golfier without breaking compatibility. For example, the codepage could interpret several characters as the same byte (like LF and ¶) do currently, which would allow me to add the proper glyphs without breaking old programs.