public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Maarten Hoes <cppcheck.libreoffice@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Saved Xlaunch 'config.xlaunch' issue
Date: Sat, 31 Jan 2015 01:19:00 -0000 [thread overview]
Message-ID: <54CC2DAB.9040603@gmail.com> (raw)
In-Reply-To: <54CBE2B3.4020607@dronecode.org.uk>
Hi,
On 30-1-2015 20:59, Jon TURNEY wrote:
> On 22/01/2015 07:55, Maarten Hoes wrote:
>> When I create and save a configuration with 'XLaunch', for example as
>> 'config.xlaunch', I have the following behavior when double clicking the
>> saved config file: It just launches XLaunch as if no configuration was
>> saved at all. When I open up the saved configuration file in an text
>> editor, all the right settings are there in the xml file. Is this
>> expected behaviour, or am I running into a bug ? I'm expecting the saved
>> configuration in the xml file to be used instead of having to fill it in
>> again.
>
> Thanks for reporting this issue.
>
> It seems that this stopped working correctly a while ago due to some
> changes in run or cygwin argument parsing.
>
> I've uploaded an updated xlaunch-20150130-1 today which should fix this.
>
Thanks, the new version fixes the issue for me: double clicking a saved
.xlaunch file now uses the saved configuration settings.
- Maarten
--
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/
next prev parent reply other threads:[~2015-01-31 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 11:49 Cygwin/X XDMCP Issue Maarten Hoes
2015-01-17 21:06 ` Maarten Hoes
2015-01-18 8:57 ` Maarten Hoes
2015-01-22 7:46 ` Maarten Hoes
2015-01-22 7:55 ` Saved Xlaunch 'config.xlaunch' issue Maarten Hoes
[not found] ` <54CBE2B3.4020607@dronecode.org.uk>
2015-01-31 1:19 ` Maarten Hoes [this message]
2015-02-02 15:21 ` Cygwin/X XDMCP Issue Jon TURNEY
2015-02-02 15:26 ` Maarten Hoes
2015-02-13 7:24 ` Maarten Hoes
2015-02-13 16:13 ` 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:
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=54CC2DAB.9040603@gmail.com \
--to=cppcheck.libreoffice@gmail.com \
--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: 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).