Any ETA for a Mercurial server ?

[Tony Mechelynck]

Hi Christian,

Last night openSUSE Tumbleweed has updated more than 9000 packages,
and their Vim is now at version 9.1.993; but of course it is not
exactly configured the way I'd like it. So I'm faced with a dilemma :
either remain (maybe forever) with the 9.1.873 which I configured
myself and didn't change since your Mercurial server went down, or use
the openSUSE version, which will always be a little behind the times
(though not as far behind as mine) and a little different from what I
like best.

I don't want to press you, but can you help me out of this dilemma ?

Best regards,
Tony.

[Christian Brabandt]

Let me check back. I'll get back to you

Thanks,
Christian
--
It's great to be smart 'cause then you know stuff.

[Tony Mechelynck]

P.S. When I try "hg in" from http://hg.vim.org/ (my new default server
address) I get 403 Forbidden, and from hg://256bit.org/vim (which I
just tried, just in case) I get 404 Not found.

Best regards,
Tony.

> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Z4QWr0YxsX82588C%40256bit.org.

[Tony Mechelynck]

On Sun, Jan 12, 2025 at 8:23 PM Christian Brabandt <cbl...@256bit.org> wrote:

[…]

> It's great to be smart 'cause then you know stuff.

The advantage of being smart is that you can play dumb. The opposite
is totally impossible.
— Attributed to Woody Allen.

[Eric Pruitt]

On Sun, Jan 12, 2025 at 04:33:28PM +0100, Tony Mechelynck wrote:
> So I'm faced with a dilemma : either remain (maybe forever) with the
> 9.1.873 which I configured myself and didn't change since your
> Mercurial server went down, or use the openSUSE version, which will
> always be a little behind the times (though not as far behind as mine)
> and a little different from what I like best.

Out of curiosity, why isn't using Git an option?

Eric

[Tony Mechelynck]

Because I've tried it in the past (for a different software package
housed on github), and it doesn't work the way I think. Many commands
do one thing in Mercurial and the opposite in git(1) and I'm sure to
mix them up. Makes me feel that at 74 years old (next Saturday) I'm
too old to learn one more version-control system that works contrary
to my fingers' reflexes. Maybe I could if its command names were more
different.

(1) E.g. git pull is the equivalent of hg fetch; git fetch is the
equivalent of hg pull. I'm sure there are others, but I'm not sure
exactly which, which makes me wary of git.

Best regards,
Tony.

[Christian Brabandt]

On Mon, 13 Jan 2025, Tony Mechelynck wrote:

> P.S. When I try "hg in" from http://hg.vim.org/ (my new default server
> address) I get 403 Forbidden, and from hg://256bit.org/vim (which I
> just tried, just in case) I get 404 Not found.

It has just been re-enabled, see: https://www.vim.org/hgweb/vim/
I'll update the homepage soon.

Thank you Marc!

Thanks,
Christian
--
Without followers, evil cannot spread.
-- Spock, "And The Children Shall Lead", stardate 5029.5

[Tony Mechelynck]

On Sun, Jan 19, 2025 at 10:29 PM Christian Brabandt <cbl...@256bit.org> wrote:
>
>
> On Mon, 13 Jan 2025, Tony Mechelynck wrote:
>
> > P.S. When I try "hg in" from http://hg.vim.org/ (my new default server
> > address) I get 403 Forbidden, and from hg://256bit.org/vim (which I
> > just tried, just in case) I get 404 Not found.
>
> It has just been re-enabled, see: https://www.vim.org/hgweb/vim/
> I'll update the homepage soon.

Ah, with a different URL. I'll try that, thanks.

… 465 new changesets : Wow ! :-)

Tony.

>
> Thank you Marc!
>
> Thanks,
> Christian
> --
> Without followers, evil cannot spread.
> -- Spock, "And The Children Shall Lead", stardate 5029.5
>

> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Z41uvQYQH9XW68gT%40256bit.org.

[Tony Mechelynck]

On Sun, Jan 19, 2025 at 10:44 PM Tony Mechelynck
<antoine.m...@gmail.com> wrote:
>
> On Sun, Jan 19, 2025 at 10:29 PM Christian Brabandt <cbl...@256bit.org> wrote:
> >
> >
> > On Mon, 13 Jan 2025, Tony Mechelynck wrote:
> >
> > > P.S. When I try "hg in" from http://hg.vim.org/ (my new default server
> > > address) I get 403 Forbidden, and from hg://256bit.org/vim (which I
> > > just tried, just in case) I get 404 Not found.
> >
> > It has just been re-enabled, see: https://www.vim.org/hgweb/vim/
> > I'll update the homepage soon.
>
> Ah, with a different URL. I'll try that, thanks.
>
> … 465 new changesets : Wow ! :-)
>
> Tony.

P.S. After adding some symlinks (as follows) to take care of my shadow
directories, now it works:
../linematch.c in every shadow directory
../README.txt and ../LICENSE in src/
("make" ran "configure" but that's no problem since my configure
arguments are passed in the environment, in a different shell for each
shadow build.)

Best regards,

[Christian Brabandt]

Note: I am not sure yet how well the hg bridge will be working on the
new server. I need to monitor it a bit for the future. Hopefully it will
work fine however.

On Sun, 19 Jan 2025, Tony Mechelynck wrote:
> P.S. After adding some symlinks (as follows) to take care of my shadow
> directories, now it works:
> ../linematch.c in every shadow directory
> ../README.txt and ../LICENSE in src/
> ("make" ran "configure" but that's no problem since my configure
> arguments are passed in the environment, in a different shell for each
> shadow build.)

I noticed the missing README.txt and LICENSE symlinks for shadow
directories and just fixed it this morning in the Makefile. linematch.c
should however be created by make shadow.

Thanks,
Christian
--
What I need is a MATURE RELATIONSHIP with a FLOPPY DISK ...

[Tony Mechelynck]

It would; but I don't run "make shadow" to recreate existing shadow
directories, I use incremental shadow builds. For it to work I need to
add a symlink to the upper (src/) level manually every time "make"
errors out with "no rule to make something.c" (which happens, but not
very often). That's no problem, I've done it before.

Best regards,
Tony.

> --
> What I need is a MATURE RELATIONSHIP with a FLOPPY DISK ...
>

> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Z41%2Bjk/0FujdqqR4%40256bit.org.