Live data from Hacker News

JetBrains IDE new Terminal Interface

blog.jetbrains.com

11–20 of 102 posts

Re: JetBrains IDE new Terminal Interface

#12
post #3

I like the visual blocking of each command. Cool idea I haven't seen in other terminals.

Apple's Terminal.app had similar functionality for a while: CMD+Up/Down to navigate between past commands and quick selection of command outputs.

Other terminals, like iTerm (MacOS only), Kitty, WezTerm and so on also have similar options, usually behind some sort of "shell integrations" feature.

Re: JetBrains IDE new Terminal Interface

#14

Not available in the "old" UI? Guess this is the beginning of the end.

You can switch between the old and new terminal in Settings/Preferences | Tools | Terminal | Enable New Terminal. I'm not what are you referring to?

> The new terminal (Beta) is now in JetBrains IDEs and will be available in the new UI

JetBrains IDEs are in a transition state right now where they have both a “New UI” that’s minimal and a cheap knock off of VSCode to lure the kiddos in, and the original “IDE-feeling” UI that’s arguably much better for actual work. A sort of approach like Reddit still having new and old years later.

The wording implies the new terminal is only available in the new JetBrains UI and not the old UI

Re: JetBrains IDE new Terminal Interface

#15

> The primary visual distinction of the new terminal is that each command is now presented in a separate block Yeah, I'd better like it if they didn't do that. This adds even more visual clutter. > A new, convenient command history has been added, which allows for filtering and makes it easier to navigate through recently executed commands. Why is ^r not enough? Oh, wait, they blocked access to that. > We took full c…

You're free to turn it off, it's just an option.

I, for one, quite appreciate the redesign. Blocking ^r is too bad though, I tried the new terminal out a month or so ago, the redesign was nice and did feel optimized.

I ultimately switched back due to some issues with the autocompletion. I hope they've fixed these issues, things like makefiles would not autocomplete in this new terminal, while working fine in the 'old' terminal.

Re: JetBrains IDE new Terminal Interface

#16
I've had a lot of trouble with commands in Warp going haywire because of how much magic there is in creating visual blocks, and it looks like Jet Brains is taking it one step further. The reason terminals are great is because they are dumb, standard interfaces where you can have full access to any system, local or remote, and directly execute binaries and interact with a command language like bash or zsh.

I feel like this terminal is counterproductive. It adds visual niceties at the cost of dumbing down the power of the terminal and removing terminal feature that will be confusing to regular terminal users. It really doesn't have to be this complicated to be useful.

Re: JetBrains IDE new Terminal Interface

#18
post #2

That’s pretty cool. I wonder how JetBrains IDEs and VS Code manage to detect the installed shells (zsh, bash, PowerShell, etc.) in the first place since I certainly have no idea how to do it in either Java or JavaScript. Maybe they write platform-specific code?

On Windows I have no idea, but on Linux it seems easy enough:

   » cat /etc/shells
   # Pathnames of valid login shells.
   # See shells(5) for details.
   
   /bin/sh
   /bin/bash
   /usr/bin/git-shell
   /bin/zsh
   /usr/bin/zsh
   /bin/rbash
   /usr/bin/rbash
   /usr/bin/bash
   /usr/bin/sh

Re: JetBrains IDE new Terminal Interface

#19
I have always wanted a notebook style UI for terminal because I need to go back to what I learnt many times (say AWS CLI commands ...with syntax as well as output saved)

The visual separation of each command and output into block seems like a step in that direction?

Re: JetBrains IDE new Terminal Interface

#20
post #2

That’s pretty cool. I wonder how JetBrains IDEs and VS Code manage to detect the installed shells (zsh, bash, PowerShell, etc.) in the first place since I certainly have no idea how to do it in either Java or JavaScript. Maybe they write platform-specific code?

Trying to run it from its usual default path for each platform would be my guess.
Post reply on HN