Coming from a point of ignorance here, but I like short for this as you can use it as a prefix, so I prefer:
kc85 (if/when distinct from m100) n82 n82a (if/when distinct from n82) n83 (if/when distinct from n82/n82a) m10 m10u (if/when distinct from m10) m100 t102 (if/when distinct from m100) t200 Short helps a lot if it will become an argument in a SUB file on CP/M as part of a build script On Wed, Jan 5, 2022, 00:39 B 9 <[email protected]> wrote: > Probably not relevant, but I used 'td200' for the Tandy 200 Terrminfo > <https://github.com/hackerb9/Tandy-Terminfo> since that's what > Radio-Shack used. > > On Tue, Jan 4, 2022 at 11:22 PM Brian White <[email protected]> wrote: > >> if it was me I'd probably make it m100, t102, t200, but I can't justify >> that based on consistency. Would the olivetti then be "om10"? yeck, and >> what would pc-8201a be? just lop off the "pc-" and the "a"? >> >> I'd probably end up just making the names longer. Even that would end up >> looking inconsistent, because 100 would have the word "model" in the name, >> maybe 102 and 200 too, but not any of the rest. You can't win :) >> >> -- >> bkw >> >> On Wed, Jan 5, 2022, 1:07 AM Willard Goosey <[email protected]> wrote: >> >>> >>> Should it be m200.def or t200.def? >>> >>> (yes im still alive) >>> (yes i think this is actually happening soon) >>> >>> Willard >>> >>> Sent from my Galaxy Tab® A >>> >>
