all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Tim Hesterberg <timh@insightful.com>
Cc: emacs-devel@gnu.org
Subject: Re: X-coding-system incompatibility, and workaround
Date: Fri, 09 Nov 2007 22:00:11 -0500	[thread overview]
Message-ID: <E1IqgZv-0003ZD-KS@fencepost.gnu.org> (raw)
In-Reply-To: <uhcjvme52.fsf@insightful.com> (message from Tim Hesterberg on Fri, 09 Nov 2007 11:07:21 -0800)

    When I create an rmail file using emacs 22.1.1, then read the
    file using emacs 21.3.1 (on another system), it generally works, but
    occasionally I'll run into a message causes a problem.

Can you provide a copy of a file that causes this problem?
(Please uuencode it before you send it.)

Can you post a *precise* test case for this bug?  The test case should
start with `emacs -q', so that your .emacs file does not affect it,
and it should show exactly what text to put in the buffer, what
commands to execute, so as to produce such a file.

    Could you modify future versions of emacs to try to avoid using
    coding systems that are not defined on earlier versions?

I don't know if this is possible.  To think about the question
we would need to figure out WHY it uses those coding systems.
That's why we need a test case, etc.

Please read the Bugs section in the Emacs manual, which provides
guidelines on how to write a bug report to give us the
necessary information so we can fix the bug.

  reply	other threads:[~2007-11-10  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 19:07 X-coding-system incompatibility, and workaround Tim Hesterberg
2007-11-10  3:00 ` Richard Stallman [this message]
2007-11-10 11:25   ` Eli Zaretskii
2007-11-11  5:21     ` Richard Stallman
2007-11-12 23:00     ` Tim Hesterberg
2007-11-13 20:02       ` Richard Stallman
2007-11-12 22:43   ` Tim Hesterberg

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=E1IqgZv-0003ZD-KS@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=timh@insightful.com \
    /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.