Occasionally when I'm using ST3, it says it has saved my changes, but it has not.
Here's what I'm experiencing:
I'll be editing a file (usually html, css, or js)
Save my changes, switch to Chrome, refresh, examine changes
Go back to ST3, make more changes, save, and switch back to Chrome
Refresh, changes are not visible. Refresh, refresh, refresh, refresh, still can not see changes.
Go back to ST3, make substantive change to file, and save again.
Go back to Chrome, refresh again, changes are updated.
This happens frequently, maybe once or twice per hour of active coding.
When it's in the state of having made/saved changes, but them not appearing, (between step #4 and #5) it looks as if ST3 has not saved the file to disk. If I cat the file out in the terminal, my changes are not shown. This leads me to believe ST3 hasn't actually committed the changes to disk, and that the problem isn't with Chrome, or other elements of my process.
If anyone could offer solutions or further troubleshooting steps, I'd really appreciate it. This is starting to drive me bonkers. This has been going on a while, but I'm sorry to say I can not seem to reliably reproduce it. Thanks!
Related
Hi All not sure if anyone is having this but when making changes it adds the blue box on the left-hand side which is fine as before this was just showing what had changed. Now though, it's added this discard change and gives you a kind of before and after within your code. It's really really annoying and difficult to make changes. I've added a screenshot here where I was just removing so spacing. The code doesn't appear to do anything until you commit. Turning off Source Control completely doesn't even get rid of it.
Does anyone have any solutions for just turning this silly feature off completely? I've always used git fine with no issues within Xcode, I don't need to see the old change just what I'm actually updating the code to be.
OS Win 10
Calibre's latest version, as it was very recently downloaded and installed.
Can someone please advise as to how to reopen the Live View Panel?
I had been editing an ePUB file's text, and also adding images. It was an easy process to add images; i.e., by clicking the desired position in the Live View Panel, and then importing a image.
Unfortunately, I do believe that I probably inadvertantly clicked on something or another, which caused the disappearance of the Live View Panel. All the other panels on the editing screen were still visible.
A search of the edit screen for a feature enabling me to view display panel agin was unsuccessful.
I tried clicking other HTML files in the Text panel, hoping it would cause the Live View Panel appear, to no avail.
I closed the entire program, and reopened it several times, with the same results.
I loaded different ePub files, and each time I went into edit mode, the Live View Panel was missing. And, all along, I did try the previously mentioned measures.
I even uninstalled Calibre and reinstalled it, twice! And, I made sure that its installation folders had been deleted upon each uninstallation. But, somehow, upon reinstallation startup, Calibre knew the very "special" folder (i.e., which I had designated in an earlier installation) into which to setup its User-related files and its library. [I thought it was probably due to system registry setting.]
Finally, I again uninstalled Calibre. However, this time, before doing a reinstallation, I restored Windows settings. I used a (restore) point that I had created prior to Calibre's first installation. I had hoped that any Registry settings related to Calibre would surely not survive. Nevertheless, upon a subsequent Calibre reinstallation, the program simply failed to display the "Live View Panel." (Go figure!)
I would certaintly appreciate any feedback.
If a file open in geany is modified by another program, and geany is then brought to the front, then geany displays a modal dialog as follows.
The file 'stuff.txt' on the disk is more recent than
the current buffer.
Do you want to reload it?
This dialog is displayed, blocking any sort of work flow if files are continually regenerated by running command-line tools. How can this behavior be changed so that the dialog does not appear, and geany automatically reloads any such file?
Close Geany (else your changes will be overwritten), then open geany.conf in a different editor. Find disk_check_timeout and set it to 0. Save that, and reopen Geany.
Open geany.conf in a different editor and set the line reload_clean_doc_on_file_change=false to reload_clean_doc_on_file_change=true
The dialog cannot be disabled and automatic reloading is not supported (which could be bad anyway, depending on whether you've made changes to the document).
That being said, I had started working on a better method using GtkInfoBar like Gedit uses so that it wouldn't block you from working but still notify you of changes. Unfortunately I haven't had much time or interest to push it through into the master branch. If you feel like trying to use it (not recommended in current out-of-date/incomplete state) or continuing work on it, the branch is here.
I've recently upgraded from Xcode 4.3 to 4.4 and I'm about to bash my screen in with frustration.
The problem I'm having is with the code completion. As I type a variable or method name, the completion window pops up with the suggestions like it's supposed to. But if I attempt to use the cursor keys to scroll between the suggestions, the suggestions disappear and the cursor moves in the code, not between the suggestions. If I press enter to accept the default suggestion, it again dismisses the suggestions and inserts a return into the code taking the cursor to the next line.
This doesn't happen every time I attempt code completion, but it does occur more often than not. For a given name I'm trying to complete, it either works or it doesn't (e.g. if I press escape to get the suggestions back, it will disappear just as quickly as the first time it disappeared for that line/name I was trying to complete). When I get to the next line of code, it's a whole new bet whether it will work or not. It seems that the closer to the actual completion of the name I am, the more likely it is to actually work and accept the suggestion or move between the suggestions. Sometimes, if I act quickly enough, I can move the highlighted suggestion one or two lines before the suggestions disappear. I'm aware that if you don't select a suggestion quickly enough that it's supposed to eventually remove the suggestions (on the order of several seconds), but this behavior is not what I'm describing. I'd be VERY happy at this point if I had a single second to actually respond and select a suggestion from the pop-up.
So far I've tried a clean of the project, deleting all of the project's derived data, and restarting xcode. All of which don't seem to affect the behavior. Any ideas? I've searched stackoverflow and google and haven't found any other people reporting this problem ...
Thanks for any ideas,
Will
UPDATE:
After upgrading to the XCode 4.6 release version (and 4.5 somewhere in the middle there), this problem is still present ... and making edits in the left/main editor window is still a work-around.
I am seeing the same with Xcode 4.4.1. It seems to be related to where the completion window pops up. Debugger pane open or closed does not change anything here.
When in the Assistant Editor trying in the right pane the completion windows flickers. Same line of code in the left window works fine. Single editor works, too.
Try upgrading to Xcode 4.4.1. I used to have this problem, but I don't seem to have it after upgrading.
If this doesn't solve the problem, a crude workaround seems to be to put a lot of blank lines at the bottom of each file - the problem seems to occur from frequently when the file is scrolled all the way to the bottom.
There is a fix (at least Xcode 4.6.3): re-create the affected file by deleting it. Now create a new file and copy the content to it and drag it into the project - done. Fixes the issue here. It seems to be tied to certain files.
I'm having some trouble with Xcode. A lot of times I'll just be typing code in, and then something will suddenly happen that screws up how the text displays on the page. Sometimes it will cut off the first characters of some lines. Other times, especially when I'm typing near the bottom (I notice it occurs when it tries to do some autocomplete but I type over it) it will not display the bottom text (like the #end) and won't take anymore text input properly.
If I quit and restart, the file displays properly again until it happens another time. Does anyone have any ideas how to fix this? I just tried reinstalling Xcode, but even after doing that I still have the same problem.
This problem is really annoying because I often have to quit and restart constantly, and sometimes it's scary because it looks like I've lost the code that I've typed in.
A couple of suggestions:
make sure you're using the latest version of Xcode (3.2.1)
rather than quit and restart, try just saving and closing the file's window and then re-open it
The real solution to this problem is close quick help.
Turns out "Quick Help" causes alot of issues with codesense.
If you close it your troubles are gone. It will work fine once you reopen it... for a while. Then it will begin messing up again.
I used to leave quick help up 24/7 so this happened frequently. I have seen other reports of this being the cause on a few other sites. Aven on this very same site. (stackoverflow)