what about emacs
bastl
I just read the README of eeedit. It states clearly that xemacs will
be supported in a later state. That is not a goal of mine, but since
the protocol is implemented by emacs too, this is of course a logical
thing. So here's an idea how to continue, keeping both projects:
eeedit is the independent "server" component (plugin) for both vim and
emacs.
vimplugin depends on eeedit and provides special mappings,
configurations etc for vim.
emacsplugin wil be done at some time by emacs people.
The ironical thing is, that vimplugin (aka vimplugin/branches/
vimclient) had the server component in the first place, while the
killer feature of "eeedit" is the GTK-embedding of vim, which will get
hard for emacs, if i get it right.
So this could be a compromise:
1) Factor out vim things from eeedit and commit it to vimplugin.
2) Rework vimplugin to use eeedit.
3) As a demonstration, showing console emacs using eeedit. Then wait
for emacs ppl to start emacsplugin.
All this would be consistent with naming.
What dou you think?
Sebastian.
bastl
David Terei
1) Very little code at moment that splitting up will make life difficult.
2) To be honest I can't see us supporting emacs for ages if ever, perhaps
Nageshwar disagrees with me here since I think he would like to support both
but I myself just want to work on Vim. Emacs wouldn't be a focus until Vim
was working well and even then I'm not sure about it since I don't think any
of us use it so we wouldn't have much motivation for it.
Anyway, see my other email I just sent in the 'Current state of the project'
thread.
Best regards,
David Terei
Edward L. Fox
On 10/2/07, David Terei <david...@gmail.com> wrote:
>
> No I don't like this at all.
>
> 1) Very little code at moment that splitting up will make life difficult.
> 2) To be honest I can't see us supporting emacs for ages if ever, perhaps
> Nageshwar disagrees with me here since I think he would like to support both
> but I myself just want to work on Vim. Emacs wouldn't be a focus until Vim
> was working well and even then I'm not sure about it since I don't think any
> of us use it so we wouldn't have much motivation for it.
Yes, I agree. IIRC I also expressed the same opinion in some other
thread before. In order to support the GVim embedding well, the
NetBeans is far from enough, we have to write some customized script
on Vim side. So the whole solution will not be editor-independent any
more.
> Anyway, see my other email I just sent in the 'Current state of the project'
> thread.
>
> Best regards,
>
> David Terei
>
> [...]
Well, most mailing lists, especially mailing lists in open source
communities, are using bottom-posting and interlaced-posting. Bram
also hates top-posting very much. Shall we also obey this custom?
Best regards,
Edward L. Fox
Nageshwar M
There is a reason why I want to give support for other editors. There
is a lot of difference between the guy who depends upon others and the
guy who serves others needs. I want our eeedit to be the second type.
If we change our mission to support emacs also, we can improve the
popularity and can make a lot of other editors to follow our protocol
(I dont know much about other editors though). And our user community
will also grow bigger. There is no need to put much effort to make our
software work for other editors as we are strictly
following the protocol, atleast I hope so. I also agree that, it takes
a very long time to go that far. First, lets do some satisfactory
work on vim. Before that, lets decide about the merging the two
projects. Please fix some timings to discuss. Saturday afternoon is
fine for me.
--
Best Regards,
Nageshwar M.
--
Best Regards,
Nageshwar M.
bastl
schrieb "Nageshwar M" <whatis...@gmail.com>:
> If we change our mission to support emacs also, we can improve the
> popularity and can make a lot of other editors to follow our protocol
> (I dont know much about other editors though). And our user community
> will also grow bigger.
True. We should keep that in mind.
> There is no need to put much effort to make our
> software work for other editors as we are strictly
> following the protocol, atleast I hope so.
Twofold: Following the protocol is ok and easy, but it's dangerous to
hardcode vim-specific things into the independent EE-client. The clean
way of doing it would be an independent eclipse plugin that acts as a
client to vim or emacs. This plugin would provide an extension point
for any external editor plugin. The design of that
interface/extensionpoint could be complicated.
So I would follow David to stick to vim for the beginning. Let's start
small: I wouldn't even know how to use emacs with the EE-protocol. I
looked around a bit to try to build a very simple prototype but I
didnt
find any docs ... Is anyone able to do a quick prototype ?
Sebastian.
Am Wed, 3 Oct 2007 00:09:37 +0800
schrieb "Edward L. Fox" <edy...@gmail.com>:
> Well, most mailing lists, especially mailing lists in open source
> communities, are using bottom-posting and interlaced-posting. Bram
> also hates top-posting very much. Shall we also obey this custom?
I agree very much, but not because of Bram (what a strange
argument :-) ) ...