unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: bug#1898 is in your domain
Date: Wed, 04 Feb 2009 15:14:23 +0900	[thread overview]
Message-ID: <E1LUb1j-0006aw-I7@etlken> (raw)
In-Reply-To: <E1LQUX3-00072y-Fi@fencepost.gnu.org> (message from Richard Stallman on Sat, 31 Jan 2009 01:44:35 -0500)

In article <E1LQUX3-00072y-Fi@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:

> Would you please investigate this bug, which is bug report  bug#1898?
> You are the expert on this code.

Ok.

---
Kenichi Handa
handa@m17n.org


> Content-Type: text/plain; charset=ISO-8859-15
> From: Richard M Stallman <rms@gnu.org>
> To: emacs-pretest-bug@gnu.org
> Subject: 23.0.60; choosing coding system
> bcc: rms-outgoing@gnu.org
> Reply-to: rms@gnu.org
> --text follows this line--
> When I visit the file losing.mbox in Pmail using C-u M-x pmail RET
> losing.mbox RET, then run M-x lynx (see code below), it asks me to
> specify the coding system.  When I type RET to choose the default,
> raw-text, it gives me this error:

>    select-safe-coding-system: Cancelled because the buffer was modified

> This only fails the first time.  If you type M-x lynx again, it works.
> However, if you type the . command which makes Pmail display the
> message, the next M-x lynx will fail again.  I did not report this
> before, because the problem was very inconvenient to reproduce in
> Rmail.  Reproducing it with Pmail is much easier because you can re-arm
> the bug with the . command.

> I tried to investigate a previous case of this, and found that the
> buffer was indeed marked as modified during the function that read the
> coding system name.  That was inside coding.c, which I do not
> understand, so I did not try to track it down.

> (The buffer text is not in fact changed.  I have no easy way
> to see if any text properties were changed.  But maybe this
> does not matter.)

> (defun lynx ()
>   (interactive)
>   (unless (re-search-backward "^From wget@gnu.org" nil t)
>     (goto-char (point-min)))
>   (save-excursion
>     (search-forward "/bin/sh")
>     (forward-line 3)
>     (let ((start (point)))
>       (search-forward "!EOF!")
>       (beginning-of-line)
>       (write-region start (point) "~/foo.html"))))

> Here's the mailbox, uuencoded.
[...]




  reply	other threads:[~2009-02-04  6:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31  6:44 bug#1898 is in your domain Richard Stallman
2009-02-04  6:14 ` Kenichi Handa [this message]
2009-02-04  7:51   ` Kenichi Handa

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LUb1j-0006aw-I7@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).