Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
You know how Linux makes a back-up file every time a file is edited, is there a way to have that file saved to a specified folder instead of it always being saved in the original file's directory?
It doesn't so much matter that you are using kde, as it does matter which program you are using. If you are using kwrite, then no, I don't think so. On the bright side, if you are just trying to avoid the clutter, there is something you can do with kwrite: Settings-> configure editor-> Open/Save-> Prefix = .
If the Prefix setting is comprised of a single period, then every temporary save file will have a period added to the front of it. In unix (and linux) this will make it a hidden file. The file will still be there, but you wont normally be able to see it.
Why would you want to that? I would think that right there near the original is where it would be most useful. -- It's not that it's some kind of versioning control. One problem w/ putting them all in the same dir. is name space collision.
Last edited by archtoad6; 09-23-2007 at 04:33 PM.
Reason: missing word -- "that"
So the annoying "ton of back-ups" was large only because of the number of files edited.
If it's that important you could (& we could help you) write a script to delete the back-ups, it could even be set to leave newer ones. You could also put it in as a cron job.
Instead of deleting, you could just move them to a back-ups sub-dir.
So the annoying "ton of back-ups" was large only because of the number of files edited.
If it's that important you could (& we could help you) write a script to delete the back-ups, it could even be set to leave newer ones. You could also put it in as a cron job.
Instead of deleting, you could just move them to a back-ups sub-dir.
Putting them in a back-up subdirectory is what I was hoping to do.
Where will the script live? Will it operate only in its own dir., or will it be put someplace like /usr/local/bin?
Will it have to check for &/or make the necessary sub-dir, or can it count on that being provided?
Will it move all back up files, of only older ones?
How will it recognize back up files?
Just Start Writing
Almost self-explanatory -- what commands wold you issue on the CLI to accomplish your goal?
I suggest you try writing & posting (here, of course) the code, keeping in mind my planning Q's as well as any ideas I have overlooked. Please use LQ "Code:" blocks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.