Orgzly support of .org_archive files

[BrianA-MN]

I have come to a point where I want to archive my old DONE items. I would like to keep both my orgzly repository and desktop repository in sync including the archive file. But this currently can't be done in orgzly, because it apparently create and write to a .org file extension. I found this out by trial and error. First create a .org file with org-mode and add some "TODO" and "DONE " tasks. Then use the default archive function of org-mode to write to an archive file (not to move to the end of existing file) with a file extension of .org_archive. Now sysc the repository with orgzly and import the .org_archive. What orgsly will do is create a new file in the repository location with the title of the org file you imported. Move some tasks from the non-archive org file to the archive, using orgzly copy and passt. Those items are placed in the newly created file, but not in the .org_archive file of the orgzly repository. Try to sync orgzly to the repository, then back to the desktop and find that the original .org file is modified, but not the .org_archive.

Org-mode archives to {filename}.org_archive (by default). Unforunately orgzly doesn't recognize the file extension. So the only way around this is to designate in the desktop org-mode an alternate "archive" file. In org-mode this can be changed with the variable org-archive-location. Or by including the variable as #+ARCHIVE: file name:: in the file header. I'm trying both methods to verify this works, but running into problems with the header variable format.

It would be nice if orgzly recognized the default .org_archive file. Any chance that can be added? I'm not looking for the org-mode archive methodology, just the read/write ability to a file with a .org_archive extension.

Thank you.

[amberin]

Since Orgzly has no concept of "archiving", it makes sense to me that it is not aware of .org_archive files. What would it do with them? If we want Orgzly to support this concept, first we'd need to define the necessary user stories that the app should support, and how the UI should work. Should archive files appear as regular notebooks? Should they be synced by the app, but remain hidden and accessible through some special menu? I believe this type of questions neee to be addressed before dealing with the file types.

[BrianA-MN]

The issue of support for org-mode archiving actions had been discussed with the old orgzly application also. I agree that the archive function would need to be addressed if orgzly-revived was trying to duplicate the org-mode archive function. BUT that is not what is suggested here. The OP was asking if orgzly could recognize other file extensions and w/r to that imported notebook extension, in org mode format (which is simple structured text)? Or is there an impediment to reading and writing to non .org extension files? Cheers.