I just downloaded TM2 build 8930, but it seems that the projects are gone?
I can open old projects (.tmproject files), but it's just showing an XML and also it's not possible anymore to create new projects..
Are they gone in TM2? If so, that would be a real bummer...
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
~Peter Jahn
On Wed, Dec 14, 2011 at 1:01 AM, Arjan82 arjan@uprise.nl wrote:
I just downloaded TM2 build 8930, but it seems that the projects are gone?
I can open old projects (.tmproject files), but it's just showing an XML and also it's not possible anymore to create new projects..
Are they gone in TM2? If so, that would be a real bummer...
View this message in context: http://old.nabble.com/Projects-are-gone-in-TM2--tp32970824p32970824.html Sent from the textmate users mailing list archive at Nabble.com.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser (toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give it a try and if you still feel hindered after some weeks, let us know about it.
While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle.
But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things.
Adam Merrifield seyDoggy vCard: seydoggy.com/vcard
On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser (toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Any code editor without project support just does not understand software development. Presumably you use Xcode. Now, you may use TM for editing your files, but, Xcode would be far less useful if it did not have the concept of projects.
I do not want a 'favorites', as that's just silly in the context of editing text. I do not, in any way, 'prefer' or 'favor' one over another. There is simply the one I am working on at the moment. And if I do not get back to it for a year, I want the files associated with that project to still be there.
And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? 1980 called and wants their hidden files back. Yes, some may prefer these files, and for the most part, they still use emacs & vi. I'm not knocking either of these, as I'm a huge fan of vi. But for anyone to say that editing the dot files is more flexible then a well-thought out preferences pane, ala Qt Designer or to a lesser extent Xcode, they are just deluding themselves. I'm interested in replacing all of my use of vim largely do to the difficulty of quickly understanding what is going on and why, and the enormous number of keyboard shortcuts one needs to remember to be proficient with the editor. Oh, and I see you referenced how many shortcuts? Huh,
I write code, and I want to concentrate on writing code. Not fiddling with the configuration, or 'favorites' of the editor.
On Wed, Dec 14, 2011 at 7:40 AM, Merrifield Adam macagp@gmail.com wrote:
While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle.
But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things.
Adam Merrifield seyDoggy vCard: seydoggy.com/vcard
On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha
and
will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser
(toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give
it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Guys, but you don't have nothing to do other that testing the alpha version of TM? :-)
You don't some code to write?
Just joking, but flames against me are welcome!
ciao!
On Dec 14, 2011, at 3:59 PM, Reaves, Timothy wrote:
Any code editor without project support just does not understand software development. Presumably you use Xcode. Now, you may use TM for editing your files, but, Xcode would be far less useful if it did not have the concept of projects.
I do not want a 'favorites', as that's just silly in the context of editing text. I do not, in any way, 'prefer' or 'favor' one over another. There is simply the one I am working on at the moment. And if I do not get back to it for a year, I want the files associated with that project to still be there.
And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? 1980 called and wants their hidden files back. Yes, some may prefer these files, and for the most part, they still use emacs & vi. I'm not knocking either of these, as I'm a huge fan of vi. But for anyone to say that editing the dot files is more flexible then a well-thought out preferences pane, ala Qt Designer or to a lesser extent Xcode, they are just deluding themselves. I'm interested in replacing all of my use of vim largely do to the difficulty of quickly understanding what is going on and why, and the enormous number of keyboard shortcuts one needs to remember to be proficient with the editor. Oh, and I see you referenced how many shortcuts? Huh,
I write code, and I want to concentrate on writing code. Not fiddling with the configuration, or 'favorites' of the editor.
On Wed, Dec 14, 2011 at 7:40 AM, Merrifield Adam macagp@gmail.com wrote: While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle.
But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things.
Adam Merrifield seyDoggy vCard: seydoggy.com/vcard
On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser (toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 14 Dec 2011, at 14:59, Reaves, Timothy wrote:
Any code editor without project support just does not understand software development. Presumably you use Xcode. Now, you may use TM for editing your files, but, Xcode would be far less useful if it did not have the concept of projects.
It may not work for you but I gave up on textmate's project feature a long time ago and just open the app's directory in textmate. I didn't find having a textmate specific view of the real directory particularly useful (i.e. being able to reorder the files and group them in some arbitrary way) and vaguely remember problems in creating new files as to where they went in the real directory structure.
You can include any other directory in your apps directory using a symlink - not quite the same as how is would be done in a project, but achieves the same thing.
I'd be curious to know what I am overlooking that makes projects so compelling.
I agree that 'favorites' don't seem that useful.
Dave.
I do not want a 'favorites', as that's just silly in the context of editing text. I do not, in any way, 'prefer' or 'favor' one over another. There is simply the one I am working on at the moment. And if I do not get back to it for a year, I want the files associated with that project to still be there.
And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? 1980 called and wants their hidden files back. Yes, some may prefer these files, and for the most part, they still use emacs & vi. I'm not knocking either of these, as I'm a huge fan of vi. But for anyone to say that editing the dot files is more flexible then a well-thought out preferences pane, ala Qt Designer or to a lesser extent Xcode, they are just deluding themselves. I'm interested in replacing all of my use of vim largely do to the difficulty of quickly understanding what is going on and why, and the enormous number of keyboard shortcuts one needs to remember to be proficient with the editor. Oh, and I see you referenced how many shortcuts? Huh,
I write code, and I want to concentrate on writing code. Not fiddling with the configuration, or 'favorites' of the editor.
On Wed, Dec 14, 2011 at 7:40 AM, Merrifield Adam macagp@gmail.com wrote: While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle.
But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things.
Adam Merrifield seyDoggy vCard: seydoggy.com/vcard
On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser (toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
My modest Opinion: you need a project support if you use a framework.
If the framework is well organized (take rails as an example) the APP directory IS the project. You don't need nothing more.
I agree that 'favorites' don't seem that useful. +1
D
On Dec 14, 2011, at 4:29 PM, Dave Baldwin wrote:
On 14 Dec 2011, at 14:59, Reaves, Timothy wrote:
Any code editor without project support just does not understand software development. Presumably you use Xcode. Now, you may use TM for editing your files, but, Xcode would be far less useful if it did not have the concept of projects.
It may not work for you but I gave up on textmate's project feature a long time ago and just open the app's directory in textmate. I didn't find having a textmate specific view of the real directory particularly useful (i.e. being able to reorder the files and group them in some arbitrary way) and vaguely remember problems in creating new files as to where they went in the real directory structure.
You can include any other directory in your apps directory using a symlink - not quite the same as how is would be done in a project, but achieves the same thing.
I'd be curious to know what I am overlooking that makes projects so compelling.
I agree that 'favorites' don't seem that useful.
Dave.
I do not want a 'favorites', as that's just silly in the context of editing text. I do not, in any way, 'prefer' or 'favor' one over another. There is simply the one I am working on at the moment. And if I do not get back to it for a year, I want the files associated with that project to still be there.
And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? 1980 called and wants their hidden files back. Yes, some may prefer these files, and for the most part, they still use emacs & vi. I'm not knocking either of these, as I'm a huge fan of vi. But for anyone to say that editing the dot files is more flexible then a well-thought out preferences pane, ala Qt Designer or to a lesser extent Xcode, they are just deluding themselves. I'm interested in replacing all of my use of vim largely do to the difficulty of quickly understanding what is going on and why, and the enormous number of keyboard shortcuts one needs to remember to be proficient with the editor. Oh, and I see you referenced how many shortcuts? Huh,
I write code, and I want to concentrate on writing code. Not fiddling with the configuration, or 'favorites' of the editor.
On Wed, Dec 14, 2011 at 7:40 AM, Merrifield Adam macagp@gmail.com wrote: While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle.
But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things.
Adam Merrifield seyDoggy vCard: seydoggy.com/vcard
On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser (toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
I've used custom plist files in project did for custom bundles i have for development (like having phpunit configuration file path, single execution file for a project no matter where you currently located in the project. I'd love to have projects support + custom project attrs editing + some king of snippets to simplify getting project attributes from bundles code.
On Wednesday, December 14, 2011 at 8:32 PM, Davide Rambaldi wrote:
My modest Opinion: you need a project support if you use a framework. If the framework is well organized (take rails as an example) the APP directory IS the project. You don't need nothing more. I agree that 'favorites' don't seem that useful. +1 D On Dec 14, 2011, at 4:29 PM, Dave Baldwin wrote:
On 14 Dec 2011, at 14:59, Reaves, Timothy wrote:
Any code editor without project support just does not understand software development. Presumably you use Xcode. Now, you may use TM for editing your files, but, Xcode would be far less useful if it did not have the concept of projects.
It may not work for you but I gave up on textmate's project feature a long time ago and just open the app's directory in textmate. I didn't find having a textmate specific view of the real directory particularly useful (i.e. being able to reorder the files and group them in some arbitrary way) and vaguely remember problems in creating new files as to where they went in the real directory structure. You can include any other directory in your apps directory using a symlink - not quite the same as how is would be done in a project, but achieves the same thing. I'd be curious to know what I am overlooking that makes projects so compelling. I agree that 'favorites' don't seem that useful. Dave.
I do not want a 'favorites', as that's just silly in the context of editing text. I do not, in any way, 'prefer' or 'favor' one over another. There is simply the one I am working on at the moment. And if I do not get back to it for a year, I want the files associated with that project to still be there. And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? 1980 called and wants their hidden files back. Yes, some may prefer these files, and for the most part, they still use emacs & vi. I'm not knocking either of these, as I'm a huge fan of vi. But for anyone to say that editing the dot files is more flexible then a well-thought out preferences pane, ala Qt Designer or to a lesser extent Xcode, they are just deluding themselves. I'm interested in replacing all of my use of vim largely do to the difficulty of quickly understanding what is going on and why, and the enormous number of keyboard shortcuts one needs to remember to be proficient with the editor. Oh, and I see you referenced how many shortcuts? Huh, I write code, and I want to concentrate on writing code. Not fiddling with the configuration, or 'favorites' of the editor. On Wed, Dec 14, 2011 at 7:40 AM, Merrifield Adam <macagp@gmail.com (mailto:macagp@gmail.com)> wrote:
While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle. But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things. Adam Merrifield seyDoggy vCard: seydoggy.com/vcard (http://seydoggy.com/vcard) On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha and will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser (toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com (mailto:textmate@lists.macromates.com) http://lists.macromates.com/listinfo/textmate
_______________________________________________ textmate mailing list textmate@lists.macromates.com (mailto:textmate@lists.macromates.com) http://lists.macromates.com/listinfo/textmate
_______________________________________________ textmate mailing list textmate@lists.macromates.com (mailto:textmate@lists.macromates.com) http://lists.macromates.com/listinfo/textmate
_______________________________________________ textmate mailing list textmate@lists.macromates.com (mailto:textmate@lists.macromates.com) http://lists.macromates.com/listinfo/textmate
_______________________________________________ textmate mailing list textmate@lists.macromates.com (mailto:textmate@lists.macromates.com) http://lists.macromates.com/listinfo/textmate
On 14 Dec 2011, at 15:59, Reaves, Timothy wrote:
Any code editor without project support just does not understand software development.
You really expect me to spend time trying to understand your workflow and spend time adopting my software to better suit your needs with an opening like that?
Presumably you use Xcode.
No, I would be far far less productive in Xcode *including* the project aspects.
TextMate consists of some 30+ frameworks each with their own unit tests — by creative use of .tm_properites I have ⌘B always run the proper make goal, including temporarily changing a certain framework to only have its unit tests run or a special “GUI” test if I’m developing a component that can be tested “outside” TextMate.
I also have adopted a few actions depending on where I am in which project/file, all via the use of the folder specific .tm_properties.
I do not want a 'favorites', as that's just silly […]
I often just skim people’s feedback because there is far too much to read, so a word of advice is to avoid superfluous text like calling things ‘silly’ and go on for lines and lines about the same thing…
And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? […]
Maybe hold judgement till you have learned more about what these allow.
1980 called and wants their hidden files back […]
OK… I stopped reading here…
In the future, please be more constructive, less judgmental, and avoid the insults.
And '.tm_properties' being far more flexible? Really? Becausr you're not a real coder if you don't modify your own dot configuration file? […]
Maybe hold judgement till you have learned more about what these allow.
I'm looking forward to the possibilities of the .tm_properties file.
I got real work done yesterday using tm2. Congrats to Allan and team.
On Dec 14, 2011, at 8:22 AM, Allan Odgaard wrote:
TextMate consists of some 30+ frameworks each with their own unit tests — by creative use of .tm_properites I have ⌘B always run the proper make goal, including temporarily changing a certain framework to only have its unit tests run or a special “GUI” test if I’m developing a component that can be tested “outside” TextMate.
That's pretty cool. Are you saying it's possible to nest .tm_properties? That is, put a "global" .tm_properties at the top level of the project and another one in a subdirectory that overrides the top-level properties. This could be useful if, for example, one of the 30 frameworks requires a custom build command.
Trevor
On 15 Dec 2011, at 06:48, Trevor Harmon wrote:
[…] Are you saying it's possible to nest .tm_properties? That is, put a "global" .tm_properties at the top level of the project and another one in a subdirectory that overrides the top-level properties. This could be useful if, for example, one of the 30 frameworks requires a custom build command.
Exactly, or one of the frameworks is MASPreferences¹ which uses another coding style than me, so I have:
# vendor/MASPreferences/.tm_properties tabSize = 4 softTabs = true TM_C_POINTER = " *"
The “root” .tm_properties though can also target subsets, for example I have:
[ "tests/t_*" ] scopeAttributes = 'attr.test.cxxtest' TM_MAKE_TARGET = '${TM_FILEPATH/^.*?([^/]*)/tests/.*$/$1/}/test'
[ "tests/t_*.mm" ] GUI_TESTS = '${TM_FILENAME/^t_(.*).mm$/$1/}'
So when I am in a test file (e.g. Framework/buffer/tests/t_buffer.cc) I have a different make goal and I have ‘attr.test.cxxtest’ in my scope so I get test assertions instead of regular debug assertions on A⇥.
Furthermore when I’m in say Frameworks/OakAppKit/tests/t_tabbar.mm I have the GUI_TESTS variable set to ‘tabbar’: normally GUI tests are skipped by the make process (because they open windows and are often interactive), but not when I’m actually in the test file such GUI test.
It sounds like .tm_properties will handle most of what projects do now in terms of saving state. A discrete project file has one big upside though: Opening the project from outside the editor.
How many of us open up Word or Photoshop and do File > Open, vs just double-clicking on an icon, or using something like Alfred or Launchbar?
TM 2 crashes/freezes whenever I tried to navigate to my project directories, so I haven't been able to live with this new workflow, but I hope there's some way to make it easier to use from outside the editor. Even if tmproj is nothing but a one-line instruction to TM to open a particular favorite, it would help.
Looking forward to future Alphas.
Thanks
On Wed, Dec 14, 2011 at 5:40 AM, Merrifield Adam macagp@gmail.com wrote:
While I haven't tried all the favorites and such in TM2 (yet) I will argue that one reason for me to use tmproj is because the app bundles I work on are obscured from normal view, making them cumbersome to navigate to. And there are far too many to add to favorites. tmproj was a nice way to have almost a symlink for TextMate, if you will, to the bundle.
But as I said, I haven't actually tried the favorites so I will hold off further commentary until I am knowledgeable to speak on such things.
Adam Merrifield seyDoggy vCard: seydoggy.com/vcard
On Dec 14, 2011, at 4:36 AM, Allan Odgaard wrote:
On 14 Dec 2011, at 10:27, Peter Jahn wrote:
As with many features, projects are most likely absent from the alpha
and
will probably be restored at a later stage, almost certainly before the final release.
We don’t intend to restore tmproj files — there is a file browser
(toggles on ⌃⌥⌘D), add to favorites (e.g. for folders) / open favorites (⌘T-style “project open” on ⇧⌘O), session restore (i.e. keep the existing stuff open on relaunch), new window with file browser showing (⌃⌘N), folder specific settings, i.e. “project settings” but far more flexible (see upcoming blog post about .tm_properties), SCM status in file browser (⇧⌘Y), show (reveal) current file in browser (⌃⌘R), etc.
Those things should make up for not having the old project files — give
it a try and if you still feel hindered after some weeks, let us know about it.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
I rely on project files for TextMate for the following reasons:
(1) I work on many different projects, bouncing between the sets of sources within each project. By opening a project file, it makes it easy for me to restore where I was at when I bounce from one project back to another.
(2) I work in a team, where each developer uses different tools on different platforms. I prefer to keep my TextMate project files in a completely separate area away from the sources so I don't have to worry about polluting the source repository with "my baggage."
(3) Because each set of sources contains multi platform files, I use the TextMate project settings to hide sources (via regex syntax) for files I don't want to see or more importantly find references in when I do a "find in project" search.
Please keep projects in TM2 or an equivalent way to group sets of sources.
Surely your whole project is inside one folder. And surely if you're working on a team, you're using git or svn.
Open the project folder. Bam. You're done. You've opened your project. If your project contains a bunch of directories lying around your system then, my friend, you are doing it wrong. (And if you have some perverse reason to do that, there are symlinks.)
And obviously you want to add .tm_properties to your .gitignore. Jeez.
I have to second the use case of using the project to filter out files and directories I don't want "Search in project" to look in. Is there way to do this in TM2 without projects?
Jeff
On Dec 14, 2011, at 5:54 PM, Morgan Harris wrote:
Surely your whole project is inside one folder. And surely if you're working on a team, you're using git or svn.
Open the project folder. Bam. You're done. You've opened your project. If your project contains a bunch of directories lying around your system then, my friend, you are doing it wrong. (And if you have some perverse reason to do that, there are symlinks.)
And obviously you want to add .tm_properties to your .gitignore. Jeez.
-- Morgan Harris Sent with Sparrow
On Thursday, 15 December 2011 at 9:47 AM, dvlogic wrote:
I rely on project files for TextMate for the following reasons:
(1) I work on many different projects, bouncing between the sets of sources within each project. By opening a project file, it makes it easy for me to restore where I was at when I bounce from one project back to another.
(2) I work in a team, where each developer uses different tools on different platforms. I prefer to keep my TextMate project files in a completely separate area away from the sources so I don't have to worry about polluting the source repository with "my baggage."
(3) Because each set of sources contains multi platform files, I use the TextMate project settings to hide sources (via regex syntax) for files I don't want to see or more importantly find references in when I do a "find in project" search.
Please keep projects in TM2 or an equivalent way to group sets of sources.
-- View this message in context: http://old.nabble.com/Projects-are-gone-in-TM2--tp32970824p32976071.html Sent from the textmate users mailing list archive at Nabble.com.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Jeff,
Try experimenting with the settings listed below in .tm_properties. They all take a glob string, so an example would be: exclude = "{*.{o,pyc},Icon\r,CVS,_darcs,_MTN,{arch},blib,*~.nib}"
Hope this helps,
-Amiel
* `exclude` * `excludeFiles` * `excludeDirectories` * `excludeInBrowser` * `excludeInFolderSearch` * `excludeInFileChooser` * `excludeFilesInBrowser` * `excludeDirectoriesInBrowser` * `include` * `includeFiles` * `includeDirectories` * `includeInBrowser` * `includeInFileChooser` * `includeFilesInBrowser` * `includeDirectoriesInBrowser` * `includeFilesInFileChooser`
On Wed, Dec 14, 2011 at 3:09 PM, Jeff Paquette paquette@atnetsend.netwrote:
I have to second the use case of using the project to filter out files and directories I don't want "Search in project" to look in. Is there way to do this in TM2 without projects?
Jeff
On Dec 14, 2011, at 5:54 PM, Morgan Harris wrote:
Surely your whole project is inside one folder. And surely if you're working on a team, you're using git or svn.
Open the project folder. Bam. You're done. You've opened your project. If your project contains a bunch of directories lying around your system then, my friend, you are doing it wrong. (And if you have some perverse reason to do that, there are symlinks.)
And obviously you want to add .tm_properties to your .gitignore. Jeez.
-- Morgan Harris Sent with Sparrow http://www.sparrowmailapp.com/?sig
On Thursday, 15 December 2011 at 9:47 AM, dvlogic wrote:
I rely on project files for TextMate for the following reasons:
(1) I work on many different projects, bouncing between the sets of sources within each project. By opening a project file, it makes it easy for me to restore where I was at when I bounce from one project back to another.
(2) I work in a team, where each developer uses different tools on different platforms. I prefer to keep my TextMate project files in a completely separate area away from the sources so I don't have to worry about polluting the source repository with "my baggage."
(3) Because each set of sources contains multi platform files, I use the TextMate project settings to hide sources (via regex syntax) for files I don't want to see or more importantly find references in when I do a "find in project" search.
Please keep projects in TM2 or an equivalent way to group sets of sources.
-- View this message in context: http://old.nabble.com/Projects-are-gone-in-TM2--tp32970824p32976071.html Sent from the textmate users mailing list archive at Nabble.com.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 15 Dec 2011, at 00:09, Jeff Paquette wrote:
I have to second the use case of using the project to filter out files and directories I don't want "Search in project" to look in. Is there way to do this in TM2 without projects?
Use one of the ‘exclude’ keys in .tm_properties, relevant links here: http://lists.macromates.com/textmate/2011-December/033476.html
One use case that I find useful is perhaps when working on a wordpress project.
Usually I exclude all of the core wordpress files and directories and only add to the project the theme and plugin folders.
wordpress folder hierarchy is something like this
wordpress wordpress/wp-includes wordpress/wp-admin wordpress/wp-content/themes/THEME_DIR wordpress/wp-content/plugins/PLUGIN_DIR
so in the project browser I would only add:
wordpress/wp-content/themes/THEME_DIR wordpress/wp-content/plugins/PLUGIN_DIR wordpress/wp-content/plugins/PLUGIN_DIR2 wordpress/wp-content/plugins/PLUGIN_DIR3
So lets say in the tm_properties for that project folder, I would add only the directories above right?
I tried using includeDirectoriesInBrowser and includeDirectories with the value being the full path but nothing happened after reloading.
Any hints?
Thanks
On Dec 14, 2011, at 3:16 PM, Allan Odgaard wrote:
On 15 Dec 2011, at 00:09, Jeff Paquette wrote:
I have to second the use case of using the project to filter out files and directories I don't want "Search in project" to look in. Is there way to do this in TM2 without projects?
Use one of the ‘exclude’ keys in .tm_properties, relevant links here: http://lists.macromates.com/textmate/2011-December/033476.html
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Dec 14, 2011, at 2:54 PM, Morgan Harris wrote:
Open the project folder. Bam. You're done. You've opened your project.
Not all projects are so simple. At work, for example, we have a very large project (150+ developers) spread across two different SCM repositories. The part I'm working on is in one repo, buried deep in the hierarchy, while its test cases are in another repo altogether. In TextMate 1.x, this wasn't a problem because a project could have a view of just those two folders, no matter where they were. But in TextMate 2, I'll have to open a root folder that's common to both -- but that pulls in hundreds of thousands of files comprising 3GB of data. I don't think "Go to File" or "Find in Project" would be very useful in that situation!
So far in this discussion I've not seen a way to handle this. I suppose I could work around it by creating symbolic links, but it would be nice to handle it within TextMate.
Trevor
On 15 Dec 2011, at 06:51, Trevor Harmon wrote:
On Dec 14, 2011, at 2:54 PM, Morgan Harris wrote:
Open the project folder. Bam. You're done. You've opened your project.
Not all projects are so simple. At work, for example, we have a very large project (150+ developers) spread across two different SCM repositories. The part I'm working on is in one repo, buried deep in the hierarchy, while its test cases are in another repo altogether. In TextMate 1.x, this wasn't a problem because a project could have a view of just those two folders, no matter where they were. But in TextMate 2, I'll have to open a root folder that's common to both -- but that pulls in hundreds of thousands of files comprising 3GB of data. I don't think "Go to File" or "Find in Project" would be very useful in that situation!
So far in this discussion I've not seen a way to handle this. I suppose I could work around it by creating symbolic links, but it would be nice to handle it within TextMate.
Yup. Create a project folder and add symlinks into it that point to all the disjoint or shared (with other projects, coworkers, etc.) files and folders you want to work on but cannot have the physical file/folder in your project folder. I haven't looked but would expect adding a command to Textmate to add symbolic link to a file/folder to the project window would be quite easy to do.
Dave.
Trevor
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Lots of new stuff to love!
I'm not tracking the discussion of .tm_properties and what it can do but I too am concerned about the loss of TM projects. I don't work on "apps" in the current trendy sense of the word so there is no inherent organization to my project's code within the file system, as others have suggested. I do numerical calculations with terminal and graphics output, pulling code from various places. My code in the file system is organized by a certain method, but I need to organize by completely different criteria in a TM project. Thus, the TM project concept gives an orthogonal method of organization which does not require re-arranging things in the file system, and each project has its own orthogonality with respect to not only the file system but other projects.
I'm willing to see what transpires, but for me, so far, the TM project is essential for my work.
I suppose it is possible to keep project-like folders in the Finder using aliases, but that takes the file management outside of TM.
Jerry
-
Allan Odgaard -
Amiel Martin -
Arjan82 -
Danil Shingarev -
Dave Baldwin -
Davide Rambaldi -
dvlogic -
Jeff Paquette -
Jerry -
Josh Kritner -
Merrifield Adam -
Morgan Harris -
Peter Jahn -
Reaves, Timothy -
Trevor Harmon -
Will -
William Pickens