search

atom / markdown-preview

📝 Markdown preview in Atom
MIT License
1.23k stars 358 forks source link

Markdown Preview option in file tree does not load file correctly if the file is not currently open #414

Open ottworks opened 8 years ago

ottworks commented 8 years ago

The garbage tab reads "E:%5CScripts%5CProjects%5CREADME.md". Tested with atom 1.10.0 beta-5 and markdown-preview 0.158.0

50Wliu commented 8 years ago

I cannot reproduce this on Windows 10 x64, Atom 1.11.0-dev-d47fd28. @0tt does this happen in safe mode (atom --safe) as well?

ottworks commented 8 years ago

Yes.

50Wliu commented 8 years ago

And what Windows version are you using?

ottworks commented 8 years ago

10 anniversary

On Aug 17, 2016 6:19 AM, "Wliu" notifications@github.com wrote:

And what Windows version are you using?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/atom/markdown-preview/issues/414#issuecomment-240408088, or mute the thread https://github.com/notifications/unsubscribe-auth/AFAoCpcctCWO0Q31iib2NG83ydBY4IoTks5qgwpngaJpZM4Jl_D_ .

lee-dohm commented 8 years ago

I also can't replicate this using Atom v1.10.0-beta7 on Mac OS X 10.11.6. @damieng, can you reproduce this? Maybe there is some assumption about drive letters or backslashes or something?

damieng commented 8 years ago

Just tried to repro this on Windows 10 anniversary.

It only happens if the file is not on C: drive.

damieng commented 8 years ago

Hmm, now I can't get it to repro since I updated markdown-preview to latest.

the-j0k3r commented 6 years ago

Hmm, now I can't get it to repro since I updated markdown-preview to latest.

I could repro this 100% of the time, in fact I came looking for an existing bug report before opening my own. So here is my "me too" report.

Windows 10, 1607 14393.1715 atom --version

Atom    : 1.20.1
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0

apm --version

apm  1.18.4
npm  3.10.10
node 6.9.5 x64
python 3.5.2
git 2.14.1.window
visual studio

It happened a great deal when reopening project next day but now, i rebooted machine a couple of times and am now on same boat as @damieng despite the version being same as before.

:/ Im sure there was a law for that.