Live data from Hacker News

Windows Terminal Quake Mode

github.com

81–90 of 91 posts

Re: Windows Terminal Quake Mode

#81

Earlier quoted context omitted.

Clink [ https://mridgers.github.io/clink/ ] adds this functionality and much more to good old fashioned command prompt (which I prefer to powershell because it's much faster and simpler)

That repo is extremely outdated. Here's the official(?) supercharged fork, which is actively developed - https://github.com/chrisant996/clink

Huh, I did wonder if there was an updated fork but I obviously didn't look hard enough. Thanks!

Re: Windows Terminal Quake Mode

#82
post #55

Earlier quoted context omitted.

Fuzzy history search like fzf does is in my experience quicker. And also works in Powershell.

Are you using PSFzf or something else? https://github.com/kelleyma49/PSFzf

I used to use PSFzf indeed: it's pretty good and got me started with fzf on PS, but the history reading nor file scanning are particularly fast so currently I'm using some C# code to do those and pipe it into fzf directly. Don't recall exactly but the most basic C# code I could come up with which does 'read history file in reverse and skip duplicates' was like 3 times faster than what PSFzf uses.

Re: Windows Terminal Quake Mode

#83
post #66
post #53

Earlier quoted context omitted.

> This is not to play Quake in WT, this allows WT to behave like the console window in Quake descendants that displays when [ ~] is pressed That's what they're saying.

Is someone having reading comprehension issues?

Is someone?

Re: Windows Terminal Quake Mode

#84
post #70
post #64

Earlier quoted context omitted.

Had been literally doing this first as a "poor man's" quake mode since moving away from ConEmu - pretty soon realised it was just enough for me. So I'd rather they find an elegant solution to UAC elevation.

Very curious as to why you moved away from ConEmu. Can you share the motivating factors? Anything to be concerned about?

I'm not the grandparent poster, but I notice ConEmu sometimes display my Linux terminal (connected via Cygwin's SSH) strangely after being resized, I would try to edit a file in Joe and trying to navigate would just update the 1st line of the console. I could scroll down in a less window but going up garbled the display...

Re: Windows Terminal Quake Mode

#85
post #60

Disregarding the geek and nostalgia factor. Why is this a feature of a specific application and not the WM? In fact it's almost already there. Just put your terminal as first item in the task list, then press Win+1 to summon a terminal and then Win+1 again to hide it. All existing window location and focus rules stay the same. What's missing?

> Why is this a feature of a specific application and not the WM?

Presumably because it's quicker or easier to implement this at the application layer rather than at the WM layer. Also, it makes the functionality available no matter which WM one is using, including ones that don't support this natively.

Re: Windows Terminal Quake Mode

#86
post #52

Earlier quoted context omitted.

AltDrag has been one of the first pieces of software I install on a Windows machine for years now. Such a time saver. As we're a little OT here, I might as well recommend you check out GridMove which moves windows to predefined positions on any of the screens with a press of a hotkey.

alt drag is something I picked up on Linux. I was delighted to find it for Windows several years ago, and the name made it really easy to find. Mac window management continues to infuriate me.

I can not recommend Contexts [1] and Rectangle [2] enough!

[1]: https://contexts.co/ [2]: https://rectangleapp.com/

Re: Windows Terminal Quake Mode

#87
post #83
post #66

Earlier quoted context omitted.

Is someone having reading comprehension issues?

Is someone?

The friendly article linked says:

> Many existing terminals support a feature whereby a user can press a keybinding anywhere in the OS, and summon their terminal application. [...] This global summon action is often referred to as "quake mode", a reference to the video game Quake, who's console slid in from the top.

The commenter I replied to said:

> This is not to play Quake in WT, this allows WT to behave like the console window in Quake descendants that displays when [ ~] is pressed.

The original article said nothing of the sort, even the part he quoted contradicted him, it was obvious that whoever wrote about this feature knew what "Quake mode" meant.

Then someone downvoted me for pointing that out.

Reading comprehension fail x2 ¯\_(ツ)_/¯

> Is someone?

Is anyone, really?

Re: Windows Terminal Quake Mode

#88
post #70
post #64

Earlier quoted context omitted.

Had been literally doing this first as a "poor man's" quake mode since moving away from ConEmu - pretty soon realised it was just enough for me. So I'd rather they find an elegant solution to UAC elevation.

Very curious as to why you moved away from ConEmu. Can you share the motivating factors? Anything to be concerned about?

It just never really worked well for me in a multi-monitor setup with two screens and a docking station... Now, Windows itself is quite terrible with this and often moves windows between screens for no reason. For example, when primary screen takes a second longer to come back from sleep, all windows float to secondary one, at least that is what I guess is happening.

Now, with ConEmu, that also caused some rendering defects and I would have to hide/show window and sometimes reopen tabs to get it to work again. If I understand correctly, ConEmu does some sort of off screen rendering hack with conhost and then just synchronizes the bitmap to where its real window is. Though I may be completely wrong and that is not how it really works. But these issues have never occurred with WT.

Otherwise, I had nothing to complain about with ConEmu, especially its UAC handling is awesome. Unless we could have proper sudo on Windows, of course. That would be even better UX :)

Re: Windows Terminal Quake Mode

#89
post #36

Earlier quoted context omitted.

And a 1000 of those are bugs that have been around since Windows 98.

Any example?

One simple one: If I start multiple Kopies/file downloads, Windows will run them all in parallel, even if they run through the same connection. So if after 50% there´s a connection drop, all of them will abort. This used to be especially bad on nicely defragmented disks, because the extra seeking makes parallel copies slower then sequential ones.

Even after all this time, they can`t figure out to automatically chain I/O operations (or at least give me some UI to do it explicitly).

Re: Windows Terminal Quake Mode

#90
post #75

Earlier quoted context omitted.

I used to use Guake but felt the need sometimes to be able to resize/move terminal open next to a window, say, for comparing something. So I instead setup a script to run a regular terminal such that it a) starts a terminal instance if none are running b) activates the terminal window if an instance is running and c) presses alt-tab to switch away from terminal if the terminal window is active. The script is bound to…

Can you share the script please? It sounds like something I'd find very useful

Sure here you go: https://pastebin.com/3B4AhiJP
Post reply on HN