Hi all!

Are there any VIM users around here that would be interested in a current version of VIM with a MUI GUI? If that's the case then you could try this out:

Spaden

Please keep in mind that this is still not done and that it might not work at all for you (it hasn't blown my machine up yet though). It needs more testing, that's why I'm writing this . The source code is also there if anyone would like to improve on it, or port it to AmigaOS or AROS (which should be trivial, I hope).

How do you start it in gui mode? :)

Really nice, I will have a try and give you feedback.
Vim is not emacs, but better than nothing ;)

[ Edited by eliot 10.02.2017 - 05:09 ]

Quote:



Like this: "vim -g"

or use gvim (I think I included a script like that?)

Quote:

Thanks!

Awesome, I need to try this!

Any chance of a "normal" vim that can run directly in the shell aswell?

After installation your can just start vim from shell

Quote:

I've tried exactly that and still only got vim in a shell...

Quote:

Hmm, strange. What does Snoopy / The debug log say?

Quote:

Do you have MCC_TheBar installed by the way? It's required and VIM won't shout (except in the debug log) if it's missing as it is right now.

OK, seems better with that mcc installed. There should be some better handling for the case it's missing because currently gives you a quite messed up shell mode (scrambled menus for instance).

There are also some easily spotted issues:

1) the installer spits an error if there's no work: partition around

2) I tried loading up a C file and moving the cursor over the text causes some graphics trash.

Quote:

Thanks for your input!

I'll (try to) fix #1.

Re #2: What font are you using?

Quote:

I think I see what you see now. A temporary workaround would be to use a bitmap font instead (now I assume that you're not, I might be wrong of course).

About the scrambled shell mode; Ctrl+L should "unscramble" things.

so, where do I set the font?

Quote:

It's using the monospace font in the MUI settings. I just realize that there's no MUI settings entry in the menu and that not everyone will have the settings gadget in the window title bar. I obviously assume way to much

New version uploaded. User is now informed when MCC_TheBar is missing and the installer no longer assumes the presence of "Work:". And a newer version of VIM, but that hardly matters in this case.

2017-02-12:
- Graphical glitches when using non bitmap fonts fixed
- Bold text support
- Update to VIM 8.0.329

Quote:


Good progress. Another thing, you should not set the EDITOR env: variable without asking the user. Just because one wants to try out vim, it doesn't mean one wants to make it the default system editor.

Quote:

True about the EDITOR, very web browser like behaviour. Got rid of it. Also made the MUI settings / about dialogs accessible from the menu.

A few questions about running vim from the shell.

The biggest problem I have is that vim seems to default to a size of 80x25 (or something similiar) no matter how big my shell-window is. Is there any way around this?

My second problem is that the arrow-keys doesn't work from a normal shell (they do work if I run it from within ksh though), I can use 'hjkl' to move the cursor but then I need to jump in/out of insert-mode all the time, and I'm used to just being able to move the cursor while in insert-mode with the arrow-keys. Is there anything I can do to get them working from the normal shell?

Quote:

I don't know the answer to any of the above I'm afraid. The reason I did spend time doing the MUI GUI was that the console version was very far from what you expect from VIM on other platforms. Maybe I'll spend some time later on to see if I can improve the console version. Or maybe someone else (you?) can have a look, it looks as if the Amiga parts in VIM could use some love (it's probably been a while).

I'm afraid I can't help much by actually doing any coding, since I don't know C. But I would be happy to help out in any way I can (testing and tweaking configurations) if someone wanted to try and "fix" vim to work in a normal shell. The gui-version works great but I just prefer to do my text-editing directly in the terminal I'm using, it's what I'm used to on other platforms!

But for now I have set the env-variable TERM to gui so it always opens the gui-variant.

I did try a few things like setting t_ku=^[0A (and \233A) and similiar tricks I found on the web but none of those made any difference from my testing, but I will continue to try and figure out a way to get the arrows working. The "size" of the window will probably need some updates in the code though, according to the docs it has worked on Amiga in the past (not so surprising since vim originated on the Amiga after all).

[ Edited by fx 15.02.2017 - 21:32 ]

Quote:

I understand the terminal part (I've never really used gvim before), and I agree, we should really have a fully working VIIM in a shell someday. About the help part; using, tweaking and giving feedback is very valuable.

BTW:

2017-02-15:
- Plugin autoloading now works
- Reconfigured to make the MatchParen (and probably others) plugin work

I did checkout your repository and played around a bit with compiling vim with different options, had some trouble getting your MUI-GUI-code to compile (complained about _ParseIFF_v1 or something which I couldn't find any reference to anywhere :/) so I simply compiled it without GUI for now. Well to the point, I actually managed to get the arrowkeys-working in a normal shell, thing is - I'm not exactly sure what I've done :)

Gonna make some more tests and report back here with my findings.

It still can't detect the size of the window though

Quote:

Sounds excellent! Let me know if you find anything interesting.