public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: rxvt won't stay running
Date: Fri, 23 Jun 2017 14:31:00 -0000	[thread overview]
Message-ID: <48af8837-5c55-3b88-307f-e492f258463c@dronecode.org.uk> (raw)
In-Reply-To: <20170622200001.GA1003@mrvideo.vidiot.com>

On 22/06/2017 21:00, Mike Brown wrote:
> On Thu, Jun 22, 2017 at 09:12:45AM -0500, Ren?? Berber wrote:
>> On 6/22/2017 4:45 AM, Mike Brown wrote:
>>> I've installed the latest (as of this writing) Cygwin base and a few other
>>> packages.
>> [snip]
>>> Any ideas why it is failing?  Something you need me to look at?  It isn't
>>> anything in the home files that I copied over from the XP box, because before
>>> I did that, I tried starting and it flashed and died.
>>
>> A long time ago rxvt changed from supporting Windows (native) to only
>> working under X-Windows (a.k.a. Cygwin/X or equivalent).

See https://cygwin.com/ml/cygwin-announce/2016-03/msg00100.html

> Ah, so in a galaxy far, far, away, it just might work. :-)
> 
> Thanks for the reason it no longer works.

To be clear: rxvt still works as an X terminal (although if you have 
need of such a thing, I'd strongly suggest you stop using rxvt and 
instead use something which has had release this decade, e.g. urxvt)

If you want a windows terminal, use mintty.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-06-23 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22  9:45 Mike Brown
2017-06-22 13:48 ` cyg Simple
2017-06-22 19:58   ` Mike Brown
2017-06-22 14:15 ` René Berber
2017-06-22 20:00   ` Mike Brown
2017-06-23 14:31     ` Jon Turney [this message]
2017-06-23 18:43       ` Mike Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48af8837-5c55-3b88-307f-e492f258463c@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).