> > - dvc commands that map to the commands of the specified backend > > I experimented a bit, the following could be a starting point for such a > function. It just collects all functions starting with xhg-dvc: > > (let ((xhg-commands)) > (mapatoms '(lambda (x) (when (and (functionp x) > (string= (substring (symbol-name x) 0 (min (length (symbol-name x)) 7)) "xhg-dvc")) > (add-to-list 'xhg-commands x)))) > xhg-commands)
ah, i see. > > - commands of specified backend that do not map to dvc commands > > No idea, how to do that. Each backend uses a namespace starting with a > prefix, e.g. xhg- > Some of these functions are candidates for commands that should be > listed. But there are also functions that are only helper functions. > Just do M-x tla- <TAB> to see what I mean. ah, ok. so i am curious. how does dvc know the mapping between its commands and the commands of the particular backend? does dvc rely on an assumption about corresponding command names, suitably prefixed -- or are the calls to specific backend commands implemented specifically within dvc? or? _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
