public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu> To: cygwin-xfree@cygwin.com Subject: Re: Issue with XWin under xlaunch Date: Tue, 24 Apr 2012 12:23:00 -0000 [thread overview] Message-ID: <4F969B17.7080407@cs.umass.edu> (raw) In-Reply-To: <4F96911C.30608@dronecode.org.uk> Ok, I can see that perhaps in some ways I was being foolish and could have figured out more of this myself. But here's something interesting. I tried this: - "Pin to Start Menu" of the supplied XLaunch short cut - Edit to change the command to: "/usr/bin/xlaunch.exe -run /home/Eliot/config.xlaunch" (since I want to start things, not build/edit a config file) The full line in the shortcut is: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/xlaunch.exe -run /home/Eliot/config.xlaunch" This works, without putting in the explicit /usr/bin/ everywhere in the .XWinrc file. BUT: I get the "extra" icon I don't want, this time for XLaunch rather than for StartXWin. So the "extra" icon seems to have to do with the bash that run.exe is starting and the fact that the bash is still there as parent to the still-running XLaunch (or StartXWin). Perhaps it is because the bash does not start the program under it in the same way that run.exe does? Regards -- EM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2012-04-24 12:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 10:24 Eliot Moss 2012-04-23 13:51 ` Jon TURNEY 2012-04-23 15:04 ` Ken Brown 2012-04-24 11:54 ` Jon TURNEY 2012-04-24 13:27 ` Ken Brown 2012-04-23 16:42 ` Eliot Moss 2012-04-23 16:46 ` Eliot Moss 2012-04-24 11:40 ` Jon TURNEY 2012-04-24 12:23 ` Eliot Moss [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=4F969B17.7080407@cs.umass.edu \ --to=moss@cs.umass.edu \ --cc=cygwin-xfree@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: linkBe 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).