Anonymous | Login | 2024-04-26 08:27 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0000975 | [1003.1(2008)/Issue 7] Shell and Utilities | Editorial | Clarification Requested | 2015-08-11 15:25 | 2016-06-02 15:16 | ||
Reporter | joerg | View Status | public | ||||
Assigned To | ajosey | ||||||
Priority | normal | Resolution | Withdrawn | ||||
Status | Closed | ||||||
Name | Jörg Schilling | ||||||
Organization | |||||||
User Reference | |||||||
Section | fc | ||||||
Page Number | 2745-2759 | ||||||
Line Number | 89811-90031 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0000975: fc prevents better history implementations, so remove it or make it optional | ||||||
Description |
The fc command is based on the history mechanism as seen in csh and based on a command serial number that does not change as long as a command is in the history. There however exist better mechanisms that implement the history as a lru list where each called command is in the history only once and if the same command is called again, it is moved from it's previous place to the last recently used location. This method is easier to understand than the cah/ksh method. Implementor should not be forced to implement an inferior concept just because POSIX defines fc to be mandatory. Note that the lru history mechanism was developed in 1982 and a fully working implementation exists since 1984. This history mechanism was added to the Bourne Shell in 2006. |
||||||
Desired Action | Mark the fc command optional or better completely remove it. | ||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |