-
Notifications
You must be signed in to change notification settings - Fork 26
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
support for AsciiDoc(tor)/reS formats #12
Comments
Hi gour. |
Hi @gour . |
@masasam Thank you very much for adding it!
There is one thing I can think of...adding ability to configure list of extensions for each markup, e.g. besides *.ad, the *.adoc or *.txt are common formats used for AsciiDoc(tor) files, similar with reST where *.txt is quite common one, so my idea is that instead of depending just on hard-cored extensions, it would be nice to provide ability that user provides his/her own (a)list for each markup format by adding to the default extension and then the code should just iterate through the list while detecting correct format? I'd gladly help, but, unfortunately, my current Elisp skills are inadequate although I hope to improve it in the future. |
Hi @gour . |
@masasam
considering that I defined:
in my init.el and just wanted to create new test.adoc file? |
Hi @gour |
Yes
;; Package-Version: 20170425.520 |
Masashı Mıyaura <notifications@github.com> writes:
Hi @gour .
Please erase the test.ad file if it exists.
There is no test.ad file.
|
@gour Could you show me your init.el. |
@masasam here is the relevant part:
|
Hi @gour . It worked. Try this ... (use-package easy-hugo |
Ahh, the trick is to put setup under
section instead of
Yes, that helps!! |
Hello,
thank you for very interesting package!
Considering I plan to use AsciiDoc(tor) markup with Hugo, what do you think to extend the package by adding support for AsciiDoc(tor)/reST markup formats?
The text was updated successfully, but these errors were encountered: