From: Leo Alekseyev <dnquark@gmail.com>
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: Sun, 13 Feb 2011 03:14:20 -0500 [thread overview]
Message-ID: <AANLkTi=cJSzX_42DXUNLgWgZ7W5EQOZqE0keazgW00dv@mail.gmail.com> (raw)
In-Reply-To: <877hdh2m7a.fsf@univie.ac.at>
> ** Shortcomings of git-link in current org HEAD
> Yet, org-git-link currently is too greedy for my daily use:
> 1. they kill org-links for org headings, if the org files are
> versioned in a git repository (and all of mine are!) and
> 2. they kill in-file-search information for versioned non-org files.
The discussion so far focused on extending the link syntax to allow
multiple pieces of "location" information (e.g. location within the
repository + location within the file), which is a good idea.
However, I think the bigger problem with org-git-link in its current
incarnation is that it forces me to use git:// links for all files
under version control, which is NOT what I want to do 90% of the time.
I have a quick hack to deal with this -- namely, commenting out
;; (add-hook 'org-store-link-functions 'org-git-store-link t)
and using a separate keybinding for storing git links using the
following function:
(defun org-git-store-link-interactively (arg)
"Store git link to current file."
(interactive "P")
(let ((org-store-link-functions (cons 'org-git-store-link
org-store-link-functions)))
(call-interactively 'org-store-link arg)
))
In addition, I'm not crazy about using the "branch@{date}" format for
storing links by default, so I hacked something that uses SHA1
instead... I could post a patch if anyone is curious.
--Leo
next prev parent reply other threads:[~2011-02-13 8:14 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
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 [this message]
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='AANLkTi=cJSzX_42DXUNLgWgZ7W5EQOZqE0keazgW00dv@mail.gmail.com' \
--to=dnquark@gmail.com \
--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).