[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #24053] start with vi keys by default if EDITOR matches vi?
From: |
dan pritts |
Subject: |
[bug #24053] start with vi keys by default if EDITOR matches vi? |
Date: |
Tue, 12 Aug 2008 20:03:51 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.16) Gecko/20080803 Camino/1.6.3 (like Firefox/2.0.0.16) |
URL:
<http://savannah.gnu.org/bugs/?24053>
Summary: start with vi keys by default if EDITOR matches vi?
Project: texinfo - GNU documentation system
Submitted by: danpritts
Submitted on: Tuesday 08/12/2008 at 20:03
Category: info
Release: 4.12
Priority: 5 - Normal
Severity: 3 - Normal
Item Group: enhancement
Privacy: Public
Open/Closed: Open
Assigned to: None
Status: None
Discussion Lock: Any
_______________________________________________________
Details:
The one really useful thing I did find in the manual page was that there is a
set of vi keybindings; i think that's great.
I'm not entirely sure this is the right thing to do, but it might be a good
idea to use these keybindings by default if the string "vi" is in the EDITOR
environment variable. I'd want to match /bin/vi, /usr/local/bin/vim, etc; so
just look for a substring.
If you do this, it might be a good idea to have a splash screen at the
beginning of the info program saying you've done so, and add a command-line
option to get rid of it, overriding whatever's in EDITOR.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24053>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #24053] start with vi keys by default if EDITOR matches vi?,
dan pritts <=