When --no-generic is passed, j4dd knows no generic names. If they are loaded every time, it could simplify AppManager. Generic names could be filtered afterwards.
It is also useful to know generic names even when they are not displayed because generic names could be in history. Now, j4dd in --no-generic can not distinguish a generic name marked in history and an invalid name. j4dd has to assume that a history entry is valid because it can't decide between these two. If it could, it could detect invalid names.
Collisions will behave a bit differently when this is implemented in --no-generic mode. But collisions are very rare in real use and being able to distinguish dead history entries is worth it.
When
--no-generic
is passed, j4dd knows no generic names. If they are loaded every time, it could simplify AppManager. Generic names could be filtered afterwards.It is also useful to know generic names even when they are not displayed because generic names could be in history. Now, j4dd in
--no-generic
can not distinguish a generic name marked in history and an invalid name. j4dd has to assume that a history entry is valid because it can't decide between these two. If it could, it could detect invalid names.