From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Yaakov Selkowitz <yselkowitz@cygwin.com>
Cc: cygwin@cygwin.com
Subject: Re: Problems with Qt5's QDesktopServices::openUrl()
Date: Thu, 10 Mar 2016 15:30:00 -0000 [thread overview]
Message-ID: <22241.37607.865000.714913@woitok.gmail.com> (raw)
In-Reply-To: Msg <56E10BFC.6080903@cygwin.com> of 2016-03-09 23:54:04 -0600 from yselkowitz@cygwin.com
Yaakov,
On Wednesday, 2016-03-09 23:54:04 -0600, you wrote:
> On 2016-03-05 09:02, Dr Rainer Woitok wrote:
> > currently I have two applications which I compiled myself under Cygwin:
> > GPSBabel and QMapShack. Both use Qt5, both provide online help via the
> > browser, and both fail doing so in my environment. The version of my
> > various Qt5 packages is 5.5.1-1.
> [snip]
> > So I assume QDesktopServices::openUrl() at least under Cygwin is having
> > a problem with blanks in path names and maybe also with the missing
> > ".exe" extension (see the "Launch failed" error message).
>
> Searching for "QDesktopServices::openUrl spaces in PATH" (without the
> quotes) turned up a lot of hits.
You are right, but the ones I found refer to blanks in the path of the
file TO BE OPENED. My problem is blanks in the path of the program that
is used to open the file. This program is picked internally by QDesk-
topServices::openUrl() and is called internally, and currently it seems
the path to it must not contain blanks.
Sincerely,
Rainer
--
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
next prev parent reply other threads:[~2016-03-10 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 15:03 Dr Rainer Woitok
2016-03-10 5:54 ` Yaakov Selkowitz
2016-03-10 15:30 ` Dr Rainer Woitok [this message]
2016-03-10 22:30 ` Yaakov Selkowitz
2016-03-11 14:39 ` Dr Rainer Woitok
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=22241.37607.865000.714913@woitok.gmail.com \
--to=rainer.woitok@gmail.com \
--cc=cygwin@cygwin.com \
--cc=yselkowitz@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).