The Neo 2 xmodmap would not be affected, I suppose. But changing the patterns in compat is certainly a change that will not be 100% backward compatible. To get rid of the warning alone, it is not worth it. However, in my opinion, if the action of a keysym would only depend on the keysym and not on the modifier map, it would be easier to make non-trivial custom layouts.
> Ok, so these warnings are just "hey, this is not ideal, but it doesn't break so if you don't have a better way, just leave it"?
They are real errors, however, xkbcomp recovers from than in a way that happens to make Neo 2 work. It's somewhat of a coincidence, but it has been that way for 6-7 years, so practically, its not too fragile. Again, the messages you see are not a sufficient reason to make big changes. Making things easier for people that what to make non-trivial custom layouts might be.
> hmm, some Neo2 people are still using xmodmap: https:/ /wiki.neo- layout. org/browser# linux/xmodmap . So just leave this warning be?
The Neo 2 xmodmap would not be affected, I suppose. But changing the patterns in compat is certainly a change that will not be 100% backward compatible. To get rid of the warning alone, it is not worth it. However, in my opinion, if the action of a keysym would only depend on the keysym and not on the modifier map, it would be easier to make non-trivial custom layouts.
> Ok, so these warnings are just "hey, this is not ideal, but it doesn't break so if you don't have a better way, just leave it"?
They are real errors, however, xkbcomp recovers from than in a way that happens to make Neo 2 work. It's somewhat of a coincidence, but it has been that way for 6-7 years, so practically, its not too fragile. Again, the messages you see are not a sufficient reason to make big changes. Making things easier for people that what to make non-trivial custom layouts might be.