all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: 55217@debbugs.gnu.org
Subject: bug#55217: 29.0.50; gnus: entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" " nnimap")
Date: Mon, 02 May 2022 10:34:31 +0200	[thread overview]
Message-ID: <87h7689vu0.fsf@gnus.org> (raw)
In-Reply-To: <87zgk0s849.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 02 May 2022 09:31:50 +0200")

Uwe Brauer <oub@mat.ucm.es> writes:

> I only upgrade GNU emacs to the below master. However when sending
> email, I now receive, from time to time (no recipe so far)
> the following error message
> ,----
> | Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" " nnimap")
> |   require(\ nnimap)
> |   gnus-get-function((\ nnimap "UCMgmail") server-opened)
> |   gnus-server-opened((\ nnimap "UCMgmail"))
> |   gnus-check-server((\ nnimap "UCMgmail"))
> |   gnus-inews-do-gcc()
> |   gnus-agent-possibly-do-gcc()

It sounds like it's parsing your Gcc header (or something in your Gcc
setup) badly -- it's including a space before "nnimap" in the symbol
it's trying to work with.

What does your Gcc header look like when you get these errors?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-02  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  7:31 bug#55217: 29.0.50; gnus: entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" " nnimap") Uwe Brauer
2022-05-02  8:34 ` Lars Ingebrigtsen [this message]
2022-05-02  9:24   ` Uwe Brauer
2022-05-02  9:37     ` Lars Ingebrigtsen
2022-05-02 12:23       ` Uwe Brauer
2022-05-03 10:08         ` Lars Ingebrigtsen
2022-05-03  5:53       ` Uwe Brauer

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=87h7689vu0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55217@debbugs.gnu.org \
    --cc=oub@mat.ucm.es \
    /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/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.