unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean McLaughlin <seanmcl@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11026@debbugs.gnu.org
Subject: bug#11026: 23.3; call-process-region deletes unicode chars
Date: Fri, 16 Mar 2012 15:06:14 -0400	[thread overview]
Message-ID: <CAO4dZbeLhyP=oBN=U-ZWAQ9-Bbo7rtM2ZN1zUUwp4J_3EmRK+g@mail.gmail.com> (raw)
In-Reply-To: <CAO4dZbcaAV17dAxoLKHUWfppRndEv10rTEz5y7M==E+1GmPxww@mail.gmail.com>

For the record, the variable is called coding-system-for-write.

2012/3/16 Sean McLaughlin <seanmcl@gmail.com>:
> I apologize.  I thought it was a bug because when I write the buffer
> to a file and use call-process it works.
>
> Thank you for your time.  I'll try to close the bug.
>
> Sean
>
> On Fri, Mar 16, 2012 at 2:57 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> From: Sean McLaughlin <seanmcl@gmail.com>
>>> Date: Fri, 16 Mar 2012 12:07:55 -0400
>>>
>>> Create a buffer called 'bug' with multi-byte chars.  For example, with
>>> the contents
>>>
>>> Alpha = α
>>>
>>> Run (call-process-region (point-min) (point-max) "cat" t t) in that
>>> buffer.  It deletes the non-ascii unicode chars and leaves everything
>>> else intact.
>>
>> This is not a bug, but a cockpit error.
>>
>> You need to bind coding-process-for-write to something sensible, like
>> utf-8.  Otherwise, `cat' will get unpredictable sequence of bytes
>> instead of the Unicode character, and will respond with another
>> unpredictable sequence.
>>
>> I think this bug report should be closed.





  reply	other threads:[~2012-03-16 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 16:07 bug#11026: 23.3; call-process-region deletes unicode chars Sean McLaughlin
2012-03-16 18:57 ` Eli Zaretskii
2012-03-16 19:03   ` Sean McLaughlin
2012-03-16 19:06     ` Sean McLaughlin [this message]
2012-03-17 22:19       ` Stefan Monnier

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='CAO4dZbeLhyP=oBN=U-ZWAQ9-Bbo7rtM2ZN1zUUwp4J_3EmRK+g@mail.gmail.com' \
    --to=seanmcl@gmail.com \
    --cc=11026@debbugs.gnu.org \
    --cc=eliz@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).