Live data from Hacker News

JetBrains IDE new Terminal Interface

blog.jetbrains.com

81–90 of 102 posts

Re: JetBrains IDE new Terminal Interface

#81
post #59

Earlier quoted context omitted.

> Maybe it’s because I almost exclusively use keyboard shortcuts? That's a reasonable suspicion, since my biggest gripe with the new UI is how it hides clear, text-based menus and labels behind more confusing icons.

Was there something in particular that you used often that was moved behind a confusing icon? I don’t really find myself digging through these menus often, instead using the action search for things I don’t know/map the keyboard shortcut to.

Yes, I genuinely just use the menus for anything I don't use often enough to map a keyboard shortcut to.

I find search dialogues to be annoying and counter to building intuitive memory for using an application. They're a "last resort" to me when the UI of a program is poorly made.

Re: JetBrains IDE new Terminal Interface

#82
post #22

Earlier quoted context omitted.

A more charitable take is that power-users are mostly hotkey users, so hiding the UI leaves more space for things that matter. That said (and with the understanding that I am, by nature, averse to changing my habits): I prefer the old UI by a long shot.

I use IntelliJ for ~10 years now, and when I read that they have a new UI, I expected the worst. But, to be honest, I fell in love on first sight (at least with the compact mode).

Compact mode is a must for me as well. When __new UI__ released for Android Studio, I didn't enable until they later rolled out the so called compact mode.

Re: JetBrains IDE new Terminal Interface

#83
post #79

Earlier quoted context omitted.

> At first glance, I love the idea of the prompt being in a static position, separated from the output. Surprised that this is the first time I've seen something like that. I effectively have that by sticking newlines into my PS1 variable. And, yes, it's because its easier to track when the prompt is always in the same place after every command.

Could you elaborate more? I'm having trouble visualizing what you mean.

> Could you elaborate more? I'm having trouble visualizing what you mean.

The standard prompt is PS1, which after every command, places the cursor at some point in the line that depends on the width of $PS1 contents.

By appending a newline to the existing PS1 variable, the cursor is always at the same point after every command - far left on the last line.

I did play with embedding the last command into the PS1 variable too, so that not only is the cursor at a constant position, but the line above it prints the last command too (!! or something like that)

Re: JetBrains IDE new Terminal Interface

#84
post #79

Earlier quoted context omitted.

Could you elaborate more? I'm having trouble visualizing what you mean.

> Could you elaborate more? I'm having trouble visualizing what you mean. The standard prompt is PS1, which after every command, places the cursor at some point in the line that depends on the width of $PS1 contents. By appending a newline to the existing PS1 variable, the cursor is always at the same point after every command - far left on the last line. I did play with embedding the last command into the PS1 variab…

I think the GGP is referring to how, in this new interface, the prompt is always pinned to the bottom even if you scroll the terminal - so you can scroll back through the output of, say, `rsync --help` to find what you need, without losing sight of the prompt pinned to the bottom.

Re: JetBrains IDE new Terminal Interface

#85
post #66

My Jetbrains software yearly subscription is the best value for money I pay for anything related to my work! Their software just improves my productivity out of sight. If you look at the prices for other subscriptions, then look at Jetbrains, you wonder, "How do they do it?" I guess they're just really good at software.

DataGrip is the best RDBMS client I've ever used, hands down. It's so far beyond the competition in my experience. Maybe something like SQL Server Management Studio is really great specifically for SQL Server, but DataGrip is fantastic. I wouldn't trust most SQL clients with a production connection honestly. Getting read only constraints and commitable changes in my SQL client is a no-brainer that most other clients…

I have to work with SQL Server and use DataGrip wherever possible, using SQL Server Management Studio only for the pieces DataGrip doesn't support (mostly running SSIS packages). My productivity really did jump when I switched to DataGrip.

Re: JetBrains IDE new Terminal Interface

#86
post #23

The problem with a lot of these tools is that they fight with the shell to provide the UX enhancements (the comments in this thread are littered with people commenting that this new terminal breaks basic feature X, Y or Z. Really what they should be doing is working with the existing command line primitives as a hook for their UX enhancements. I know those existing primitives are 50 years old and suck in a great many…

I'll keep an eye on your project. Are you planning to support tmux control mode like iTerm2 does?

Re: JetBrains IDE new Terminal Interface

#87
post #79

Earlier quoted context omitted.

Could you elaborate more? I'm having trouble visualizing what you mean.

> Could you elaborate more? I'm having trouble visualizing what you mean. The standard prompt is PS1, which after every command, places the cursor at some point in the line that depends on the width of $PS1 contents. By appending a newline to the existing PS1 variable, the cursor is always at the same point after every command - far left on the last line. I did play with embedding the last command into the PS1 variab…

Ah yeah, I do this too. The hostname and current working dir gets its own line, then on the line below I have my prompt sigil (% or $, depending on shell). What I meant was in the new Jetbrains IDE terminal, the prompt is pinned in a pane at the bottom of the window while you view your output doing its thing in the pane above.

Re: JetBrains IDE new Terminal Interface

#89
post #23

The problem with a lot of these tools is that they fight with the shell to provide the UX enhancements (the comments in this thread are littered with people commenting that this new terminal breaks basic feature X, Y or Z. Really what they should be doing is working with the existing command line primitives as a hook for their UX enhancements. I know those existing primitives are 50 years old and suck in a great many…

I'll keep an eye on your project. Are you planning to support tmux control mode like iTerm2 does?

I'm not planning on supporting split panes (though I'm sure that feature will eventually be written), instead relying on multiplexers like tmux to fill that gap for the time being. I don't really know enough about tmux's control mode to understand how I might integrate it but I, personally, didn't like iTerm2's integration much so if I did interface with tmux at a lower level then it might look somewhat different to iTerm2.

That all said, at this point in time I'm not discounting any ideas.

Re: JetBrains IDE new Terminal Interface

#90
post #81

Earlier quoted context omitted.

Was there something in particular that you used often that was moved behind a confusing icon? I don’t really find myself digging through these menus often, instead using the action search for things I don’t know/map the keyboard shortcut to.

Yes, I genuinely just use the menus for anything I don't use often enough to map a keyboard shortcut to. I find search dialogues to be annoying and counter to building intuitive memory for using an application. They're a "last resort" to me when the UI of a program is poorly made.

Makes sense! Don’t mean to do that annoying internet thing where I am saying you are wrong and I am right, just curious to hear more specifics about it, thanks!
Post reply on HN