Kyle Meyer <k...@kyleam.com> writes: > Rasmus <ras...@gmx.us> writes: > >>>> Has Joey spoken for or against automatic fetching of content when >>>> requested? >>> >>> I think I'm missing something. Why would he have an issue with running >>> "git annex get"? >> >> I don't have anything against it, but in OP he also talks about >> implementing something similar for ox-$BACKEND output... Which doesn’t >> seem like a bad request. Why should org-attachment support git-annex >> other parts of Org not? But I don’t think we want to support annexed >> files in general. (What about LFS’ed files? Assuming a similar feature >> exists) > > I think Joey is a vim user, so I doubt he's said anything about an Emacs > program choosing to call "git annex get" :)
I want to know if e.g. the git annex (assistant?) could support transparently getting files. That is once I try to open file X, which is annexed and stored somewhere else, X will automatically be fetched /without/ the need to call "git annex get" first. I don’t know enough about annex, or file systems, to make a guess. [And I always just call "git annex get ." in the root of the annexed folder]. > But yeah, that's a good point about which parts of Org should support or > care about annexed files. IMO export and nearly all parts of Org should > not. I see org-attach as an exception because it is focused on managing > external files and already has some support for doing so with git and > git-annex. (I think it would be fine for org-attach to support other > ways of storing files, should someone care to implement it.) But I > don't actually use org-attach, so I may be off the mark here. The problem sounds like an Upstream Problemᵀᴹ (IMO), and I’d be happy to get rid of org-attach-git-annex-cutoff, i.e. cutting back on the "explicit" support (in favor of the better tools for this problem built into git annex). Rasmus -- Together we will make the possible totalllly impossible!
