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
org mode prefers lowercase keywords now #303
Comments
Merged
@memeplex PERSONALLY I AM ALL FOR THE LOWERCASE CONVENTION, SINCE UPPERCASE CONVENTIONS ARE FALLING OUT OF STYLE EVERYWHERE. |
This is now sorted |
vyorkin
added a commit
to vyorkin-forks/yasnippet-snippets
that referenced
this issue
Sep 27, 2019
* upstream/master: (114 commits) java: unify array creation of main and main_class Renamed "switch" (which is not in lisp) to "cond" which is. Move .nosearch to ./snippets subdirectory Fix aref snippet c++: make cin recognize whether 'using namespace std' exists Do not underline, it is a subscript. Adds several flutter snippets for dart-mode rust: make fns/pfns like the rest of the function templates (fix AndreaCrotti#323) Add Debian and derivatives installation instructions Update crate Add perl use snippet. Downcase org snippets--AndreaCrotti#303 change key from google_* to goog_* Improved org snippets, removed cruft. add labelcref and left-right Update equation Update align A bash snippet to get the directory a script is located in collapse newlines Use group to create hybrid menu ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since some months ago the org mode codebase is preferring lowercase blocks and keywords. See for example this commit. Also, the template expansion based on 9.2 hardcodes
#+begin_/#+end_
in lowercase. Unfortunately, the snippets in this collection are all uppercase. Since there surely are and will be people that prefer the uppercase convention, what can be done to provide both options? Offer two sets of snippets? In case of providing just one, it's going to be time to move to lowercase.The text was updated successfully, but these errors were encountered: