Hi Dov,
Dov Grobgeld dov.grobg...@gmail.com writes:
Thanks for the link. I wasn't aware of that package. I see that I
have a conflict in syntax as I used double colon for indicating the
git repo while org-git-link.el used double colon for search pattern.
The double colon is standard in Org
Thanks for your suggestion Bastien, but unfortunately it does not directly
map to the shortcut that I implemented in my package. In my *old* syntax:
git:repo::file.txt
file.txt is a search pattern for a *file* with in the symbolic repo repo
which maps to a real repo through the hash variable
I imagine git allows a lot of opportunities for more features that we
would want in such a link. Perhaps a more general, flexible, lispy
keyword-style syntax would be useful here? Or handle with different
link types and shunt off to a git call?
--
The Kafka Pandemic:
Thanks for the link. I wasn't aware of that package. I see that I have a
conflict in syntax as I used double colon for indicating the git repo while
org-git-link.el used double colon for search pattern. Thus to join the
packages I need to change the syntax. Which of the following would make
more
Hi Dov,
Dov Grobgeld dov.grobg...@gmail.com writes:
I thought I would share the following hack that I did with git.
In my org-mode notebook I often find myself references files that
reside in various private git repos. So far I have referenced these
either by just writing their name or
* Dov Grobgeld dov.grobg...@gmail.com wrote:
I thought I would share the following hack that I did with git.
In my org-mode notebook I often find myself references files that reside in
various private git repos. So far I have referenced these either by just
writing their name or giving a
