From: "Jason Fritz (CO/EWU)" <jason.fritz@ericsson.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: 1.5.18-1: cygwin.bat/bash fails after installing Cygwin
Date: Thu, 20 Oct 2005 18:46:00 -0000 [thread overview]
Message-ID: <9F3F9D47408B7144B594DBBF67F77BAC010833C8@eusrcmw720.eamcs.ericsson.se> (raw)
> On Thu, 20 Oct 2005, Jason Fritz wrote:
>
> I don't know much about the implementation of Cygwin bash,
> but perhaps it has a bug and it's not setting HOME like it
> should? I think from the info I posted above that it's
> clearly not working as intended.
Some more (possibly) interesting information:
I installed rxvt, and running rxvt -without- setting HOME does the right thing. That is, it starts up a console window and bash runs without any errors.
On the other hand, I'm exaggerating by saying it "does the right thing." If HOME isn't set, rxvt sets the font size and spacing to something very big, and the text onscreen looks ridiculous. If HOME -is- set, on the other hand, rxvt's font size/spacing looks neat and small. I wish I could provide details on what the font size actually is in both cases, but I don't know how to find that info.
Let me try to illustrate w/i the confines of ASCII :)
I f H O M E i s n o t s e t , i t l o o k s l i k e t h i s
If HOME is set, it looks normal
Anyway, I'm a relative Cygwin newbie, but it seems to me that Cygwin tools might not behave nicely without manually setting HOME and PATH.
Take care and thanks for your help,
Jason
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2005-10-20 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 18:46 Jason Fritz (CO/EWU) [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 19:15 Jason Fritz (CO/EWU)
2005-10-20 18:20 Jason Fritz (CO/EWU)
2005-10-20 18:44 ` Igor Pechtchanski
2005-10-20 17:36 Jason Fritz (CO/EWU)
2005-10-20 17:49 ` Igor Pechtchanski
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=9F3F9D47408B7144B594DBBF67F77BAC010833C8@eusrcmw720.eamcs.ericsson.se \
--to=jason.fritz@ericsson.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).