You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: course-definition.yml
+10-5Lines changed: 10 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1303,6 +1303,16 @@ stages:
1303
1303
description_md: |-
1304
1304
In this stage, you'll add support for [history](https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html#index-history) as a shell builtin.
1305
1305
1306
+
### The history builtin
1307
+
1308
+
[history](https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html#index-history) as a shell builtin that lists previously executed commands. Example usage:
1309
+
```bash
1310
+
$ history
1311
+
1 previous_command_1
1312
+
2 previous_command_2
1313
+
3 history
1314
+
```
1315
+
1306
1316
### Tests
1307
1317
1308
1318
The tester will execute your program like this:
@@ -1321,11 +1331,6 @@ stages:
1321
1331
1322
1332
The tester will then execute the `type history` command and expect the output to be `history is a shell builtin`.
1323
1333
1324
-
### Notes
1325
-
1326
-
- For now we're just testing that the `type` builtin identifies `history` as a valid builtin.
1327
-
- We'll handle the actual implementation of the `history` builtin in later stages.
1328
-
1329
1334
marketing_md: |-
1330
1335
In this stage, you'll add support for the `history` builtin command in `type`.
0 commit comments