Kevin Brubeck Unhammer

global-minor-mode?

1

This seems like it'd be useful to have everywhere (perhaps with a list of exception-modes).

Hangul spaces are treated as valid character identifiers in JavaScript

1

See https://stackoverflow.com/a/48274520/69663 Maybe if we're in js2-mode or another javascript-mode, we could also highlight these little critters.

Turning on this mode in a gnus article will overwrite the existing fontification of e.g. From, Subject etc.

missing parseTimeM

1

AFAICT, there's no https://hackage.haskell.org/package/time-1.11.1.1/docs/Data-Time-Format.html#v:parseTimeM (nor https://hackage.haskell.org/package/time-1.11.1.1/docs/Data-Time-Format.html#v:defaultTimeLocale ) in Data.Thyme.Format, making it not quite drop-in compatible

For regular bidix lt-proc -b, we want to just copy over unconsumed tags and that is fine: ``` $ echo '^kake$' |lt-proc -b nob-nno.autobil.bin ^kake/kake$ ``` When using regular generation...

Option to output '~' as compound separator

1

`apertium-pretransfer` has option `-e treat ~ as compound separator` – I don't know if any other tools have this, but it would be nice if we could implement support for...

Carefulcase eats words it can't generate

4

If the dictionary has ```xml kakenekake pc-anepc PC-anePC ``` then we get ```sh $ echo '^kake$ ^KAKE$ ^kake$'|lt-proc -C nob.autogen.bin kakene kakene ``` I would like it to just fall...

lt-proc -b explodes on a-zA-Z regexes + long input

5

b.dix: ```xml [a-zA-Z]+ ``` ```sh $ lt-comp lr b.dix b.bin regex@standard 3 105 $ echo '^HYPERSENSITIVITET$' | \time lt-proc -b b.bin ^HYPERSENSITIVITET/HYPERSENSITIVITET$ 0.18user 0.04system 0:00.22elapsed 100%CPU (0avgtext+0avgdata 141920maxresident)k 0inputs+0outputs (0major+36137minor)pagefaults...

Support for `ANY_CHAR` in regular dix files?

1

Then we could have bidix entries like ``. This would require changes to the compiler to allow it, and presumably trim and compose, perhaps also fst_processor?

Expand (some) ICU character classes in regex_compiler?

3

At the very least, getting Lower and Upper ranges would be nice, so we could ```xml \\p{Lu}\\p{Ll}+ ``` and whatnot. If we do the "simple" thing and just expand like...