You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering what is the benefit of using the .page-file-extension in combination with the header
---format : whatever---
Isn't it simpler to choose the reader based on the file-extension (.md, .org, .html, .tex, .rst, ...)? Links then still look the same; but gitit has to look for the first occurrence of the basename of the file. For example
Here comes the [link](blah).
with blah.md to find.
The text was updated successfully, but these errors were encountered:
The idea was to have a simple mapping from URL to file.
Otherwise gitit would have to make multiple queries of the
filestore each time a page is requested (first trying .md,
then .rst, then .html, etc.).
Also, I had thought that people might want to include org,
md, rst, etc. files in their repositories as regular files,
not to be rendered as wiki pages. The present system gives
them a choice: if it's .page, it will be rendered as a wiki
page, and if it's .html, it will be rendered as an HTML upload.
I'm wondering what is the benefit of using the
.page
-file-extension in combination with the headerIsn't it simpler to choose the reader based on the file-extension (
.md, .org, .html, .tex, .rst, ...
)? Links then still look the same; butgitit
has to look for the first occurrence of thebasename
of the file. For examplewith
blah.md
to find.The text was updated successfully, but these errors were encountered: