It is as if a formerly blank seeming file changes some sort of state so that when a fresh emacs tries to open it the file shows up as it should. BadFile1, BadFile2, BadFile3) are now visible right from the start - as they should be on a normally functioning computer. Now, here's the interesting bit: when I start a new terminal window and fire up an emacs loading the same init file then the formerly bad files (e.g. Next, similar to the originally reported case, I hit m-x revert buffer between 1 and 4(?) times and, poof!, the text appears and I am begrundgingly happy again. I haven't seem any error messages akin to "File exists, but cannot be read", but still this is bad behavior and it seems related to the original problem. For other files, call them BadFile1, BadFile2, BadFile3, when I switch to them the screen is blank and I know they have LOTs of text in them. When I change the emacs buffer (c-x b) to point to some files, call them GoodFile1, GoodFile2, there text is visible, i.e. part of the init is to open these files in emacs). I seem to be able to reproduce a very similar behavior when I start emacs using an init file that starts an emacs with about 30 different text files open. new windows, or re-opens when I have closed the buffer).
And once I finally DO open one of those obstinate files, it easily opens using emacs in other contexts (e.g. I usually (always?) am able to open the file. hit m-x revert buffer twice as described above). I try various work arounds to open the file (e.g. This is more or less a repeatable problem (specifically I have gotten "File exists, but cannot be read" several times in the last 2 weeks. The problem is that a file should open on the first try, no questions asked! I do m-x revert buffer again and this time the file reads in fine. "Opening input file: Input/output error, /Users/fred/Dropbox/foo/bar/bam/baz.txt" I try to open a file using emacs c-x c-f /Users/fred/Dropbox/foo/bar/bam/baz.txt.
0 kommentar(er)
