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

Setting templates #58

Open
lionel- opened this issue Feb 19, 2016 · 2 comments
Open

Setting templates #58

lionel- opened this issue Feb 19, 2016 · 2 comments

Comments

@lionel-
Copy link
Contributor

lionel- commented Feb 19, 2016

Currently the template option is set up to expand a full path. This makes it difficult to use a template from the pandoc templates folder. E.g. (pandoc--set 'template "mycustomtemplate") will result in a failure.

Is there a workaround for this? If not, would you consider removing the 'full-path qualifier for that option?

@joostkremers
Copy link
Owner

Yes, I see the problem. Pandoc searches in its template directory if --template does not specify a fully qualified path, so I guess pandoc-mode should allow this as well. I'll need to think about how to best implement this, though. Just removing the full-path qualifier doesn't seem like the best idea, since this problem probably exists with other file options as well.

@joostkremers
Copy link
Owner

I did some work reorganising the way file options are handled. Now by default, every file option is stored as a relative path, so if you set the template file and type mycustomtemplate or something, that's exactly what's stored. If you want to store an absolute path, you can use the prefix argument C-u.

Also, if you use pandoc--set, as you do, relative file names are not expanded anymore. Only file names that are absolute are expanded. That should solve your problem.

Let me know if you run into problems.

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

2 participants