public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
	'Andy Hall' 	<A.Hall@servicepower.com>
Subject: RE: A question about cygstart
Date: Wed, 14 Jan 2009 23:45:00 -0000	[thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A211B41E8D@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <0FF3B6512477714C939F9B6310F6F97A02A92610@loui-dc1.sp.servicepower.com>

Andy Hall wrote on Wednesday, January 14, 2009 12:57 PM:
> I start Visual Studio in the scripts as follows.
>
> cygstart --showminimized   "/cygdrive/c/Program Files/Microsoft
> Visual Studio 8/Common7/IDE/devenv.exe" /edit
>
> If Visual Studio is not ruining, Visual Studio will start minimized.
> However, if Visual Studio is already running, a subsequent invocation
> of the same command will bring up the window maximized.
>
> No combination of options to cygstart seems to overcome this.   What
> other approaches are available.

Does devenv.exe behave similarly when started from a shortcut without
cygstart?

Sounds like as it loads, devenv.exe may be looking for other instances
and then deciding what to do on its own.  You might see if Visual Studio
has any options that can change that behavior.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

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

      reply	other threads:[~2009-01-14 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 18:27 Andy Hall
2009-01-14 23:45 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]

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=0105D5C1E0353146B1B222348B0411A211B41E8D@NIHMLBX02.nih.gov \
    --to=bbuchbinder@niaid.nih.gov \
    --cc=A.Hall@servicepower.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).