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

Designate output directory #26

Open
stevepiercy opened this issue Jul 13, 2021 · 5 comments
Open

Designate output directory #26

stevepiercy opened this issue Jul 13, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@stevepiercy
Copy link

Is your feature request related to a problem? Please describe.

When converting all files, a new file is created as a sibling to the original. I must copy all these files to separate directory to build the converted files and compare to the original.

Describe the solution you'd like

It would be nice to be able to designate an output directory separate from the source directory. This would make it easier to build the converted files.

Describe alternatives you've considered

There might be an existing option to redirect output of which I am not aware, whether that is with this app or a shell command. I might create a shell script that uses rsync to move files into a separate directory to build the converted docs.

@stevepiercy stevepiercy added the enhancement New feature or request label Jul 13, 2021
@welcome
Copy link

welcome bot commented Jul 13, 2021

Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.

If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).

Welcome to the EBP community! 🎉

@chrisjsewell
Copy link
Member

thanks, yeh this shouldn't be too difficult, although I haven't got much time to do it right now 😬

The way I have set it up to run now is best used with a git version controlled repo. Then you can run and compare the changes with a git related tool

If you want to try making a PR, the code to change would be here:

for path in paths:

@stevepiercy
Copy link
Author

Thanks for the pointer to the code. I wrote a shell script that I think I can adapt for this purpose. It's also on my "things to do for open source list". 😜

@chrisjsewell
Copy link
Member

Haha yeh my TODO list always seems to get longer

@stevepiercy
Copy link
Author

Our motto in the Pylons Project: "Operating at the speed of open source."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants