Peep
Path: ForcingAndInitiative
· Prev: KoThreatFunctions · Next: RawPeep
Difficulty: Introductory Keywords: Go term
![[Diagram]](../../diagrams/25/a0fb7309ce144614b15bc5e02aaf60b6.png) | Peep |
A peep in go is a threat to cut (nozoki in Japanese).[1]
The white move peeps Black's loose connection: what it actually threatens is a push through and cut (called degiri in Japanese). Not all moves that threaten to cut are peeps though; if the cut is too indirect or the cutting point only just formed then the word wouldn't be used..
![[Diagram]](../../diagrams/20/49fca232f0da458d1a2c1624b2e9ba2a.png) | Examples |
and are both peeps, threatening Black a and White b respectively.
Bob Myers: Is really a peep? Of course it threatens to cut, but my intuitive impression is that a peep is more often a stand-alone stone threatening to cut. More generally, I'd hope that this page could be expanded to discuss the issue of why to play a peep, if that's not been covered elsewhere. The idea of a peep as a sort of probe or forcing move, making the opponent commit himself; classical sequences such as a peep against a one-point jump in preparation for a jump on the other side.
creates the cutting point at a, and sets up the chance of cutting there. But it isn't a peep. This would be called an example of atekomi.
[1] Also but rarely called peek or poke in English.
By the way, 'poke' must die. There is some explanation on English Go Terms / Discussion about the possible rudeness of 'peep'; I think native speakers of English will find this hilarious unless they have lived an extremely sheltered life.
-- Charles
- Bill: "Poke" is the brainchild of one translator who thought that "peep" was salacious. I guess he did not think about all the meanings of "poke". ;-)
Charles Yes, indeed; such was my implication. Not for a family web site, though.
Jasonred : In certain situations, when you ignore bad aji, and your opponent takes advantage of it, "Oh, no! He poked me! Now I'm poked!"
DougRidgway Craig Hutchinson, writing in Go Winds, has used at least two of these terms to refer to slightly different threats
to cut. I'm not sure of the distinction he's trying to draw, however. He also uses the terms "peg" and "pin" to refer to
various ways of connecting.
Bill: Well, anyway, this is a poke:
![[Diagram]](../../diagrams/30/1b2b837040bbd3c48a4a06a655cd72ee.png) | Poke |
Xris: Are you allowed to show such a diagram on a page available to minors ;-)
![[Diagram]](../../diagrams/36/aa7a3fed3618cbfc4033ad5c3d4d6630.png) | With a standard tesuji? |
I saw this siuation in a game and it was handled like this instead of just blocking at a. This was described to be a standard tesuji.. Any comments on it? - Reuven
Charles I remember something written in an old BGJ - in reply to a pro saying a play was standard, an amateur 2 dan saying he wished he could find such things in a game.
![[Diagram]](../../diagrams/14/d26e827eccf59e0a534bbf76e0bfae03.png) | With a standard tesuji? (ii) |
Here the point is that can be played, but then after , White has big worries about Black at b later. If White plays b to capture, right now, then the peep at turned out to be gote, so Black will be happy.
![[Diagram]](../../diagrams/22/0067cacc1f1054ebcbe59987f0250a1e.png) | With a standard tesuji? (iii) |
One variation: White gets into big trouble.
Maybe some exceptions could be put at the "Even a moron connects against a peep" proverbs page? Or on some other "How to handle a peep?" page?
Further reading
Contributors
Path: ForcingAndInitiative
· Prev: KoThreatFunctions · Next: RawPeep
This is a copy of the living page
"Peep" at
Sensei's Library.
2004 the Authors, published under the OpenContent License V1.0.
|