On 2017-06-30, Christian Brabandt wrote:
> On Fr, 30 Jun 2017, Christian Brabandt wrote:
>
> >
> > On Fr, 30 Jun 2017, Gary Johnson wrote:
> >
> > > As sure as I know how to be. I applied the patch to a system at
> > > home and to one at work. Both fail the same way. I ran "patch
> > > --dry-run -p1 < ~/.vim/backupdir.patch" again on the second system
> > > to check and it reported that the patches were already there.
> > >
> > > Running the test gives me just this and an empty test_backup.res
> > > file.
> > >
> > > $ make test_backup.res
> > > VIMRUNTIME=../../runtime; export VIMRUNTIME; ../vim -f -u unix.vim
> > > -U NONE --noplugin --not-a-term -S runtest.vim test_backup.vim
> >
> > Results are stored in the messages file. The newstyle tests do not
> > output the result of the test by default, you need to manually check
> > the messages file for the results.
$ cat messages
>From test_backup.vim:
Executing Test_backup()
Executing Test_backup2()
Executed 2 tests
> Hm, just one wild guess: Does it work after you save a second time?
No. I edited one file in $HOME four times and each backup went into
the designated backup directory but without the full path name.
I tried a lot of experiments. They all worked unless I used my
actual ~/.vimrc. I discovered that the problem occurs, that is, the
full path name is not used for the backup file name, when
set backupcopy=yes
Regards,
Gary
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
