On 12/11/2014 21:46, Joe Taylor wrote: > Hi Bill, Hi Joe, > >> Given the implications for JTAlert-X I would prefer not to change that >> path, what is the objection to space characters in paths? > OK, I suppose that's a good enough reason to leave it alone, at this > point. > > In general, I think space characters embedded in pathnames are a royal > pain. I avoid them whenever possible. Fair enough, I have long become comfortable with spaces in filenames on *nix systems where they cause no issues apart from having to escape them which I do without thinking on the command line. Windows was a bit late to the party with spaces in file names with its still in place eight dot three DOS legacy (and yet they used spaces on the most common system paths like "Program Files" and "My Documents"!) but TBH I suffer more issues with the twisted case sensitive on write and case insensitive on read nature of paths on Windows file systems which plays havoc with shared network file systems.
I am happy to change it if Laurie doesn't mind but it will require some coordinated release magic along the lines of the adoption of standard paths for writeable files and some probably code changes to set the window titles a little differently. > > -- Joe 73 Bill G4WJS. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
