> Date: Thu, 6 Apr 2017 13:40:40 -0400
> From: Brandon Amos
> To: implementations-list@lists.ourproject.org, emacs-orgm...@gnu.org
> Subject: [O] Evil-mode keymapping being overridden by org-mode
> Message-ID: <20170406174040.ga7...@gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi, I
Hi Brandon,
I'm guessing you're using evil-org-mode. This sounds like a symptom of that
package, which has "t" bound to org-todo. I don't think you've tried to do
this with just evil installed, because not only can I not reproduce it, but
C-a a doesn't even open the agenda.
Eivind
On Thu, Apr 6,
I have found a solution to this problem.
This keymapping was coming from the spacemacs org-mode layer:
https://github.com/syl20bnr/spacemacs/blob/bd7ef98e4c35fd87538dd2a81356cc83f5fdi02f3/layers/%2Bemacs/org/local/evil-org/evil-org.el#L134
In my init, this mapping can also be over-written to `ev
Frank Fischer writes:
Ahhh, yes, the capital S does it. I've got to get a better handle on
these text objects, but I imagine it has something to do with s
capturing more than S does?
In any case, thank you. I'm exploring vim through evil-mode and I've
liked the experience so far (though not enou
It does work for me (although I have to use ysSfprint [note the capital
S], for some reason). So, please provide a complete example to reproduce
the problem, including your Emacs, Evil and evil-surround version and a
test file (otherwise it's hard to reproduce the problem).
Frank
Am 05.04.2015 um
max6166 writes:
> Thank you so much, Oscar. The above method is working great so far.
You're welcome.
> I was thinking of adapting your code for other purposes, but I am concerned
> about your warning. What are the potential problems with this code?
The problem with advising `call-interactive
Óscar Fuentes wanadoo.es> writes:
> Another approach is to advice `call-interactively'. Again, untested
> code:
>
> (defvar maybe-enter-insert-mode-commands
> '(org-insert-heading)
> "List of commands that trigger insert mode.")
>
> (defun maybe-enter-insert-mode (command &rest args)
> (wh
max6166 writes:
> Thank you very much, Oscar. The above code gives the error:
>
> add-hook: Wrong type argument: symbolp, (evil-visual-post-command
> linum-update-current t) [2 times]
That's because there is a missing quote. The correct call to add-hook
is:
(add-hook 'post-command-hook 'maybe-e
Óscar Fuentes wanadoo.es> writes:
> I would try adding a function to `post-command-hook' that enters
> instert-mode when `insert-command' is in a list of symbols.
>
> Totally untested code:
>
> (defvar maybe-enter-insert-mode-commands
> '(org-insert-heading)
> "List of commands that trigger
Óscar Fuentes writes:
> I would try adding a function to `post-command-hook' that enters
> instert-mode when `insert-command' is in a list of symbols.
s/insert-command/last-command
___
implementations-list mailing list
implementations-list@lists.ourp
max6166 writes:
> There are many emacs commands after which I almost always immediately want
> to insert text. This often requires entering insert mode after the initial
> command.
>
> Is there any way to instead enter insert mode automatically after certain
> commands?
>
> For example, in org-mo
On Monday, 10 Nov 2014 at 13:20, Eric S Fraga wrote:
[...]
> I would like for evil to be disabled in this buffer. I have tried
>
> (add-to-list 'evil-emacs-state-modes 'pabbrev-mode)
A little more digging and I realised that it should have been
'pabbrev-select-mode in the above. Using
Am 14.09.2014 um 00:17 schrieb Russell Dunphy:
> Hi, new to Emacs (Evil-mode persuading me that it’s worth attempting the
> switch). Have a few questions.
>
> I’m trying to get adhoc key mappings working as they would in vim.. So for
> example if I open a new Clojure file I might want to quickly
Frank,
I installed evil as a git submodule. I had not ran make. Running it seemed
to fix the issue, thanks!
Keep up the awesome work, this piece of software rocks!
- Marcelo.
On Mon, Mar 25, 2013 at 2:13 PM, Frank Fischer wrote:
> On 2013-03-25, Marcelo de Moraes Serpa wrote:
> > --=
On 2013-03-25, Marcelo de Moraes Serpa wrote:
> --===1345460708==
> Content-Type: multipart/alternative; boundary=14dae93991634b71a304d8c55214
>
> --14dae93991634b71a304d8c55214
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hey Frank, thank you for the reply.
>
> I have updated to
Hey Frank, thank you for the reply.
I have updated to the latest revision, and while this conf option does work
in the terminal, it doesn't work from the Cocoa GUI.
However, I have an old version of evil that does work fine both in the
terminal and Cocoa with this setup. It's at revision
0f53eebc
On 2013-03-25, Marcelo de Moraes Serpa wrote:
> Hi list,
>
> I'm using Emacs on OSX (GNU Emacs 24.3.1 (x86_64-apple-darwin, NS
> apple-appkit-1038.36)), with evil-mode. I'm having an issue with the "C-["
> combo for ESC. On Emacs 23, it used to work fine, and exit from insert mode
> correctly when
On Sun, Jan 06 2013 (01:25), Daniel Friedman
wrote:
> Hi everyone,
>
> I'm quite new to hacking elisp (and this mailing list), so please bear
> with me!
>
[23 lines snipped]
>
> There are two main things that I need help with:
> 1. Why am I getting this error, even when there is a word under t
On 2012-07-17, Vegard Øye wrote:
> The `evil-default-cursor' variable is initialized to the current
> cursor color when Evil is loaded. This is to ensure that if another
> state changes the color, it is changed back by Normal state.
>
> http://article.gmane.org/gmane.emacs.vim-emulation/919/
>
On 2012-07-17 09:03 +0200, Frank Fischer wrote:
> On 2012-07-16, Michael Markert wrote:
>
>> change the default value of `evil-default-cursor' to nil and evaluate
>> the code above instead always if `evil-default-cursor' is nil
>
> To be honest, I have no idea why we've once set the default value
On 2012-07-16, Michael Markert wrote:
> For a less makeshift version I'd suggest either
>
> 1) change the default value of `evil-default-cursor' to nil and evaluate
>the code above instead always if `evil-default-cursor' is nil
I would go with this, setting the default value to either nil or
Hi Keshav,
On Mon, Jul 16 2012 (04:12), Keshav Kini wrote:
> evil-mode is so evil that it has stained my cursor black, as black as
> the soul of evil-mode!
[...]
> Then I suspected that the theme was just badly designed. But on a hunch,
> I tried commenting out the line "(evil-mode 1)", and r
On Mon, Jul 16, 2012 at 10:12:22AM +0800, Keshav Kini wrote:
> How can I fix this? Is it a bug in evil-mode, or am I just doing
> something wrong?
I'm not 100% sure, but google for the "evil-default-cursor" variable,
and also maybe "set-cursor-color".
Actually, here is a very relevant link
http:/
From: Simon Carter
Subject: Evil-mode and camelcase movement
Date: Sat, 2 Jun 2012 20:20:40 +0100
> I was wondering if there was a canonical method for allowing camelcase and
> underscore word movement in evil-mode.
If you are looking for Evil implementation of camelcasemotion.vim
(http://www.v
On Sat, Jun 02 2012 (21:20), Simon Carter wrote:
> I was wondering if there was a canonical method for allowing camelcase
> and underscore word movement in evil-mode.
Not to my knowledge.
> I've looked at the suggestion in
> http://slashusr.wordpress.com/2011/09/15/heretical-confessions-of-an-
On 2011-10-29 20:58 +0100, Frank Terbeck wrote:
> There was one thing though, the mode line tags, which didn't quite
> fit into my existing mode line setup. ... I guess my real question
> is: Will the `evil-*-state-tag' stuff be a stable way to configure
> this?
Yes. Most of the properties of a s
On Tue, Jul 26, 2011 at 19:44, Vegard Øye wrote:
> On 2011-07-26 09:45 +0200, Nikolai Weibull wrote:
>> If, however, there are clashes between Dired mappings and Evil
>> movement mappings, then they need to be resolved and looking at
>> NERDTree for suggestions might make sense in this case.
>
>
On 2011-07-26 09:45 +0200, Nikolai Weibull wrote:
> If you want to add NERDTree-specific mappings to Dired mode, then
> by all means add them to your .emacs, but keep them out of Evil.
I agree. My only concern was any Dired commands that might have been
overwritten by the vi bindings for "h", "j"
On 2011-07-25 18:57 +0200, laputa5 wrote:
> It is caused by that for some reason my recentf-mode is always on,
> and it always returns Emacs in `evil-initial-state-for-buffer'.
> so I changed the function a bit, but now I think about it, it's
> easier to just do the following, or remove it in the
On Sun, Jul 24, 2011 at 19:31, Vegard Øye wrote:
> On 2011-07-23 08:15 +0200, Neeraj Sharma wrote:
>> Regarding dired mode, I do see its in emacs state by default but
>> i find it somewhat confusing for the fingers to go back and forth
>> between j/k (other modes) and n/p (dired).
> Dired now co
>> In the following case, doing a "va(" or "vi(" doesn't work.
>> (aaa "bb[]bb" aa)
>> where [] is the cursor.
>
> Fixed in commit 6e74963.
Thanks for fixing this. It works great now.
> The state a mode comes up in can be changed with
> `evil-set-initial-state', e.g.,
>
> (evil
On 2011-07-23 08:15 +0200, Neeraj Sharma wrote:
> Regarding dired mode, I do see its in emacs state by default but
> i find it somewhat confusing for the fingers to go back and forth
> between j/k (other modes) and n/p (dired).
Dired now comes up in Normal state by default (commit 9a44dbe).
As a
On 2011-07-24 02:03 +0200, laputa5 wrote:
> After I did a 'git pull' today, I noticed most files/modes are
> opened with 'emacs' state by default, which wasn't the case
> before I pulled the updates. Is this intentional?
Yes, but it's not permanent. I intend to give most Emacs modes
vi bindings,
Thanks for the reply Vegard. I just pulled the latest and it does seem to
fix my issue with windows shell mode.
Regarding dired mode, I do see its in emacs state by default but i find it
somewhat confusing for the fingers to go back and forth between j/k (other
modes) and n/p (dired). Moreover, ev
On 2011-07-21 22:36 +0200, Neeraj Sharma wrote:
> Thanks for the wonderful evil mode.
Thanks for your interest in Evil. Please note that Evil is under
development and some features (e.g., Ex) are still missing.
You can always get the latest updates with "git pull".
> Shell-mode on windows: It bl
ad. 2) I think that the problem is that Dired buffers are not started
in Emacs-mode per default (they are started in normal mode -> new
keymap). Try C-z inside the dired buffer and then everything should
work. The Dired stuff should already be fixed in commit 51e4b94d ! Try
updating your evil repo.
36 matches
Mail list logo
