| Anonymous | Login | Signup for a new account | 11-10-2008 10:38 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000025 | [BusyBox] New Features | feature | always | 01-17-05 17:58 | 09-14-05 07:01 | ||||
| Reporter | pgf | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 1.00 | ||||||
| Summary | 0000025: vi-editing mode for ash | ||||||||
| Description |
as a long-time vi user, and an editor curmudgeon in general, i missed having a vi-mode in ash when doing development on or when using a busybox-based system, so i finally implemented it. it's not perfect, of course: no undo, no searching, the 'w' and 'b' commands are actually 'W' and 'B' (vi users will know what i mean), but it does have 'p', so you can put back what you've deleted (which was necessary to be able to enter "xp", something my typing demands that i do pretty often :-). it builds on top of emacs-mode -- so most (all?) of the emacs commands (e.g. ^A, ^F, ^B, ^N, ^P) still work while you're "inserting" in vi-mode. this is either a bug or a feature, but mostly it's just a fallout of the implementation. turning on CONFIG_FEATURE_COMMAND_EDITING_VI adds another couple of kbytes on an x86 system (which is roughly 25% more than emacs-mode by itself). with luck, i'm not the only person to think this is useful or worthwhile, and hopefully someone else can try it and offer a comment. |
||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |