Old-school 95/98 DOS 7(.1) EDIT had a mostly unknown '/40' (any number works) parameter that enabled binary-viewed-as-ASCII editing of files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14.6k
- Forks
- 734
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 4
Description
Quickly; No, it's not just a screen-column-width display flag.
EDIT.com at one point had a feature (I've very recently learned it's virtually unknown) to open files in a binary-as-ascii mode for byte-specific editing/viewing, it's (only, afaik) enabled by passing 2-numbers after a forward-slash [eg "/40"] as a parameter/argument to EDIT on the command line.
While it **is** a _mostly-undocumented feature_, it was unquestionably useful as it significantly expands EDIT's capability.. and, to my knowledge, it's the only native way to make byte-specific changes to files in DOS.
The /40 parameter [eg; `edit /40 file.exe`, `edit /60 file.exe`, etc] would open EDIT in a special mode, displaying an ASCII-character representation of binary data, and keeping the text/data display wrapped at whatever column number was specified.
Could this functionality be added to this incarnation/recreation of EDIT?.. Though preferably with true HEX display/edit, rather than the old ASCII weirdness
(More info if anyone's trying to find it themselves; Digging around as much as I could, it seems the functionality was added to DOS's (ver 7/7.1) copy of EDIT when it was rewritten to remove it's dependency on QBASIC. Certainly, however, DOS 6.22's stock EDIT doesn't support the feature and just spits out the generic help screen when passed a /## parameter)
Edit: Also attached an image demonstrating the functionality :)
EDIT editing itself in /60-mode, showing about window with version info.. ediception? ^_^
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with `edit /40 file.exe` and related `/##` arguments, then trace the command-line argument handling and editor mode entry points. Compare the requested DOS behavior with the preferred true hex display/editing approach; done should include a defined binary-editing mode and coverage for the supported parameter behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100