Issue 89663 - vi key bindings
Summary: vi key bindings
Status: CLOSED WONT_FIX
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.0 Beta
Hardware: All All
: P3 Trivial with 3 votes (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@framework
URL:
Keywords:
: 4183 5686 29797 (view as issue list)
Depends on:
Blocks:
 
Reported: 2008-05-19 23:44 UTC by viperoo
Modified: 2010-06-16 00:09 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description viperoo 2008-05-19 23:44:47 UTC 
This is probably a grave case of positive thinking ... - there must be more
people than me that would like to have most important vi key bindings when
editing ...

So please let all us who want those bindings have them. (And let all others stay
away from them ...)
Comment 1 Dotan Cohen 2010-03-08 22:14:07 UTC 
Note that Abiword has VI keybindings (and Emacs too). It works great and greatly
increases one's productivity. I think it is a natural for OOo.
Comment 2 eric.savary 2010-06-15 02:45:43 UTC 
@viperoo: you are allowed to dream but we (OOo core developers, QA, UX people)
have to keep a certain healthy mainstream way.

Beside the fact that *I* (be sure I am not the only one!) find the vi shortcuts
sometimes totally awkward (even geeky gamers have invented more usability
choosing AWSD than the poor inline HJKL of vi) I LOVE vi!

Because vi is a great *editor* just like Emacs is.

But sorry... "Editor"? I am not aware that we have such a product... We have a
word processor (Writer) a spreadsheet (Calc) a presentation program (Impress)
and more but no *editor*.

Or would you request an export filter from Draw Bitmap -> ASCII Art? (just
because it's the same level of interest and effort)

To the rhetoric of your report: "*let* all us who want those bindings have
them". Of course we *let* you! We let you define a specification which says for
which app this applies, for which functions, design a visual mode, define the UI
for this visual mode, implement the whole stuff, QA it and integrate it!

In other words, please, feel free to build a team which will implement this as
an extension and *let* us, core developers:
- fix our crashes
- make main features better
- implement features a *real* number of people want since years.

Your request is VALID but the answer is unfortunately WONTFIX.
Comment 3 eric.savary 2010-06-15 02:46:17 UTC 
.
Comment 4 eric.savary 2010-06-15 02:47:04 UTC 
closed
Comment 5 eric.savary 2010-06-15 23:24:43 UTC 
*** Issue 29797 has been marked as a duplicate of this issue. ***
Comment 6 eric.savary 2010-06-15 23:26:50 UTC 
*** Issue 4183 has been marked as a duplicate of this issue. ***
Comment 7 eric.savary 2010-06-15 23:28:20 UTC 
*** Issue 5686 has been marked as a duplicate of this issue. ***
Comment 8 viperoo 2010-06-16 00:09:35 UTC 
OK, thanks. I have sent this on the the VIM devel mailing list to see if someone
there has time and interest to do it.

I got to much myself to do with Emacs devel so I can't take this, but thanks for
telling us that the idea is welcome and that tested code will be welcome. That
is great!

(I am using Emacs with vi key bindings, of course ... ;-)