all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: thomas@koch.ro
Cc: John Wiegley <johnw@newartisans.com>, emacs-orgmode@gnu.org
Subject: Re: org-attach should detect git also higher in the filesystem
Date: Sat, 31 Aug 2013 16:05:22 +0200	[thread overview]
Message-ID: <09688E5F-AF8A-4AA6-8B0C-EB5FAF4BFBEF@gmail.com> (raw)
In-Reply-To: <4738097.ljaNXQUGza@x121e>

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

Hi Thomas,

I think this has been fixed today with 

http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=2c38c3acc0b5d1cb3bb26f45829d711bb6f4009c

Could you please check if this is correct?

Thank you.

- Carsten

On 5.8.2013, at 23:58, Thomas Koch <thomas@koch.ro> wrote:

> Hi,
> 
> I tested org-attach with the org file being inside a git repo. I observed that 
> the auto-commit feature of org-attach seems to work only if the data directory 
> is the root of a git repo (detected by looking for a .git folder in the data 
> folder).
> 
> I'd like however to have the org file in the git repo too and the data folder 
> being a sub-folder of the git repo. Actually I'd also like to use git-annex 
> here.
> 
> Some options of git rev-parse might be helpful here instead of coding the repo 
> detection check by hand in elisp: 
> 
> --show-toplevel
>           Show the absolute path of the top-level directory.
> 
> --is-inside-work-tree
>           When the current working directory is inside the work tree of the 
> repository print "true", otherwise "false".
> 
> What do you think?
> 
> Regards,
> 
> Thomas Koch, http://www.koch.ro
> 


[-- Attachment #2: Type: text/html, Size: 1914 bytes --]

      reply	other threads:[~2013-08-31 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 21:58 org-attach should detect git also higher in the filesystem Thomas Koch
2013-08-31 14:05 ` Carsten Dominik [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09688E5F-AF8A-4AA6-8B0C-EB5FAF4BFBEF@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=johnw@newartisans.com \
    --cc=thomas@koch.ro \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.