On Sunday 22 April 2007 22:54, Earnie Boyd wrote:
> > On the subject of RXVT, Brian Dessent recently suggested on
> > MinGW-MSYS, that the default MSYS startup mode should be made
> > `--norxvt', to avoid recurring questions relating to pty problems.
> Maybe the installer could ask before creating the shortcut?
Yes, that would be an option. An alternative would be to create two=20
shortcuts, one for each mode.
A possible problem with asking, is that the newbie doesn't know=20
beforehand, what problems lie in wait, if RXVT is chosen.
> > I asked for a vote on this, and while only a handful of users cared
> > enough to reply, those who did were unanimously of this same
> > opinion. I think we should address this, for the upcoming release.
> I don't remember if I answered,
I don't believe you did: the question was asked on MinGW-MSYS, after you=20
had curtailed delivery from that list.
> I would have been against it=20
> probably. =A0 But I know how to modify the shortcut to give a different
> response. =A0I give the RXVT term in my MSYS.BAT a value of xterm and
> all is well with me.
OTOH, I have found RXVT to be quite unusable. Building `groff' hangs at=20
about 80% complete. Running `nroff' interactively, the input stream=20
cannot be terminated, unless it's invoked as `cat | nroff [option...]'.
The suggestion was prompted by another round of enquiries about the old=20
chestnut: `Where did my terminal output go? Why do I have to hit the=20
<enter> key to see prompts? After I've done this, why don't I get to=20
type the response?' Of course, us old hands know what's going on here,=20
but it is horribly confusing for the newcomer.
Yes, the standard native console *is* grossly ugly. This time around, I=20
gave an extended reply, describing how I set it up so that I get most=20
of the advantages of RXVT, without the headaches; (about the only thing=20
I lose is the ability to resize the window by dragging its frame).