Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command length limited not documented #254

Closed
ole-tange opened this issue Jan 1, 2016 · 4 comments
Closed

Command length limited not documented #254

ole-tange opened this issue Jan 1, 2016 · 4 comments

Comments

@ole-tange
Copy link

@ole-tange ole-tange commented Jan 1, 2016

There is a limit on the length on the command. This limit should either be removed (preferred) or documented in the man page:

$ tmux1.8 new-session -d echo' '"`yes | head -c 2028`"
OK 
$ tmux1.8 new-session -d echo' '"`yes | head -c 2029`"
command too long

$ tmux1.9 new-session -d echo' '"`yes | head -c 16344`"
OK
$ tmux1.9 new-session -d echo' '"`yes | head -c 16345`"
failed to send command
@ThomasAdam
Copy link
Contributor

@ThomasAdam ThomasAdam commented Jan 1, 2016

I don't see this as a problem, and this is something most people shouldn't be hitting anyway.

@krader1961
Copy link

@krader1961 krader1961 commented Jan 1, 2016

I agree that this isn't a problem in practice. A 2KB command buffer should be more than enough. These are supposed to be commands a human would type interactively at a shell; not entire scripts. And removing the limit complicates the code and just shifts the problem. What happens when someone does something really stupid and attempts to send a "command" several hundred megabytes in length? Having said that it would be a good idea to document the limit; preferably with a rationale like the one I mentioned earlier.

@nicm
Copy link
Member

@nicm nicm commented Jan 15, 2016

I don't feel particularly strongly that this needs to be documented but if someone sends a change I'll look at it.

@nicm nicm closed this Jan 15, 2016
@lock
Copy link

@lock lock bot commented Feb 16, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants