unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Addison-Wood <richard@wetafx.co.nz>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 2148@emacsbugs.donarmstrong.com
Subject: bug#2148: In shell mode, comint-send-input seems to cut off at 254 characters
Date: Mon, 09 Feb 2009 14:15:22 +1300	[thread overview]
Message-ID: <498F83AA.1000105@wetafx.co.nz> (raw)
In-Reply-To: <87zlgz7d3o.fsf@cyd.mit.edu>

I have more information about what is going on.

Can you see if you can reproduce it?

After opening a new shell buffer, I type:

/bin/tcsh -f

to get a tcsh shell without running custom start-up stuff.

Then, I type this:

set filec

to turn on tcsh's file completion mechanisms (since this is one of the 
settings that my start-up stuff does).

And then, when I type this:

echo 
_234567_10_234567_20_234567_30_234567_40_234567_50_234567_60_234567_70_234567_80_234567_90_23456_100_23456_110_23456_120_23456_130_23456_140_23456_150_23456_160_23456_170_23456_180_23456_190_23456_200_23456_210_23456_220_23456_230_23456_240_23456_250_23456_260

I get the strange behaviour I described before.

Alternatively, If I type this:

unset filec

I can enter that long line without a problem.

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'.







  reply	other threads:[~2009-02-09  1:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 16:18 bug#2148: In shell mode, comint-send-input seems to cut off at 254 characters Chong Yidong
2009-02-09  1:15 ` Richard Addison-Wood [this message]
2009-02-10  0:11   ` Richard M Stallman
  -- strict thread matches above, loose matches on Subject: below --
2009-04-07  4:48 bug#2148: " 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

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=498F83AA.1000105@wetafx.co.nz \
    --to=richard@wetafx.co.nz \
    --cc=2148@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /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).