unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan J Third <alan@idiocy.org>
To: Richard Addison-Wood <richard@wetafx.co.nz>
Cc: 2148@debbugs.gnu.org
Subject: bug#2148: Re: In shell mode, comint-send-input seems to cut off at 254 characters
Date: Wed, 13 Jan 2016 21:11:14 +0000	[thread overview]
Message-ID: <m2io2xyykt.fsf@galloway.idiocy.org> (raw)
In-Reply-To: <m2oacpyzjh.fsf@galloway.idiocy.org> (Alan J. Third's message of "Wed, 13 Jan 2016 20:50:26 +0000")

Alan J Third <alan@idiocy.org> writes:

> Alan J Third <alan@idiocy.org> writes:
>
>> Chong Yidong <cyd@stupidchicken.com> writes:
>>
>>> The ^D is sent in process.c:5781.  If we are splitting a string into
>>> chunks for sending to the process, Emacs puts in an EOF (C-d) to "force
>>> it through".
>>>
>>> I can't think of any fix, off the top of my head.  Stefan, can you?  If
>>> not, we could simply document this limitation in PROBLEMS.
>>
>> I can't replicate this in Emacs 25 (or Emacs 24.5) on OS X, and I can't find the code
>> described above in the source, or at least in send_process. Can someone
>> who knows their way around better than me please confirm whether the
>> offending code has been removed, please?
>
> OK, this code is no longer in Emacs. It was removed sometime in the life
> of Emacs 24:
>
> commit 2b0a91e78f83fb446cc38efb99399e83ad2cded3
> Author: Stefan Monnier <monnier@iro.umontreal.ca>
> Date:   Mon Apr 12 22:07:48 2010 -0400
>
>     Try to solve the problem of spurious EOF chars in long lines of text
>     sent to interactive subprocesses.
>     * sysdep.c (child_setup_tty): Do not enable ICANON any more.
>     (system_process_attributes): Remove unused var `ttotal'.
>     * process.c (send_process): Don't bother breaking long line with EOF
>     chars when talking to ttys any more.
>     (wait_reading_process_output): Output a warning when called in such
>     a way that it could block without being interruptible.
>
> So I believe we can close this bug.

Apologies, I think I closed this bug report without cc'ing you in. As
described above the behaviour you reported was removed some time ago. If
you're still experiencing it in a recent version of Emacs, please let me
know.

-- 
Alan Third





      reply	other threads:[~2016-01-13 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  4:48 bug#2148: Re: In shell mode, comint-send-input seems to cut off at 254 characters Chong Yidong
2009-04-07 14:09 ` bug#2148: " Stefan Monnier
2009-04-07 14:22   ` Chong Yidong
2009-04-07 15:47     ` Stefan Monnier
2009-04-08 18:33   ` Richard M Stallman
2009-02-02  3:20     ` Richard Addison-Wood
2014-10-19 14:18       ` Dorish Apira
2014-10-22  1:11         ` Alexis
2016-01-10 22:34 ` bug#2148: " Alan J Third
2016-01-11  3:48   ` Richard Stallman
2016-01-13 20:50   ` Alan J Third
2016-01-13 21:11     ` Alan J Third [this message]

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=m2io2xyykt.fsf@galloway.idiocy.org \
    --to=alan@idiocy.org \
    --cc=2148@debbugs.gnu.org \
    --cc=richard@wetafx.co.nz \
    /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).