From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 2148@emacsbugs.donarmstrong.com
Subject: bug#2148: Re: In shell mode, comint-send-input seems to cut off at 254 characters
Date: Tue, 07 Apr 2009 00:48:39 -0400 [thread overview]
Message-ID: <87bpr9ul08.fsf@cyd.mit.edu> (raw)
> [in shell mode]
> /bin/tcsh -f
> set filec
> echo [very long line]
>
> I get the strange behaviour I described before.
>
> So, in /bin/tcsh, one of the things that 'set filec' turns on is to use
> control-D to show a list of what matches the prefix of the immediately
> preceding word.
>
> It appears that 'send_process(proc, buf, len, object)' in process.c will
> determine that it should send a maximum of 254 characters and will send
> '\004' at each 254 character interval.
>
> It still seems strange to me that emacs would have this behaviour. Is
> that really how it should be done? I wouldn't think that I would be the
> only user who would be using /bin/tcsh with 'set filec'.
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.
next reply other threads:[~2009-04-07 4:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 4:48 Chong Yidong [this message]
2009-04-07 14:09 ` bug#2148: In shell mode, comint-send-input seems to cut off at 254 characters 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
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=87bpr9ul08.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=2148@emacsbugs.donarmstrong.com \
--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 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).