-
Notifications
You must be signed in to change notification settings - Fork 62
abbreviations
This needs to be much more well thought out. What's been done so far is a gross hack. Special cases, conflicts, incomplete support.
Configuration files' Abbreviation=XXX directives will be treated as advisory. They are to be an initial suggestion only, and if their content is acceptable (meaning no conflict) then they are propagated to modops.conf. All real abbreviation support then comes out of modops.conf. Provide for creating, changing, deleting an abbreviation.
Ensure lack of conflicts. Incoming install abbrev is checked against all current abbrevs for duplication, rejection. Give non-modal dialog announcements about automatic choices (both acceptance and rejection) of abbrevs.
All module reference contexts need to be prepared to handle abbrevs, e.g. parallel module set and adv.search mod.lists currently do not do it. Makes for funny displays and empty output.
We must allow that an abbrev can supersede a real module name: My NET (kkNET) can be used as NET. Michael's engKJV2006 can be used as KJV. Option-setting and formatting rules affect the abbrev-named module. This effectively makes the real NET or KJV inaccessible. Is this a good/acceptable thing?
Items from original TODO file:
- remove inconsistent use cases
- add manual abbrev choice