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

Sword path #5

Closed
DavidHaslam opened this issue Jun 16, 2019 · 5 comments
Closed

Sword path #5

DavidHaslam opened this issue Jun 16, 2019 · 5 comments

Comments

@DavidHaslam
Copy link

Please tweak Ezra to use the same Sword path in Linux and Windows as do other front-ends such as Xiphos.

Then all modules already installed using Xiphos, or created locally using Sword tools will be immediately available to Ezra.

Refer to email thread in sword-devel mailing list.

David

tobias-klein added a commit that referenced this issue Jun 21, 2019
@tobias-klein
Copy link
Member

Fixed. Fix will be available in upcoming version 0.8.1.

@alerque
Copy link
Collaborator

alerque commented Jun 21, 2019

I haven't inspected the actual behavior yet, but the release notes for 0.8.1 make it sound like you are copying modules found in the normal Sword paths into another location. Is that what you did? If so why not just use them in place?

@tobias-klein
Copy link
Member

tobias-klein commented Jun 21, 2019 via email

@alerque
Copy link
Collaborator

alerque commented Jun 21, 2019

Okay so the sync is to a different format, not just shuffling same-format content around for the sake of it being in a different place. I'm good with that. Long term if using Sword content is the way to go skipping the intermediate formate altogether might be nice, but I don't have an issue with taking things one step at a time. Finding the modules I already have downloaded for use in other apps is a great step forward!

Thanks for the clarification.

@tobias-klein
Copy link
Member

tobias-klein commented Jun 21, 2019 via email

alerque pushed a commit to alerque/ezra-project that referenced this issue Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants