From: Dmitry Gutov <dgutov@yandex.ru>
To: Kevin Brubeck Unhammer <unhammer@fsfe.org>
Cc: 18788@debbugs.gnu.org
Subject: bug#18788: 24.4; vc-git-working-revision vs mode-line gives error
Date: Mon, 02 Feb 2015 15:10:54 +0200 [thread overview]
Message-ID: <54CF775E.2090408@yandex.ru> (raw)
In-Reply-To: <87twz7hzae.fsf@mm.st>
On 01/31/2015 03:09 PM, Kevin Brubeck Unhammer wrote:
> The repo I've seen it with under ~ if that makes any difference (ie.
> ~/.git) – I can't remember if I've seen it other places.
Is '~/.git' the name of the directory under version control? That could
be the cause of your problem: there is a directory with this name in
(almost) every Git repository, and it's used to store all version
control information. Git could be getting confused by this name.
> I get
>
> fatal: Not a git repository: .git
This points to the above explanation. However, it's odd that you can't
reproduce the problem reliably.
> Notably, this only happens with files that are in subdirectories of ~
> (but still tracked by the ~ repo), not with files that are directly
> inside ~. E.g. it happens with ~/org/gtd.org, but not with ~/.gitignore.
Did that happen with files inside ~/org/gtd.org? Was the error message
the same?
> When I restarted emacs to see if it had anything to do with my init.el,
> the bug was gone again.
Yeah, I think we'll need a solid reproduction to fix it.
next prev parent reply other threads:[~2015-02-02 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 8:31 bug#18788: 24.4; vc-git-working-revision vs mode-line gives error Kevin Brubeck Unhammer
2014-12-14 11:15 ` Dmitry Gutov
2014-12-15 9:50 ` Kevin Brubeck Unhammer
2015-01-31 13:09 ` Kevin Brubeck Unhammer
2015-02-02 13:10 ` Dmitry Gutov [this message]
2015-02-02 13:53 ` Kevin Brubeck Unhammer
2015-12-26 16:22 ` Lars Ingebrigtsen
2015-12-27 8:15 ` Kevin Brubeck Unhammer
2015-02-11 6:08 ` nil
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=54CF775E.2090408@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18788@debbugs.gnu.org \
--cc=unhammer@fsfe.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 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.