all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Magit 2 troubleshooting
Date: Sun, 30 Aug 2015 01:19:48 +0300	[thread overview]
Message-ID: <87a8t9enzv.fsf@gmail.com> (raw)
In-Reply-To: <87mvxap3ac.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Sat, 29 Aug 2015 16:39:23 +0200")

Ludovic Courtès (2015-08-29 17:39 +0300) wrote:

> Alex Kost <alezost@gmail.com> skribis:
>
>> So I wish people good luck with moving to Magit2 :-)
>
> So!  I’ve upgraded ‘magit’ and ‘magit-svn’, but now (require 'magit-svn)
> yields this:
>
>
> Debugger entered--Lisp error: (void-function magit-key-mode-add-group)
>   magit-key-mode-add-group(svn)
[...]
> Does that ring a bell?

I don't see any reference to 'magit-key-mode-add-group' in
"magit-svn.el".  May it happen because you have an old "magit-svn" in
your "~/.emacs.d/elpa/" dir which has a priority over "magit-svn" from
guix?

> (Another thing I noticed is that the ‘git-commit-mode’ module has been
> renamed to ‘git-commit’.  Just mentioning it in case someone gets hit by
> this one.)

As well, as ‘git-rebase-mode’ → ‘git-rebase’.

-- 
Alex

  reply	other threads:[~2015-08-29 22:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 18:56 [PATCH] gnu: magit: Update to 2.2.0 Alex Kost
2015-08-17 19:38 ` Thompson, David
2015-08-18  7:19   ` Alex Kost
2015-08-18 12:11     ` Thompson, David
2015-08-22 17:31 ` Mark H Weaver
2015-08-22 20:48   ` Alex Kost
2015-08-25 19:04   ` [PATCH] gnu: magit: Update to 2.2.1 Alex Kost
2015-08-27  9:18     ` Ludovic Courtès
2015-08-27 15:20       ` Alex Kost
2015-08-29 14:39         ` Magit 2 troubleshooting Ludovic Courtès
2015-08-29 22:19           ` Alex Kost [this message]
2015-08-29 22:37           ` Alex Kost

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=87a8t9enzv.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.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.