On Wed, Aug 19, 2009 at 5:02 AM, Wen Pu wrote:
>
> Thanks for your detailed explanation.
Incidentally Deniz' explanation is also valid for Yi.
> I've never tried to find out how it works on Emacs, though I'm so used
> to hit C-g :)
If you want to bind C-g to some special functionality in dired,
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 293 by ddvlad: vim mode -- command operates only on first window
http://code.google.com/p/yi-editor/issues/detail?id=293
What steps will reproduce the problem?
1. open yi (only tested with vim emulation)
2. edit fileA
3. type
Updates:
Status: Accepted
Comment #5 on issue 291 by noel.kalman: Pending key presses are not
reliably shown
http://code.google.com/p/yi-editor/issues/detail?id=291
The fix has been rolled back, thus reopening so we won't forget this. As I
understand it, the preferred solution is
to
On Wed, Aug 19, 2009 at 3:40 AM, wrote:
>
>
> Comment #5 on issue 288 by jeffwheeler: Cursor status is not up to date
> http://code.google.com/p/yi-editor/issues/detail?id=288
>
> As m.niloc pointed out, this breaks the Vim implementation. Iin the cmd
> mode, it never even refreshes from
> the bo
Comment #6 on issue 291 by JeanPhilippe.bernardy: Pending key presses are
not reliably shown
http://code.google.com/p/yi-editor/issues/detail?id=291
I don't observe the issue, except in vim keymap at the very first keypress.
--
You received this message because you are listed in the owner
or
Updates:
Summary: Pending key presses are not reliably shown in vim keymap
Comment #7 on issue 291 by noel.kalman: Pending key presses are not
reliably shown in vim keymap
http://code.google.com/p/yi-editor/issues/detail?id=291
Oh, I understand it's fixed in emacs mode. It's still ther
Comment #8 on issue 291 by JeanPhilippe.bernardy: Pending key presses are
not reliably shown in vim keymap
http://code.google.com/p/yi-editor/issues/detail?id=291
To handle the "Unrecognized input: " case properly, Yi.Core.dispatch should
be
re-shuffled so that a fresh keymap is constructed
On Wed, Aug 19, 2009 at 3:38 AM, Jean-Philippe
Bernardy wrote:
> I'm going to explain the idea of how this works, so other people can
> fix details like this.
> Consider Yi.Keymap.extractTopKeymap. It constructs the keymap that's
> actually going to be
> used. Notice that it runs startKeymap once
On Wed, Aug 19, 2009 at 2:07 PM, Jeff Wheeler wrote:
> I really appreciate your explanation, and it helps me understand the
> situation much better.
I'm glad this helps. I'll try to do this more in the future.
>> It is a little annoying. Whenever a new buffer is created the start
>> actions hav
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 294 by jan2ary: Build issue: No instance for (Binary
(PL.PointedList (PL.PointedList Window)))
http://code.google.com/p/yi-editor/issues/detail?id=294
What steps will reproduce the problem?
1.Build yi from trunk
Instead of
Wed Aug 19 09:54:39 EDT 2009 Jeff Wheeler
* Begin adding startInsertKeymap to KeymapSet
Ignore-this: 9e91278e9a67f4f3765a6ba9f0098a61
M ./src/Yi/Keymap.hs -11 +11
M ./src/Yi/Keymap/Vim.hs -18 +27
M ./src/Yi/MiniBuffer.hs -2 +5
--~--~-~--~~~---~--~---
This doesn't resolve the issue --- it still doesn't work when opening
the initial buffer in Vim --- but the minibuffer mode works, at the
very least. I'll continue playing with it when I can.
Jeff Wheeler
--~--~-~--~~~---~--~~
Yi development mailing list
yi-devel@g
12 matches
Mail list logo
