ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Looking at Atom and VS Code

    IT Discussion
    5
    26
    1.2k
    Loading More Posts
    • 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.
    • stacksofplatesS
      stacksofplates
      last edited by stacksofplates

      line.gif

      snaps back to the correct place in Vim mode :man_shrugging:

      ObsolesceO 1 Reply Last reply Reply Quote 0
      • ObsolesceO
        Obsolesce @stacksofplates
        last edited by

        @stacksofplates said in Looking at Atom and VS Code:

        @Pete-S said in Looking at Atom and VS Code:

        @stacksofplates said in Looking at Atom and VS Code:

        As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.

        https://github.com/microsoft/vscode/issues/34457

        Great thanks. Too bad it's not just a simple setting.

        Having the settings in JSON like that is nice because it's easy to back up. There's an extension that syncas all of your extensions and settings to a gist in GitHub.

        I still use VSCode a good bit but most of my stuff is done in JetBrains tools now.

        Sync is built in to VSCode for a bit now.

        stacksofplatesS 1 Reply Last reply Reply Quote 0
        • ObsolesceO
          Obsolesce @stacksofplates
          last edited by Obsolesce

          @stacksofplates said in Looking at Atom and VS Code:

          line.gif

          snaps back to the correct place in Vim mode :man_shrugging:

          It does by default.

          I've never come across a need for virtual space. If I don't have anything written on a line, I wouldn't need a line comment there?

          I've always used comment blocks or comments above.

          I don't like when comments are on the same line as your code, following the code. It's just so messy looking, and from what I've seen, is not best practice.

          stacksofplatesS 1 2 Replies Last reply Reply Quote 0
          • stacksofplatesS
            stacksofplates @Obsolesce
            last edited by

            @Obsolesce said in Looking at Atom and VS Code:

            I've never come across a need for virtual space. If I don't have anything written on a line, I wouldn't need a line comment there?

            I just tried it in GoLand and I don't like it. If I'm going to a line it's usually so I can edit that line. It's uncomfortable to not jump to the actual data on the line.

            1 Reply Last reply Reply Quote 0
            • stacksofplatesS
              stacksofplates @Obsolesce
              last edited by

              @Obsolesce said in Looking at Atom and VS Code:

              @stacksofplates said in Looking at Atom and VS Code:

              @Pete-S said in Looking at Atom and VS Code:

              @stacksofplates said in Looking at Atom and VS Code:

              As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.

              https://github.com/microsoft/vscode/issues/34457

              Great thanks. Too bad it's not just a simple setting.

              Having the settings in JSON like that is nice because it's easy to back up. There's an extension that syncas all of your extensions and settings to a gist in GitHub.

              I still use VSCode a good bit but most of my stuff is done in JetBrains tools now.

              Sync is built in to VSCode for a bit now.

              I haven't used it for a bit since I started using GoLand.

              1 Reply Last reply Reply Quote 0
              • 1
                1337 @Obsolesce
                last edited by

                @Obsolesce said in Looking at Atom and VS Code:

                I've never come across a need for virtual space. If I don't have anything written on a line, I wouldn't need a line comment there?

                It's not made specifically for comments, that just an example.
                It's really more about how the cursor moves in general.

                A good editor should be versatile enough to accommodate whatever people are used to and since VS Code and Atom unfortunately isn't versatile enough for my needs I have to look elsewhere.

                The question is what. I'd want something that has the editing options I need, is cross-platform, preferably open source and has good integration options.

                JetBrains IDEs looks good but are not open source.

                ObsolesceO stacksofplatesS 2 Replies Last reply Reply Quote 0
                • ObsolesceO
                  Obsolesce @1337
                  last edited by

                  @Pete-S said in Looking at Atom and VS Code:

                  VS Code and Atom unfortunately isn't versatile enough for my needs I have to look elsewhere.

                  Nothing wrong with finding the right one for your personal needs. G/l

                  1 Reply Last reply Reply Quote 1
                  • stacksofplatesS
                    stacksofplates @1337
                    last edited by

                    @Pete-S said in Looking at Atom and VS Code:

                    JetBrains IDEs looks good but are not open source.

                    PyCharm and IntelliJ IDEA are

                    1 Reply Last reply Reply Quote 1
                    • JaredBuschJ
                      JaredBusch
                      last edited by

                      I have been coding (full time developer) and scripting since 1995 and I have never once wanted a feature like that.

                      1 Reply Last reply Reply Quote 1
                      • gotwfG
                        gotwf @1337
                        last edited by gotwf

                        @Pete-S Nope. Don't sling code. That said, worked with lots of devs providing ops support. The extremely bright genius types that stand out and really had my respect, each technical team leads, were using one of:

                        • VS Code
                        • IntelliJ EDEA

                        And notably, they'd seem to swap back and forth from time to time. At least long enough to trial new features of new releases. Big Company was footing the tooling bill so cost was not a consideration for them. Ymmv.

                        1 Reply Last reply Reply Quote 1
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post