-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
search and view readonly #1612
Comments
Can you elaborate on what exactly doesn't work? Also you are using old version, please try v0.7.0. There were some fixes related to docset storage being a read-only directory. |
Hi,
It is the same behavior in v0.6.0 and v0.7.0.
On docsets with the '>' Sign searching works and the documenttree can be opened.
On docsets without '>' there is no tree and no results on searching.
And all docsets are readonly!
Am 8. Apr. 2024, um 16:40, Oleg Shparber ***@***.******@***.***>> schrieb:
Can you elaborate on what exactly doesn't work? Also you are using old version, please try v0.7.0. There were some fixes related to docset storage being a read-only directory.
—
Reply to this email directly, view it on GitHub<#1612 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHVRQP35ZFIIMFCEJS7TKATY4KT6XAVCNFSM6AAAAABF4XROHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSHEZTMMZUGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
There's something wrong with your setup. Docsets which cannot be expanded are corrupted. Try manually deleting them from docset storage directory (path can be found in settings), and reinstalling. |
Hi,
reinstalltion does not help!
Ich can turn off and on the '>' Sign with the rigths for writing - there is NO corruption in the docsets...
LG Bernhard
DI Höfling Bernhard
HTL-Donaustadt
Donaustadtstraße 45
1220 Wien
Mobile: (+43)680 5013606
Email: ***@***.***
Web: http://www.htl-donaustadt.at
Oleg Shparber wrote:
There's something wrong with your setup. Docsets which cannot be expanded are corrupted. Try manually deleting them from docset storage directory (path can be found in settings), and reinstalling.
—
Reply to this email directly, view it on GitHub<#1612 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHVRQP7KTGJV5BZA5QDK3ALY4MROZAVCNFSM6AAAAABF4XROHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTHAZDQOJZGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I am not sure if this is the same problem, but I am not able to interface with or test embedded HTML demos in my Zeal v0.6.1 (same version) documentation browser. I am able to successfully view demonstrations such as for SVG (Scalable Vector Graphics) though. |
We need to set our docsets readonly. Some of the docsets are view and searchable (e.g. Angular, CMake) and some not (eg. C++, CSS). What can we do?
When the docsets are writeable, all works, but we don't want to do.
We use the portable Version of Zeal.
The text was updated successfully, but these errors were encountered: