View Revision in the subversion bundle is not working for me. The dialogue window appears briefly and then disappears. Checking the console, there is the following error message:
error 63 (File name too long) opening sem /tm_dialog async/ markkalderon/1.
The thing is, my file names aren't particularly long. The command chokes no matter how small the file name. Any ideas how to debug this?
Thanks, Mark
same here. it used to work, but not anymore. This is both "Diff revisions" and "Diff with revision"
On Apr 8, 2007, at 2:35 AM, Mark Eli Kalderon wrote:
View Revision in the subversion bundle is not working for me. The dialogue window appears briefly and then disappears. Checking the console, there is the following error message:
error 63 (File name too long) opening sem /tm_dialog async/ markkalderon/1.
The thing is, my file names aren't particularly long. The command chokes no matter how small the file name. Any ideas how to debug this?
Thanks, Mark
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 8. Apr 2007, at 15:16, Constantinos Neophytou ♎ wrote:
same here. it used to work, but not anymore. This is both "Diff revisions" and "Diff with revision"
You also get the “file name too long” error?
Could you guys try give a reproducible example, i.e. a file residing in a public repository (as the command works fine for me)?
Also be sure not to have outdated versions of the Subversion bundle / Support folder:
http://macromates.com/wiki/Troubleshooting/RevertToDefaultBundles
On Apr 8, 2007, at 2:35 AM, Mark Eli Kalderon wrote:
View Revision in the subversion bundle is not working for me. The dialogue window appears briefly and then disappears. Checking the console, there is the following error message:
error 63 (File name too long) opening sem /tm_dialog async/ markkalderon/1.
The thing is, my file names aren't particularly long. The command chokes no matter how small the file name. Any ideas how to debug this?
Thanks, Mark
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Apr 9, 2007, at 12:40 PM, Allan Odgaard wrote:
You also get the “file name too long” error?
Yes, in the console... After trying to execute the command 3 times on the same file: error 63 (File name too long) opening sem /tm_dialog async/ Constantinos/6. error 63 (File name too long) opening sem /tm_dialog async/ Constantinos/7. error 63 (File name too long) opening sem /tm_dialog async/ Constantinos/8.
Apart from that error in the console, there are no notification of any kind, the window just pops up and immediately disappears, and that's it. The other diff commands work just fine.
I'd like to note that a few weeks back the commands were working just fine with the same repository...
Could you guys try give a reproducible example, i.e. a file residing in a public repository (as the command works fine for me)?
Unfortunately all the subversion repositories I'm working on are private, but they all have the same problem...
Also be sure not to have outdated versions of the Subversion bundle / Support folder:
http://macromates.com/wiki/Troubleshooting/RevertToDefaultBundles
I had (for some reason) a copy of the subversion bundle checked out on my local machine. After updating it, all the diff commands stopped working (something about a file not found). Since I had no local modifications, I just removed the checked out bundle and reloaded the bundles in textmate. Then the behavior went back to what I described..
On 9. Apr 2007, at 10:33, Constantinos Neophytou ♎ wrote:
[...] Yes, in the console... After trying to execute the command 3 times on the same file: error 63 (File name too long) opening sem /tm_dialog async/ Constantinos/6.
Looking into the error, it seems the semaphore name is too long, and coincidentally both you and mark has a name of 32 characters, so that might be the limit (excl. null byte).
I changed the code to use the user ID instead of name, so that should result in a shorter semaphore name.
To test the update do:
mkdir -p /Library/Application\ Support/TextMate cd /Library/Application\ Support/TextMate svn co http://macromates.com/svn/Bundles/trunk/PlugIns
Then relaunch TextMate -- and you want to remove the checked-out plug- in again, after next TM update (to revert to the default version).
On Apr 9, 2007, at 2:44 PM, Allan Odgaard wrote:
Looking into the error, it seems the semaphore name is too long, and coincidentally both you and mark has a name of 32 characters, so that might be the limit (excl. null byte).
I changed the code to use the user ID instead of name, so that should result in a shorter semaphore name.
To test the update do:
mkdir -p /Library/Application\ Support/TextMate cd /Library/Application\ Support/TextMate svn co http://macromates.com/svn/Bundles/trunk/PlugIns
Then relaunch TextMate -- and you want to remove the checked-out plug-in again, after next TM update (to revert to the default version).
Yep, that did the trick... thanks!
On Apr 9 2007, at 10:14, Allan Odgaard wrote:
On 9. Apr 2007, at 10:33, Constantinos Neophytou ♎ wrote:
[...] Yes, in the console... After trying to execute the command 3 times on the same file: error 63 (File name too long) opening sem /tm_dialog async/ Constantinos/6.
Looking into the error, it seems the semaphore name is too long, and coincidentally both you and mark has a name of 32 characters, so that might be the limit (excl. null byte).
I changed the code to use the user ID instead of name, so that should result in a shorter semaphore name.
To test the update do:
mkdir -p /Library/Application\ Support/TextMate cd /Library/Application\ Support/TextMate svn co http://macromates.com/svn/Bundles/trunk/PlugIns
Then relaunch TextMate -- and you want to remove the checked-out plug-in again, after next TM update (to revert to the default version).
Thanks, Allan, that worked for me as well. Best, Mark