From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Fast linking to files in private git repos through a hyperlink
Date: Thu, 26 Apr 2012 21:06:04 +0300 [thread overview]
Message-ID: <CA++fsGF0WChVEcwt9uR9Ou5rA9b_XnczDE2SZcEUFkx0VGRuHA@mail.gmail.com> (raw)
In-Reply-To: <87zk9yh9u9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2170 bytes --]
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 my-org-repos. The whole
idea was that I wanted to be able to use the symbolic name as a shortcut.
In addition file.txt is not the path of a file in the repo, but a search
pattern for a file in the repo. In case of duplicates the user is prompted
to interactively resolve the file. In addition I would also like to add a
search pattern for a string in the file.
My problem is how to merge this syntax with the org-git-link.el which uses
the syntax
git:/home/user/repo/data/results.png::nobelprize
where /home/.../results.png is the name of the path to a file and
nobelprize is the name of a tag.
Both my linking and the org-git-linking are two different equally valid use
cases. My problem is how to merge both these use cases under a single
syntax.
Regards,
Dov
On Thu, Apr 26, 2012 at 17:00, Bastien <bzg@gnu.org> wrote:
> Hi Dov,
>
> Dov Grobgeld <dov.grobgeld@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 for indicating the search pattern,
> please use it this way too.
>
> > Thus to join the packages I need to change the syntax. Which of the
> > following would make more sense:
> >
> > git:@repo:file-in-repo::pattern-in-file
> > git://repo/file-in-repo::pattern-in-file
> >
> > or perhaps some other syntax? Suggestions?
>
> git:[user@?][repo-server]:[git-repo-itself]::[search-pattern]
>
> When user is set, the repo-server URL won't have a protocol
> (git will be used by default as a protocol.)
>
> When user is not set, the repo-server may contain git:// or
> http:// as the protocol.
>
> But I didn't test your packing, so I'm maybe shooting in the
> dark for this syntax suggestion.
>
> HTH,
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 2980 bytes --]
next prev parent reply other threads:[~2012-04-26 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 11:24 Fast linking to files in private git repos through a hyperlink Dov Grobgeld
2012-04-19 18:49 ` Karl Voit
2012-04-20 12:01 ` Bastien
2012-04-21 21:19 ` Dov Grobgeld
2012-04-26 14:00 ` Bastien
2012-04-26 18:06 ` Dov Grobgeld [this message]
2012-04-26 18:32 ` Samuel Wales
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=CA++fsGF0WChVEcwt9uR9Ou5rA9b_XnczDE2SZcEUFkx0VGRuHA@mail.gmail.com \
--to=dov.grobgeld@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).