Bug reports on Gnus from Emacs trunk

Bug reports on Gnus from Emacs trunk

[Christoph]

With the massive amount of development that is going on in Gnus, how 
important are bug reports right now and how/where should bugs be 
reported? `M-x gnus-bug' or the emacs bug tracker? I'd hate to waste 
people's time on stuff that would be fixed in the next commit or two anyway.

I am new to Gnus and it is difficult for me to tell what is an artifact 
of development or a real bug.

Thanks,
Christoph

Re: Bug reports on Gnus from Emacs trunk

[Tassilo Horn]

Christoph <cschol2112@googlemail.com> writes:

Hi Christoph,

> With the massive amount of development that is going on in Gnus, how
> important are bug reports right now

It's always good to report regressions as early as possible.  Of course,
before writing a report, be sure to update your checkout once again.
Maybe it's already working again.

> and how/where should bugs be reported? `M-x gnus-bug' or the emacs bug
> tracker?

I guess right now it's best to use M-x gnus-bug RET (which adds tons of
useful information to the mail) and change the To-address to
ding@gnus.org (the Gnus development list).  And you might also want to
subscribe to that list (or read it on Gmane: gmane.emacs.gnus.general)
to see if others are already discussing that issue.

Bye,
Tassilo

Re: Bug reports on Gnus from Emacs trunk

[Christoph]

On 10/5/2010 1:40 AM, Tassilo Horn wrote:

> I guess right now it's best to use M-x gnus-bug RET (which adds tons of
> useful information to the mail) and change the To-address to
> ding@gnus.org (the Gnus development list).  And you might also want to
> subscribe to that list (or read it on Gmane: gmane.emacs.gnus.general)
> to see if others are already discussing that issue.

Sounds good. Thanks Tassilo.

Christoph

Re: Bug reports on Gnus from Emacs trunk

[Karl Fogel]

Christoph <cschol2112@googlemail.com> writes:
>With the massive amount of development that is going on in Gnus, how
>important are bug reports right now and how/where should bugs be
>reported? `M-x gnus-bug' or the emacs bug tracker? I'd hate to waste
>people's time on stuff that would be fixed in the next commit or two
>anyway.
>
>I am new to Gnus and it is difficult for me to tell what is an
>artifact of development or a real bug.

Same question here.

For example, in trunk head as of right now (rev 101804), when I'm in a
Gnus summary buffer and I run 'B m' (for `gnus-summary-move-article'), I
get an error:

  Symbol's function definition is void: remove-if-not

The debugger confirms what the source code implies:

  Debugger entered--Lisp error: (void-function remove-if-not)
    remove-if-not(gnus-valid-move-group-p [0 0 0 some-group-name
                                           0 0 some-other-group-name
                                           0 more-hash-data 0 0 ...])
  gnus-read-move-group-name("Move" nil (174666) "")
  gnus-summary-move-article(nil)
  call-interactively(gnus-summary-move-article nil nil)

The function 'remove-if-not' is defined in lisp/emacs-lisp/cl-seq.el.
It's listed in cl-loaddefs.el, too, but clearly somehow it's not getting
loaded.  I can hack around it for now, but there's surely a Right Fix
that any Gnus hacker will know.

What's the right place to report this kind of thing?

Re: Bug reports on Gnus from Emacs trunk

[Lars Magne Ingebrigtsen]

Karl Fogel <kfogel@red-bean.com> writes:

> For example, in trunk head as of right now (rev 101804), when I'm in a
> Gnus summary buffer and I run 'B m' (for `gnus-summary-move-article'), I
> get an error:
>
>   Symbol's function definition is void: remove-if-not

It's a known issue -- I think we were promised a fix tonight.  :-)

> What's the right place to report this kind of thing?

ding@gnus.org

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen