search

momodalo / vimtouch

vimtouch
Apache License 2.0
350 stars 71 forks source link

:m+1 #9

Closed momodalo closed 11 years ago

momodalo commented 11 years ago

:m+1 (which worked under 1.5) alternatively works or acts as za…

reported by Thierry Guillemin

tguillemin commented 11 years ago

Let us say that the new Quickbar (on a Galaxy Nexus with JB) has an erratic behaviour : this affects randomly all keys (but not on each session).

Has there been a re-definition of the "touch zones" (please forgive my jargon) ?

momodalo commented 11 years ago

I add the :m+1 and :m-2 on my GS3 with JB and tried for several times. I didn't see issue there. There are two changes related to quickbar in the v1.6 are

  1. use vim's doCommand() to send ":" command instead of sending strings.
  2. the layout is redesigned to make quickbar position movable.

Do you see the issue after changing the quickbar position or it's default? I can modify a special version for you to use send string instead of doCommand. Can you help to test the apk?

tguillemin commented 11 years ago

I am sorry to be a nuisance for what is a minor glitch. I still have small incidents with the new quickbar, but they have changed :

Sincerely, this is a minor drawback, and I do not want to hamper your work, which means you should not lose time by modifying a special version (and do not forget that I do not code, I just write and Vimtouch is a godsend). Anyhow, if you find it useful to have me test this, I shall be very pleased to do so, however incompetent I am...

Thierry

PS : how is it possible in .vimrc to map the menu pencil which pops up the keyboard ?

On Thu, Sep 27, 2012 at 12:48 AM, David Tao notifications@github.comwrote:

I add the :m+1 and :m-2 on my GS3 with JB and tried for several times. I didn't see issue there. There are two changes related to quickbar in the v1.6 are

  1. use vim's doCommand() to send ":" command instead of sending strings.
  2. the layout is redesigned to make quickbar position movable.

Do you see the issue after changing the quickbar position or it's default? I can modify a special version for you to use send string instead of doCommand. Can you help to test the apk?

— Reply to this email directly or view it on GitHubhttps://github.com/momodalo/vimtouch/issues/9#issuecomment-8909308.

tguillemin commented 11 years ago

I may have a clue for the "problems" I encountered.

The shortcuts are left-aligned on the Quickbar keys. I may have (my fingers are not tiny) pressed on the characters and not in the center of the Quickbar key, thus overlapping on the neighboring key.

Hope that helps...

On Thu, Sep 27, 2012 at 12:48 AM, David Tao notifications@github.comwrote:

I add the :m+1 and :m-2 on my GS3 with JB and tried for several times. I didn't see issue there. There are two changes related to quickbar in the v1.6 are

  1. use vim's doCommand() to send ":" command instead of sending strings.
  2. the layout is redesigned to make quickbar position movable.

Do you see the issue after changing the quickbar position or it's default? I can modify a special version for you to use send string instead of doCommand. Can you help to test the apk?

— Reply to this email directly or view it on GitHubhttps://github.com/momodalo/vimtouch/issues/9#issuecomment-8909308.

momodalo commented 11 years ago

I just change the quickbar keys to gravity=center. Hope this can help to reduce the user scenario. Thank you for the clue and if you can give more update after upgrading to v1.7, it will be great for me to track this issue

momodalo commented 11 years ago

https://github.com/momodalo/vimtouch/commit/c5a2c5994f8e8dc28ece11fc337b3d7fd47e0e55

tguillemin commented 11 years ago

I shall. When will 1.7 be available ?

Another question (neither a bug nor a request, just for my information) : why did you choose to deliver VimTouch as a standalone application without BusyBox ?

Thanks again

On Sun, Sep 30, 2012 at 4:29 PM, David Tao notifications@github.com wrote:

I just change the quickbar keys to gravity=center. Hope this can help to reduce the user scenario. Thank you for the clue and if you can give more update after upgrading to v1.7, it will be great for me to track this issue

— Reply to this email directly or view it on GitHubhttps://github.com/momodalo/vimtouch/issues/9#issuecomment-9014096.

momodalo commented 11 years ago

I uploaded the v1.7pre https://github.com/momodalo/vimtouch/downloads You can use it to have a try before the formal release. VimTouch doesn't have busybox because it's just a editor only. However, I understand as we put the full vim runtime support in the VimTouch. More features will depend on a shell and extra commands(ex: grep). The shell and tools can be package as extra downloads and let user can download later.

br, David

momodalo commented 11 years ago

v1.7 released