>> What I mean is you can’t just look at a board and know the ko “state” - but yes I’m sure in practice it’s not that important.
> Chess also has this "problem" thanks to rules like castling and en passant capture.
Chess is intended to be stateful. If you forget whether a castle has occurred (and then the king walked back to its starting position, and a rook repositioned into the corner) or not, chess players will note that you've messed up the game. The castling rule is there to stop you from castling more than once.
Go is not intended to be stateful, and if you forget that a particular board layout may have come up in the past, go players will not note that you've messed up the game. It doesn't matter. The ko rule isn't there to stop you from repeating a board twice. It's there to stop you from having to repeat a board layout an infinite number of times, because things like the need for food and sleep would interfere with the game.
Wrt the implementation concern, this distinction means, for example, that you must always track the castling state regardless of whether a player asks for it, whereas you're fine not bothering to track the history of a go board unless a player asks for it. You can just say "if you want to invoke ko, press this button, and we'll remember that board layout, and if it's already been flagged, the game will draw". That isn't done, but it could be done.
I'm not a Go player so I don't really know how it works in practice, but what you are saying seems to disagree with the wording in Wikipedia, so I'm curious which one is correct?
You say:
> if you forget that a particular board layout may have come up in the past, go players will not note that you've messed up the game. It doesn't matter. The ko rule isn't there to stop you from repeating a board twice.
Wikipedia says:
> Rule 8. A play is illegal if it would have the effect (after all steps of the play have been completed) of creating a position that has occurred previously in the game.
> Consequence (ko rule). One may not play in such a way as to recreate the board position following one's previous move.
> While its purpose is similar to that of the threefold repetition rule of Western chess, it differs from it significantly in nature; the superko rule bans moves that would cause repetition, whereas Western chess allows such moves as one method of forcing a draw.
To me that sounds like you do need to track this, in both chess and in Go, though for different reasons (to force a draw vs to prevent an illegal move). Is this not enforced in practice?
Out of interest, what do you use the context menu for in a terminal emulator so often that it bothers you? I can't even remember the last time I opened it.
I hide all UI and use only the context menu, 90% of the time to open a new tab, 5% of the time to split a tab, and 4% of the time to bring up the config dialog. 1% to open a new window, though I'm often doing Ctrl+Alt+T for that recently.
This is what I've done since SGI 4DWM Terminal (and ancient NT Command Prompt), and almost all other terminal emulators can be configured to do so. Konsole stands alone (to my knowledge) in its insistence on cruft all over the interface. The terminal widget itself seems fine.
To be clear, I don't mind obscure options, but they should live in the control panel. See my cousin comment for more details.
All these things have keyboard shortcuts If the context menu bothers you, it would seem worth it to use them for frequent actions. CTRL+Shift+T opens a new tab for instance. It's way more efficient anyway in an app that's so keyboard centric.
I don't find that context menu so bad to be honest. If you use it often you should know where things are anyway.
Overall I'm quite surprised at the hate Konsole receives in this HN thread. Removing the toolbars is two clicks away and only needs to be done once. Even the menu bar can be hidden. Such a konsole window would be just the terminal, no cruft, no UI elements. To me we are in the "some people will never be happy for no clear reasons" territory.
I've been using it for years I'm very happy with it. Its search feature is awesome, and its ability to have infinite scroll history is very nice too, it has decent performance.
The one terrible thing I have seen about konsole is that the toolbar buttons were highjacking the keyboard bindings in the terminal, but it was a bug, I think this is now fixed and a workaround was to remove the toolbar.
When I start typing I want to execute the new idea immediately. No other tabbed terminal (that I’ve used) prevents this besides konsole, simply because the context menu is (un)optimized to include the kitchen sink instead of the one item I want.
Folks trying to talk me into a new workflow can’t succeed because I’m multiplatform. Gnome terminal, iTerm2, Win Terminal, etc. konsole is the oddball and least used of the group. Partly because the context menu is a mess.
Would prefer it much smaller, but it has what I need, is better organized, items are at least theoretically useful, doesn’t include the full menu, and I don’t use it as much.
No, I mentioned that this is solved with a couple of clicks to do once if you are bothered by this. I see few reasons to complain really. One could prefer having different defaults (and I would, actually), but it's not like their are awful neither.
Had the toolbars been difficult or impossible to customize or remove, I wouldn't say, but here ulyou can make it look to your taste completely. The issue is a taste question and is a "meh" at best.
Yes, that's the downplaying part. Configuring bad default away doesn't make a user happy the bad default existed and required wasting time fixing it (of course it's not a couple of clicks, that's also downplaying, you'd have to first acquire the knowledge that it's possible (not all UIs can be customized) and how to do it (e.g., some DEs require installing some DE Shell Extension to be able to find the relevant config))
Defaults cannot always please every unique user. That's an impossible goal.
It's fine that impossibly picky users get to click through a few settings once to set their environment to their liking. I'm one myself sometimes.
I wonder if vocal people here who hate this minor (yes, I'll die on this hill) stuff so much took the time to even report this as an issue in KDE's bugtracker. Here's the link if it's not already done:
> Defaults cannot always please every unique user. That's an impossible goal.
You're just continuing in your quest to ignore the issue. Just set the goal at "most users", that's fine, you'll still need to defend this actual screen waste to make an argument, but you can't hide behind a generic "can't please everyone"
> hate
There is no hate, you've made it up to make your argument sound better.
> this minor (yes, I'll die on this hill)
No one is looking at, let alone fighing, you on this imaginary hill. The other commenter explicitly said it's not a big issue. I also agree it's minor. Stop bringing more straws for your scarecrow!
> took the time to even report this
To waste it on a repeat of this argument with ~0 chance of a win? Again, you've made up that hate, so there is no motivation in doing that, a more productive use of that time is to use a better terminal (or just configure it away), so that's usually what happens
Doesn't help when coming from a browser. Ctrl+Alt+T works without the Terminal in focus however. Ctrl+Shift+T needs me to click in the terminal first then go back to the keyboard. Waste of time.
I almost always switch windows with Alt+Tab, not with a mouse, so it fits very well for that flow. Understandable if it doesn't do the trick for you though.
I’m well aware of all these hotkeys. The issue is I’m using the mouse with my browser, scrolling clicking etc. Reading gives me an idea so I click on my terminal that’s always open. This is the best time to open a tab imho, and have been doing it for decades.
Thankfully there are a dozen terminals to choose from that don’t make konsole’s minor mistakes. (Although chances are they made others.)
To add to the sibling comment, your CPU is not going to be using 100 W (if it can even reach that!) for more than a few seconds in total during 15 min of typical Photoshop use.
I think you may be mixing up profiles and containers.
Profiles do have a built-in UI at about:profiles or by launching Firefox with -P, neither of which requires an extension. Admittedly this UI is a bit basic, but a better version is being rolled out (https://support.mozilla.org/en-US/kb/profile-management). Running multiple profiles side by side does indeed involve running multiple instances of the browser.
Containers are an internal API and need an extension like Multi-account Containers to provide a GUI (though this is an official extension by Mozilla), however they don't require running multiple copies of the browser.
Skype chats used to be peer-to-peer, so older history would only be kept locally by the client. If you have backups of your user/home directory from that time, it might be recoverable. IIRC they were stored in an SQLite database, so it's not too difficult to export them.
YouTube deliberately tries to prevent background playback by using web APIs to detect when the page is no longer visible and pausing the video. The extension prevents YouTube from doing that.
Aliases are not expanded in shell scripts, unless they explicitly opt into it. Additionally, they are run in a non-interactive shell, so will not load your ~/.bashrc where you probably defined the alias.
> This page is not supported. > Please visit the author’s profile on the latest version of X to view this content.
...I am using the version which their own server just served me.
reply