Hi I fired up in the Group buffer G G then inserted the search string but I obtained What is the problem? Debugger entered--Lisp error: (wrong-type-argument listp gnus-search-run-query) eval((nnselect-function . gnus-search-run-query) t) gnus-summary-set-local-parameters("nnselect:nnselect-87mtsph6ap.fsf") gnus-summary-setup-buffer("nnselect:nnselect-87mtsph6ap.fsf") gnus-summary-read-group-1("nnselect:nnselect-87mtsph6ap.fsf" t t nil nil nil) gnus-summary-read-group("nnselect:nnselect-87mtsph6ap.fsf" t t nil nil nil nil) gnus-group-read-group(t t "nnselect:nnselect-87mtsph6ap.fsf" nil) gnus-group-read-ephemeral-group("nnselect-87mtsph6ap.fsf" (nnselect "nnselect") nil (#<buffer *Group*> . group) nil nil ((nnselect-specs (nnselect-function . gnus-search-run-query) (nnselect-args (search-query-spec (query . "Hoja 4") (raw)) (search-group-spec ("nnimap:UCMgmail" "nnimap+UCMgmail:INBOX")))) (nnselect-artlist))) gnus-group-read-ephemeral-search-group(nil) funcall-interactively(gnus-group-read-ephemeral-search-group nil) call-interactively(gnus-group-read-ephemeral-search-group nil nil) command-execute(gnus-group-read-ephemeral-search-group)
Uwe Brauer <oub@mat.ucm.es> writes:
> Hi
>
> I fired up in the Group buffer
>
> G G
>
> then inserted the search string but I obtained
>
> What is the problem?
>
> Debugger entered--Lisp error: (wrong-type-argument listp gnus-search-run-query)
> eval((nnselect-function . gnus-search-run-query) t)
> gnus-summary-set-local-parameters("nnselect:nnselect-87mtsph6ap.fsf")
That area of `gnus-summary-set-local-parameters' is wrapped in an
`ignore-errors':
(ignore-errors
(push (car elem) vars)
(if (boundp (car elem))
(set (make-local-variable (car elem)) (eval (nth 1 elem) t))
(eval (nth 1 elem) t)))
So I don't see how you're actually getting an error!
[-- Attachment #1: Type: text/plain, Size: 509 bytes --] > Uwe Brauer <oub@mat.ucm.es> writes: > That area of `gnus-summary-set-local-parameters' is wrapped in an > `ignore-errors': > (ignore-errors > (push (car elem) vars) > (if (boundp (car elem)) > (set (make-local-variable (car elem)) (eval (nth 1 elem) t)) > (eval (nth 1 elem) t))) > So I don't see how you're actually getting an error! I hate to ask this, but could it be the registry[1]?? Footnotes: [1] (I obtained a message that it is corrupt! BTW I think I know why that happens) [-- Attachment #2: smime.p7s --] [-- Type: application/pkcs7-signature, Size: 5673 bytes --]
Uwe Brauer <oub@mat.ucm.es> writes:
>> Uwe Brauer <oub@mat.ucm.es> writes:
>
>> That area of `gnus-summary-set-local-parameters' is wrapped in an
>> `ignore-errors':
>
>> (ignore-errors
>> (push (car elem) vars)
>> (if (boundp (car elem))
>> (set (make-local-variable (car elem)) (eval (nth 1 elem) t))
>> (eval (nth 1 elem) t)))
>
>> So I don't see how you're actually getting an error!
>
>
>
> I hate to ask this, but could it be the registry[1]??
No, I don't see how it could be. Wrapping `ignore-errors' around
something that raises an error should always swallow the error.
Eric Abrahamsen <eric@ericabrahamsen.net> writes: > No, I don't see how it could be. Wrapping `ignore-errors' around > something that raises an error should always swallow the error. Perhaps running with `debug-on-signal' switched on? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> No, I don't see how it could be. Wrapping `ignore-errors' around
>> something that raises an error should always swallow the error.
>
> Perhaps running with `debug-on-signal' switched on?
Huh, I wasn't aware of that. Seems unlikely in this case, but I
certainly can't think of anything else!
[-- Attachment #1: Type: text/plain, Size: 388 bytes --] >>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes: > Eric Abrahamsen <eric@ericabrahamsen.net> writes: >> No, I don't see how it could be. Wrapping `ignore-errors' around >> something that raises an error should always swallow the error. > Perhaps running with `debug-on-signal' switched on? Right this is what I used to obtain the bug trace, I should have added that information. [-- Attachment #2: smime.p7s --] [-- Type: application/pkcs7-signature, Size: 5673 bytes --]
[-- Attachment #1: Type: text/plain, Size: 570 bytes --] >>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes: > Lars Ingebrigtsen <larsi@gnus.org> writes: >> Eric Abrahamsen <eric@ericabrahamsen.net> writes: >> >>> No, I don't see how it could be. Wrapping `ignore-errors' around >>> something that raises an error should always swallow the error. >> >> Perhaps running with `debug-on-signal' switched on? > Huh, I wasn't aware of that. Seems unlikely in this case, but I > certainly can't think of anything else! Ok, so I was the culprit, but I still cannot search. Shall I submit a bug report? [-- Attachment #2: smime.p7s --] [-- Type: application/pkcs7-signature, Size: 5673 bytes --]
Uwe Brauer <oub@mat.ucm.es> writes:
>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>>> No, I don't see how it could be. Wrapping `ignore-errors' around
>>>> something that raises an error should always swallow the error.
>>>
>>> Perhaps running with `debug-on-signal' switched on?
>
>> Huh, I wasn't aware of that. Seems unlikely in this case, but I
>> certainly can't think of anything else!
>
>
> Ok, so I was the culprit, but I still cannot search. Shall I submit a
> bug report?
Yes, in this case the error you reported is probably totally unrelated
to whatever error you're experiencing: it's just an artifact of having
turned on "too much" debugging. If you're using an Emacs from the past
week or so it should be enough to `toggle-debug-on-error' and get a
backtrace. Otherwise you'll have to look in *Messages* and see if
there's a line formed like:
"nnselect-run: %s on %s gave error %s"