fangzhou | 13 Dec 16:03 2014
Picon

Problem with defadvice for evil-find-char

Hi developers,
    I'm tring to add some <Input Method Engine> support/compatibility for evil-mode recently.
    Now I'm having trouble with advising the evil-find-char (evil-find-char &optional COUNT CHAR).

    I want to automatically switch to an IME when typing _f_ in normal-mode, and switch back to English after entring the CHAR.  To do so, I add a before-advice to evil-find-char, but finding that the advice will actually work after entering the CHAR.

    Is there any mechanism which would enable me to exec some code right after typing f ? Redefine the function and kbd macro are no good if there is a better way.
                                                                                                                       
                                                                                                                    Regards
_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Óscar Fuentes | 1 Dec 16:23 2014
Picon

Visual mode permanently activates transient-mark-mode

Sorry for reporting this bug here, but BitBucket refuses to work saying
"CSRF verification failed. Request aborted." for whatever I try to do on
it.

I have transient-mark-mode deactivated on my .emacs. Entering Visual
mode activates it (which is fine) but after exiting Visual mode it
remains active (i.e. `transient-mark-mode' var is assigned `t'.)

In Evil's sources I see some complex machinery dealing with
transient-mark-mode, so it is not a case of the devs assuming that all
users have transient-mark-mode on its default setting (active).

To reproduce:

emacs -Q

load and activate Evil.

M-x transient-mark-mode
C-h v transient-mark-mode

Check that the value is nil

v ESC (enter and exit visual mode)

C-h v transient-mark-mode

Now the value is t.
Tom Short | 30 Nov 03:04 2014
Picon

spacemacs and other approaches for organizing emacs packages

Hi everyone,

I've been looking to update the mess that is my .emacs file. Looking
around, there are many new Evil packages and new ways of managing
them. I've come across the following as a rather ambitious way to
integrate Evil into many modes:

https://github.com/syl20bnr/spacemacs

Anyone have an opinion on it? I'm trying it briefly. I like the
discover-ability, but it's a lot of new muscle memory to learn.

Any other suggestions for organizing .emacs? I mainly use Org, ESS,
and of course Evil.
Alexander Shukaev | 14 Nov 16:25 2014
Picon

eww-link-keymap

Hey!

`eww-link-keymap' occurs when one places point over some hyperlink. It looks like `eww-link-keymap' takes precedence over `evil-normal-state-map' and friends. Why? How to avoid it?

Thanks in advance,
Alexander
_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Óscar Fuentes | 10 Nov 16:29 2014
Picon

Naughty undo-tree

From time to time undo-tree behaves strangely. With a single undo step
it can undo a char insert or whole paragraphs that took several minutes
to enter. Worse, sometimes it fails while trying to redo with:

  primitive-undo: Unrecognized entry in undo list undo-tree-canary

Combined with one of those huge undo steps, this amounts to serious data
loss.

Does someone else experience these problems?

Is Evil handicapped in some way if I stop using undo-tree?
Eric S Fraga | 10 Nov 14:20 2014
Picon
Picon

evil mode with pabbrev: how to select alternatives

Dear all,

Using pabbrev in a buffer with evil works fine if the default suggestion
is desired, simply by hitting TAB.  However, if I hit TAB twice, this
brings up the pabbrev buffer with alternate selections from which an
alternative is selected by typing a digit.  This buffer comes up in evil
mode which is not appropriate.  

I would like for evil to be disabled in this buffer.  I have tried

      (add-to-list 'evil-emacs-state-modes 'pabbrev-mode)

but this appears to have no effect.  I can, of course, type C-z and then
the choice but this is somewhat clumsy.

Any suggestions?

Thanks,
eric

--

-- 
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.50.1 + Ma Gnus v0.12 + evil-git-999ec15
: BBDB version 3.1.2 (2014-04-27 15:05:20 -0500)
Alexander Shukaev | 7 Nov 17:59 2014
Picon

A few questions on Evil

Hello,
everyone!

I have 2 questions on Evil:
  1. How to wipe out all the default key maps which are present in `evil-maps.el' preferably with as few calls as possible? Note that I'm aware of how to do that with 1 by 1 `undefined' assignmetns, but I'm looking for something simpler.
  2. Is this

    (evil-define-key 'normal global-map (kbd "<left>") 'do-something)

    indentical to

    (define-key evil-normal-state-map (kbd "<left>") 'do-something)

    ?
Regards,
Alexander.
_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Trevor Murphy | 1 Nov 19:26 2014
Picon

[PATCH 2/2] Remove manual override to `evil-mode' docstring.

The `define-globalized-minor-mode' macro generates a docstring that
covers the same information, includes references to more functions, and
fits the standard used by many global minor modes.
---
 evil-core.el | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/evil-core.el b/evil-core.el
index cb440b7..7b7309c 100644
--- a/evil-core.el
+++ b/evil-core.el
 <at>  <at>  -193,12 +193,6  <at>  <at>  To enable Evil globally, do (evil-mode 1)."
     (ad-update-regexp "^evil")
     (with-no-warnings (evil-esc-mode -1))))

-(put 'evil-mode 'function-documentation
-     "Toggle Evil in all buffers.
-Enable with positive ARG and disable with negative ARG.
-See `evil-local-mode' to toggle Evil in the
-current buffer only.")
-
 (defun evil-change-state (state &optional message)
   "Change the state to STATE.
 If STATE is nil, disable all states."
--

-- 
2.1.2
Trevor Murphy | 29 Oct 17:15 2014
Picon

[Bug?] Evil does not activate when loaded via customize

Hi, list!

I'm perverse and want to install Evil via package.el and load it 
via customize.  I notice that Evil does not turn on at startup 
when I customize evil-mode to t.  I still have to explicitly call 
(evil-mode 1) in my init-file.

Is this known behavior?  If so, is it a bug?  If so, can I fix it 
somehow?

Note: I know the documentation explicitly tells me to install Evil 
like so:
      (add-to-list 'load-path "~/.emacs.d/evil")
      (require 'evil)
      (evil-mode 1)
As said, I'm just being perverse.  Thanks for any pointers!
--
Trevor Murphy, ASA, MAAA
GnuPG Key: 0x83881C0A
Jabba Laci | 19 Oct 15:56 2014
Picon

tildes + helm integration

Hi,

I'm new to the list and Evil. In the past 3 days I could customize lots of things. I would have 2 questions:

1) Is there a way to show blue tildes (~) after the last line of a file? I miss that feature.

2) I installed the Helm plugin but it stole some key bindings that I'm used to. For instance, "gf" in Evil opens the file under the cursor, while "gf" in Helm means "find a file". So I uncommented Helm in my config file, but I'd like to use it. Do you have a solution how to prevent it from stealing key bindings? In my config file I also changed the order of imports (first Helm then Evil, then vice versa) but it didn't help.

Thanks,

Laszlo
_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
David Nebauer | 18 Oct 10:33 2014

T, t, F, f operators crash into debugger

When vim operators T, t, F and f fail in vim because the target cannot 
be found, it triggers an error which sounds a bell, but otherwise does 
not interrupt editing.

In evil, on the other hand, when T, T, F and f operators fail in evil 
they cause the debugger to open in another buffer with the lisp error 
"Can't find X" where X is the target character.

To an emacs/evil newcomer like me it seems a predictable error like this 
should not cause code execution to crash and invoke the debugger. My 
naive suggestion would be that it should indicate an error (perhaps 
using the system bell or returning an error message in the minibuffer) 
but continue running without crashing in to the debugger.

I accept that it takes only the press of the 'q' button to close the 
debugger and return to editing. Nonetheless, that is one button more 
than vim. Further, because I associate the debugger with a program 
crash, every time T, t, F or f fail in evil I am briefly jarred out of 
my editing mindset.

Is there any way to prevent a failed F, f, T or t operation from 
crashing and invoking the debugger?

Gmane