DOSKEY

From Wikipedia, the free encyclopedia

Template:DMCA

Page Module:Infobox/styles.css has no content.

DOSKEY
[[Programmer|DeveloperTemplate:Pluralize from text]]Microsoft, IBM, Novell, ReactOS contributors
Initial release1991, 34–35 years ago
Template:Infobox software/simple
EnginePage Template:Plainlist/styles.css has no content.Template:EditAtWikidata
Operating systemMS-DOS, PC DOS, OS/2, eComStation, ArcaOS, Novell DOS 7, DR-DOS, Windows, ReactOS
PlatformCross-platform
TypeCommand
Websitedocs.microsoft.com/en-us/windows-server/administration/windows-commands/doskey
RepositoryPage Template:Plainlist/styles.css has no content.

Script error: No such module "Check for conflicting parameters".

DOSKEY is a command in DOS, OS/2,[1] Windows,[2] and ReactOS[3] that adds command history, macro functionality, and improved editing features to the COMMAND.COM and cmd.exe command-line interpreter shells.

History

The command was included as a terminate-and-stay-resident program with MS-DOS and PC DOS versions 5 and later,[4] then Windows 9x,[5] and finally Windows 2000[6] and later.

In early 1989, functionality similar to DOSKEY was introduced with DR-DOS 3.40 with its HISTORY CONFIG.SYS directive. This enabled a user-configurable console input history buffer and recall as well as pattern search functionality on the console driver level, that is, fully integrated into the operating system and transparent to running applications. In the summer of 1991, DOSKEY was introduced in MS-DOS/PC DOS 5.0 in order to provide some of the same functionality. DOSKEY also added a macro expansion facility, though special support was required before applications such as command line processors could take advantage of it. Starting with Novell DOS 7 in 1993, the macro capabilities were provided by an external DOSKEY command as well. In order to also emulate the DOSKEY history buffer functionality under DR-DOS, the DR-DOS DOSKEY worked as a front end to the resident history buffer functionality, which remained part of the kernel.

DOSKEY has also been included in IBM OS/2 Version 2.0.[7]

In current Windows NT-based operating systems, the DOSKEY functionality is built into CMD.EXE, although the DOSKEY command is still used to change its operation.

The DOSKEY command is not available in FreeDOS, which has such features built into the command interpreter.[8]

Usage

Command switches

DOSKEY allows the use of several command switches:

DOSKEY [/switch ...] [macroname=[text]]

Page Template:Mono/styles.css has no content./REINSTALL
Installs a new copy of DOSKEY.
Page Template:Mono/styles.css has no content./LISTSIZE=[size]
Sets size of command history buffer to size.
Page Template:Mono/styles.css has no content./MACROS
Displays all DOSKEY macros.
Page Template:Mono/styles.css has no content./MACROS:ALL
Displays all DOSKEY macros for all executables which have DOSKEY macros.
Page Template:Mono/styles.css has no content./MACROS:[executable name]
Displays all DOSKEY macros for the given executable.
Page Template:Mono/styles.css has no content./HISTORY
Displays all commands stored in memory.
Page Template:Mono/styles.css has no content./INSERT
Specifies that new text typed is inserted in old text.
Page Template:Mono/styles.css has no content./OVERSTRIKE
Specifies that new text overwrites old text.
Page Template:Mono/styles.css has no content./EXENAME=exename
Specifies the executable.
Page Template:Mono/styles.css has no content./MACROFILE=filename
Specifies a file of macros to install.
Page Template:Mono/styles.css has no content./APPEDIT
(undocumented - since MS-DOS 7)
Page Template:Mono/styles.css has no content./COMMAND
(undocumented - since MS-DOS 7)
Page Template:Mono/styles.css has no content./PERMANENT
(undocumented - since MS-DOS 7)
Page Template:Mono/styles.css has no content./SCRSIZE
(undocumented - since MS-DOS 7)
Page Template:Mono/styles.css has no content./XHISTORY
(undocumented - since MS-DOS 7)
[macroname]
Specifies a name for a macro created.
[text]
Specifies commands to record.

Keyboard shortcuts

During a DOSKEY session, the following keyboard shortcuts can be used:

Script error: No such module "key". and Script error: No such module "key".
Recall commands
Script error: No such module "key".
Clears command line
Script error: No such module "key".
Clears command line from the cursor to the beginning of the line.
Script error: No such module "key".
Clears command line from the cursor to the end of the line.
Script error: No such module "key".
Displays command history
Script error: No such module "key".
Clears command history
Script error: No such module "key".
Searches command history
Script error: No such module "key".
Selects a command by number
Script error: No such module "key".
Clears macro definitions

Command macros

DOSKEY implements support for command macros, a simple text-substitution facility which is used somewhat like command line aliases in other environments.

Page Template:Mono/styles.css has no content.$T
Command separator. Allows multiple commands in a macro.
Page Template:Mono/styles.css has no content.$1Page Template:Mono/styles.css has no content.$9
Batch parameters. Equivalent to Page Template:Mono/styles.css has no content.%1-Page Template:Mono/styles.css has no content.%9 in batch programs.
Page Template:Mono/styles.css has no content.$*
Symbol replaced by everything following the macro name on command line.

Alternatives

The absence of a command history in COMMAND.COM was a serious inconvenience ever since the earliest versions of MS-DOS. Numerous third-party programs have been written to address the issue; many were available long before Microsoft supplied DOSKEY. Some of them, including JP Software's 4DOS and NDOS, also provide additional editing capabilities lacking in DOSKEY, such as filename completion. Some of the better-known DOSKEY alternatives are Jack Gersbach's DOSEDIT, Chris Dunford's CED, Sverre Huseby's DOSED, Ashok Nadkarni's CMDEDIT, Steven Calwas's ANARKEY, Eric Tauck's TODDY, and enhanced DOSKEY written by Paul Houle.

Paul Houle's Enhanced DOSKEY[9] is designed to be an enhanced drop-in replacement for the DOSKEY.COM that ships with MS-DOS and Windows 9x/Windows Me. It also has a smaller disk and memory-resident footprint. The primary added feature is command and file "auto-completion" via the Tab key. Version 2.5, released in 2014, also adds full support for long filenames (LFN).

See also

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content."JaTomes Help - OS/2 Commands". Archived from the original on 2019-04-14. Retrieved 2019-07-28.
  2. ^ Page Module:Citation/CS1/styles.css has no content."Doskey | Microsoft Docs". 2009-09-11.
  3. ^ Page Module:Citation/CS1/styles.css has no content."Reactos/Reactos". GitHub. 2021-11-02.
  4. ^ Page Module:Citation/CS1/styles.css has no content.Wolverton, Van (2003). Running MS-DOS Version 6.22 (20th Anniversary Edition), 6th Revised edition. Microsoft Press. ISBN 0-7356-1812-7.
  5. ^ Page Module:Citation/CS1/styles.css has no content.Tim O'Reilly; Troy Mott; Walter Glenn (1999). Windows 98 in a Nutshell: A Desktop Quick Reference. O'Reilly. ISBN 978-1565924864.
  6. ^ Page Module:Citation/CS1/styles.css has no content.Frisch, Æleen (2001). Windows 2000 Commands Pocket Reference. O'Reilly. ISBN 978-0-596-00148-3.
  7. ^ OS/2 2.0 Redbooks Volume 2 - DOS and Windows Environment (GG24-3731)
  8. ^ Page Module:Citation/CS1/styles.css has no content."FreeDOS command: doskey". Archived from the original on 2011-11-07.
  9. ^ Page Module:Citation/CS1/styles.css has no content."Enhanced DOSKEY.com -- with auto-completion Paul Houle".

Further reading

Page Module:Side box/styles.css has no content.Page Template:Sister project/styles.css has no content.

Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found.