Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

vc in emacs problem with git

86 views
Skip to first unread message

Rustom Mody

unread,
Aug 27, 2009, 11:28:43 AM8/27/09
to help-gn...@gnu.org, Git Mailing List
This is emacs 23 using the new 'updated-for-modern-dvcs' vc
I see a mode line saying (note the colon)
Git:master

In the info on vc (Version control and the mode line) the emacs manual says:

  The character between the back-end name and the revision ID
indicates the version control status of the file.  `-' means that the
work file is not locked (if locking is in use), or not modified (if
locking is not in use).  `:' indicates that the file is locked, or that
it is modified.

However at the shell a git status says
# On branch master
nothing to commit (working directory clean)

If I close and reopen the file the colon becomes a -
But I get a message:

`working-revision' not found: using the old `workfile-version' instead.


Rustom Mody

unread,
Aug 27, 2009, 12:14:33 PM8/27/09
to help-gn...@gnu.org, Git Mailing List
Just updating my own question:
when I do a C-x v v (vc-next-action)
which is supposed to be the most basic operation for checking in a file I get

Wrong type argument: stringp, nil

So vc can be assumed to be a broken I guess?

Anselm Helbig

unread,
Aug 27, 2009, 5:10:03 PM8/27/09
to
At Thu, 27 Aug 2009 21:44:33 +0530,

Rustom Mody <rusto...@gmail.com> wrote:
>
> Just updating my own question:
> when I do a C-x v v (vc-next-action)
> which is supposed to be the most basic operation for checking in a file I get
>
> Wrong type argument: stringp, nil
>
> So vc can be assumed to be a broken I guess?

I had a similar problem. The cause was an old git.el I had lying
around. You should check if vc-git works when you turn off all
customization, i.e. with emacs -Q. Another possible source of old git
support files might be your OS. Debian and friends automatically
install git support for emacs along with the git package. Loading it
is disabled here for Emacs 23, though (Ubuntu Jaunty).

HTH,

Anselm

--
Anselm Helbig
mailto:anselm.helb...@googlemail.com

rustom

unread,
Aug 28, 2009, 1:43:46 AM8/28/09
to
On Aug 28, 2:10 am, Anselm Helbig <anselm.helbig

+news2...@googlemail.com> wrote:
> At Thu, 27 Aug 2009 21:44:33 +0530,
>
> mailto:anselm.helbig+news2...@googlemail.com

Thanks! That tracked it --that is vc works with emacs -Q and fails
without.
But now how to track where the problem is?
I can hardly use emacs with -Q !!

Anselm Helbig

unread,
Aug 28, 2009, 3:31:09 AM8/28/09
to
At Thu, 27 Aug 2009 22:43:46 -0700 (PDT),

Well, try emacs -q (no .emacs loading) and emacs --no-site-file (no
loading of site-specific customizations). What does

M-x locate-library vc-git

give you?

Tassilo Horn

unread,
Aug 28, 2009, 4:18:47 AM8/28/09
to help-gn...@gnu.org
Anselm Helbig <anselm.helb...@googlemail.com> writes:

Hi!

>> Thanks! That tracked it --that is vc works with emacs -Q and fails
>> without.
>> But now how to track where the problem is?
>> I can hardly use emacs with -Q !!
>
> Well, try emacs -q (no .emacs loading) and emacs --no-site-file (no
> loading of site-specific customizations). What does
>
> M-x locate-library vc-git
>
> give you?

And also check `M-x list-load-path-shadows' to find which external elisp
files shadow emacs builtins.

Bye,
Tassilo

rustom

unread,
Aug 29, 2009, 10:31:21 AM8/29/09
to
On Aug 28, 1:18 pm, Tassilo Horn <tass...@member.fsf.org> wrote:

Thanks Anselm & Tassilo
The specific info from Anselm -- checkout vc-git.el -- helped me track
the culprit. I had been trying it earlier; it neither worked and also
evidently broke the working vc. When I renamed it out of the way the
problem (seems) to have gone.

But Tassilo's method is the way of tracking down such problems in the
first place so thanks.

Rustom Mody

unread,
Aug 30, 2009, 4:54:07 AM8/30/09
to help-gn...@gnu.org, Git Mailing List
On Sun, Aug 30, 2009 at 12:11 AM, Junio C Hamano<git...@pobox.com> wrote:
> Rustom Mody <rusto...@gmail.com> writes:
>
>> Just updating my own question:
>> when I do a C-x v v (vc-next-action)
>> which is supposed to be the most basic operation for checking in a file I get
>>
>>  Wrong type argument: stringp, nil
>>
>> So vc can be assumed to be a broken I guess?
>
> Have you checked contrib/emacs/README?
> --

Sorry Junio I should have checked.

Actually I had earlier checked.
Then I tried many emacs-git options, none of which worked.
Then I upgraded my emacs to 23 in which the vc is upgraded for dvses like git.
Time passed and I forgot what I had found, made worse by the fact that
sometimes I'm on windows and sometimes on linux and the 'working'
status of different things is quite different.

However the point is that I was not loading the older vc-git.el at
all. emacs was getting the wrong one.
It may be better if vc were hardened so that it gets its own vc-*.els
in preference to random stuff lying on the load-path.


Junio C Hamano

unread,
Aug 29, 2009, 2:41:24 PM8/29/09
to Rustom Mody, help-gn...@gnu.org, Git Mailing List
0 new messages