Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: XEmacs Beta <xemacs-beta@xemacs.org>, ding@gnus.org
Subject: Re: [Bug: 21.5-b29] gnus can't send in 21.5.29 but in 21.4.22
Date: Wed, 21 Sep 2011 09:20:57 +0200	[thread overview]
Message-ID: <87y5xiqs2u.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87ty86bqwj.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 21 Sep 2011 10:55:24 +0900")

On Wed, Sep 21 2011, Stephen J. Turnbull wrote:

> Uwe Brauer writes:
>
>  > This is bizzare: I have install a no-gnus version which I
>  > use either with 21.4.22 Or 21.5.29.
>  > 
>  > I wanted to send a message with 2 PDF attachments. It worked
>  > fine in 21.4.22 but in 21.5.29 I obtained an error which I
>  > attach. Since it works in 21.4.22 I hesitate to send a bug
>  > report to the gnus list.
>
> Unfortunately, this isn't bizarre at all.  Both XEmacs 21.5 and Gnus
> use private space character sets internally for various purposes, and
> you contribute to that by using X-symbol, most likely.  There are only
> about 10 of them so it's a scarce resource.
>
> Please show us the output of M-x list-character-sets so we can see
> where the resource drain is coming from.
>
> Aidan may be able to help you with XEmacs's use since he implemented
> the JIT Unicode charset stuff, but IIRC he hard-coded it so there's
> probably nothing you can do by customizing a variable---it will need
> code changes.  It's more likely that a workaround can be found in Gnus
> IMO, but since XEmacs is more a platform than an application, IMHO it
> should be reserving private charsets for applications written in Emacs
> Lisp.  So I wouldn't be surprised if the Gnus folks take the position
> that this is an XEmacs 21.5 limitation, and put low priority on
> addressing it.

This problem came up before:
<http://thread.gmane.org/gmane.emacs.gnus.general/68154>.

There you may find a possible solution[1] or a workaround[2] there.  I
don't know why[1] hasn't been implemented.

,----[ http://thread.gmane.org/gmane.emacs.gnus.general/68154/focus=68185 ]
| Gnus should bind `coding-system-for-read' then to the value of
| `mm-binary-coding-system' that defaults to `binary'.  However,
| it seems to have been set to nil or `undecided':
`----

,----[ http://thread.gmane.org/gmane.emacs.gnus.general/68154/focus=68189 ]
| Cool, thanks!, this definitely helped me track down a work-around.
| I don't know what is actually causing the problem (It seems unique
| to me), but by adding the .pdf extension to the
| file-coding-system-alist for binary, it will successfully send files
| that were previously failing.
`----

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



       reply	other threads:[~2011-09-21  7:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877h53i7um.fsf@gilgamesch.quim.ucm.es>
     [not found] ` <87ty86bqwj.fsf@uwakimon.sk.tsukuba.ac.jp>
2011-09-21  7:20   ` Reiner Steib [this message]
2011-09-21 17:32     ` Lars Magne Ingebrigtsen
2011-09-22  1:59       ` Katsumi Yamaoka
2011-09-22  4:44         ` Katsumi Yamaoka
2011-09-22  6:50           ` Reiner Steib
2011-09-22 11:10             ` Katsumi Yamaoka
2011-09-22  9:39           ` Uwe Brauer
2011-09-26 19:19           ` Lars Magne Ingebrigtsen
2011-09-26 23:25             ` Katsumi Yamaoka

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=87y5xiqs2u.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=oub@mat.ucm.es \
    --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).