You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure here is a right place to report this, since the problem is in the docset, but may be this problem requires more common solution in the code.
When opening many topics in Zeal for linux, e, g. javascript:for
there is an error:
Error opening /home/vitaly/.local/share/Zeal/Zeal/docsets/JavaScript.docset/Contents/Resources/Documents/developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for.html: No such file or directory
Failed to load URL file:///home/vitaly/.local/share/Zeal/Zeal/docsets/JavaScript.docset/Contents/Resources/Documents/developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for.html.
The reason is that 'Statements/' folder is lowercased in the docset: 'statements/'.
There are several such case mismatches in the docset.
Original docsets are prepared for Dash in Mac OS which uses not case-sensitive filesystem. So case mismatch between link and filename is unnoticeable to Dash users (and even Zeal Windows users), so there are not so many chances for them to be repaired, and many chances that new discrepancies would appear again and again.
Quick fix is to just rename the path, but we will have to do it again and again.
May be it is possible instead in the case of such an error just try to search for the file case-insensitively?
The text was updated successfully, but these errors were encountered:
Not sure here is a right place to report this, since the problem is in the docset, but may be this problem requires more common solution in the code.
When opening many topics in Zeal for linux, e, g.
javascript:for
there is an error:
The reason is that 'Statements/' folder is lowercased in the docset: 'statements/'.
There are several such case mismatches in the docset.
Original docsets are prepared for Dash in Mac OS which uses not case-sensitive filesystem. So case mismatch between link and filename is unnoticeable to Dash users (and even Zeal Windows users), so there are not so many chances for them to be repaired, and many chances that new discrepancies would appear again and again.
Quick fix is to just rename the path, but we will have to do it again and again.
May be it is possible instead in the case of such an error just try to search for the file case-insensitively?
The text was updated successfully, but these errors were encountered: