* Bug reports on Gnus from Emacs trunk
@ 2010-10-05 3:52 Christoph
2010-10-05 7:40 ` Tassilo Horn
2010-10-05 16:18 ` Karl Fogel
0 siblings, 2 replies; 5+ messages in thread
From: Christoph @ 2010-10-05 3:52 UTC (permalink / raw)
To: emacs-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug reports on Gnus from Emacs trunk
2010-10-05 3:52 Bug reports on Gnus from Emacs trunk Christoph
@ 2010-10-05 7:40 ` Tassilo Horn
2010-10-05 11:45 ` Christoph
2010-10-05 16:18 ` Karl Fogel
1 sibling, 1 reply; 5+ messages in thread
From: Tassilo Horn @ 2010-10-05 7:40 UTC (permalink / raw)
To: Christoph; +Cc: emacs-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug reports on Gnus from Emacs trunk
2010-10-05 7:40 ` Tassilo Horn
@ 2010-10-05 11:45 ` Christoph
0 siblings, 0 replies; 5+ messages in thread
From: Christoph @ 2010-10-05 11:45 UTC (permalink / raw)
To: Tassilo Horn; +Cc: emacs-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug reports on Gnus from Emacs trunk
2010-10-05 3:52 Bug reports on Gnus from Emacs trunk Christoph
2010-10-05 7:40 ` Tassilo Horn
@ 2010-10-05 16:18 ` Karl Fogel
2010-10-05 16:58 ` Lars Magne Ingebrigtsen
1 sibling, 1 reply; 5+ messages in thread
From: Karl Fogel @ 2010-10-05 16:18 UTC (permalink / raw)
To: emacs-devel
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?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug reports on Gnus from Emacs trunk
2010-10-05 16:18 ` Karl Fogel
@ 2010-10-05 16:58 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 5+ messages in thread
From: Lars Magne Ingebrigtsen @ 2010-10-05 16:58 UTC (permalink / raw)
To: ding; +Cc: emacs-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-10-05 16:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-05 3:52 Bug reports on Gnus from Emacs trunk Christoph
2010-10-05 7:40 ` Tassilo Horn
2010-10-05 11:45 ` Christoph
2010-10-05 16:18 ` Karl Fogel
2010-10-05 16:58 ` Lars Magne Ingebrigtsen
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.