Bug#1004118: E1187: Failed to source defaults.vim

[Robert Siemer]

Package: vim-tiny
Version: 2:8.2.3995-1
Severity: normal
X-Debbugs-Cc: Robert.Siem...@backsla.sh

vim-tiny should come with defaults.vim, I believe. Which way I’m not sure,
but it seems vim-common does not deliver it and vim-tiny does not depend
on vim-runtime, which has it.

-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.tiny
/usr/bin/vim is /usr/bin/vim.tiny

-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-8-686-pae (SMP w/2 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vim-tiny depends on:
ii libacl1 2.3.1-1
ii libc6 2.33-3
ii libselinux1 3.3-1+b1
ii libtinfo6 6.3-2
ii vim-common 2:8.2.3995-1

vim-tiny recommends no packages.

Versions of packages vim-tiny suggests:
pn indent <none>

-- no debconf information

[Robert Siemer]

I’m pretty sure that it was a vim alternative at the time I installed it. – Might have been 10+ years ago, though.

Anyway... good to know which way to go now.

Regards,

Robert

On Fri, Jan 21, 2022 at 2:39 PM Debian Bug Tracking System <ow...@bugs.debian.org> wrote:

This is an automatic notification regarding your Bug report
which was filed against the vim-tiny package:

#1004118: E1187: Failed to source defaults.vim

It has been closed by James McCoy <jame...@debian.org>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact James McCoy <jame...@debian.org> by
replying to this email.


--
1004118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



---------- Forwarded message ----------
From: James McCoy <jame...@debian.org>
To: Robert Siemer <Robert.Siem...@backsla.sh>, 100411...@bugs.debian.org
Cc: 
Bcc: 
Date: Fri, 21 Jan 2022 08:37:52 -0500
Subject: Re: Bug#1004118: E1187: Failed to source defaults.vim

On Fri, Jan 21, 2022 at 03:58:58AM +0100, Robert Siemer wrote:
> vim-tiny should come with defaults.vim, I believe.

No, vim-tiny exists purely to provide a vi binary in the base system and
therefore is geared towards a vi-like experience more so than a vim-like
experience.

This is why vim-tiny does not register itself as an option for the vim
alternative.

If you want it to be more vim-like, then installing vim-runtime is a
reasonable step to take.

Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

[Diederik de Haas]

On Fri, 21 Jan 2022 08:37:52 -0500 James McCoy <jame...@debian.org> wrote:
> On Fri, Jan 21, 2022 at 03:58:58AM +0100, Robert Siemer wrote:

> > vim-tiny should come with defaults.vim, I believe.
>

> No, vim-tiny exists purely to provide a vi binary in the base system and
> therefore is geared towards a vi-like experience more so than a vim-like
> experience.
>
> This is why vim-tiny does not register itself as an option for the vim
> alternative.

I don't know if it was the trigger for this bug report, but on a freshly
installed (very) minimal bookworm (arm64) system with vim-tiny, using it
produces the error as mentioned in the bug subject:

$ vim.tiny .ssh/authorized_keys

E1187: Failed to source defaults.vim

Press ENTER or type command to continue

After pressing ENTER, I can use it.
While I understand that vim-tiny won't give me the full vim experience, it
currently does give the above error on every invocation.
I don't recall it gave that/a error before.

My guess is that this bug wasn't a feature request (which would've had
severity wishlist).

Cheers,
Diederik

[James McCoy]

On Tue, Feb 01, 2022 at 06:19:43PM +0100, Diederik de Haas wrote:
> On Fri, 21 Jan 2022 08:37:52 -0500 James McCoy <jame...@debian.org> wrote:
> > On Fri, Jan 21, 2022 at 03:58:58AM +0100, Robert Siemer wrote:
> > > vim-tiny should come with defaults.vim, I believe.
> >
> > No, vim-tiny exists purely to provide a vi binary in the base system and
> > therefore is geared towards a vi-like experience more so than a vim-like
> > experience.
> >
> > This is why vim-tiny does not register itself as an option for the vim
> > alternative.
>
> I don't know if it was the trigger for this bug report, but on a freshly
> installed (very) minimal bookworm (arm64) system with vim-tiny, using it
> produces the error as mentioned in the bug subject:
>
> $ vim.tiny .ssh/authorized_keys
> E1187: Failed to source defaults.vim
> Press ENTER or type command to continue

The binary vim.tiny is an implementation detail. I tried to move
them under /usr/libexec, but that caused the alternatives to reset their
priorities for existing installs, so it had to be reverted.

The intended use is to invoke the binary through the named alternatives
(vi, view, ex, editor).

> After pressing ENTER, I can use it.
> While I understand that vim-tiny won't give me the full vim experience, it
> currently does give the above error on every invocation.
> I don't recall it gave that/a error before.

When invoked as vi it doesn't, because that triggers Debian's patch to
only use the tiny config. I'll talk with upstream about whether an
error should really be emitted when defaults.vim isn't available.

I'll also look into whether there's anything that should be adjusted for
the aforementioned patch.

[Dagfinn Ilmari Mannsåker]

James McCoy wrote:
> On Tue, Feb 01, 2022 at 06:19:43PM +0100, Diederik de Haas wrote:
>> $ vim.tiny .ssh/authorized_keys
>> E1187: Failed to source defaults.vim
>> Press ENTER or type command to continue
>
> The binary vim.tiny is an implementation detail. I tried to move
> them under /usr/libexec, but that caused the alternatives to reset their
> priorities for existing installs, so it had to be reverted.
>
> The intended use is to invoke the binary through the named alternatives
> (vi, view, ex, editor).
>

> When invoked as vi it doesn't, because that triggers Debian's patch to
> only use the tiny config.

Given that `vim.tiny` registers itself for the `view` and `editor`
alternatives, it really should not throw any errors or warnings when
invoked via them (I noticed this because `sudoedit` falls back to
`editor` if the `$EDITOR` and `$VISUAL` environment variables aren't
set).

- ilmari

[James McCoy]

Agreed. I intend to update the vim.tiny patch so that it would avoid
this message. I just haven't gotten to it yet.