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
The organice file browser only displays files with a .org extension, but there's no requirement that org files have that extension (-*- mode: org; -*- works fine in emacs). It's possible to specify a path to an arbitrary file in the browser, but organice treats a filename like .../org.txt as a directory ... usually (and then gets stuck listing it). Once in a while it opens it as an org file, but I don't know what the circumstances are.
The text was updated successfully, but these errors were encountered:
Furthermore, it's a design decision to show only folders as well as '.org' and '.org_archive' files in the file browser in organice to remove potential clutter.
Remedies:
Regarding 1: Are you interested to build this file local variable as new feature?
Regarding 2: I propose a new config flag in the settings. Some people might prefer to show only .org and .org_archive files, some might chose to show all. Are you interested in building this new feature?
I solved it for myself with a hard link to a name ending with .org (no symlinks on Dropbox/Windows). I'll have to think about contributing ... I have decades of experience with many programming languages but JavaScript isn't one of them.
Good workaround with the hardlinks 👍 Symlinks unfortunately won't work in different scenarios (also webdav).
I'll have to think about contributing ... I have decades of experience with many programming languages but JavaScript isn't one of them.
That sounds great! JavaScript is not that hard when you have background in other languages. I'd say that's especially true when you're in a codebase with established patterns to adhere to.
If you do want to contribute, we'd be happy to help with reviews, docs and testing, of course!
The organice file browser only displays files with a .org extension, but there's no requirement that org files have that extension (
-*- mode: org; -*-
works fine in emacs). It's possible to specify a path to an arbitrary file in the browser, but organice treats a filename like .../org.txt as a directory ... usually (and then gets stuck listing it). Once in a while it opens it as an org file, but I don't know what the circumstances are.The text was updated successfully, but these errors were encountered: