OllyDbg - there are several patches applied but it still says that file was unmodified and doesn't save changes of patches to modded *.exe . Somehow before the addition of each new patch it saves ok with notice of changing the file, but with next it doesn't. And with the third I don't know how to overcome it. How to save them - am I doing something wrong?
The message
Basing on your comments - There is no such Save to file or Edit -> Save to file when you right click in the CPU window. You are doing somethng wrong.
The correct way to save the patches to new file is:
Open CPU window
Right click -> Copy to executable -> All modifications
Click Copy all in the new window
In the new window Right click -> Save file
Related
I have been learning for just over a month now and I started my first project and I was coming to a close with it and literally last sec the CSS file is blank. I am using chrome and atom text editor. I did not have my git acc linked to it so history is not saved on it. The only thing showing on the file for the class is "
1
*
*
*
*
*
"
When I hit backspace it takes forever to delete because I'm pretty sure my code is just hidden there or something. I have no idea what happened. I spent some hours trying to fix it but no dice.
Have you tried opening the file in explorer?
If you right click on your project folder there is an option to open in file explorer. (This may say "Show in file manager" if you're using the latest version of Atom)
Check if the file is there, if it is, try opening it notepad or another simple text editor.
If it's not there it may have been corrupted, I've used atom quite a bit and never encountered this problem.
If it is, you can always just delete the file in your project folder and make a new one, pasting the contents in from when you opened it in notepad.
I'm just trying out Atom for the first time and I find it bothersome that Atom keeps opening a new window for each file I click on - I'd prefer that it defaulted to opening each file in the same window.
I'm hoping for something along the lines of "open_files_in_new_window" : false, in Sublime. Unfortunately, all the google results I'm seeing just lament that this toggle is not immediately obvious.
In your terminal you can type atom -a <filename||folder> and the file(s) will open within the same atom window.
Go to Settings > Packages, look for the tabs package. In the settings for this package, choose "use preview Tabs".
Per the atom -h command, one should open files with -n=false or --new-window=false argument passed so that they are opened in an existing window, e.g.
atom -n=false ~/Desktop/test.py
One could make atom -n=false an alias of atom in the ~/.bashrc or ~/.zshrc file, or one could edit the corresponding file in /home/<your username>/.local/share/applications so that the command it invokes is, for instance, /usr/lib/atom/atom -n=false %F.
Just in the editor window, drag the open tab by mouse onto the window you need.
Is there a way to quickly open files in sublime text2?
At the moment I open files like this.
I open my terminal and enter
subl source/myproj/myfile.rs
Can I do this inside of sublime text2/3?
Also when I want to create a new file in source/myproj/ I usally press ctrl + n to create a new window and then I hit ctrl + s to save and name the file. The problem is when I hit ctrl + s my file system dialog opens and I have to use my mouse.
I think I saw someone using vim and he just could say source/myproj/mynewfile.rs and then the file would be created.
Is this possible in sublime text 2/3?
To quickly open a file in your current project, you can hit Ctrl+P and start writing the filename. This will sort through the files in your project and give you a little list, most likely the one you are looking for is pre selected, but if not, it is somewhere near the topmost options to select from, use arrow key down and highlight it, press enter and you just opened that file.
Another option to quickly create a file is using the AdvancedNewFile plugin.
When you hit Ctrl+n, it asks near the bottom of the window for a path and filename, once you enter it, it opens the new tab with the file already created, not an untitled file to later use system dialog to save to disk.
There have been too many times where I have accidentally clicked the X on the top right window in Sublime Text 2. I then loose my undo/redo history.
Edit: I have tried to set hot_exit to false in default and user settings.
Look for hot_exit in Preferences.sublime-settings
// Exiting the application with hot_exit enabled will cause it to close
// immediately without prompting. Unsaved modifications and open files will
// be preserved and restored when next starting.
//
// Closing a window with an associated project will also close the window
// without prompting, preserving unsaved changes in the workspace file
// alongside the project.
"hot_exit": true,
and set it to false.
Install the plugin Local History.
Every time you modify a file, a copy of the old contents is kept in
the local history.
Either do it through Package Control (If you don't have it already, install it)
Or get it on Github
I've a file in a folder and I don't know anything about this file (how it's generated and updated) because it comes from an application running on my system of which I don't have the source code.
The file format is clearly json and I successfully created an hard link to it (using the shell command ln file hardLinkToFile) and placed it on another directory.
At this point I check the "2" files and they are exactly the same as expected, but when I perform an action in the application that cause an update of the original file the hard link doesn't get updated.
Any idea on how I can solve this problem?
UPDATE: As pointed out by both Vlad Lazarenko and mvds the file probably get deleted and a new one is created, is there something I can do to obtain a solution equivalent to the hard-link one I thought initially about?
If a hard link is not getting updated, it means that application is removing the old file and creates a new one. Thus, you still have a hard copy of the previous file, but new file has a totally different inode, though path is still the same. You can verify it simply by changing the content of that file yourself - the link should get updated.
I am getting the same behavior in TextEdit, but not in TextMate. I would suspect this is due to the revision control built in to OS X Lions document architecture. TextEdit uses versioning, while TextMate does not. Most likely this function replaces the file instead of changing it, as described by #Vlad Lazarenko.
#Vlad and Francesco. It's really in this way. I verified that vi leaves the inode unchanged and the src and dest file are both changed, while e.g. the kate editor doesn't and I was getting mad to understand why the changes I made in the src file weren't also in the dest file.
You can easily check this with the command ls -li srcfile destfile before editing one of them with each editor I mentioned.
By the way it's not nice that the hard link are application dependent
I guess it is a bit too late...
Anyways, accidentally I found that, if you change the default app for the file, the hard link gets separated from original file. Even if you click on change all and do not relate to that specific file.