6 ms·

Weird, I love the font size and the font in general. I use it everyday and it's way, way better than the normal powershell terminal.

oefrha 7y ago
What I meant is that changing any setting at all is a great pain at the moment.
- nicoburns 7y ago
  I mean, quite a few apps aimed at developers do this. Sublime Text for example. I can't imagine many people who aren't comfortable editing a text file would be using a terminal.
  - oefrha 7y ago
    At least with Sublime Text the configuration file would be opened in the app itself, not goddamn Visual Studio. Also, can do is one thing, likes to do (learning a JSON schema to change the font size) is something else. Oh, and tons of people use a terminal under guidance when they need to accomplish something that’s otherwise difficult or impossible.
    - qayxc 7y ago
      The configuration file opens in whatever app is associated with the format. If you associated JSON files with VS then that's specific to your personal setup and unrelated to the Terminal app. You also don't need to learn JSON schema and - I'm sorry to say this - but if editing a well-documented text format is too much of a hurdle to you, then maybe you're simply not the target demographic for the app. The tons of people who blindly use copy-pasta wouldn't even need to use the Terminal app (a tool explicitly aimed at power users and devs), so that's a non-argument to start with.
      - oefrha 7y ago
        Thanks for labeling me a noob while I have been editing text configs for a decade and a half. Again, passable != good, and there’s hardly any defense for a GUI application putting all common settings in a text configuration, especially when you need to configure colors, fonts, etc. I’m pretty sure the terminal app was advertised as the next generation console experience for Windows, which means it is going to replace cmd, and will be used by non-power users. Re binding: that’s just the default when VS is installed. Also, whether it’s Visual Studio is irrelevant, what’s relevant is it definitely isn’t Windows Terminal. Edit: By replacing cmd I probably meant replacing conhost or something. Not completely sure about Windows separation of shells and terminal emulators but the idea should be clear.
        s9w 7y ago
        People who use a terminal know how to edit a json file. That approach has good tradition by now with Sublime etc, see the poster above. And I'm pretty sure VS doesn't auto-associate itself with json files. They handled this in the best way possible imo.
        oefrha 7y ago
        Last time I’m gonna say this: configuring fonts, colors, etc. is possible with a text file, doesn’t mean it’s any good.
        s9w 7y ago
        That's up to opinion. I just wanted to join in to voice another opinion since some people in MS have recently been on a "even a single opinion is enough to act" policy (see VS Santa hat debacle), which I'm trying to prevent.
        qayxc 7y ago
        > I’m pretty sure the terminal app was advertised as the next generation console experience for Windows, which means it is going to replace cmd, and will be used by non-power users. I'd love to hear a legit day-to-day use case, though. I'm honestly very curious to hear about that since even as a developer, I pretty much never use the command line (outside of WSL, which I don't consider a typical use-case either).

oefrha 7y ago

What I meant is that changing any setting at all is a great pain at the moment.

nicoburns 7y ago
I mean, quite a few apps aimed at developers do this. Sublime Text for example. I can't imagine many people who aren't comfortable editing a text file would be using a terminal.
- oefrha 7y ago
  At least with Sublime Text the configuration file would be opened in the app itself, not goddamn Visual Studio. Also, can do is one thing, likes to do (learning a JSON schema to change the font size) is something else. Oh, and tons of people use a terminal under guidance when they need to accomplish something that’s otherwise difficult or impossible.
  - qayxc 7y ago
    The configuration file opens in whatever app is associated with the format. If you associated JSON files with VS then that's specific to your personal setup and unrelated to the Terminal app. You also don't need to learn JSON schema and - I'm sorry to say this - but if editing a well-documented text format is too much of a hurdle to you, then maybe you're simply not the target demographic for the app. The tons of people who blindly use copy-pasta wouldn't even need to use the Terminal app (a tool explicitly aimed at power users and devs), so that's a non-argument to start with.
    - oefrha 7y ago
      Thanks for labeling me a noob while I have been editing text configs for a decade and a half. Again, passable != good, and there’s hardly any defense for a GUI application putting all common settings in a text configuration, especially when you need to configure colors, fonts, etc. I’m pretty sure the terminal app was advertised as the next generation console experience for Windows, which means it is going to replace cmd, and will be used by non-power users. Re binding: that’s just the default when VS is installed. Also, whether it’s Visual Studio is irrelevant, what’s relevant is it definitely isn’t Windows Terminal. Edit: By replacing cmd I probably meant replacing conhost or something. Not completely sure about Windows separation of shells and terminal emulators but the idea should be clear.
      - s9w 7y ago
        People who use a terminal know how to edit a json file. That approach has good tradition by now with Sublime etc, see the poster above. And I'm pretty sure VS doesn't auto-associate itself with json files. They handled this in the best way possible imo.
        oefrha 7y ago
        Last time I’m gonna say this: configuring fonts, colors, etc. is possible with a text file, doesn’t mean it’s any good.
        s9w 7y ago
        That's up to opinion. I just wanted to join in to voice another opinion since some people in MS have recently been on a "even a single opinion is enough to act" policy (see VS Santa hat debacle), which I'm trying to prevent.
      - qayxc 7y ago
        > I’m pretty sure the terminal app was advertised as the next generation console experience for Windows, which means it is going to replace cmd, and will be used by non-power users. I'd love to hear a legit day-to-day use case, though. I'm honestly very curious to hear about that since even as a developer, I pretty much never use the command line (outside of WSL, which I don't consider a typical use-case either).