Shell escape - Revision history

ChasonBot at 09:39, 21 December 2015

2015-12-21T09:39:57Z

Bulwersator: delinkify operating system (Special:WantedPages)

2013-05-04T21:50:10Z

delinkify operating system (Special:WantedPages)

Schneelocke: use {{kbd}}

2010-05-03T23:58:32Z

use {{kbd}}

Paxed: kbd

2009-04-22T15:17:08Z

kbd

Eidolos: The source code for Unix in a single file? Wow! :)

2006-08-31T04:29:47Z

The source code for Unix in a single file? Wow! :)

Kernigh: In four paragraphs, describe the shell escape, including how it does upon Unix.

2006-08-31T00:05:51Z

In four paragraphs, describe the shell escape, including how it does upon Unix.

New page

In game, the [[!]] key triggers the '''shell escape'''. This should send you to a command line; exit the shell to return to NetHack. The exact behavior varies by [[operating system]].

It only works if the person who compiled the game had SHELL defined in [[config.h]]. Persons who build the game for [[public server]]s or other environments in which the player should not reach a shell will disable it.

In the [[source code]], the <tt>dosh</tt> function handles this. The code for this function, if any, is somewhere under the <tt>nethack-3.4.3/sys</tt> directory for your operating system.

The file <tt>nethack-3.4.3/sys/unix/unixunix.c</tt> contains the source for [[Unix]]. If there is a <tt>SHELL</tt> environment variable, then NetHack will start that program, else NetHack will attempt to run <tt>/bin/sh</tt>. In most shells, the <tt>exit</tt> command will then return you to NetHack. Since most Unix now have job control, you could just press Control-Z to suspend NetHack and return to the calling shell instead of starting a subshell; for that reason some players may never think to use the shell escape.

[[Category:Commands]]

← Older revision		Revision as of 09:39, 21 December 2015
Line 7:		Line 7:
	The file <tt>nethack-3.4.3/sys/unix/unixunix.c</tt> contains the source for shell-escaping for a [[Unix]] system. If there is a <tt>SHELL</tt> environment variable, then NetHack will start that program, else NetHack will attempt to run <tt>/bin/sh</tt>. In most shells, the <tt>exit</tt> command will then return you to NetHack. Since most Unix now have job control, you could just press {{kbd\|Ctrl\|Z}} to suspend NetHack and return to the calling shell instead of starting a subshell; for that reason some players may never think to use the shell escape.		The file <tt>nethack-3.4.3/sys/unix/unixunix.c</tt> contains the source for shell-escaping for a [[Unix]] system. If there is a <tt>SHELL</tt> environment variable, then NetHack will start that program, else NetHack will attempt to run <tt>/bin/sh</tt>. In most shells, the <tt>exit</tt> command will then return you to NetHack. Since most Unix now have job control, you could just press {{kbd\|Ctrl\|Z}} to suspend NetHack and return to the calling shell instead of starting a subshell; for that reason some players may never think to use the shell escape.
	[[Category:Commands]]		[[Category:Commands]]
		+	{{nethack-343}}

← Older revision		Revision as of 21:50, 4 May 2013
Line 1:		Line 1:
−	In game, the {{kbd\|!}} key triggers the '''shell escape'''. This should send you to a command line; exit the shell to return to NetHack. The exact behavior varies by [[operating system]].	+	In game, the {{kbd\|!}} key triggers the '''shell escape'''. This should send you to a command line; exit the shell to return to NetHack. The exact behavior varies by operating system.

	It only works if the person who compiled the game had SHELL defined in [[config.h]]. Persons who build the game for [[public server]]s or other environments in which the player should not reach a shell will disable it.		It only works if the person who compiled the game had SHELL defined in [[config.h]]. Persons who build the game for [[public server]]s or other environments in which the player should not reach a shell will disable it.

@@ Line 5: / Line 5: @@
 In the [[source code]], the <tt>dosh</tt> function handles this. The code for this function, if any, is somewhere under the <tt>nethack-3.4.3/sys</tt> directory for your operating system.
-The file <tt>nethack-3.4.3/sys/unix/unixunix.c</tt> contains the source for shell-escaping for a [[Unix]] system. If there is a <tt>SHELL</tt> environment variable, then NetHack will start that program, else NetHack will attempt to run <tt>/bin/sh</tt>. In most shells, the <tt>exit</tt> command will then return you to NetHack. Since most Unix now have job control, you could just press Control-Z to suspend NetHack and return to the calling shell instead of starting a subshell; for that reason some players may never think to use the shell escape.
+The file <tt>nethack-3.4.3/sys/unix/unixunix.c</tt> contains the source for shell-escaping for a [[Unix]] system. If there is a <tt>SHELL</tt> environment variable, then NetHack will start that program, else NetHack will attempt to run <tt>/bin/sh</tt>. In most shells, the <tt>exit</tt> command will then return you to NetHack. Since most Unix now have job control, you could just press {{kbd|Ctrl|Z}} to suspend NetHack and return to the calling shell instead of starting a subshell; for that reason some players may never think to use the shell escape.
 [[Category:Commands]]

@@ Line 1: / Line 1: @@
-In game, the [[!]] key triggers the '''shell escape'''. This should send you to a command line; exit the shell to return to NetHack. The exact behavior varies by [[operating system]].
+In game, the {{kbd|!}} key triggers the '''shell escape'''. This should send you to a command line; exit the shell to return to NetHack. The exact behavior varies by [[operating system]].
 It only works if the person who compiled the game had SHELL defined in [[config.h]]. Persons who build the game for [[public server]]s or other environments in which the player should not reach a shell will disable it.
@@ Line 6: / Line 6: @@
 The file <tt>nethack-3.4.3/sys/unix/unixunix.c</tt> contains the source for shell-escaping for a [[Unix]] system. If there is a <tt>SHELL</tt> environment variable, then NetHack will start that program, else NetHack will attempt to run <tt>/bin/sh</tt>. In most shells, the <tt>exit</tt> command will then return you to NetHack. Since most Unix now have job control, you could just press Control-Z to suspend NetHack and return to the calling shell instead of starting a subshell; for that reason some players may never think to use the shell escape.
 [[Category:Commands]]