all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 12409@debbugs.gnu.org, "Fabián Ezequiel Gallina" <fabian@anue.biz>
Subject: bug#12409: 24.2.50; OS X Python completion leaks junk to inferior-python-mode buffer
Date: Mon, 8 Oct 2012 21:49:45 +0200	[thread overview]
Message-ID: <864920C4-FDBB-4AAB-8146-42CAAA3B3AEF@swipnet.se> (raw)
In-Reply-To: <jwvfw5oss0v.fsf-monnier+emacs@gnu.org>

Hello.

Python does not write them, using dtruss i see:

write_nocancel(0x1, "'aaaa;aaaaaa'\n\0", 0xE)		 

No \r in sight.

	Jan D.

8 okt 2012 kl. 21:07 skrev Stefan Monnier <monnier@iro.umontreal.ca>:

>> (format "\r?\n\\(?:%s\\|%s\\|%s\\)$" works.  It is a bad idea to use literal
>> ^M in files, so take Andreas advice and use \r.
> 
> BTW, could someone investigate into the cause of these ^M?
> IOW, we need to look at the actual bytes that Python sends to Emacs,
> then figure out why Emacs's EOL-conversion doesn't handle them (are
> the bytes wrong, or is the process's coding-system set incorrectly?).
> 
> 
>        Stefan






  reply	other threads:[~2012-10-08 19:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11  5:22 bug#12409: 24.2.50; OS X Python completion leaks junk to inferior-python-mode buffer Dan Davison
2012-09-12  8:09 ` martin rudalics
2012-10-07 18:05   ` Jan Djärv
2012-09-24 18:32 ` Fabián Ezequiel Gallina
2012-10-01  1:00 ` Fabián Ezequiel Gallina
2012-10-07 19:51 ` Fabián Ezequiel Gallina
2012-10-08  7:24   ` Jan Djärv
2012-10-08 14:07     ` Fabián Ezequiel Gallina
2012-10-08 16:44       ` Andreas Schwab
2012-10-08 18:46       ` Jan Djärv
2012-10-08 19:07         ` Stefan Monnier
2012-10-08 19:49           ` Jan Djärv [this message]
2012-10-08 21:57             ` Fabián Ezequiel Gallina

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=864920C4-FDBB-4AAB-8146-42CAAA3B3AEF@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=12409@debbugs.gnu.org \
    --cc=fabian@anue.biz \
    --cc=monnier@iro.umontreal.ca \
    /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.