> I've been following this thread for a while now. Is there a team handling
> the vim.org site? Maybe we can collect a few people interested enough to
> volunteer? I'm interested for one. That team could be responsible for
> ensuring issues like these are fixed, and the general updates of the sit
On Do, 08 Jun 2023, Owajigbanam Ogbuluijah wrote:
> Hey Bram,
>
> I've been following this thread for a while now. Is there a team handling the
> vim.org site? Maybe we can collect a few people interested enough to
> volunteer?
> I'm interested for one. That team could be responsible for ensur
Hey Bram,
I've been following this thread for a while now. Is there a team handling
the vim.org site? Maybe we can collect a few people interested enough to
volunteer? I'm interested for one. That team could be responsible for
ensuring issues like these are fixed, and the general updates of the si
On Wednesday, 7 June 2023 at 17:17:32 UTC+2 Bram Moolenaar wrote:
Christian wrote:
> On Di, 06 Jun 2023, Bram Moolenaar wrote:
>
> > I have created a ticket. Unfortunately the information we have is not
> > very specific, that makes it difficult to pinpoint the problem. If you
> > notice th
Christian wrote:
> On Di, 06 Jun 2023, Bram Moolenaar wrote:
>
> > I have created a ticket. Unfortunately the information we have is not
> > very specific, that makes it difficult to pinpoint the problem. If you
> > notice the problem, plesae gather as much information as you can,
> > especia
On Di, 06 Jun 2023, Bram Moolenaar wrote:
> I have created a ticket. Unfortunately the information we have is not
> very specific, that makes it difficult to pinpoint the problem. If you
> notice the problem, plesae gather as much information as you can,
> especially the exact time, and let me
John Beckett wrote:
> On Tuesday, June 6, 2023 at 3:31:29 AM UTC+10 Bram Moolenaar wrote:
>
> > I have see some DB errors the last few days. Usually the problem goes
> > away a bit later, e.g. after an hour. I have no clue what might cause this.
>
> Are you able to ask for help at the hosting
On Tuesday, June 6, 2023 at 3:31:29 AM UTC+10 Bram Moolenaar wrote:
I have see some DB errors the last few days. Usually the problem goes
away a bit later, e.g. after an hour. I have no clue what might cause this.
Are you able to ask for help at the hosting service? The problem would
probably
Christian wrote:
> On Sa, 03 Jun 2023, Lifepillar wrote:
>
> > On 2023-06-02, Bram Moolenaar wrote:
> >
> > > You could try using another browser.
> >
> > I have tried with Safari, Brave, and LibreWolf (~Firefox) on macOS to no
> > avail. I have taken care to disable ad blockers and, afaics,
On Sa, 03 Jun 2023, Lifepillar wrote:
> On 2023-06-02, Bram Moolenaar wrote:
>
> > You could try using another browser.
>
> I have tried with Safari, Brave, and LibreWolf (~Firefox) on macOS to no
> avail. I have taken care to disable ad blockers and, afaics, only
> cross-site cookies are blo
On 2023-06-02, Bram Moolenaar wrote:
> You could try using another browser.
I have tried with Safari, Brave, and LibreWolf (~Firefox) on macOS to no
avail. I have taken care to disable ad blockers and, afaics, only
cross-site cookies are blocked.
Life.
--
--
You received this message from th
> On 2023-05-26, Edward McGuire wrote:
> > I offered a tarball containing an ftdetect, a syntax, and a README and
> > LICENSE.
> > The site replied: "The package you uploaded (vim-noweb.tgz) is empty".
>
> I am getting the same error, e.g.:
>
>
On Fr, 02 Jun 2023, Lifepillar wrote:
> On 2023-05-26, Edward McGuire wrote:
> > I offered a tarball containing an ftdetect, a syntax, and a README and
> > LICENSE.
> > The site replied: "The package you uploaded (vim-noweb.tgz) is empty".
>
> I am getti
On 2023-05-26, Edward McGuire wrote:
> I offered a tarball containing an ftdetect, a syntax, and a README and
> LICENSE.
> The site replied: "The package you uploaded (vim-noweb.tgz) is empty".
I am getting the same error, e.g.:
vim-solarized8-1.5.0.tar.gz is empt
> > > Just curious if this works with a zip extension or a simple .vmb for
> > > vimball.
> >
> > Great question. I had not heard of vimball. I will try it and see if
> > that gets around the error.
>
> See :h vimball
>
> > Is vimball the most portable format? Should the example be updated
>
On Di, 30 Mai 2023, Edward McGuire wrote:
> On Tuesday, May 30, 2023 at 12:38:34 PM UTC Christian Brabandt wrote:
> > What is the script id? I might be able to check it on the server (no
> > promises
> however).
>
> Originally "vim-noweb", and also when I ran into the problem I tried making
>
On Tuesday, May 30, 2023 at 12:38:34 PM UTC Christian Brabandt wrote:
> What is the script id? I might be able to check it on the server (no
promises however).
Originally "vim-noweb", and also when I ran into the problem I tried making
the ID the same as the filename "vim-noweb.tar.gz" and "vim-
On Fr, 26 Mai 2023, Edward McGuire wrote:
> This is my first time to try to contribute a Vim plugin to vim.org.
> Where is this newbie going wrong?
>
> I offered a tarball containing an ftdetect, a syntax, and a README and
> LICENSE.
> The site replied: "The pa
This is my first time to try to contribute a Vim plugin to vim.org.
Where is this newbie going wrong?
I offered a tarball containing an ftdetect, a syntax, and a README and
LICENSE.
The site replied: "The package you uploaded (vim-noweb.tgz) is empty".
I have already extracted my own
19 matches
Mail list logo