Ctrl + M + O shortcut to collapse all functions doesn't work in Visual Studio 2017









up vote
-1
down vote

favorite












This is for a C++ project



I used to be able to collapse all functions in my source code with Ctrl + M + O shortcut in VS 2015, but this doesn't work any longer in VS 2017.



Ctrl + M still works to collapse the current function



Can anyone help restore this useful functionality?










share|improve this question





















  • the <Strg+M, O> chord is usually mapped to "collapse to definitions", which does what you describe. it works in my VS2017 in a C++ solution, and it should according to documentation and this great reference. did you chose a non-standard developer profile when you first started after installation, or remap something via addins or the additional keyboard assignments in Options > Environment > Keyboard?
    – dlatikay
    Nov 9 at 22:24














up vote
-1
down vote

favorite












This is for a C++ project



I used to be able to collapse all functions in my source code with Ctrl + M + O shortcut in VS 2015, but this doesn't work any longer in VS 2017.



Ctrl + M still works to collapse the current function



Can anyone help restore this useful functionality?










share|improve this question





















  • the <Strg+M, O> chord is usually mapped to "collapse to definitions", which does what you describe. it works in my VS2017 in a C++ solution, and it should according to documentation and this great reference. did you chose a non-standard developer profile when you first started after installation, or remap something via addins or the additional keyboard assignments in Options > Environment > Keyboard?
    – dlatikay
    Nov 9 at 22:24












up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











This is for a C++ project



I used to be able to collapse all functions in my source code with Ctrl + M + O shortcut in VS 2015, but this doesn't work any longer in VS 2017.



Ctrl + M still works to collapse the current function



Can anyone help restore this useful functionality?










share|improve this question













This is for a C++ project



I used to be able to collapse all functions in my source code with Ctrl + M + O shortcut in VS 2015, but this doesn't work any longer in VS 2017.



Ctrl + M still works to collapse the current function



Can anyone help restore this useful functionality?







c++ windows visual-studio-2017






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 9 at 22:17









Mich

614631




614631











  • the <Strg+M, O> chord is usually mapped to "collapse to definitions", which does what you describe. it works in my VS2017 in a C++ solution, and it should according to documentation and this great reference. did you chose a non-standard developer profile when you first started after installation, or remap something via addins or the additional keyboard assignments in Options > Environment > Keyboard?
    – dlatikay
    Nov 9 at 22:24
















  • the <Strg+M, O> chord is usually mapped to "collapse to definitions", which does what you describe. it works in my VS2017 in a C++ solution, and it should according to documentation and this great reference. did you chose a non-standard developer profile when you first started after installation, or remap something via addins or the additional keyboard assignments in Options > Environment > Keyboard?
    – dlatikay
    Nov 9 at 22:24















the <Strg+M, O> chord is usually mapped to "collapse to definitions", which does what you describe. it works in my VS2017 in a C++ solution, and it should according to documentation and this great reference. did you chose a non-standard developer profile when you first started after installation, or remap something via addins or the additional keyboard assignments in Options > Environment > Keyboard?
– dlatikay
Nov 9 at 22:24




the <Strg+M, O> chord is usually mapped to "collapse to definitions", which does what you describe. it works in my VS2017 in a C++ solution, and it should according to documentation and this great reference. did you chose a non-standard developer profile when you first started after installation, or remap something via addins or the additional keyboard assignments in Options > Environment > Keyboard?
– dlatikay
Nov 9 at 22:24












1 Answer
1






active

oldest

votes

















up vote
0
down vote













In Visual Studio you can explore shortcuts using Tools | Options | Environment | Keyboard.



To see what CTRL+M, CTRL+O does, click on the "Press shortcut keys" box so the cursor is located within it and type CTRL+M, CTRL+O. The text box below will show what the shortcut is assigned to (if anything).



In the screenshot below you can see that my copy of Visual Studio 2017 has the shortcut assigned to Edit.CollapsetoDefinitions in the context of the Text Editor.



I left the context drop-down at "Global". But a shortcut may have different meanings in different contexts. You may need to change the drop-down to "Text Editor" to see the shortcut binding you are interested in.



Screenshot of Visual Studio Options | Environment | Keyboard - Shortcuts



To find out what shortcut (if any) is assigned to a command click on the "Show commands containing" box to locate the cursor within it and type the command (or part of it). Then select the command you are interested in from the shortlist offered.



In the screenshot below you can see that in my copy of Visual Studio 2017 there is only one command containing "CollapsetoDefinitions" and that command is assigned CTRL+M, CTRL+O.



Screenshot of Visual Studio Options | Environment | Keyboard - Show Commands



As suggested in the comments, your profile may have assigned a different meaning to CTRL+M, CTRL+O and/or may have assigned a different shortcut to Edit.CollapsetoDefinitions. You may get some idea of what caused the change by examining your own settings.



You might be able to change your copy of Visual Studio back to using standard settings by using Tools | Import and Export Settings | Reset all settings. But of course you risk losing other shortcuts and settings created by whatever changed your system.



If you choose to take this tack be sure to say "yes" when asked if you want to save your current settings before resetting. That way you can at least restore them if you decide resetting was a bad idea.



Alternatively, if CollapsetoDefinitions is assigned a different shortcut, you could decide to use that shortcut instead of CTRL+M, CTRL+O.



Or, if you don't care about losing the existing definition (if any) for CTRL+M, CTRL+O then you could use the Keyboard Options page to assign that shortcut back to CollapsetoDefinitions. If you choose this last option, you'll probably want to change the "Global" drop-down to "Text Editor" on the Keyboard Options page to limit the scope of your change.






share|improve this answer






















    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    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',
    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


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233975%2fctrl-m-o-shortcut-to-collapse-all-functions-doesnt-work-in-visual-studio-20%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








    up vote
    0
    down vote













    In Visual Studio you can explore shortcuts using Tools | Options | Environment | Keyboard.



    To see what CTRL+M, CTRL+O does, click on the "Press shortcut keys" box so the cursor is located within it and type CTRL+M, CTRL+O. The text box below will show what the shortcut is assigned to (if anything).



    In the screenshot below you can see that my copy of Visual Studio 2017 has the shortcut assigned to Edit.CollapsetoDefinitions in the context of the Text Editor.



    I left the context drop-down at "Global". But a shortcut may have different meanings in different contexts. You may need to change the drop-down to "Text Editor" to see the shortcut binding you are interested in.



    Screenshot of Visual Studio Options | Environment | Keyboard - Shortcuts



    To find out what shortcut (if any) is assigned to a command click on the "Show commands containing" box to locate the cursor within it and type the command (or part of it). Then select the command you are interested in from the shortlist offered.



    In the screenshot below you can see that in my copy of Visual Studio 2017 there is only one command containing "CollapsetoDefinitions" and that command is assigned CTRL+M, CTRL+O.



    Screenshot of Visual Studio Options | Environment | Keyboard - Show Commands



    As suggested in the comments, your profile may have assigned a different meaning to CTRL+M, CTRL+O and/or may have assigned a different shortcut to Edit.CollapsetoDefinitions. You may get some idea of what caused the change by examining your own settings.



    You might be able to change your copy of Visual Studio back to using standard settings by using Tools | Import and Export Settings | Reset all settings. But of course you risk losing other shortcuts and settings created by whatever changed your system.



    If you choose to take this tack be sure to say "yes" when asked if you want to save your current settings before resetting. That way you can at least restore them if you decide resetting was a bad idea.



    Alternatively, if CollapsetoDefinitions is assigned a different shortcut, you could decide to use that shortcut instead of CTRL+M, CTRL+O.



    Or, if you don't care about losing the existing definition (if any) for CTRL+M, CTRL+O then you could use the Keyboard Options page to assign that shortcut back to CollapsetoDefinitions. If you choose this last option, you'll probably want to change the "Global" drop-down to "Text Editor" on the Keyboard Options page to limit the scope of your change.






    share|improve this answer


























      up vote
      0
      down vote













      In Visual Studio you can explore shortcuts using Tools | Options | Environment | Keyboard.



      To see what CTRL+M, CTRL+O does, click on the "Press shortcut keys" box so the cursor is located within it and type CTRL+M, CTRL+O. The text box below will show what the shortcut is assigned to (if anything).



      In the screenshot below you can see that my copy of Visual Studio 2017 has the shortcut assigned to Edit.CollapsetoDefinitions in the context of the Text Editor.



      I left the context drop-down at "Global". But a shortcut may have different meanings in different contexts. You may need to change the drop-down to "Text Editor" to see the shortcut binding you are interested in.



      Screenshot of Visual Studio Options | Environment | Keyboard - Shortcuts



      To find out what shortcut (if any) is assigned to a command click on the "Show commands containing" box to locate the cursor within it and type the command (or part of it). Then select the command you are interested in from the shortlist offered.



      In the screenshot below you can see that in my copy of Visual Studio 2017 there is only one command containing "CollapsetoDefinitions" and that command is assigned CTRL+M, CTRL+O.



      Screenshot of Visual Studio Options | Environment | Keyboard - Show Commands



      As suggested in the comments, your profile may have assigned a different meaning to CTRL+M, CTRL+O and/or may have assigned a different shortcut to Edit.CollapsetoDefinitions. You may get some idea of what caused the change by examining your own settings.



      You might be able to change your copy of Visual Studio back to using standard settings by using Tools | Import and Export Settings | Reset all settings. But of course you risk losing other shortcuts and settings created by whatever changed your system.



      If you choose to take this tack be sure to say "yes" when asked if you want to save your current settings before resetting. That way you can at least restore them if you decide resetting was a bad idea.



      Alternatively, if CollapsetoDefinitions is assigned a different shortcut, you could decide to use that shortcut instead of CTRL+M, CTRL+O.



      Or, if you don't care about losing the existing definition (if any) for CTRL+M, CTRL+O then you could use the Keyboard Options page to assign that shortcut back to CollapsetoDefinitions. If you choose this last option, you'll probably want to change the "Global" drop-down to "Text Editor" on the Keyboard Options page to limit the scope of your change.






      share|improve this answer
























        up vote
        0
        down vote










        up vote
        0
        down vote









        In Visual Studio you can explore shortcuts using Tools | Options | Environment | Keyboard.



        To see what CTRL+M, CTRL+O does, click on the "Press shortcut keys" box so the cursor is located within it and type CTRL+M, CTRL+O. The text box below will show what the shortcut is assigned to (if anything).



        In the screenshot below you can see that my copy of Visual Studio 2017 has the shortcut assigned to Edit.CollapsetoDefinitions in the context of the Text Editor.



        I left the context drop-down at "Global". But a shortcut may have different meanings in different contexts. You may need to change the drop-down to "Text Editor" to see the shortcut binding you are interested in.



        Screenshot of Visual Studio Options | Environment | Keyboard - Shortcuts



        To find out what shortcut (if any) is assigned to a command click on the "Show commands containing" box to locate the cursor within it and type the command (or part of it). Then select the command you are interested in from the shortlist offered.



        In the screenshot below you can see that in my copy of Visual Studio 2017 there is only one command containing "CollapsetoDefinitions" and that command is assigned CTRL+M, CTRL+O.



        Screenshot of Visual Studio Options | Environment | Keyboard - Show Commands



        As suggested in the comments, your profile may have assigned a different meaning to CTRL+M, CTRL+O and/or may have assigned a different shortcut to Edit.CollapsetoDefinitions. You may get some idea of what caused the change by examining your own settings.



        You might be able to change your copy of Visual Studio back to using standard settings by using Tools | Import and Export Settings | Reset all settings. But of course you risk losing other shortcuts and settings created by whatever changed your system.



        If you choose to take this tack be sure to say "yes" when asked if you want to save your current settings before resetting. That way you can at least restore them if you decide resetting was a bad idea.



        Alternatively, if CollapsetoDefinitions is assigned a different shortcut, you could decide to use that shortcut instead of CTRL+M, CTRL+O.



        Or, if you don't care about losing the existing definition (if any) for CTRL+M, CTRL+O then you could use the Keyboard Options page to assign that shortcut back to CollapsetoDefinitions. If you choose this last option, you'll probably want to change the "Global" drop-down to "Text Editor" on the Keyboard Options page to limit the scope of your change.






        share|improve this answer














        In Visual Studio you can explore shortcuts using Tools | Options | Environment | Keyboard.



        To see what CTRL+M, CTRL+O does, click on the "Press shortcut keys" box so the cursor is located within it and type CTRL+M, CTRL+O. The text box below will show what the shortcut is assigned to (if anything).



        In the screenshot below you can see that my copy of Visual Studio 2017 has the shortcut assigned to Edit.CollapsetoDefinitions in the context of the Text Editor.



        I left the context drop-down at "Global". But a shortcut may have different meanings in different contexts. You may need to change the drop-down to "Text Editor" to see the shortcut binding you are interested in.



        Screenshot of Visual Studio Options | Environment | Keyboard - Shortcuts



        To find out what shortcut (if any) is assigned to a command click on the "Show commands containing" box to locate the cursor within it and type the command (or part of it). Then select the command you are interested in from the shortlist offered.



        In the screenshot below you can see that in my copy of Visual Studio 2017 there is only one command containing "CollapsetoDefinitions" and that command is assigned CTRL+M, CTRL+O.



        Screenshot of Visual Studio Options | Environment | Keyboard - Show Commands



        As suggested in the comments, your profile may have assigned a different meaning to CTRL+M, CTRL+O and/or may have assigned a different shortcut to Edit.CollapsetoDefinitions. You may get some idea of what caused the change by examining your own settings.



        You might be able to change your copy of Visual Studio back to using standard settings by using Tools | Import and Export Settings | Reset all settings. But of course you risk losing other shortcuts and settings created by whatever changed your system.



        If you choose to take this tack be sure to say "yes" when asked if you want to save your current settings before resetting. That way you can at least restore them if you decide resetting was a bad idea.



        Alternatively, if CollapsetoDefinitions is assigned a different shortcut, you could decide to use that shortcut instead of CTRL+M, CTRL+O.



        Or, if you don't care about losing the existing definition (if any) for CTRL+M, CTRL+O then you could use the Keyboard Options page to assign that shortcut back to CollapsetoDefinitions. If you choose this last option, you'll probably want to change the "Global" drop-down to "Text Editor" on the Keyboard Options page to limit the scope of your change.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 9 at 23:55

























        answered Nov 9 at 23:49









        Frank Boyne

        3,4271426




        3,4271426



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233975%2fctrl-m-o-shortcut-to-collapse-all-functions-doesnt-work-in-visual-studio-20%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

            How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

            Syphilis

            Darth Vader #20