ediff-mode should be in emacs state
On 20 Aug 2011, York Zhao wrote:
I believe ediff-mode should be in emacs state.
I think so, too. And here are some more: - wab-compilation-mode (used by tidy) - sldb-mode (slime debugger) - w3m-mode - gdb-breakpoints-mode - gdb-memory-mode And here I'm not so sure (because they don't do much): - gdb-disassembly-mode - gdb-frames-mode - gdb-locals-mode - gdb-registers-mode - gdb-threads-mode Michael
On Sat, Aug 20, 2011 at 1:13 AM, Michael Markert <[email protected]> wrote:
On 20 Aug 2011, York Zhao wrote:
I believe ediff-mode should be in emacs state.
I think so, too.
And here are some more: (...)
Shouldn't this be done the other way around? I mean - wouldn't a list of modes in normal state (with emacs state being the default) make more sense than a list of modes *not* in normal state? Cheers, -- José A. Romero L. escherdragon at gmail "We who cut mere stones must always be envisioning cathedrals." (Quarry worker's creed)
On 2011-08-20 14:00 +0200, José A. Romero L. wrote:
I mean - wouldn't a list of modes in normal state (with emacs state being the default) make more sense than a list of modes *not* in normal state?
If and only if the mode is used for editing text, it should come up in Normal state. If one handles editing modes as the default case, one has to list non-editing modes; if one handles non-editing modes as the default case, one has to list editing modes. In other words, it boils down to whether one looks at Emacs as a text editor with a very flexible extension language, or as an operating system with text editing as one of its applications. Evil implicitly takes the former view. -- Vegard
On 20 Aug 2011, José A. Romero L. wrote:
On Sat, Aug 20, 2011 at 1:13 AM, Michael Markert <[email protected]> wrote:
On 20 Aug 2011, York Zhao wrote:
I believe ediff-mode should be in emacs state.
I think so, too.
And here are some more: (...)
Shouldn't this be done the other way around? I mean - wouldn't a list of modes in normal state (with emacs state being the default) make more sense than a list of modes *not* in normal state?
This was discussed here as well: http://thread.gmane.org/gmane.emacs.vim-emulation/945 and resulted in the addition of `evil-default-state'. But I don't think it's useful to change for users unless a list of normal state modes is included as well. I'm not sure it would be less work to change the default state to emacs and gather normal state modes instead of emacs state modes. <tongue-in-cheek> And a vim-emulation that defaults to a non-vim state? Come on! </tongue-in-cheek> Michael
On Sat, Aug 20, 2011 at 3:13 PM, Michael Markert <[email protected]> wrote: (...)
And a vim-emulation that defaults to a non-vim state? Come on! (...)
Indeed :-D By the way, could you please add the following four: sr-mode sr-virtual-mode sr-tree-mode sr-buttons-mode These are for the Sunrise Commander file manager. Cheers, -- José A. Romero L. [email protected] "We who cut mere stones must always be envisioning cathedrals." (Quarry worker's creed)
On 2011-08-20 15:37 +0200, José A. Romero L. wrote:
On 2011-08-20 15:22 +0200, Michael Markert wrote:
And some more (sorry for the trickling):
- slime-xref-mode - slime-inspector-mode - slime-thread-control-mode
By the way, could you please add the following four:
sr-mode sr-virtual-mode sr-tree-mode sr-buttons-mode
Added in commit fdb4f66. -- Vegard
On 2011-08-20 01:13 +0200, Michael Markert wrote:
On 20 Aug 2011, York Zhao wrote:
I believe ediff-mode should be in emacs state.
And here are some more:
- wab-compilation-mode (used by tidy) - sldb-mode (slime debugger) - w3m-mode - gdb-breakpoints-mode - gdb-memory-mode And here I'm not so sure (because they don't do much): - gdb-disassembly-mode - gdb-frames-mode - gdb-locals-mode - gdb-registers-mode - gdb-threads-mode
Added in commit 81b532b. -- Vegard
On 20 Aug 2011, Vegard Øye wrote:
On 2011-08-20 01:13 +0200, Michael Markert wrote:
On 20 Aug 2011, York Zhao wrote:
I believe ediff-mode should be in emacs state.
And here are some more: ...
Added in commit 81b532b.
And some more (sorry for the trickling): - slime-xref-mode - slime-inspector-mode - slime-thread-control-mode Michael
And some more (sorry for the trickling):
- slime-xref-mode - slime-inspector-mode - slime-thread-control-mode
Hi Michael, I'm impressed that you seemed to know a bunch of emacs mode which is good and I think you must have been using emacs for a long time. So among the modes you have suggested adding to emacs state so far, which one do you like the best or you think really useful? Thanks, York
On 20 Aug 2011, York Zhao wrote:
I'm impressed that you seemed to know a bunch of emacs mode which is good and I think you must have been using emacs for a long time.
Well actually it's only roughly two years but as a student I see a lot different things and _of course_ there's an emacs mode for it :)
So among the modes you have suggested adding to emacs state so far, which one do you like the best or you think really useful?
There's so much great stuff but among the emacs state modes that would be - well obviously org-(agenda-)mode (and calfw a calendar view for it; cfw;calendar-mode) - magit the first git frontend I found that actually adds value (and monky its mercurial counterpart -- not as complete but still better than the rest) - ibuffer-mode; great buffer management - gnus; mail in emacs has a lot of benefits - and of course slime; it's just great And if you look for great apps: Take a look at anything and ace-jump-mode (find-char on steroids). Michael
participants (4)
-
José A. Romero L. -
Michael Markert -
Vegard Øye -
York Zhao