From: Bastien <bastien.guerry@wikimedia.fr>
To: Gregor Kappler <gregor.kappler@univie.ac.at>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-git-link does not support locational information within file
Date: Fri, 11 Feb 2011 18:17:58 +0100 [thread overview]
Message-ID: <87zkq2trqx.fsf@gnu.org> (raw)
In-Reply-To: <877hdh2m7a.fsf@univie.ac.at> (Gregor Kappler's message of "Thu, 03 Feb 2011 16:04:57 +0100")
Hi Gregor,
Gregor Kappler <gregor.kappler@univie.ac.at> writes:
> 2. use git versioned files transparently, i.e. org-git-store-link
> should support search (org-ids and text files) in linked git
> revisions of files.
I've look into this. We could code things to add a search string:
[[git:~/my.org::master@{2011-02-07}::Org code]]
^^
... but I'm reluctant to change the general syntax of links, even
if that's just for git links.
> 3. define an interactive function that can update the revision
> information of a link at mark to the current branch head of the
> file (so I can update all links to new FS folder structure.)
You mean update
[[git:~/my.org::master@{2011-02-07}::Org code]]
to
[[git:~/my.org::master@{2011-02-11}::Org code]]
?
Can you provide an explicit example?
> I am still lame at elisp - so my implementation skills are
> limited. With the great work in org-git-link all backend stuff seems
> there, only needing more glue. Any hints how to achieve this would be
> very welcome!
org-git-link.el is quite readable, and I'd welcome ideas on how to
extend it to fulfill your wishes without extending Org's link syntax
too much...
Thanks!
--
Bastien
next prev parent reply other threads:[~2011-02-11 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 15:04 org-git-link does not support locational information within file Gregor Kappler
2011-02-11 17:17 ` Bastien [this message]
2011-02-11 17:58 ` Samuel Wales
2011-02-11 18:05 ` Samuel Wales
2011-02-12 11:17 ` Bastien
2011-02-12 20:44 ` Samuel Wales
2011-02-13 12:20 ` Achim Gratz
2011-02-15 20:11 ` Gregor Kappler
2011-02-13 8:14 ` Leo Alekseyev
2011-02-15 20:15 ` Gregor Kappler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkq2trqx.fsf@gnu.org \
--to=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=gregor.kappler@univie.ac.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).