On Fr, 14 Dez 2018, Tama McGlinn wrote:
> I am having the same problem, using Neovim on Windows. There is now a
> github page for netrw, but it is out-of-date, and so I cannot use it
> to check what the bugfix ended up being for this; I am using netrw
> v156, but the github so far only goes to v
I am having the same problem, using Neovim on Windows. There is now a github
page for netrw, but it is out-of-date, and so I cannot use it to check what the
bugfix ended up being for this; I am using netrw v156, but the github so far
only goes to v142. I need the github not because I don't know
On Di, 03 Jul 2018, norbert.keli...@opeast.org wrote:
> I am another Windows user having a problem with the copy function in netrw.
>
> I was getting the "not executable error," so I downloaded and installed v163b
> from your website. Now the error is different:
>
> **error** (netrw) copy fai
I am another Windows user having a problem with the copy function in netrw.
I was getting the "not executable error," so I downloaded and installed v163b
from your website. Now the error is different:
**error** (netrw) copy failed; perhaps due to vim's current directory not matching netrw's (G:/
On Thursday, November 10, 2016 at 2:36:22 AM UTC+9, DrChip wrote:
> mattn wrote:
> > On Wednesday, November 9, 2016 at 10:53:08 PM UTC+9, Tony Mechelynck wrote:
> >> On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote:
> >>> On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
> Cesar Ro
On Thursday, November 10, 2016 at 2:49:16 AM UTC+9, DrChip wrote:
> mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windows for a long time. Most of
> > operations which use Windows commands of cmd.exe doesn't work because netrw
> > checks the command exists by ex
> You don't like the maintainer model; I differ. Many times I have had to
> reject
incorrect changes;
Totally agree.
On Wed, Nov 9, 2016 at 12:48 PM, Charles E Campbell <
drc...@campbellfamily.biz> wrote:
> mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windo
mattn wrote:
> Hi, Dr. Chip and list.
>
> I met some problems on netrw on Windows for a long time. Most of operations
> which use Windows commands of cmd.exe doesn't work because netrw checks the
> command exists by executable(). The commands are defined like:
>
> let g:netrw_localcopycmd= expan
mattn wrote:
> On Wednesday, November 9, 2016 at 10:53:08 PM UTC+9, Tony Mechelynck wrote:
>> On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote:
>>> On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
Cesar Romani wrote:
Netrw actually doesn't check that expand("$COMSPEC") is exe
On Wednesday, November 9, 2016 at 10:53:08 PM UTC+9, Tony Mechelynck wrote:
> On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote:
> > On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
> >> Cesar Romani wrote:
> >
> >> Netrw actually doesn't check that expand("$COMSPEC") is execuable befor
On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote:
> On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
>> Cesar Romani wrote:
>
>> Netrw actually doesn't check that expand("$COMSPEC") is execuable before
>> setting up g:netrw_localcopycmd; instead, it uses that if netrw reports
>> has("w
On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
> Cesar Romani wrote:
> Netrw actually doesn't check that expand("$COMSPEC") is execuable before
> setting up g:netrw_localcopycmd; instead, it uses that if netrw reports
> has("win32") || has("win95") || has("win64") || has("win16"
Cesar Romani wrote:
> On 08/11/2016 04:08 a.m., mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windows for a long time. Most of
> > operations which use Windows commands of cmd.exe doesn't work because
> > netrw checks the command exists by executable(). The comman
On 08/11/2016 04:08 a.m., mattn wrote:
> Hi, Dr. Chip and list.
>
> I met some problems on netrw on Windows for a long time. Most of
> operations which use Windows commands of cmd.exe doesn't work because
> netrw checks the command exists by executable(). The commands are
> defined like:
>
> let
Hi, Dr. Chip and list.
I met some problems on netrw on Windows for a long time. Most of operations
which use Windows commands of cmd.exe doesn't work because netrw checks the
command exists by executable(). The commands are defined like:
let g:netrw_localcopycmd= expand("$COMSPEC")." /c copy"
15 matches
Mail list logo
