public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: open IE from command line
Date: Thu, 22 Dec 2016 18:14:00 -0000	[thread overview]
Message-ID: <f56639d6-0026-ad44-ea9d-15d634c1b42f@SystematicSw.ab.ca> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A704BBD5E7C@USA7109MB022.na.xerox.net>

On 2016-12-22 07:25, Nellis, Kenneth wrote:
> Mystery solved (to my satisfaction). After writing, I realized that
> the script wasn't working consistently, sometimes causing IE to
> misbehave as I originally posted. A bit of digging showed that it was
> working if invoked from a bash session initiated by "chere", but not
> otherwise. Comparing environment variables between the two, I notice
> my regular session doesn't include several variables that chere does.
> Prime suspects:
>  * CommonProgramFiles(x86)
>  * CommonProgramW6432
>  * PUBLIC
>  * ProgramData
>  * ProgramFiles(x86)
>  * ProgramW6432
> Experimentation will no doubt find the culprit, and will put me back 
> in business.

Check your Cygwin/mintty startup shortcut target or other command line 
looks like: 
	"...\bin\mintty.exe -i /Cygwin-Terminal.ico -"
where the final " -" ensures that the shell is invoked as a login shell, 
otherwise normal login setup may not be done correctly or fully.

Confirm that you still have /bin/cygwin-console-helper installed.

Failing that, check if your profile or rc scripts are doing, using, or 
invoking something which sanitizes your environment or changes it 
incompatibly.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2016-12-22 18:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 16:15 Nellis, Kenneth
2016-12-20 17:20 ` Lee
2016-12-20 22:10   ` cyg Simple
2016-12-20 22:51   ` Andrey Repin
2016-12-20 23:32     ` Eliot Moss
2016-12-21  0:50       ` Lee
2016-12-21 14:11   ` Nellis, Kenneth
2016-12-21 14:46     ` Buchbinder, Barry (NIH/NIAID) [E]
2016-12-21 16:14     ` Lee
2016-12-21 17:01     ` Nellis, Kenneth
2016-12-22  1:04       ` Doug Henderson
2016-12-22  1:25         ` Doug Henderson
2016-12-22 13:43           ` Nellis, Kenneth
2016-12-22 13:54             ` cyg Simple
2016-12-22 13:51         ` cyg Simple
2016-12-22 14:26           ` Nellis, Kenneth
2016-12-22 15:51             ` Andrey Repin
2016-12-22 20:56               ` Nellis, Kenneth
2016-12-22 18:14             ` Brian Inglis [this message]
2016-12-21  7:30 ` Brian Inglis

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=f56639d6-0026-ad44-ea9d-15d634c1b42f@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).