more command returns “Too many arguments in command line”

I have a Windows 10 machine where running the more command returns "Too many arguments in command line." if I pass any filename, whether the file exists or not.

So far I've only seen this on one Windows 10 Home 64-bit x64 system.

Running where more returns C:WindowsSystem32more.com as I would expect.

Is this behavior of more expected? I've never encountered this on previous versions of Windows.

edited Oct 27 '18 at 3:28

asked Oct 26 '18 at 20:39

MrEricSir

1345

1

Certainly not expected. more cowbell correctly displays the file cowbell on my Windows 10 Pro 64-bit system.

– dave
Oct 26 '18 at 22:09

please include a paste from the command line showing this

– barlop
Oct 27 '18 at 3:36

According to ms docs (docs.microsoft.com/en-us/windows-server/administration/…) you need to add > after more if you use it without flags, have you tried so?

– Máté Juhász
Oct 27 '18 at 4:37

add a comment |

I have a Windows 10 machine where running the more command returns "Too many arguments in command line." if I pass any filename, whether the file exists or not.

So far I've only seen this on one Windows 10 Home 64-bit x64 system.

Running where more returns C:WindowsSystem32more.com as I would expect.

Is this behavior of more expected? I've never encountered this on previous versions of Windows.

edited Oct 27 '18 at 3:28

asked Oct 26 '18 at 20:39

MrEricSir

1345

1

Certainly not expected. more cowbell correctly displays the file cowbell on my Windows 10 Pro 64-bit system.

– dave
Oct 26 '18 at 22:09

please include a paste from the command line showing this

– barlop
Oct 27 '18 at 3:36

According to ms docs (docs.microsoft.com/en-us/windows-server/administration/…) you need to add > after more if you use it without flags, have you tried so?

– Máté Juhász
Oct 27 '18 at 4:37

add a comment |

I have a Windows 10 machine where running the more command returns "Too many arguments in command line." if I pass any filename, whether the file exists or not.

So far I've only seen this on one Windows 10 Home 64-bit x64 system.

Running where more returns C:WindowsSystem32more.com as I would expect.

Is this behavior of more expected? I've never encountered this on previous versions of Windows.

edited Oct 27 '18 at 3:28

asked Oct 26 '18 at 20:39

MrEricSir

1345

I have a Windows 10 machine where running the more command returns "Too many arguments in command line." if I pass any filename, whether the file exists or not.

So far I've only seen this on one Windows 10 Home 64-bit x64 system.

Running where more returns C:WindowsSystem32more.com as I would expect.

Is this behavior of more expected? I've never encountered this on previous versions of Windows.

windows

edited Oct 27 '18 at 3:28

asked Oct 26 '18 at 20:39

MrEricSir

1345

edited Oct 27 '18 at 3:28

asked Oct 26 '18 at 20:39

MrEricSir

1345

edited Oct 27 '18 at 3:28

asked Oct 26 '18 at 20:39

MrEricSir

1345

asked Oct 26 '18 at 20:39

MrEricSir

1345

asked Oct 26 '18 at 20:39

MrEricSir

1345

1

Certainly not expected. more cowbell correctly displays the file cowbell on my Windows 10 Pro 64-bit system.

– dave
Oct 26 '18 at 22:09

please include a paste from the command line showing this

– barlop
Oct 27 '18 at 3:36

According to ms docs (docs.microsoft.com/en-us/windows-server/administration/…) you need to add > after more if you use it without flags, have you tried so?

– Máté Juhász
Oct 27 '18 at 4:37

add a comment |

1

Certainly not expected. more cowbell correctly displays the file cowbell on my Windows 10 Pro 64-bit system.

– dave
Oct 26 '18 at 22:09

please include a paste from the command line showing this

– barlop
Oct 27 '18 at 3:36

According to ms docs (docs.microsoft.com/en-us/windows-server/administration/…) you need to add > after more if you use it without flags, have you tried so?

– Máté Juhász
Oct 27 '18 at 4:37

Certainly not expected. more cowbell correctly displays the file cowbell on my Windows 10 Pro 64-bit system.

– dave
Oct 26 '18 at 22:09

please include a paste from the command line showing this

– barlop
Oct 27 '18 at 3:36

According to ms docs (docs.microsoft.com/en-us/windows-server/administration/…) you need to add > after more if you use it without flags, have you tried so?

– Máté Juhász
Oct 27 '18 at 4:37

add a comment |

3 Answers
3

active

oldest

votes

I just reproduced your problem on my own system. I definitely see what you're talking about... but I never noticed it before, because I always use more following a pipe (|), like this:

type filename.txt | more

That command works just fine on my system.

edited Oct 26 '18 at 20:58

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

add a comment |

I can reproduce this, too, on Windows 10 Enterprise (version 1803, build 17134.407). I can confirm Joel Coehoorn's and MrEricSir's solutions work. FWIW, I liked the /E option because it made more behave more like the UNIX flavor.

My solution was to use input redirection:

more < cowbell.txt

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

add a comment |

I can't find this documented anywhere but I found a workaround. In this particular case more works as expected if extended features are enabled with the /E flag.

For example, the following will display example.txt:

more /E example.txt

edited Jan 9 at 5:09

answered Oct 26 '18 at 20:39

MrEricSir

1345

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1370353%2fmore-command-returns-too-many-arguments-in-command-line%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

I just reproduced your problem on my own system. I definitely see what you're talking about... but I never noticed it before, because I always use more following a pipe (|), like this:

type filename.txt | more

That command works just fine on my system.

edited Oct 26 '18 at 20:58

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

add a comment |

I just reproduced your problem on my own system. I definitely see what you're talking about... but I never noticed it before, because I always use more following a pipe (|), like this:

type filename.txt | more

That command works just fine on my system.

edited Oct 26 '18 at 20:58

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

add a comment |

I just reproduced your problem on my own system. I definitely see what you're talking about... but I never noticed it before, because I always use more following a pipe (|), like this:

type filename.txt | more

That command works just fine on my system.

edited Oct 26 '18 at 20:58

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

I just reproduced your problem on my own system. I definitely see what you're talking about... but I never noticed it before, because I always use more following a pipe (|), like this:

type filename.txt | more

That command works just fine on my system.

edited Oct 26 '18 at 20:58

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

edited Oct 26 '18 at 20:58

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

answered Oct 26 '18 at 20:44

Joel Coehoorn

24.2k971119

add a comment |

My solution was to use input redirection:

more < cowbell.txt

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

add a comment |

My solution was to use input redirection:

more < cowbell.txt

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

add a comment |

My solution was to use input redirection:

more < cowbell.txt

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

My solution was to use input redirection:

more < cowbell.txt

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

answered Dec 29 '18 at 15:46

Armadillo Jim

1213

add a comment |

I can't find this documented anywhere but I found a workaround. In this particular case more works as expected if extended features are enabled with the /E flag.

For example, the following will display example.txt:

more /E example.txt

edited Jan 9 at 5:09

answered Oct 26 '18 at 20:39

MrEricSir

1345

add a comment |

I can't find this documented anywhere but I found a workaround. In this particular case more works as expected if extended features are enabled with the /E flag.

For example, the following will display example.txt:

more /E example.txt

edited Jan 9 at 5:09

answered Oct 26 '18 at 20:39

MrEricSir

1345

add a comment |

I can't find this documented anywhere but I found a workaround. In this particular case more works as expected if extended features are enabled with the /E flag.

For example, the following will display example.txt:

more /E example.txt

edited Jan 9 at 5:09

answered Oct 26 '18 at 20:39

MrEricSir

1345

I can't find this documented anywhere but I found a workaround. In this particular case more works as expected if extended features are enabled with the /E flag.

For example, the following will display example.txt:

more /E example.txt

edited Jan 9 at 5:09

answered Oct 26 '18 at 20:39

MrEricSir

1345

edited Jan 9 at 5:09

answered Oct 26 '18 at 20:39

MrEricSir

1345

answered Oct 26 '18 at 20:39

MrEricSir

1345

answered Oct 26 '18 at 20:39

MrEricSir

1345

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Jtdylktuy