-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add recipe for org-wiki. #4268
Add recipe for org-wiki. #4268
Conversation
I have sent PR(caiorss/org-wiki#6) about package header. And please check following comment
|
Why not use the slash separator (/) instead of dash (-) because it works like a Clojure namespaces that uses / syntax ? It is easier in this way to group the functions by common prefix separating the prefix of the function and grouping them by pseudo "namespaces" that is more completion friendly and also better to the eyes. Why not innovate ? The slash convention doesn't mess anything on Emacs. By using the slash it is more easier to know to the package the function belongs. |
- Issue: Function directory-list is not defined, this causes run-time error. (melpa/melpa#4268 (comment))
It is Emacs Lisp coding convention. https://www.gnu.org/software/emacs/manual/html_node/elisp/Coding-Conventions.html |
All right, I have updated the code according to the Elisp coding conventions. But this conventions should be updated. Emacs lacks namespaces and the user has a hard time to spot visually to what package the function belongs. This notation taken from Clojure separates better the prefix of package name from the function name and it makes the functions more search friendly and completion friendly. |
We're not here to discuss language design, sorry, but you can bring it up on the emacs mailing list if you feel strongly. Whatever you think of them currently, the elisp conventions are there to support uniformity of code, so that we can all comfortably read and contribute to each other's code, so this is a matter of community benefit rather than individual preferences. (And I say this as someone who has worked a lot with Clojure, so I agree that its namespaces are nice.) Some additional specific feedback:
Hope that helps! |
Thanks for the feedback.
I've fixed the docstrings.
I have fixed the trailing parenthesis and the empty lines.
I have removed the function org-open-file-with-system, but the function org-wiki-xdg-open didn't do the same as that. It opens any file with system's default application like *.dwg files with Autocad or *.odf spreadsheet with Libreoffice calc.
Ok. I did it. |
At least one still has its subsequent lines indented.
Not as far as I can see. There are still lots of empty random lines before/after |
@caiorss are you still planing on making (pushing?) the requested changes, or should we close this? |
@caiorss Ping? :) |
It has been half a year and I am closing this now. Feel free to reopen when you have the time to finish this. |
As org-wiki appears to be unmaintained, I've decided to make my own fork, atlas48/org-lwiki, and am taking feedback for how to improve the codebase. |
Brief summary of what the package does
Org-wiki is an org-mode extension that provides tools to manage and build a desktop wiki where each wiki page is an org-mode file.
Direct link to the package repository
https://github.com/caiorss/org-wiki
Your association with the package
Author and maintainer.
Relevant communications with the upstream package maintainer
None
Checklist