Le Fri, 16 Apr 2021 16:57:37 -0700,
"Steve Silverwood" <steve.silverwood@xxxxxxxxx> a écrit :
I did as you requested. Oddly enough, when I made that change, two
things happened: First, it ran correctly and used the contents of
GPODDER_HOME to see the configuration on the G: drive. Second, it
did not generate an output file at the location specified. I used
the name of an output file in a specific directory, though, rather
than just a name and then having to hunt for it, so maybe that made
the difference.
Anyway, it worked. Now I'll remove that change and see what
happens....
Weird. I removed the ">" output capture and restarted the app as
before. it's still running fine! What magical mystery did that
cause that made it work properly? I have no clue!!!
//Steve//
-----Original Message-----
From: gpodder-bounce@xxxxxxxxxxxxx <gpodder-bounce@xxxxxxxxxxxxx> On
Behalf Of Brand Huntsman Sent: Friday, 16 April, 2021 15:00
To: gpodder@xxxxxxxxxxxxx
Subject: [gpodder] Re: 3.10.18 now won't see GPODDER_HOME pointing to
my G: drive
On 14:46 Fri 16-Apr-2021, Steve Silverwood wrote:
OK, tried running gpodder.exe directly from the command prompt
In the icon that launches gpodder, can you change the program name to
"whatever-it-currently-is > gpodderoutput.txt", run it and find that
text file.
See the answer below if the program name has "start" in it.
https://superuser.com/questions/1198821/how-do-i-read-the-console-output-of-a-windows-gui-application
Attachment:
pgpa5bSG_EyL2.pgp
Description: Signature digitale OpenPGP
