Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A file suffixing ~ is created right before you write but is deleted write after you successfully written, if you don't have backup set but writebackup set.
So what's the use of this backup file
It is a very old program. A lot of odd things were done because of reasons we don't have today. Simple thing might have been very limited ram. You'd have to find the guys that made it or find any old documentation but I'd suspect a person who were to re-write it today would do it much differently.
To build on what Jefro said, in the early days of personal computers 30 or more years ago (I never used mainframes) it was not uncommon for computers just to lock up in the middle of something and have to be restarted.
To build on what Jefro said, in the early days of personal computers 30 or more years ago (I never used mainframes) it was not uncommon for computers just to lock up in the middle of something and have to be restarted.
You will appreciate it if you are editing a remote file over ssh. If the link goes down (ignoring tmux or screen for the sake of this example) or the remote host is rebooted by the hosting company, your vim edits are safe and recoverable.
If a bunch of ~ files annoys you, put them all in one place by specifying "set backupdir=xxxxx" and run a cron job periodically to delete old files in that directory.
You will appreciate it if you are editing a remote file over ssh. If the link goes down (ignoring tmux or screen for the sake of this example) or the remote host is rebooted by the hosting company, your vim edits are safe and recoverable.
If a bunch of ~ files annoys you, put them all in one place by specifying "set backupdir=xxxxx" and run a cron job periodically to delete old files in that directory.
That sounds about right, I just saw these files a few times, while I don't think it comes from vim, because I found no reason to generate a ~file in such manner. Maybe it comes from gedit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
