George Sokolsky writes: > I had to apply it manually on the latest org-20200518 (line numbers > changed in this new version or me too lame) - the patch seem to fix the > below problem and works just fine!
The patch was against the master branch (specifically 9bc0cc7fb), not the maint branch which is the source of the ELPA archive. > IMHO using "#+FILETAGS: ARCHIVE" is one of legitimate ways of applying > ARCHIVE tag to items in org. I think this statement is a reply to me saying that "I'd guess that it's uncommon to try to set the ARCHIVE tag at the file level [because...]". To be clear, that didn't contain a claim one way or the other about whether "#+FILETAGS: ARCHIVE" is a legitimate way to apply an archive tag. But based on me taking the time to look into a code change, it probably doesn't surprise you that my first thought was "hmph, yeah, seems like that _should_ work". George Sokolsky later writes: > Kyle, could you please apply the patch to the org repository? I sent out the patch so that others have the opportunity to provide feedback on it as well as your initial message. If no one does (which is fine), at some point in the next few days I'll revisit the patch, maybe inspect the surrounding code a bit more, and apply it (assuming I don't end up convincing myself that it's a bad idea or needs more work).
