man does not work (too many arguments)












18















I get this an error when trying to run man on a Linux system:



$ LC_ALL=C man man

man: Too many arguments
Try 'man --help' or 'man --usage' for more information.


My man command doesn't seem to be an alias:



command -v man: /usr/bin/man 


What's going on?










share|improve this question









New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • What is the output of "alias man" or simply "alias"?

    – rbrtflr
    22 hours ago






  • 1





    Is your man an alias? Check with type man or command -v man.

    – Kusalananda
    22 hours ago






  • 1





    @jayooin It's setting the default locale to the standard C locale. There is nothing strange about that bit.

    – Kusalananda
    22 hours ago






  • 7





    I'm pretty sure this only made it to Hot Network Questions because the title is hilarious

    – jalalipop
    11 hours ago






  • 3





    Yes, let's sow confusion in interpersonal.SE :)

    – rackandboneman
    11 hours ago
















18















I get this an error when trying to run man on a Linux system:



$ LC_ALL=C man man

man: Too many arguments
Try 'man --help' or 'man --usage' for more information.


My man command doesn't seem to be an alias:



command -v man: /usr/bin/man 


What's going on?










share|improve this question









New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • What is the output of "alias man" or simply "alias"?

    – rbrtflr
    22 hours ago






  • 1





    Is your man an alias? Check with type man or command -v man.

    – Kusalananda
    22 hours ago






  • 1





    @jayooin It's setting the default locale to the standard C locale. There is nothing strange about that bit.

    – Kusalananda
    22 hours ago






  • 7





    I'm pretty sure this only made it to Hot Network Questions because the title is hilarious

    – jalalipop
    11 hours ago






  • 3





    Yes, let's sow confusion in interpersonal.SE :)

    – rackandboneman
    11 hours ago














18












18








18








I get this an error when trying to run man on a Linux system:



$ LC_ALL=C man man

man: Too many arguments
Try 'man --help' or 'man --usage' for more information.


My man command doesn't seem to be an alias:



command -v man: /usr/bin/man 


What's going on?










share|improve this question









New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I get this an error when trying to run man on a Linux system:



$ LC_ALL=C man man

man: Too many arguments
Try 'man --help' or 'man --usage' for more information.


My man command doesn't seem to be an alias:



command -v man: /usr/bin/man 


What's going on?







man






share|improve this question









New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 22 hours ago









terdon

129k32253428




129k32253428






New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 22 hours ago









NeedHelpNeedHelp

985




985




New contributor




NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






NeedHelp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • What is the output of "alias man" or simply "alias"?

    – rbrtflr
    22 hours ago






  • 1





    Is your man an alias? Check with type man or command -v man.

    – Kusalananda
    22 hours ago






  • 1





    @jayooin It's setting the default locale to the standard C locale. There is nothing strange about that bit.

    – Kusalananda
    22 hours ago






  • 7





    I'm pretty sure this only made it to Hot Network Questions because the title is hilarious

    – jalalipop
    11 hours ago






  • 3





    Yes, let's sow confusion in interpersonal.SE :)

    – rackandboneman
    11 hours ago



















  • What is the output of "alias man" or simply "alias"?

    – rbrtflr
    22 hours ago






  • 1





    Is your man an alias? Check with type man or command -v man.

    – Kusalananda
    22 hours ago






  • 1





    @jayooin It's setting the default locale to the standard C locale. There is nothing strange about that bit.

    – Kusalananda
    22 hours ago






  • 7





    I'm pretty sure this only made it to Hot Network Questions because the title is hilarious

    – jalalipop
    11 hours ago






  • 3





    Yes, let's sow confusion in interpersonal.SE :)

    – rackandboneman
    11 hours ago

















What is the output of "alias man" or simply "alias"?

– rbrtflr
22 hours ago





What is the output of "alias man" or simply "alias"?

– rbrtflr
22 hours ago




1




1





Is your man an alias? Check with type man or command -v man.

– Kusalananda
22 hours ago





Is your man an alias? Check with type man or command -v man.

– Kusalananda
22 hours ago




1




1





@jayooin It's setting the default locale to the standard C locale. There is nothing strange about that bit.

– Kusalananda
22 hours ago





@jayooin It's setting the default locale to the standard C locale. There is nothing strange about that bit.

– Kusalananda
22 hours ago




7




7





I'm pretty sure this only made it to Hot Network Questions because the title is hilarious

– jalalipop
11 hours ago





I'm pretty sure this only made it to Hot Network Questions because the title is hilarious

– jalalipop
11 hours ago




3




3





Yes, let's sow confusion in interpersonal.SE :)

– rackandboneman
11 hours ago





Yes, let's sow confusion in interpersonal.SE :)

– rackandboneman
11 hours ago










1 Answer
1






active

oldest

votes


















34














Check the existence of MANOPT variable.




MANOPT

If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format.




source



Example:



$ MANOPT='foo bar'
$ export MANOPT
$ man man
man: Too many arguments
Try 'man --help' or 'man --usage' for more information.
$


An obvious ad-hoc fix is to unset MANOPT. Then you should investigate where the variable came from.






share|improve this answer
























  • So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

    – wjandrea
    6 hours ago











  • @wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

    – mosvy
    2 hours ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});






NeedHelp is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495232%2fman-does-not-work-too-many-arguments%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









34














Check the existence of MANOPT variable.




MANOPT

If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format.




source



Example:



$ MANOPT='foo bar'
$ export MANOPT
$ man man
man: Too many arguments
Try 'man --help' or 'man --usage' for more information.
$


An obvious ad-hoc fix is to unset MANOPT. Then you should investigate where the variable came from.






share|improve this answer
























  • So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

    – wjandrea
    6 hours ago











  • @wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

    – mosvy
    2 hours ago
















34














Check the existence of MANOPT variable.




MANOPT

If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format.




source



Example:



$ MANOPT='foo bar'
$ export MANOPT
$ man man
man: Too many arguments
Try 'man --help' or 'man --usage' for more information.
$


An obvious ad-hoc fix is to unset MANOPT. Then you should investigate where the variable came from.






share|improve this answer
























  • So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

    – wjandrea
    6 hours ago











  • @wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

    – mosvy
    2 hours ago














34












34








34







Check the existence of MANOPT variable.




MANOPT

If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format.




source



Example:



$ MANOPT='foo bar'
$ export MANOPT
$ man man
man: Too many arguments
Try 'man --help' or 'man --usage' for more information.
$


An obvious ad-hoc fix is to unset MANOPT. Then you should investigate where the variable came from.






share|improve this answer













Check the existence of MANOPT variable.




MANOPT

If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format.




source



Example:



$ MANOPT='foo bar'
$ export MANOPT
$ man man
man: Too many arguments
Try 'man --help' or 'man --usage' for more information.
$


An obvious ad-hoc fix is to unset MANOPT. Then you should investigate where the variable came from.







share|improve this answer












share|improve this answer



share|improve this answer










answered 22 hours ago









Kamil MaciorowskiKamil Maciorowski

1,5191827




1,5191827













  • So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

    – wjandrea
    6 hours ago











  • @wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

    – mosvy
    2 hours ago



















  • So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

    – wjandrea
    6 hours ago











  • @wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

    – mosvy
    2 hours ago

















So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

– wjandrea
6 hours ago





So why is the error Too many arguments? Like if I export MANOPT=foo, why doesn't it say No manual entry for foo?

– wjandrea
6 hours ago













@wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

– mosvy
2 hours ago





@wjandrea man is probably splitting MANOPT on spaces and then running the resulting array through getopt(3), and complain if any non-option arguments (ie arguments not starting with a dash) are left. They could've used a better error message. Anyways, even a single argument is too much for it: try MANOPT=man man man.

– mosvy
2 hours ago










NeedHelp is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















NeedHelp is a new contributor. Be nice, and check out our Code of Conduct.













NeedHelp is a new contributor. Be nice, and check out our Code of Conduct.












NeedHelp is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495232%2fman-does-not-work-too-many-arguments%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Always On Availability groups resolving state after failover - Remote harden of transaction...

Restoring from pg_dump with foreign key constraints