devd -ol . returns error on Windows 7 about devd HOT 10 CLOSED

I just downloaded 0.4 and the problem has gone away for me.

from devd.

Hi there. I'm unable to reproduce this on Windows 10 - I'm hoping this means it's fixed in the latest release, rather than indicating some difference between Windows versions. Could you please try again with the latest release and re-open the ticket if the problem still exists?

from devd.

I have devd-0.3 in windows 7.

$ devd --version
0.3

I try to start devd with watching dot directory, but returns error.

$ devd -ol .
devd: error: Could not watch routes for livereload: The filename, directory name, or volume label syntax is incorrect.

-w is also error.

$ devd -ow . .
devd: error: Could not watch path for livereload: The filename, directory name, or volume label syntax is incorrect.

When specified as '.' then succeed.

$ devd -ol .\
20:54:42: Listening on http://devd.io (127.0.0.1:80)
20:54:43: GET /
  <- 200 OK 4.3kB

from devd.

I find the latest release, 0.3, has this problem on both Windows 7 64 as well as on Windows 10 64.
screenshot of it occurring on Windows 10 -> http://i.imgur.com/lAWbu3R.png

On Win 7, this occurs in both cmd.exe as well as using Cygwin's bash. On Windows 10, I don't have cygwin loaded, but it shows up in cmd.exe.

from devd.

Hi folks. OK, lets dig into this a bit more. @jerryasher - out of curiosity, do you see the issue with powershell on Windows 10?

from devd.

Yeah, I do still see it even under powershell
http://i.imgur.com/jbRxYKV.png

from devd.

An alternative is devd %cd% -ol
Seems to work everywhere

On Sun, Jan 17, 2016 at 8:48 PM, Jerry Asher [email protected]
wrote:

Yeah, I do still see it even under powershell
http://i.imgur.com/jbRxYKV.png

—
Reply to this email directly or view it on GitHub
#25 (comment).

from devd.

devd %cd% -ol

That does work in cmd, thanks, fwiw, it doesn't work in PowerShell.

from devd.

Hi - I'm still unable to reproduce this on any of my test systems (Windows 10) - devd -l . and variations work perfectly for me. Could someone please confirm that this still doesn't work with the current master. If that's the case, I'll roll up my sleeves and get a test system running earlier versions of Windows up and running.

Also, the thought occurs that this might be to do with the current working directory when running the command. If the error still occurs, could you please also show me the path for the directory you're serving.

from devd.

OK, I'll close this issue for now. If anyone else is still seeing this, please re-open.

from devd.