Skip to content
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

Docset path in portable edition should be relative #956

Closed
AyrA opened this issue Jul 13, 2018 · 2 comments
Closed

Docset path in portable edition should be relative #956

AyrA opened this issue Jul 13, 2018 · 2 comments

Comments

@AyrA
Copy link

AyrA commented Jul 13, 2018

Info

Version: Zeal 0.5.0 Portable x64

Details

The docset path in the portable version should be relative if possible. Right now when zeal.ini doesn't exists, the application will fill in the full docsets path into the settings dialog. If the settings are saved without the user manually changing the path to a relative one, Zeal will save the absolute path which breaks the portability.

Steps to reproduce

  1. Create directory Zeal and put the portable application in this directory
  2. Launch Zeal, go to "Tools > Preferences" and click "OK", no need to change any setting
  3. Install at least one documentation
  4. Exit Zeal and rename the Zeal directory to something else
  5. Launch Zeal again. The installed documentations are gone until the path is fixed manually or the ini file deleted.

Temporary Fix

Anyone experiencing this issue can fix it temporarily by just typing docsets into the docsets path in the preferences.

Fix

Make sure that the portable version of Zeal uses a relative directory as default instead of an absolute.

@trollixx
Copy link
Member

Valid observation. I think Zeal should use relative path if docset storage lies inside application directory.

@trollixx trollixx added this to the 0.6.1 milestone Sep 28, 2018
@lock
Copy link

lock bot commented Mar 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Mar 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants