public inbox for
help / color / mirror / Atom feed
Subject: Re: Dfficulty with xorg-server-1.17.1-2.
Date: Sun, 01 Mar 2015 14:06:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

                                    2015.03.01.09:06:13 EST

Hi Jon,

       Thanks for the tips.

George                       gee_barrick_at_kent_dot_edu

On 2/28/15, Jon TURNEY <> wrote:
> On 25/02/2015 14:30, GEORGE BARRICK wrote:
>>     I have one small note for other folks who might like to run their
>> system in a way similar to mine.  I like to have xlaunch automatically
>> start a single colored xterm for me (in multi-window mode).  After
>> that I just open more from the command line as it suits me.  If I use
>> the command line embedded in the installed xlaunch.lnk file:
>> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/xlaunch.exe
>> it always prompts me through the tiresome "configure & start" GUI at
>> the beginning.  Adding the phrase
>> -run ~/config/config.xlaunch
>> at the end of that command line always gets ignored in favor of the
>> "configure & start" GUI.
> You need to quote the whole command line for bash after the -c,
> otherwise bash treats words after the first one as positional parameters.
> However, getting this quotation passed correctly through run requires a
> little bit of gymnastics, but this should work:
> C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "xlaunch -run
> ~/config/config.xlaunch"
>> However, when I strip the invocation of the
>> bash from that command:
>> C:\cygwin\bin\run.exe /usr/bin/xlaunch.exe -run ~/config/config.xlaunch
>> the xlaunch goes right ahead to run the single xterm that's described
>> in my ~/config/config.xlaunch file.
> This is not quite equivalent as there is no login shell in the ancestry
> of whatever your config.xlaunch starts, so your ~/.profile may not have
> been read.
> For that reason, using 'bash -l -c ""' is preferred and that's what
> start menu links that cygwin installs generally use.
> --
> Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  parent reply	other threads:[~2015-03-01 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 18:13 GEORGE BARRICK
2015-02-24 19:36 ` Jim Reisert AD1C
2015-02-24 21:39   ` Jon TURNEY
2015-02-24 21:50     ` Jon TURNEY
2015-02-25  1:36       ` GEORGE BARRICK
2015-02-25 17:23         ` GEORGE BARRICK
     [not found]           ` <>
2015-03-01 14:06             ` GEORGE BARRICK [this message]
2015-02-25 13:26     ` Jim Reisert AD1C
2015-02-25 14:30     ` Jim Reisert AD1C
2015-02-25 17:22       ` Jon TURNEY
2015-02-24 21:44 ` Jon TURNEY

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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).