3 ms·
The linked issue is probably useful if someone using Emacs/Org exports Org to Markdown format, and then uploads to a Github issue as that feature proposes. But
by kaushalmodi 8y ago
The linked issue is probably useful if someone using Emacs/Org exports Org to Markdown format, and then uploads to a Github issue as that feature proposes. But then I fail to see the advantage of that flow vs just committing the Markdown file to any online git repo and letting Netlify etc. take care of publishing the blog.
Because.. uploading a Markdown file to a Github issue is one thing, but then what about refactoring, occasional post edits, etc.? Probably keep on overwriting the same Github issue with updated Markdown files?
You don't have to reply to these questions here.. just some thought if you do invest time in implementing this feature request.
- fileeditview 8y agoI just now saw your comment. You are right it takes away some benefits if you don't use the Github markdown editor to write/edit the issues. The only "benefit" I can still see then is the great commenting system that is attached to each issue. I added some more features to glyph over the last two weeks however I had not put any more thought into this feature so far. It is really low priority for me right now and I guess it's not THAT useful so that's ok :) Thanks for your input however. It is always very welcome.