Re: Matching long strings doesn't work




zwenneh@xxxxxxxxxxx wrote:
I'm working on a program that has a command line. Now the users of this
program have requested that we extend the command line to support
longer commands, ie go from 1024 to 16K characters.

Question - to what kind of system are you telneting? Are you certain
that 16k data strings are accepted?

The reason I ask is this. On most unix systems I've used, there is a
max number of characters that the input driver will accept - usually
around 1k or so - and, after that, the driver either blocks or tosses
the results.

To get around this, I typically have to turn off things like handling
of backspace, job control, etc. and just use the device in "raw" mode.

.



Relevant Pages

  • Re: Matching long strings doesnt work
    ... I'm sure UNIX is ... and then there's a thousand characters and it hangs. ... On most unix systems I've used, ... max number of characters that the input driver will accept - usually ...
    (comp.lang.tcl)
  • Re: Read a line under MS/Unix/Mac
    ... Unix systems, when opening a DOS ... characters are *not* removed from the stream when reading. ... endings as single newline characters. ...
    (comp.lang.c)
  • Re: Read a line under MS/Unix/Mac
    ... Unix systems, when opening a DOS EOL ... characters are *not* removed from the stream when reading. ... Unix systems don't recognize the sequence as ...
    (comp.lang.c)
  • Re: is there definition of "binary file" or "text file"
    ... to tie this into Janis and Joe's argument... ... text file can contain "control characters", ... non-ASCII characters. ... UNIX systems. ...
    (comp.unix.shell)
  • Re: Read a line under MS/Unix/Mac
    ... Unix systems, when opening a DOS EOL ... characters are *not* removed from the stream when reading. ... Unix systems don't recognize the sequence as ...
    (comp.lang.c)