Alan Hargreaves writes: > That one item is of course the "style issue". [...] > Is this really an issue for the ARCs, or is this an > implementation detail?
The issue of style is architectural because of these concerns: - conformance to applicable standards - consistency with other Solaris applications - compatibility with other platforms Once you get past all of those, I think it's just a matter of taste. I'm not sure that makes it an "implementation detail," but it's no longer quite architectural. On matters of taste, especially where we aren't able to agree on the right answer, we've historically invoked the UIRB. Is that what's needed here? I hope not. (Is there any open process for the UIRB ... ?) I'd be happy with a default gmacs mode for ksh93[1]. I slightly agree with Joe that picking a default for everyone seems a bit presumptuous, but given that it's fairly easy to show that the normal key bindings for gmacs generally just do what a novice user expects and that's not true for any other editing mode[2], I think it's the best choice. That choice is also consistent with the default editing mode for "libtecla" (PSARC 2004/330; see also the tecla(5) man page), so I think it's architecturally sound for Solaris. Even if GNOME/GTK is driving off in a bizarre and unnatural Windows-like direction. 1. Full disclosure: as you can tell from my email headers, I'm a GNU emacs user. 2. "I have to hit the 'a' key twice to add an 'a', and then it doesn't even put the 'a' where I wanted, but instead puts it later on the line. And then I'm stuck in some kind of weird mode. What gives?" -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
