Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Some commit today broke my Gnus
Date: Thu, 03 Feb 2011 21:25:43 +0100	[thread overview]
Message-ID: <871v3o6f20.fsf@member.fsf.org> (raw)
In-Reply-To: <87r5bp3pm4.fsf@fastmail.fm> (Tassilo Horn's message of "Thu, 03 Feb 2011 20:05:55 +0100")

Tassilo Horn <tassilo@member.fsf.org> writes:

Hi!

> since I've updated my git checkout some minutes ago until commit
> 647c17891849c561534af42b619e9679259ba2b3, I get a very strange warning
> on startup.
>
>   Warning: Warning - invalid active: 
>
> And, after that happens, my *scratch* buffer has been modified to this:
>
> \;\; This buffer is for notes you don\'t want to save, and for Lisp evaluation.
> \;\; If you want to create a file, visit that file with C-x C-f,
> \;\; then enter the text in that file\'s own buffer.
>
> What's going on?

The commit

--8<---------------cut here---------------start------------->8---
commit 26be1f2820f24c95bc97369e86c6f0bd9b389cea
Author: Adam Sjøgren <asjo@koldfront.dk>
Date:   Thu Feb 3 11:49:30 2011 -0800

    * gnus-start.el (gnus-get-unread-articles): Fix the call to methods
    that have no groups.
--8<---------------cut here---------------end--------------->8---

fixes the issue for me again.

Bye,
Tassilo
-- 
Sent from my Emacs



  reply	other threads:[~2011-02-03 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 19:05 Tassilo Horn
2011-02-03 20:25 ` Tassilo Horn [this message]
2011-02-04 19:00 ` Lars Ingebrigtsen
2011-02-04 19:03   ` Tassilo Horn

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=871v3o6f20.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).