What could be the solution for the E510?
Hiroshi Iwatani
E510 Can't create backup file ..... (in Japanese)
whenever I try to save the edited result from the GUI menu.
The command w! or wq! does work, though.
What could be the cause of the E510 problem and the solution?
Vim version is 7.2.60 .... from the distribution pkg
Thanks in advance.
--
Hiroshi Iwatani: http://homepage1.nifty.com/algafield/
*stop cruelty* Annual number of institutionally euthanized cats and dogs
including kittens and puppies: US 5 million, JP 500 thousand. How about
your country? *for our better karma*
---------------------
Tony Mechelynck
> On the new Linux Fedora 10 distribution, gvim always emits
>
> E510 Can't create backup file ..... (in Japanese)
>
> whenever I try to save the edited result from the GUI menu.
>
> The command w! or wq! does work, though.
>
> What could be the cause of the E510 problem and the solution?
>
> Vim version is 7.2.60 .... from the distribution pkg
>
> Thanks in advance.
>
1. Where is the file you are editing? Is it a remote file being edited
over ftp or something?
2. Many bugfixes have been published since 7.2.60 has come and gone: the
current patchlevel is 7.2.132. Maybe it's time to roll a compile of your
own? See my HowTo page,
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
See a one-line description of every patch so far at
http://ftp.vim.org/pub/vim/patches/7.2/README
Best regards,
Tony.
--
(letter from Mark to Mike, about the film's probale certificate)
For an 'A' we would have to: Lose as may shits as possible Take Jesus
Christ out, if possible Loose "I fart in your general direction" Lose
"the oral sex" Lose "oh, fuck off" Lose "We make castanets out of
your
testicles"
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD
Hiroshi Iwatani
Tony Mechelynck wrote:
> On 08/03/09 04:58, Hiroshi Iwatani wrote:
>> On the new Linux Fedora 10 distribution, gvim always emits
>>
>> E510 Can't create backup file ..... (in Japanese)
>>
>> whenever I try to save the edited result from the GUI menu.
>>
>> The command w! or wq! does work, though.
>>
>> What could be the cause of the E510 problem and the solution?
>>
>> Vim version is 7.2.60 .... from the distribution pkg
>>
>> Thanks in advance.
>>
>
> 1. Where is the file you are editing? Is it a remote file being edited
> over ftp or something?
They are ordinary local files in various directories.
I used to be a <root> Linuxer, even in the new distro.
Does that have something to do with ..... ?
>
> 2. Many bugfixes have been published since 7.2.60 has come and gone: the
> current patchlevel is 7.2.132. Maybe it's time to roll a compile of your
> own? See my HowTo page,
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
>
> See a one-line description of every patch so far at
> http://ftp.vim.org/pub/vim/patches/7.2/README
I know Tony is the greatest on this ML at all times but like to see other wisdom, if any.
>
>
> Best regards,
> Tony.
Tony Mechelynck
>
>
> Tony Mechelynck wrote:
>> On 08/03/09 04:58, Hiroshi Iwatani wrote:
>>> On the new Linux Fedora 10 distribution, gvim always emits
>>>
>>> E510 Can't create backup file ..... (in Japanese)
>>>
>>> whenever I try to save the edited result from the GUI menu.
>>>
>>> The command w! or wq! does work, though.
>>>
>>> What could be the cause of the E510 problem and the solution?
>>>
>>> Vim version is 7.2.60 .... from the distribution pkg
>>>
>>> Thanks in advance.
>>>
>> 1. Where is the file you are editing? Is it a remote file being edited
>> over ftp or something?
> They are ordinary local files in various directories.
> I used to be a<root> Linuxer, even in the new distro.
> Does that have something to do with ..... ?
Well, usually the backup is created in the same directory as the
original -- but of course, for that to work, you need file-creation
permission in that directory.
What is your 'backupdir' option set to?
:verbose set backupdir?
It is a comma-separated list. I recommend having it start with . or ./
(both of which mean the directory of the editfile) and end with one or
more directories where you have all permissions with your current username.
>
>> 2. Many bugfixes have been published since 7.2.60 has come and gone: the
>> current patchlevel is 7.2.132. Maybe it's time to roll a compile of your
>> own? See my HowTo page,
>> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
>>
>> See a one-line description of every patch so far at
>> http://ftp.vim.org/pub/vim/patches/7.2/README
> I know Tony is the greatest on this ML at all times but like to see other wisdom, if any.
>
>>
>> Best regards,
>> Tony.
--
"I have to convince you, or at least snow you ..."
-- Prof. Romas Aleliunas, CS 435
Hiroshi Iwatani
Tony is the greatest again, as usual.
On my .vimrc file inherited from the previous distro has the line:
set backupdir=$HOME/vimbackups
But I didn't create the vimbackups dir on my root directory. Vim doesn't make it automatically, either.
I have made it. Now, everything works fine. The big irritating splinter's gone.
Small issue can give prolonging big pain ...
--
Tony Mechelynck
> Thanks.
> Tony is the greatest again, as usual.
> On my .vimrc file inherited from the previous distro has the line:
>
> set backupdir=$HOME/vimbackups
>
> But I didn't create the vimbackups dir on my root directory. Vim doesn't make it automatically, either.
>
> I have made it. Now, everything works fine. The big irritating splinter's gone.
> Small issue can give prolonging big pain ...
The advantage of having a 'backupdir' starting with . is that (a) it is
usually possible to create backups in the same directory as the file;
(b) it avoids problems if you edit files with the same name in different
directories (such as ftplugin/html.vim and syntax/html.vim) (c) since
that is the default, it allows getting the |ATTENTION| warning if you
(or you and someone else) try to edit the same file in two different
Vims, which of course can be courting disaster if both made changes then
save their own changes, with the one saving last overriding any changes
made by the other... Sometimes I do want to open the same file in two
Vims, but that warning is then a healthy "roadsign" reminding me that
one of them should be read-only.
Best regards,
Tony.
--
"I wouldn't recommend sex, drugs or insanity for everyone, but they've
always worked for me."
-- Hunter S. Thompson