Hangup - Revision history

Furey: Send some references to wikipedia. Fixes redlinks. Also copy edit the first sentence.

2024-06-18T14:28:59Z

Send some references to wikipedia. Fixes redlinks. Also copy edit the first sentence.

Umbire the Phantom: de-SLEX

2022-10-05T02:31:18Z

de-SLEX

Elronnd: link to bilious rgrn; correct capitalization for 'Usenet'

2020-07-01T22:37:31Z

link to bilious rgrn; correct capitalization for 'Usenet'

SophiaMakoto: Added not about Slex.

2017-11-12T14:05:27Z

Added not about Slex.

ChasonBot at 14:33, 19 December 2015

2015-12-19T14:33:47Z

Ais523: mention NetHack 4 behaviour

2015-06-06T19:34:19Z

mention NetHack 4 behaviour

SophiaMakoto at 23:43, 9 May 2015

2015-05-09T23:43:55Z

SophiaMakoto: Added danger of hangup just before ascending.

2015-05-09T23:40:58Z

Added danger of hangup just before ascending.

24.113.80.29: /* information about SIGHUP bug fix from DevTeam */

2014-08-19T22:43:06Z

‎information about SIGHUP bug fix from DevTeam

Tjr: link to individual bug

2013-03-09T08:06:55Z

link to individual bug

@@ Line 1: / Line 1: @@
-A '''hangup''' occurs when you disconnect a [[terminal]] from the programs running in it. Originally, "hangup" referred to the process of ending a telephone call by placing (or hanging up) the phone on the hook. Some terminals connected to computers using phone lines (for example, with old [[DOS]] or [[Macintosh]] software like the communication modes of Microsoft Works or AppleWorks) and became subject to hangup. With windowing systems, you can now cause hangups by closing [[terminal emulator]]s or DOS prompts with programs still running on them. With the Internet, you can cause a hangup by quitting your [[telnet]] or [[ssh]] client while still running programs. More generally, a hangup is any instance when a parent process quits.
+A '''hangup''' occurs when you disconnect a [[wikipedia:computer terminal|computer terminal]] from the programs connected to it. Originally, "hangup" referred to the process of ending a telephone call by placing (or hanging up) the phone on the hook. Some terminals connected to computers using phone lines (for example, with old [[DOS]] or [[Macintosh]] software like the communication modes of Microsoft Works or AppleWorks) and became subject to hangup. With windowing systems, you can now cause hangups by closing [[wikipedia:terminal emulator|terminal emulator]]s or DOS prompts with programs still running on them. With the Internet, you can cause a hangup by quitting your [[telnet]] or [[wikipedia:ssh|ssh]] client while still running programs. More generally, a hangup is any instance when a parent process quits.
-If you hangup while [[NetHack]] is running, then (on systems with the SIGHUP [[signal]], such as [[Unix]], [[VMS]] and [[Microsoft Windows]]), the hangup function at [[save.c#line83]] will save your game. For players who use NetHack's [[tty]] interface, an easy way to save the game is to close the terminal emulator or telnet client with NetHack's [[tty]] interface inside it.
+If you hangup while [[NetHack]] is running, then (on systems with the SIGHUP [[wikipedia:signal (IPC)|signal]], such as [[Unix]], [[VMS]] and [[Microsoft Windows]]), the hangup function at [[save.c#line83]] will save your game. For players who use NetHack's [[tty]] interface, an easy way to save the game is to close the terminal emulator or telnet client with NetHack's [[tty]] interface inside it.
 Beware of hanging up during a prompt, as it has the effect of [[esc|cancelling]] the prompt. You will not get a refund on your [[wish]] or [[genocide]] order. If a hangup is triggered after offering the [[Amulet of Yendor]] on the [[Astral Plane]] but before [[Ascension|ascending]], you will render the game [[unwinnable]]; upon reloading the game, you will not have the amulet and be stuck on the Astral Plane!

@@ Line 6: / Line 6: @@
 One of the listed [[bugs in NetHack 3.4.3#SC342-3|bugs]] involves some method of using hangup to cheat. [[Cheating#Hangup_saves]] describes some ways to cheat using a hangup save. [[DevTeam]] member Pat Rankin provided some information about how this bug is fixed in the [[next version]] of NetHack in [https://bilious.alt.org/rgrn/?130838-130845,130848,130851,130868-130875#p130868 this Usenet post.]
 == Variants ==
 In [[NetHack 4]], the game is saved continuously, meaning that a hangup has the same effect as simply quitting the game. When reloading the game, it returns to the exact same point (perhaps even at a prompt or in the middle of a turn) via replaying all user commands that were input since the last time the game could be saved in the normal way.
 [[Category:Development]]
 {{nethack-343}}

← Older revision		Revision as of 22:37, 1 July 2020
Line 5:		Line 5:
	Beware of hanging up during a prompt, as it has the effect of [[esc\|cancelling]] the prompt. You will not get a refund on your [[wish]] or [[genocide]] order. If a hangup is triggered after offering the [[Amulet of Yendor]] on the [[Astral Plane]] but before [[Ascension\|ascending]], you will render the game [[unwinnable]]; upon reloading the game, you will not have the amulet and be stuck on the Astral Plane!		Beware of hanging up during a prompt, as it has the effect of [[esc\|cancelling]] the prompt. You will not get a refund on your [[wish]] or [[genocide]] order. If a hangup is triggered after offering the [[Amulet of Yendor]] on the [[Astral Plane]] but before [[Ascension\|ascending]], you will render the game [[unwinnable]]; upon reloading the game, you will not have the amulet and be stuck on the Astral Plane!

−	One of the listed [[bugs in NetHack 3.4.3#SC342-3\|bugs]] involves some method of using hangup to cheat. [[Cheating#Hangup_saves]] describes some ways to cheat using a hangup save. [[DevTeam]] member Pat Rankin provided some information about how this bug is fixed in the [[next version]] of NetHack in [https://~~groups~~.~~google~~.~~com~~/d/~~msg/rec.games.roguelike.nethack/Atg9JKrGpfw/Ua23WDLMZmsJ~~ this ~~UseNet~~ post.]	+	One of the listed [[bugs in NetHack 3.4.3#SC342-3\|bugs]] involves some method of using hangup to cheat. [[Cheating#Hangup_saves]] describes some ways to cheat using a hangup save. [[DevTeam]] member Pat Rankin provided some information about how this bug is fixed in the [[next version]] of NetHack in [https://bilious.alt.org/rgrn/?130838-130845,130848,130851,130868-130875#p130868 this Usenet post.]

@@ Line 3: / Line 3: @@
 If you hangup while [[NetHack]] is running, then (on systems with the SIGHUP [[signal]], such as [[Unix]], [[VMS]] and [[Microsoft Windows]]), the hangup function at [[save.c#line83]] will save your game. For players who use NetHack's [[tty]] interface, an easy way to save the game is to close the terminal emulator or telnet client with NetHack's [[tty]] interface inside it.
-Beware of hanging up during a prompt, as it has the effect of [[esc|cancelling]] the prompt. You will not get a refund on your [[wish]] or [[genocide]] order. If you hangup after offering the [[Amulet of Yendor]] on the [[Astral Plane]] but before [[Ascension|ascending]], you will render the game [[unwinnable]]!
+Beware of hanging up during a prompt, as it has the effect of [[esc|cancelling]] the prompt. You will not get a refund on your [[wish]] or [[genocide]] order. If a hangup is triggered after offering the [[Amulet of Yendor]] on the [[Astral Plane]] but before [[Ascension|ascending]], you will render the game [[unwinnable]]; upon reloading the game, you will not have the amulet and be stuck on the Astral Plane!
 One of the listed [[bugs in NetHack 3.4.3#SC342-3|bugs]] involves some method of using hangup to cheat. [[Cheating#Hangup_saves]] describes some ways to cheat using a hangup save. [[DevTeam]] member Pat Rankin provided some information about how this bug is fixed in the [[next version]] of NetHack in [https://groups.google.com/d/msg/rec.games.roguelike.nethack/Atg9JKrGpfw/Ua23WDLMZmsJ this UseNet post.]
 In [[NetHack 4]], the game is saved continuously, meaning that a hangup has the same effect as simply quitting the game. When reloading the game, it returns to the exact same point (perhaps even at a prompt or in the middle of a turn) via replaying all user commands that were input since the last time the game could be saved in the normal way.
 [[Category:Development]]
 {{nethack-343}}

← Older revision		Revision as of 14:33, 19 December 2015
Line 10:		Line 10:

	[[Category:Development]]		[[Category:Development]]
		+	{{nethack-343}}

← Older revision		Revision as of 19:34, 6 June 2015
Line 6:		Line 6:

	One of the listed [[bugs in NetHack 3.4.3#SC342-3\|bugs]] involves some method of using hangup to cheat. [[Cheating#Hangup_saves]] describes some ways to cheat using a hangup save. [[DevTeam]] member Pat Rankin provided some information about how this bug is fixed in the [[next version]] of NetHack in [https://groups.google.com/d/msg/rec.games.roguelike.nethack/Atg9JKrGpfw/Ua23WDLMZmsJ this UseNet post.]		One of the listed [[bugs in NetHack 3.4.3#SC342-3\|bugs]] involves some method of using hangup to cheat. [[Cheating#Hangup_saves]] describes some ways to cheat using a hangup save. [[DevTeam]] member Pat Rankin provided some information about how this bug is fixed in the [[next version]] of NetHack in [https://groups.google.com/d/msg/rec.games.roguelike.nethack/Atg9JKrGpfw/Ua23WDLMZmsJ this UseNet post.]
		+
		+	In [[NetHack 4]], the game is saved continuously, meaning that a hangup has the same effect as simply quitting the game. When reloading the game, it returns to the exact same point (perhaps even at a prompt or in the middle of a turn) via replaying all user commands that were input since the last time the game could be saved in the normal way.

	[[Category:Development]]		[[Category:Development]]