When trying to open new file from the command prompt which is
outside of the current working directory my first instinct is to
start with ~/. Unfortunately :open doesn’t expand it into the
value of ${HOME}. Would it be possible to make vis understand
this expansion?

Best,

Matěj

-- 
http://matej.ceplovi.cz/blog/, @mcepl@floss.social
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
The law, in its majestic equality, forbids the rich as well as
the poor to sleep under bridges, to beg in the streets, and to
steal bread.
    -- Anatole France

On Wed Nov 13, 2024 at 3:06 PM CET, Matěj Cepl wrote:
> When trying to open new file from the command prompt which is
> outside of the current working directory my first instinct is to
> start with ~/. Unfortunately :open doesn’t expand it into the
> value of ${HOME}. Would it be possible to make vis understand
> this expansion?

Specifically, when I type

:open ~/<TAB>

nothing happens. Yes, when I type the entire line,

:open ~/Documents/<Enter>

`vis-open` takes over the function and everything works as
it should. But at the same time, when I type the entire path
manually

:open /ho<TAB>

prompt obligingly expands eventually to

:open /home/matej/Documents

just by pressing TAB and ENTER. Could we make this completion
working even just with ~/ start of the path?

Best,

Matěj

-- 
http://matej.ceplovi.cz/blog/, @mcepl@en.osm.town
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
Whenever Christ our life is revealed, then also you will be
revealed with Him in glory.
    -- Colossians 3:4 (Green’s Literal Translation)