@billyfish

Slightly off topic, but highly related; has anyone looked into this:

https://github.com/widelec-BB/git-morphos

It's also a part of AROS contrib.


With that being said, I think it's great to have sgit as well.

@kas1e

Yes, it won't work as it is now. You could create an OS4 build target if you'd like to handle the OS4 icon / toolbar at build time.

Regarding "unpack and run": Does lha on OS4 handle symlinks? I might be doing something wrong here, but creating symlinks like evim -> vim (to start vim in simplified mode) doesn't seem to work on MorphOS.

What is the value of PROGDIR: when using symlinks?

@walkero

I'm not to keen on writing an application like that. The possible number of options would be infinite. This is Vim ;)

@trixie

Indeed, it's just that "VIM:" is used by the part of Vim that I haven't touched (and have been for many many years) and I try to do as little patching as possible.

About the installer; like I said, having an installer doesn't make it impossible to not use it.

@kas1e

I think it's nice to have an installer. It makes it possible for the user to do choices after build time, choosing toolbar themes for example, handling .vimrc, perhaps installing plugins and so on. It also makes it possible to create a single archive for all platforms, without the user having to manually pick binaries.

Of course it's not strictly necessary, it's still possible to do an "unpack and run" installation for users who wish to do so. And I kind of like writing installers anyway ;)

@redfox

I've started to migrate the whole thing to GitHub. There's still some work left on the installer to make it work on all platforms but building it should work.

It would be great if there are people interested in becoming a collaborator / creating pull requests.

https://github.com/sodero/MUI-Vim

@kas1e

Quote:

Sounds like clib2 is the way to go ;)

@kas1e

Yes, clib2 is a good idea.

Who's maintaining newlib?

@kas1e

Ah, my bad. I was grep:in through 8.1.x sources.

@kas1e

Very nice!

@kas1e

It's also called from f_setperm(..) in evalfunc.c.

@salass00

Ah, then $f is really null, nix, nada.

@kas1e

Good findings!

SetProtection is called indirectly (via mch_setperm) in several places in Vim.

The values $2 and $f are interesting. $2 is HSPARWD and $f is HSPA.

8 7 6 5 4 3 2 1 <- Bit number
h s p a r w e d <- corresponding protection flag

0 = flag set
1 = flag clear

@kas1e

Excellent. Thanks Mason.

@kas1e

I don't have any paypal account.

Whenever Trixie donates money to you for Vim, I will simultaneously donate the same amount to you for Dopus. To keep it simple, and avoid PayPal fees, we might as well bypass me

@kas1e
@trixie

Sounds good. I need to do some work on the installer to cater for all platforms.

@kas1e

Beautiful!

Are there any restrictions on how Masons icons can be used? Can we use them for AROS and MorphOS as well? I don't know what format OS4 icons are in. Are they just PNG:s or something else?

@kas1e

I think I have a fix for this. It's not a problem in the Amiga specific parts of Vim, it's about the general startup procedure of Vim that needs to be adapted so that we can support both console mode and GUI mode. And still support the possibility to start a shell from within the GUI version for '!' operations.

@nubechecorre

I think that's a good idea. The Amiga specific parts of Vim receive death threats from time to time and this could be a way of showing the world that these lines of code still matter.

Perhaps I should consider migrating the project to GitHub and giving it a proper name (not 'spaden' = 'the spade').

@kas1e

Fresh toolbar icons is a nice idea, I'm not the best artist out there, and I have a fondness for grey and dull things and I realize that most people don't :)

That could be something that the installer takes care of though. We could make it possible to select toolbar gfx at install time. But the default should definitely be Masons icons if he wants to / is willing to create new icons.