Block Dia Diagram Editor from saving backup copies of files - dia

Dia Diagram Editor always saves backup files in .dia~ file. Is there any way to turn this off. It is very anoying, I have to manually delete these files each time I save a change to my diagram.
I went through preferences, but found noting that corresponds.
I have also went through both FAQs:
http://dia-installer.de/doc/faq.html.en
https://wiki.gnome.org/Apps/Dia/Faq
but found nothing as well.

Nope, it turned out that such feature does not exist.
As for now, Dia Diagram Editor will always save:
*.dia file (holding current version of the file),
*.dia~ file (holding previous version of the file).

Related

Image corrupted after longer coding session

i'm rather new to pharo and I just started another new pharo project (on version 9) and lost my image as the process crashed upon saving.
I cant even load the image anymore.
I have all the changes still in the .changes file, is there any way to file in .changes files into a new image or have Epicea apply those changes?
I can of course manually copy paste all my changes, but that would be a pain with 1500+ lines of unsaved changes.
Happy about any solutions :)
In pharo-local/ombu-sessions you'll find the epicea change stored as ombu files. You can use the code changes browser to load them. If you select the directory of them of the crashed process (of course make a backup copy first) you can apply the changes you want

How to tell Intellij the file base when unshelving?

I shelved files using Intellij with the intention of separating changes made in Master into separate branches. On trying to "unshelve", Intellij is telling me it cannot find the file base for many of my files.
For example, the Intellij "Unshelve Changes" dialog is complaining about files as:
C:\Users\rcoe\intellij-workspace\proj\D:\cygwin64\home\rcoe\git\proj 14 files
When I remap the 14 files and tell Intellij to remove files from the shelf that have been successfully unshelved, it fails to unshelf any. I am not able to unshelve any of these files. A huge problem, as my shelf contains many more than just these 14 files, as I have a maven multi module project and this problem exists across all of them.
When I manually remap the files inside the Unshelve Changes dialog, Intellij does show the base as being changed. But closing the dialog doesn't change a thing. Any help on making this work would be appreciated.
Thanks.
EDIT:
I managed to remove 14 of 16 files that I needed. I found that by selecting one file at a time, I could unshelve each file. I did not have to re-do the manual mapping process. It seems the two files that refuse to get re-mapped were causing the others to not get unshelved. There is nothing out of the ordinary with the last two files. When I try to unshelve and then find a new base for the files, the file chooser dialog takes me right to the files.

NSIS doesn't backup all files

An NSIS installer creates a fairly large folder structure. When the installer starts, it checks the registry to see if there is a current version installed...
Then it asks if you want to make a backup of the current folder.
It works most of the time, but sometimes when it is backing up older versions, instead of copying over the entire directory, it only copies the icon.
!insertmacro un.MoveFolder "$INSTDIR" "${BACKUP_FOLDER}" "*.*"
Reference: http://nsis.sourceforge.net/MoveFileFolder
!insertmacro MoveFolder "$INSTDIR\[path\]source-folder[\]" "$INSTDIR\[path\]destination-folder[\]" "file-mask"
Afterwards, it moves on to the delete section...
Could it be that it doesn't have time to do it ? it starts the next process before finishing the move ?
What else could be going on so that it does not copy the entire folder ?
During the installer, I see
Create folder c:\backup_folder
Moving files: c:\current_folder\*.* to c:\backup_folder\
Delete file: c:\current_folder\file1.........
And at the end, backup_folder has only the icon (not all the files)
Edit: The solution - please see my post here NSIS difficulty moving folders - $INSTDIR is indeed a special folder so I had to move the uninstaller to a $TEMP folder.
Is there any reason why you cannot use the built-in CopyFiles command?
To debug this I would suggest that you add a DetailPrint near the top of the .MoveFolder_Locate_moveFile function. If you see all the file names go by then the problem is the move operation in that function, if not then the problem is in the ${Locate} macro used by this code.
Another alternative is to watch the filesystem operations with Process Monitor...

Xcode snapshots

What exactly does Xcode do with project snapshots after the Xcode project is moved or renamed. I have noticed they completely disapear...Where should I look?
Defintely not in ~/Library/Application Support/Developer/Shared/SnapshotRepository.sparseimage
~/Library/Application Support/Developer/Shared/SnapshotRepository.sparseimage is a disk image. You have to mount it and look in there.
Snapshots are stored based on a hash of the project name; change the project name and you lose the snapshot history. If you take a snapshot of the new project, and can find the old snapshot on the disk image, you can probably move the old snapshot into the new one's directory.
If they are not in ~/Library/Application Support/Developer/Shared/SnapshotRepository.sparseimage then I think you may be out of luck. I tend to rely on snapshots only as a first line of defence, with Time Machine as a more reliable second line, and then SCM and proper backups as the third and fourth.
They are inside the image allright... but making so that Xcode will recognize them won't be that easy...
In that image, you have the folder with all the snapshots (with some hierarchy)... and a plist file... in that plist file they have a HARDCODED (non relative to project file) paring system between each snapshot and the ORIGINAL PATH of the project folder.
So, if you really want to move/rename yar project, you'll need to change ALL the paths in that little plist file...
P.S.
if you're gonna do the changes, you might wanna close Xcode before you do... it might make him angry... :P
Another thing you should be aware of:
If you open and mount ~/Library/Application Support/Developer/Shared/SnapshotRepository.sparseimage as a disk image and then start Xcode to recover or look into your snapshots Xcode will complain that the Snapshot Repository is broken and move it into the Trash!
So remember to unmount the repository before starting Xcode.
To recover a trashed Snapshot Repository just drag it into the correct path (see above) and remove the date stamp inside the filename.
I ran in to this issue having renamed the App and if I renamed it back to the original, quit Xcode and reopened it the restores were available again.

Why does my PDF ask for a password after being retrieved from Visual SourceSafe?

PREFACE: Yes we're moving away from VSS in the next few months.
One of my web projects contains, as one of its files, a PDF. The PDF on our QA site is being pulled from VSS.
A QA tester recently told me he's being prompted for a password when he tries to open it. VSS says the file I have on disk is different than the one it has, so I updated it, but afterwards it's still being shown as different.
So basically VSS is mangling my PDF and the results are so wobbly that Adobe Acrobat Reader is confused and thinks it has a password.
I've tried adding it as Auto-Detect and as Binary. Same results.
Why does my PDF ask for a password after being retrieved from Visual SourceSafe and how can I prevent it?
Do you have the SourceSafe 2005 Update installed?
Handy list of known issues: http://blogs.msdn.com/richardb/archive/2007/06/06/list-of-bugs-fixed-in-sourcesafe-2005-gdr.aspx
The PDF bug was one of the most commonly requested hotfixes: http://support.microsoft.com/kb/925234
I've tried adding it as Auto-Detect and as Binary. Same results.
To be clear, are you adding a version of the file you know is not already corrupted? Even so, there are plenty of other bug fixes on the list above which can cause random file corruption -- try that first.
You can remove PDF password by this tool:
Advanced PDF Password Remover 5.0
Step 1: Import PDF files
Click the "Add File(s)" button, browse your computer to find the PDF files and load them.You can import as many as 200 PDF files into this program for every batch processing.The imported files are listed in the file list window as below.
Step 2: Set output folder
You can customize a folder to save the output files all together. The default folder is My Documents\Advanced PDF Password Removerr. Click "Brows" button to specify a folder on your computer, or you can make a new folder manually in the text box.
Step 3: Remove restrictions
Click "Start" button, and the files are processed one by one.
"SUCCEED" is displayed in the Result column after the removing process is finished.