Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. One more silly editor question...

One more silly editor question...

Scheduled Pinned Locked Moved The Lounge
question
6 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Lost User
    wrote on last edited by
    #1

    OK, I use this often - place cursor on the right side of the "{" and click on it... most (!) often the editor highlights the content covered until the "}"... fine how about something like that to cover the text between #ifdef ... #endif Thanks

    J L 2 Replies Last reply
    0
    • L Lost User

      OK, I use this often - place cursor on the right side of the "{" and click on it... most (!) often the editor highlights the content covered until the "}"... fine how about something like that to cover the text between #ifdef ... #endif Thanks

      J Offline
      J Offline
      jeron1
      wrote on last edited by
      #2

      If you are referring to an editor on CP, maybe Bugs and Suggestions[^] would be a better place to post.

      "the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle

      1 Reply Last reply
      0
      • L Lost User

        OK, I use this often - place cursor on the right side of the "{" and click on it... most (!) often the editor highlights the content covered until the "}"... fine how about something like that to cover the text between #ifdef ... #endif Thanks

        L Offline
        L Offline
        Lost User
        wrote on last edited by
        #3

        Visual Studio will highlight all connected #if, #elif, #else, #endif, when you click in one of them, but it does not appear to have a similar jump feature. Visual Studio Code the same. [edit] I was wrong, see Daniel Pfeffer's reply below. [/edit]

        J D 2 Replies Last reply
        0
        • L Lost User

          Visual Studio will highlight all connected #if, #elif, #else, #endif, when you click in one of them, but it does not appear to have a similar jump feature. Visual Studio Code the same. [edit] I was wrong, see Daniel Pfeffer's reply below. [/edit]

          J Offline
          J Offline
          jmaida
          wrote on last edited by
          #4

          codeblocks does something similar i use these regularly to handle small versions of code

          "A little time, a little trouble, your better day" Badfinger

          1 Reply Last reply
          0
          • L Lost User

            Visual Studio will highlight all connected #if, #elif, #else, #endif, when you click in one of them, but it does not appear to have a similar jump feature. Visual Studio Code the same. [edit] I was wrong, see Daniel Pfeffer's reply below. [/edit]

            D Offline
            D Offline
            Daniel Pfeffer
            wrote on last edited by
            #5

            In Visual Studio, place the cursor on an #if, #ifdef, #elif, #else, or #endif and type ctrl-}. This will move between the connected directives. I don't know about Visual Studio Code.

            Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

            L 1 Reply Last reply
            0
            • D Daniel Pfeffer

              In Visual Studio, place the cursor on an #if, #ifdef, #elif, #else, or #endif and type ctrl-}. This will move between the connected directives. I don't know about Visual Studio Code.

              Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

              L Offline
              L Offline
              Lost User
              wrote on last edited by
              #6

              Thanks Daniel, I was sure I tried that yesterday and it did not work. I must have used the wrong key.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups