For me, go to project folder has stopped working. Anyone else having this problem?
Works for me, both from the menu and with keyboard.
On Wed, Nov 20, 2013 at 4:19 AM, Jacob Carlborg doob@me.com wrote:
For me, go to project folder has stopped working. Anyone else having this problem?
-- /Jacob Carlborg
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 20 Nov 2013, at 17:19, Jacob Carlborg wrote:
For me, go to project folder has stopped working. Anyone else having this problem?
Is it a problem only with the key binding or also the menu item?
If the latter, could it be you have just set your projectDirectory manually via .tm_properties and it resolves to some bogus value? To get the path of the variable you can press ⌃R on a line containing the following:
echo "$TM_PROJECT_DIRECTORY"
To read the projectDirectory setting press ⌃R on a line containing:
"$TM_QUERY" -s projectDirectory
Note that if the value is unset (by you) then this command will “fail”.
On 2013-11-22 03:14, Allan Odgaard wrote:
Is it a problem only with the key binding or also the menu item?
Both. I don't exactly remember the correct behavior but I expected the selection in the file browser to change. I also tried with the Git diff command, that uses the selection in the file browser.
If the latter, could it be you have just set your projectDirectory manually via .tm_properties and it resolves to some bogus value? To get the path of the variable you can press ⌃R on a line containing the following:
echo "$TM_PROJECT_DIRECTORY"
This command shows the correct path.
To read the projectDirectory setting press ⌃R on a line containing:
"$TM_QUERY" -s projectDirectoryNote that if the value is unset (by you) then this command will “fail”.
This command fails with "Setting or variable 'projectDirectory' not found". I'm not sure if I'm executing it correctly. I did the same as with the first command.
I have not changed any of these settings and I've tried several projects.
On 22 Nov 2013, at 19:58, Jacob Carlborg wrote:
Is it a problem only with the key binding or also the menu item?
Both. I don't exactly remember the correct behavior but I expected the selection in the file browser to change. I also tried with the Git diff command, that uses the selection in the file browser.
The action should change the location in the file browser to the designated project folder.
No selection will change, and if the file browser is already showing your project folder, then it will effectively be a no-op.
Could this just be a misunderstanding of what the action does?
[…] if the value is unset (by you) then this command will “fail”.
This command fails […] I'm not sure if I'm executing it correctly.
As said, it will fail if the setting is not explicitly set, so this is expected.
On 2013-11-23 03:53, Allan Odgaard wrote:
The action should change the location in the file browser to the designated project folder.
No selection will change, and if the file browser is already showing your project folder, then it will effectively be a no-op.
Could this just be a misunderstanding of what the action does?
Yes, it seems so. I got the impression it would select the project folder. What I'm actual was looking for was way to see the SCM diff of the whole project. By default pressing Cmd+Y + a number will only perform that SCM action on the selected file. I was thinking I could select the project folder to get the effected I wanted. I now found that it was the Go -> SCM Status I was looking for. Sorry for the confusion.
On 25 Nov 2013, at 3:14, Jacob Carlborg wrote:
[…] What I'm actual was looking for was [a] way to see the SCM diff of the whole project. By default pressing Cmd+Y + a number will only perform that SCM action on the selected file […]
What you probably want here is ⇧⌘A which is “Deselect All” and with no selection, actions should generally work on the entire project.
Related is ⌃⌘R to select the current document.
On 2013-11-26 09:49, Allan Odgaard wrote:
What you probably want here is ⇧⌘A which is “Deselect All” and with no selection, actions should generally work on the entire project.
Did not know about that one, thanks.
Related is ⌃⌘R to select the current document.
Yes, but most of the item I want to check the status (or similar) for the whole project, not just a single file.
-
Allan Odgaard -
Curt Sellmer -
Jacob Carlborg