public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: Does not work well: rlwrap + rxvt + cmd
Date: Wed, 24 Aug 2011 15:40:00 -0000	[thread overview]
Message-ID: <j3360e$6au$1@dough.gmane.org> (raw)
In-Reply-To: <1314198447.17029.140258133233741@webmail.messagingengine.com>

On 08/24/11 08:07, Ronald Fischer wrote:
> I would like to run cmd.exe within a rxvt terminal on Windows 7.
My question is why? Why do you want to run cmd.exe?
> Problem is that calling the cmd.exe command history does not work (it 
> seems that the cursor keys are not passed properly to cmd.exe).
>
> In one thread in this mailing list, it was recommended to wrap the 
> rxvt call by rlwrap:
>
> rlwrap rxvt -e cmd.exe
>
> However, this doesn't solve the problem.
>
> Any other suggestions?
My suggestion would be to abandon cmd.exe altogether. This is not some 
smug response or anything like that. Simply put, I have not found a 
single thing that I need to have cmd.exe around to do it. In fact the 
only time I go into cmd.exe is to proof to others "See it fails in 
straight cmd.exe too".

I also find the cmd shell and command language inferior in that there's 
nothing special or even convenient in cmd that can't be done even 
quicker and better in bash. Now that's a subjective opinion and can be 
considered smug but it's held with literally years of using Cygwin and 
Unix/Linux systems together. It's demonstrable that scripts you might 
develop for bash under Cygwin work equally as well if you simply move 
them onto say Linux, Solaris, HP-UX, FreeBSD, etc. (sans the obvious 
non-portable things you might do with Cygwin specific executables like 
cygpath as well as Windows pathnames or other assumptions. Suffice to 
say, however, that you can program in that portability). I know - I do 
it all the time.

Given the above I must question again - why do you want to run cmd.exe?
> Maybe any alternative to the standard Windows console? On Windows XP I 
> used the sourceforge-project Console2, but on Windows 7 it crashes so 
> often, that I am looking for a different solution.
>
> In particular, I like with rxvt (and with Console2) the ease of 
> copyiing and pasting text, in particular text spanning more than one 
> line. 
I used rxvt for a long time. I too enjoy the copy and paste semantics 
and the ability to resize the term and it just works correctly. 
Additionally rxvt pays attention to ~/.Xdefaults settings which is 
convenient. However I've since switched to mintty. You should check it out.

As the other guy said, I don't think that running cmd.exe will work with 
the arrows because cmd.exe is expecting access to the console in a 
"Windows way". That said, and if you're hellbent on using cmd.exe, I 
vaguely recall another terminal emulator program (not a Cygwin thing 
mind you) called, I believe just "Terminal" (Good luck googling that!) 
which (insert fuzzy memory here) I believe used a hidden cmd console 
window to allow the Windows program the proper console environment while 
translating that to the non-hidden Terminal window. That might work...
-- 
Andrew DeFaria <http://defaria.com>
It's not an optical illusion. It just looks like one.


--
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

  parent reply	other threads:[~2011-08-24 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 15:07 Ronald Fischer
2011-08-24 15:15 ` Eliot Moss
2011-08-25  7:34   ` Ronald Fischer
2011-08-24 15:16 ` Charles Wilson
2011-08-24 15:40 ` Andrew DeFaria [this message]
2011-08-24 15:52   ` Ronald of Steiermark
2011-08-24 15:56     ` Eliot Moss
2011-08-25  7:51       ` Ronald Fischer
2011-08-25 17:46         ` Andrew DeFaria
2011-08-24 16:04     ` Andrew DeFaria
2011-08-25  7:54       ` Ronald of Steiermark
2011-08-25 17:37         ` Andrew DeFaria

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='j3360e$6au$1@dough.gmane.org' \
    --to=andrew@defaria.com \
    --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).