Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Michael Baer <gnus@mikesoffice.com>
Cc: ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: Error sending attached files
Date: Sat, 17 Jan 2009 21:22:28 +0100	[thread overview]
Message-ID: <877i4tk7i3.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3r637lpm5.fsf@mikesoffice.com> (Michael Baer's message of "Mon, 12 Jan 2009 21:52:18 -0800")

Looks like a problem in XEmacs' `insert-file-contents-internal' to me.
Cc-ing xemacs-beta...

On Tue, Jan 13 2009, Michael Baer wrote:

> I've been having an error when sending attached files with gnus
> email that has been driving me crazy.  I was hoping someone on this
> list might have some insight into the problem.  It is somewhat
> inconsistent and seems to happen more often with pdf and MS Word
> files.  If it happens with a file, it won't send that file and will
> continue to fail on repeated tries.  Although, if I reopen and save
> a doc again with Openoffice or convert a pdf to something else, it
> often will send the new file.  I usually attach the file with
> mml-attach-file (C-c C-a), but when I try to send I get the error
> message below:
>
> Invalid operation: No more character sets free for this dimension, 1
>
> The error message is kind of amusing, but doesn't really make much
> sense to me in this context.
>
> I'm using a Fedora 9 on a PPC platform, and I was using the version
> of gnus that is standard on F9 (I forget what version gnus is, it's
> xemacs 21.5.28-6) but I switched to the source gnus-5.10.10 with no
> noticeable change in this error.
>
> The debug on error output is:
>
> Debugger entered--Lisp error: (invalid-operation "No more character sets free for this dimension" 1)
>   insert-file-contents-internal("~/wtemp/scan/temp.pdf" nil nil nil
>     nil undecided used-codesys) 
>   byte-code("..." [buffer-file-coding-system-for-read
>     coding-system-for-read return-val visit filename coding-system
>     run-hook-with-args insert-file-contents-access-hook
>     run-hook-with-args-until-success insert-file-contents-pre-hook
>     find-file-coding-system-for-read-from-filename raw-text
>     find-coding-system lwarn notice "Invalid coding-system (%s), using
>     'undecided" undecided insert-file-contents-internal used-codesys
>     start end replace] 9)
>   insert-file-contents("~/wtemp/scan/temp.pdf" nil nil nil nil)
>   mm-insert-file-contents("~/wtemp/scan/temp.pdf" nil nil nil nil t)
[...]
>   mml-generate-mime()
>   message-encode-message-body()
>   message-send-mail(nil)
>   message-send-via-mail(nil)
>   message-send(nil)
>   message-send-and-exit(nil)
>   call-interactively(message-send-and-exit)
>
> It's not making much sens to me, but any suggestions would
> definitely be appreciated,

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2009-01-17 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  5:52 Michael Baer
2009-01-17 20:22 ` Reiner Steib [this message]
2009-01-18 10:58   ` Aidan Kehoe
2009-01-19  2:28     ` Katsumi Yamaoka
2009-01-20  6:16       ` Michael Baer

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=877i4tk7i3.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=gnus@mikesoffice.com \
    --cc=xemacs-beta@xemacs.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).