git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: vc in emacs problem with git

From
RMRustom Mody <rustompmody@gmail.com>
Date
Aug 27, 2009, 16:14 UTC
Message-ID
<f46c52560908270914o7027dc0bo873544dc0687cc48@mail.gmail.com>
In-Reply-To
<f46c52560908270828o574c0de6s17189a7326a1376d@mail.gmail.com>

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?
On Thu, Aug 27, 2009 at 8:58 PM, Rustom Mody<rustompmody@gmail.com> wrote:
Show 21 quoted lines
> 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.
>
Previous: Rustom ModyNext: Tassilo Horn
Message 2 of 6 in “vc in emacs problem with git”
  1. Rustom ModyAug 27, 2009
  2. Rustom ModyAug 27, 2009
  3. Tassilo HornAug 27, 2009
  4. Rustom ModyAug 29, 2009
  5. Junio C HamanoAug 29, 2009
  6. Rustom ModyAug 30, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.