Custom Query (31 matches)
Results (10 - 12 of 31)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#15 | fixed | Implement Greg's mode recognition | ||
Description |
Greg Jarvis changed the previous NEPMD mode recognition to add the following: o recognize Unix shebang o fully configurable mode detection o ... Unfortunately the provided code has at least one severe bug, that I'm not able to debug in shortness. That might be the reason that Greg had problems to get it implemented for some modes in the past. Moreover, it would lead to a much slower mode detection as it was before. The method before was also far from being optimal (e.g. mode files were read at every file load or settings were written at every load or every load causes the mode config files being read twice). OTOH, I would like to have that implemented. |
|||
#3 | fixed | Improve notifications | ||
Description |
E.g. popup a MsgBox? instead of a hint on the message line. Applies for:
Additionally:
|
|||
#19 | invalid | Install should not overwrite default key definitions (unless the user agrees to it) | ||
Description |
Long-time users of the old default key definitions may find it very upsetting to discover that as a result of installing a new version of NEPMD (with the "new and improved" key definitions), the key strokes they are used to using no longer work in the same way. (Count me in this group!) Presuming that any user's customized key definitions would already be kept intact, this ticket only applies to previous NEPMD users who do not have customized key definitions. I propose that the install detect a preexisting NEPMD installation without any custom key definitions. If it detects such an installation, then either: 1) Automatically copy the old default key defs into the myepm subtree, making the old default keys a "custom" key definition for the new installation; or 2) Describe the new key defs to the user and ask if it is OK to install the new defs as the default. If the user agrees, then overwrite the previous default key defs. If the user does not agree, then follow option 1 above. Either way the new key defs will be installed into the netlabs subtree giving the user the option to use the new key defs by backing out the previously-default-but-now-custom defs. |