this post was submitted on 03 Feb 2024
988 points (98.3% liked)

linuxmemes

21222 readers
141 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] zalgotext@sh.itjust.works 18 points 9 months ago

    One particular pain for me in VSCode is that it puts a .vscode folder in my repo, which I have to specifically exclude from git every single time.

    That's pretty standard behavior for IDEs. Like Jetbrains IDEs store their config in a .idea folder in the root of the workspace, Visual Studio has a config directory in the root of the workspace, xcode probably does the same thing... It's standard practice, and a simple thing to account for - as you said, just add it to your .gitignore and you're golden. That allows people to use whatever IDE they want and configure it however they like.