Re[2]: [vim/vim] www.vim.org website certificate expired (Issue #13079)

2023-09-26 Fir de Conversatie SAQUIB AKHTAR
Hi - It's a great news to see the www.vim.org hosted very quickly to new 
provider. Everything now works fine. But vim.org --->does not resolves 
or redirects to www.vim.org , can someone fix this by adding 1 CNAME in 
DNS ?


Best Regards
Saquib Akhtar


-- Original Message --

From "Christian Brabandt" 

To "vim/vim" 
Cc "Subscribed" 
Date 27-09-2023 11:26:41 AM
Subject Re: [vim/vim] www.vim.org website certificate expired (Issue 
#13079)




This should be fixed now since we have been moved to a new hosting 
provider. See the announcements on the vim_announce 
 list


the ssl cert should also work now.

so I am closing this now.

—
Reply to this email directly, view it on GitHub 
.
You are receiving this because you are subscribed to this 
thread.Message ID: 



--
--
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 a topic in the 
Google Groups "vim_dev" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/vim_dev/SsXNsBhfIRM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/13079/1736748333%40github.com 
.


--
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ema4cce6c4-0e8e-452e-b18a-ba409c532174%405a296976.com.


Re: Moving the Vim Homepage on 26.09.2023

2023-09-26 Fir de Conversatie Christian Brabandt


On Di, 26 Sep 2023, JohnBeckett wrote:

> And script  does not exist but there is no error:
> https://www.vim.org/scripts/script.php?script_id=

This also works now.

Best,
Christian
-- 
In war, truth is the first casualty.
-- U Thant

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ZRPAsrLkJn0yd7bj%40256bit.org.


Re: Moving the Vim Homepage on 26.09.2023

2023-09-26 Fir de Conversatie Christian Brabandt
Tony,

On Mi, 27 Sep 2023, Tony Mechelynck wrote:

> This is Tony Mechelynck and I'm using the mail interface because the
> Google Groups interface lets me neither paste from the clipboard nor
> attach a text file.
> 
> Indeed, when I browse to https://www.vim.org/ the ShowIP extension to
> SeaMonkey tells me that I am at 31.172.117.18 which is the correct new
> IP. The Vim Tips wiki, at vim.fandom.org, is also (as expected) still
> accessible. However when I follow a link to a script, for instance
> https://www.vim.org/scripts/script.php?script_id=2822 (a link found at
> https://vim.fandom.com/wiki/Showing_the_ASCII_value_of_the_current_character)
> which is supposed to be the page for the unicode.vim plugin, all I get
> is a blank page (NOT Error 404) which (again according to ShowIP) is
> supposed to come from 31.172.117.18. I have tried other script IDs, as
> well as searched for scripts directly from the vim.org homepage,
> always with the same (lack of) result.

Everything has been migrated, but the old php5 code had some issues. In 
particular the new php version is much more strict now.
I fixed the problem, that the script.php did not show the correct page. 
This should work now and downloading also works now.

Thanks,
Chris 
-- 
Majority, n.:
That quality that distinguishes a crime from a law.

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ZRPAfpY6dZp%2BOLfi%40256bit.org.


Re: Moving the Vim Homepage on 26.09.2023

2023-09-26 Fir de Conversatie JohnBeckett


I expect there is some simple problem in the new PHP because no links to 
scripts appear to be working. For example, I believe the most recent script 
is 6078 and its link currently shows a blank page (and view source shows 
there was no output):
https://www.vim.org/scripts/script.php?script_id=6078

And script  does not exist but there is no error:
https://www.vim.org/scripts/script.php?script_id=

John

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6d1cee55-4fdb-4993-8fd3-8f28bab22f97n%40googlegroups.com.


Re: Moving the Vim Homepage on 26.09.2023

2023-09-26 Fir de Conversatie Tony Mechelynck
P.S. I also tried with Firefox instead of SeaMonkey, with the same (lack 
of) results.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/b6904108-1301-48cc-b0ac-1898c4ad0dd0n%40googlegroups.com.


Re: Moving the Vim Homepage on 26.09.2023

2023-09-26 Fir de Conversatie Tony Mechelynck
On Tue, Sep 26, 2023 at 10:05 PM Christian Brabandt  wrote:
>
> Dear all,
> the homepage has been moved to our new provider wavestack. It should be
> much more stable and performant again.
>
> There may still be some problems with the old php code, so if you notice
> anything, please let me know and I'll fix it.
>
> Best,
> Christian
> --
> The fancy is indeed no other than a mode of memory emancipated from the order
> of space and time.  -- Samuel Taylor Coleridge
>
This is Tony Mechelynck and I'm using the mail interface because the
Google Groups interface lets me neither paste from the clipboard nor
attach a text file.

Indeed, when I browse to https://www.vim.org/ the ShowIP extension to
SeaMonkey tells me that I am at 31.172.117.18 which is the correct new
IP. The Vim Tips wiki, at vim.fandom.org, is also (as expected) still
accessible. However when I follow a link to a script, for instance
https://www.vim.org/scripts/script.php?script_id=2822 (a link found at
https://vim.fandom.com/wiki/Showing_the_ASCII_value_of_the_current_character)
which is supposed to be the page for the unicode.vim plugin, all I get
is a blank page (NOT Error 404) which (again according to ShowIP) is
supposed to come from 31.172.117.18. I have tried other script IDs, as
well as searched for scripts directly from the vim.org homepage,
always with the same (lack of) result.

Has the scripts database all gone to never-never land ? Or else, what
did I do wrong ?

FWIW, I am using a fiber connection in Brussels, Belgium, and at the moment,
* "systemctl status wicked" tells me
● wicked.service - wicked managed network interfaces
 Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled;
preset: disabled)
 Active: active (exited) since Wed 2023-09-27 00:00:12 CEST; 1h 54min ago
Process: 1267 ExecStart=/usr/sbin/wicked --systemd ifup all
(code=exited, status=0/SUCCESS)
   Main PID: 1267 (code=exited, status=0/SUCCESS)
CPU: 70ms

Sep 26 23:59:47 linux-tuxedo systemd[1]: Starting wicked managed
network interfaces...
Sep 27 00:00:12 linux-tuxedo wicked[1267]: lo  up
Sep 27 00:00:12 linux-tuxedo wicked[1267]: eth0up
Sep 27 00:00:12 linux-tuxedo systemd[1]: Finished wicked managed
network interfaces.
* "ifstatus eth0" tells me the following, which I don't understand
(except the first line saying that it is up):
eth0up
  link: #2, state up, mtu 1500
  type: ethernet, hwaddr f0:2f:74:1d:e9:8a
  config:   compat:suse:/etc/sysconfig/network/ifcfg-eth0
  leases:   ipv4 dhcp granted
  leases:   ipv6 dhcp granted, ipv6 auto granted
  addr: ipv6 2a02:a03f:64bb:3801:cfd8:dc79:7fe0:4d62/64 [auto]
  addr: ipv6 2a02:a03f:64bb:3801:f22f:74ff:fe1d:e98a/64 [auto]
  addr: ipv4 192.168.129.0/23 [dhcp]
  route:ipv4 default via 192.168.128.1 [dhcp]
  route:ipv6 default via fe80::6e3:1aff:febf:d672 metric 1024 proto ra
* If the above is only between my fibre modem and my computer, then I
have no access to the internal configuration of the modem.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAJkCKXvi119Tv92ZL64zYVEajOOzZiCc8Gsn8GEyGR0%2Bb3nKMA%40mail.gmail.com.


Re: Moving the Vim Homepage on 26.09.2023

2023-09-26 Fir de Conversatie Christian Brabandt
Dear all,
the homepage has been moved to our new provider wavestack. It should be 
much more stable and performant again.

There may still be some problems with the old php code, so if you notice 
anything, please let me know and I'll fix it.

Best,
Christian
-- 
The fancy is indeed no other than a mode of memory emancipated from the order
of space and time.  -- Samuel Taylor Coleridge

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ZRM5ktY07Wq26wGQ%40256bit.org.


lockvar on a function arg

2023-09-26 Fir de Conversatie Ernie Rael
Here's a legacy script that has a function that locks it's argument 
which is a dictionary in this example. Since this is probably the most 
complex legacy script I've written, I want to make sure it's 
expected/good behavior. (the proceeding after an error is spooky, but 
convenient...)


Asking because vim9script doesn't handle it.

-ernie

   func Lock(x)
    lockvar a:x
   endfunc

   let val = {'a': 99}

   call Lock(val)

   call extend(val, {'b': 100})
   echo val
   let val = {'c': 101}
   echo val

--
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/2e6291ac-7f83-8853-d014-fb2d22d8a30e%40raelity.com.