Hello all,
I must be missing something simple, but this morning my TM refused to open any projects, old or new. I am using build 1324. The projects I tried to open are all listed under Window, but they are not visible. I closed all other apps, rebooted, but the problem remains.
Jenny
On 7. Nov 2006, at 16:31, Jenny Harrison wrote:
I must be missing something simple, but this morning my TM refused to open any projects, old or new. I am using build 1324. The projects I tried to open are all listed under Window, but they are not visible. I closed all other apps, rebooted, but the problem remains.
Try select a project from the window menu and then some of the other options, such as Arrange in Front, Zoom, and Minimize -- see if that affects it.
On Nov 7, 2006, at 10:38 AM, Allan Odgaard wrote:
On 7. Nov 2006, at 16:31, Jenny Harrison wrote:
I must be missing something simple, but this morning my TM refused to open any projects, old or new. I am using build 1324. The projects I tried to open are all listed under Window, but they are not visible. I closed all other apps, rebooted, but the problem remains.
Try select a project from the window menu and then some of the other options, such as Arrange in Front, Zoom, and Minimize -- see if that affects it.
None of these affects it. I have closed all other apps, and all other TM files. The projects are listed under Window but are nowhere to be seen. New Project just gives a new untitled project in Window menu which is also invisible.
Jenny
On 7. Nov 2006, at 16:31, Jenny Harrison wrote:
I must be missing something simple, but this morning my TM refused to open any projects, old or new. I am using build 1324. The projects I tried to open are all listed under Window, but they are not visible. I closed all other apps, rebooted, but the problem remains.
Try select a project from the window menu and then some of the other options, such as Arrange in Front, Zoom, and Minimize -- see if that affects it.
None of these affects it. I have closed all other apps, and all other TM files. The projects are listed under Window but are nowhere to be seen. New Project just gives a new untitled project in Window menu which is also invisible.
I kept experimenting and found that if I toggled between minimize and zoom several times, a small window would eventually show up for each of the projects, old and new. I had to do this for each one separately. But all I can see for each is a window with the title of the project at the top. The drawer is invisible and the contents of the old project are not yet to be found.
Jenny
On 7. Nov 2006, at 20:09, Jenny Harrison wrote:
I kept experimenting and found that if I toggled between minimize and zoom several times, a small window would eventually show up for each of the projects, old and new. I had to do this for each one separately. But all I can see for each is a window with the title of the project at the top. The drawer is invisible and the contents of the old project are not yet to be found.
Okay, from the shell try the following line to see what size TM has stored to use for new projects:
defaults read com.macromates.textmate OakProjectWindowFrame
If this seems bogus, delete it by executing (while TM is not running):
defaults delete com.macromates.textmate OakProjectWindowFrame
This won’t fix existing projects though, these have a ‘windowFrame’ setting embedded in them -- you can open the project file from terminal (with mate) to read the XML file and locate the ‘<key>windowFrame</key>’ followed by a string near the bottom, and simply delete these two lines.
If the problem turns out to be bogus window frames, let me know if you ever use a dual monitor setup (and I will btw add some integrity checks for windows sizes ;) ).
I kept experimenting and found that if I toggled between minimize and zoom several times, a small window would eventually show up for each of the projects, old and new. I had to do this for each one separately. But all I can see for each is a window with the title of the project at the top. The drawer is invisible and the contents of the old project are not yet to be found.
Okay, from the shell try the following line to see what size TM has stored to use for new projects:
defaults read com.macromates.textmate OakProjectWindowFrame
If this seems bogus, delete it by executing (while TM is not running):
defaults delete com.macromates.textmate OakProjectWindowFrame
This won’t fix existing projects though, these have a ‘windowFrame’ setting embedded in them -- you can open the project file from terminal (with mate) to read the XML file and locate the ‘<key>windowFrame</key>’ followed by a string near the bottom, and simply delete these two lines.
If the problem turns out to be bogus window frames, let me know if you ever use a dual monitor setup (and I will btw add some integrity checks for windows sizes ;) ).
That worked! Thanks so much Allan. I executed the delete command you suggested and was then able to open a new projects window. I dragged my old files into its drawer and all is well. I do not use a dual monitor set up. The problem seemed to arise after I installed a plugin for Quicksilver that had a TM icon, but with a name I did not recognize. I just reinstalled QS and see that plugin is no longer available. I am guessing that was the problem.
I know how interesting it must be to work on all the cool cutting edge developments that are coming out, rapid fire, and admire you very much to take the time to help with this problem. I enjoy watching from the sidelines since little tidbits fall my way from time to time that I can understand and are ever so useful. TM is now an indispensable part of my life and I simply love it.
Jenny
On Nov 7, 2006, at 9:38 PM, Allan Odgaard wrote:
If the problem turns out to be bogus window frames, let me know if you ever use a dual monitor setup (and I will btw add some integrity checks for windows sizes ;) ).
Heh - I often use my tmproject files across two machines (I keep the tmproject files in subversion and svn lock/unlock them so I remember not to have them open on one than more machine at a time) with different monitor setups, so I'd certainly appreciate integrity checks. :-)
(Now that I know what's going on I'll probably just write a wrapper for my checkin/checkout of the project file which resets the embedded windowFrame setting.)
j.
On 8. Nov 2006, at 05:20, Jay Soffian wrote:
On Nov 7, 2006, at 9:38 PM, Allan Odgaard wrote:
If the problem turns out to be bogus window frames, let me know if you ever use a dual monitor setup (and I will btw add some integrity checks for windows sizes ;) ).
Heh - I often use my tmproject files across two machines (I keep the tmproject files in subversion and svn lock/unlock them so I remember not to have them open on one than more machine at a time) with different monitor setups, so I'd certainly appreciate integrity checks. :-)
What sort of problems have you experienced?
I tried editing the tmproj file to set a zero width/height, but it does snap back to a 100 x 100 (or so) before brought on screen. I.e. I didn’t find any place where adding integrity checks would solve anything.
On 11/7/06, Allan Odgaard throw-away-1@macromates.com wrote:
This won't fix existing projects though, these have a 'windowFrame' setting embedded in them -- you can open the project file from
Is this kept in the resource fork on the Mac FS? I develop both on Mac and Linux machines. What else does TextMate keep in the resource fork? Since subversion ignores resource forks what happens to any settings which go into a resource fork? I know there is a patch to subversion to work with resource forks but I haven't gone to the trouble of doing it since I haven't seen any odd behaviour thus far and also I'd like to stay with Debian's apt-get for pkg managemet.
-bakki
On 8. Nov 2006, at 15:19, Bakki Kudva wrote:
On 11/7/06, Allan Odgaard throw-away-1@macromates.com wrote:
This won't fix existing projects though, these have a 'windowFrame' setting embedded in them -- you can open the project file from
Is this kept in the resource fork on the Mac FS?
No, it is kept in the project file (.tmproj).
[...] What else does TextMate keep in the resource fork?
http://macromates.com/textmate/manual/ saving_files#extended_attributes_metadata