If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Suggestion for publishing (beta) changes

I would like to suggest a few things here to improve the cooperation in working on VEDIT's macros etc.

Reason: It's a bit difficult to get all and every message here in the forum and to check if there is a change to a macro or so included.

One means to improve that may be a "sticky" thread at least here in the beta forum,
containg only announcements of new or changed macros.

Hmmm, even that may not be an optimal solution...
So please let me imagine a bit further.

What about a version control system for macros and other text files regarding Vedit?

To make a bit clearer what I mean I created a demo for that (@Ted: I hope it's o.k. to publish it that way. If not, please let me know and I'll delete it immediately)

I'm already using Mercurial (and TortoiseHg as GUI) - a distributed version control system for some of my software developments.

So I created a Mercurial repository containing my main Vedit installation, but without the executables and without the user parts stored under %APPDATA%).
To fill it with a bit of life I began with Vedit 6.21.1 and went up to 6.21.3 and further.

This is an excellent suggestion and thank you for the demo.
Certainly a Sticky listing the latest macros would be easy to post. Or perhaps two Stickies - one in alphabetic order and one in chronological order.

I mentioned this to Phil (my brother and our CIO) and he suggested using Git and more specifically Github. Don't know about other VCSs, but Git allows forking a project (e.g. one specific macro) so that you could e.g. have your own versions of a VEDIT macro. Later, if I merge in your and changes from others, the fork closes and we again have just one version of the macro.

Phil also asked if VEDIT could automatically download updates, and I said "Not yet".
I also understand that many VEDIT users wouldn't want critical macros to automatically update.