SCFinderPlugin is not in the TM2 plugin folder. Quicksilver doesn't crash, just TM2. Also, SVN isn't involved in the crashes. Most of the files being modified are not under version control.
I'll see if I can narrow it down a bit to more exact circumstances.
(My Versions, just in case)
OS X 10.7.3, Build 1D50b
TM2, Version 2.0 (9090)
svn, version 1.6.17 (r1128011) compiled Nov 8 2011, 18:14:46
--Lewy
> On Feb 29, 2012, at 9:10 AM, Allan Odgaard wrote:
>
>> On 29/02/2012, at 03.03, Lewy wrote:
>>
>>> I am getting a LOT of crashes (TM2) when working with files in the project sidebar (right name?). Even things like rename a file, or add a file to favorites will crash TM2. What's interesting is that the crash occurs AFTER the work is done. When I reopen TM2, the file has been renamed or whatever I was trying to do.
>>>
>>> I can supply the crash log to whomever wants it along with a specific case.
>>
>> I don’t think this is normal — my hunch is that there is an issue with the Subversion SCM driver and your working copies, since a) your other post suggest some incompatibility, and b) the SCM code runs after file system changes, which seems to be when you get the crash.
>>
>> For now you can try run w/o subversion and see if you get any crashes.
>>
>> I will see your crashes later (unless you disabled submission).
>
> Possibly unrelated, but SCFinderPlugin causes Quicksilver to crash. If that’s installed, it could be the problem.
>
> --
> Rob McBroom
> <http://www.skurfer.com/>
I have created a wiki page for Project Management under TM2, you can find it here:
http://wiki.macromates.com/Suggestions/ProjectManagementInTextMate2
I wrote Project Management rather than Projects since Allen does not intend to add projects to the 2.0 release (and quite possibly also not at a later date). So my intention was to collect
(1) suggestions on how to improve the file pane,
(2) how to replicate/adapt the workflow for people who have previously used projects and
(3) reasons why the filesystem-centric approach is not suited to meet their needs.
I'd be happy if other people contribute and add suggestions. Perhaps it can become a handy tool for Allen to collect useful feedback.
Max
David,
I had to use "attr.save-on-deactivate" in the Scope Selector instead, but
that did the trick! Thanks so much for explaining this to me.
On Wed, Feb 29, 2012 at 12:39 PM, <textmate-request(a)lists.macromates.com>wrote:
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 29 Feb 2012 18:39:20 +0000
> From: David Howden <dhowden(a)gmail.com>
> To: TextMate users <textmate(a)lists.macromates.com>
> Subject: [TxMt] Re: textmate Digest, Vol 45, Issue 50
> Message-ID:
> <CAP2kWKGbE+81=t_5On1x_hDbdXaZr9LOO7gTwWifCUnxk+NH-Q(a)mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> So this works for me. In the .tm_properties file:
>
> [ *.tex ]
> scopeAttributes = 'attr.save-on-deactivate'
>
> Then put attr.save-on-deactive in the scope for the 'Save on focus lost'
> command.
>
> Be careful: scopeAttributes seem to only be attached to files when you open
> them, so if you change .tm_properties be sure to re-open the files. You
> can make sure that the scope attribute has been set by using the "Show
> Scope" command in bundle development or Ctrl-Shift-P, just to check that
> the attribute is being set properly.
>
> David.
>
>
Works just fine. Discovers the two modified files and matches the command line report.
That's good. TM2 works. )-:
That's bad. But not on my stuff. (-:
Time to review what I'm doing. Thanks.
Lewy
On Feb 29, 2012, at 5:25 AM, textmate-request(a)lists.macromates.com wrote:
> From: Allan Odgaard <mailinglist(a)textmate.org>
> Subject: [TxMt] Re: working with SVN
> Date: February 29, 2012 5:05:05 AM AKST
> To: TextMate users <textmate(a)lists.macromates.com>
> Reply-To: TextMate users <textmate(a)lists.macromates.com>
>
>
> On 29/02/2012, at 09.57, Lewy wrote:
>
>> […] TM2 didn't find the Uncommitted changes. It return [screenshot follows]
>
> What version of (CLI) svn are you using?
>
> Can you try to do a new checkout e.g. http://svn.textmate.org/trunk/Manual/pages/en/ — edit a page and see if that gets picked up.
Thanks, David. Your edits were enough to get the command working for me.
How would a person go about limiting the scope of this command by file
type? I understand that this is possible but haven't been able to get it to
work yet.
Seems like the Scope Selector or Content Match fields would be the place
for that (using something similar to [ *.{css,txt,markdown,md,mdown} ] for
the syntax) but I can't get it to work. I've tried this syntax with or
without the brackets.
--
Erik
On Wed, Feb 29, 2012 at 9:24 AM, <textmate-request(a)lists.macromates.com>wrote:
>
> Message: 5
> Date: Wed, 29 Feb 2012 15:17:50 +0000
> From: David Howden <dhowden(a)gmail.com>
> To: TextMate users <textmate(a)lists.macromates.com>
> Subject: [TxMt] Re: scopeAttributes and deactivate working?
> Message-ID:
> <CAP2kWKEubFLk0TaqaBXNd9B5szv_wwitCBWt6idRsDDMdJBaMQ(a)mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Ed.
>
> Try removing the scope selector and see if it works. I have input set to
> "Nothing", and output to "Discard".
>
> I have added the command to the text bundle, so if you are still having
> problems I can just send you a copy of that.
>
> David.
>
> On Wed, Feb 29, 2012 at 3:12 PM, PowerPod <ed.moss(a)4ssom.com> wrote:
>
> >
> > I created a "Command" in my personal bundle with:
> >
> > Scope Selector: attr.save-on-deactive
> > Key Equivalent:
> > Tab Trigger:
> > Semantic Class: callback.application.did-deactivate
> > Content Match:
> > Save: Modified Documents
> > Input: Scope Format: Text
> > Output: Replace Input Format: Text
> > Caret Placement: After Output
> > Scroll for new output (unchecked)
> >
> > Still no joy. Yes, I am anxious to get this working. :) I really
> appreciate
> > your help.
> >
> > Thanks,
> >
> > Ed.
> >
> >
> > David Howden wrote:
> > >
> > > Hi
> > >
> > > Ok, so as I understand it you you now need to have a command which has
> > the
> > > scope set to attr.save-on-deactive, and is fired by the semantic
> > > class: callback.application.did-deactivate
> > > and is set to save all modified documents.
> > >
> > > David.
> > >
> > > On Tue, Feb 28, 2012 at 5:00 PM, Edwin Moss <ed.moss(a)4ssom.com> wrote:
> > >
> > >> I am having no joy in getting this to work in my .tm_properties file.
> > >>
> > >> [ *.{rb,erb,haml,js,html} ]
> > >> scopeAttributes = 'attr.save-on-deactivate'
> > >>
> > >> Has anyone else got it to work? Any help would be appreciated.
> > >>
> > >> Thanks,
> > >>
> > >> Ed
> > >>
> > >>
> > >> _______________________________________________
> > >> textmate mailing list
> > >> textmate(a)lists.macromates.com
> > >> http://lists.macromates.com/listinfo/textmate
> > >>
> > >
> > >
> > > _______________________________________________
> > > textmate mailing list
> > > textmate(a)lists.macromates.com
> > > http://lists.macromates.com/listinfo/textmate
> > >
> >
> > --
> > View this message in context:
> >
> http://old.nabble.com/scopeAttributes-and-deactivate-working--tp33408128p33…
> > Sent from the textmate users mailing list archive at Nabble.com.
> >
> >
> > _______________________________________________
> > textmate mailing list
> > textmate(a)lists.macromates.com
> > http://lists.macromates.com/listinfo/textmate
> >
>
I am getting a LOT of crashes (TM2) when working with files in the project sidebar (right name?). Even things like rename a file, or add a file to favorites will crash TM2. What's interesting is that the crash occurs AFTER the work is done. When I reopen TM2, the file has been renamed or whatever I was trying to do.
I can supply the crash log to whomever wants it along with a specific case.
Lewy
Hi, most of my work with TextMate is with XML files. TM2 only seems to be
able to tidy really small files - anything of a reasonable size, it just
deletes my XML. Is this a known issue that will be fixed, or is there some
workaround?
--
View this message in context: http://old.nabble.com/-TM2--XML-Tidy-tp33410232p33410232.html
Sent from the textmate users mailing list archive at Nabble.com.
Uh, no. I hadn't found those. I was using cmd-y, which brought up the menu. However, your comment looks like it's just what I wanted, except it didn't find everything.
Command line svn returns:
bash-$ svn status
X data
M _README-DEV.mdown
M org-bylaws-v4.php
? css/bp-boiler-2.css
M org-board-v4.php
M org-licenses-v4.php
Performing status on external item at 'data'
bash-$
Which is correct. "data" is an external, and the css file is a mistake I haven't yet removed. The others had one line changes. TM2 didn't find the Uncommitted changes. It return [screenshot follows]
Looks like this is trying to do what I wanted. I'm glad to find it. Dunno why it didn't succeed.
Lewy
> On 28 Feb 2012, at 21:11, Lewy wrote:
>
>> I have been using cmd-Y with SVN. It works fairly well, however has one problem for me. When I select status (zero from the list) it shows me the status only of one file. What I want is what the SVN command line does -- to show the status of files that are modified, added, deleted, whatever.
>>
>> The idea is to find everything I just modified for a commit. Commit seems to work only on one file as well. Is there a way to work with the repository instead of just one file?
>
> Hi,
>
> did you try to click at the blueish "smart folder" or "SCM Status" ⇧⌘Y?
>
> There you see all uncommitted changes. Simply select all or whatever what do you want to commit, or diff against working copy ... via ⌘Y.
>
> Best,
> --Hans
I have been using cmd-Y with SVN. It works fairly well, however has one problem for me. When I select status (zero from the list) it shows me the status only of one file. What I want is what the SVN command line does -- to show the status of files that are modified, added, deleted, whatever.
The idea is to find everything I just modified for a commit. Commit seems to work only on one file as well. Is there a way to work with the repository instead of just one file?
Not a really big issue since I can go to command line or some GUI, but it would be nice to do that within TM2.
--Lewy
... opening of the same favorite project should maximize it instead of opening a new instance of it.
It's a minor feature request ;)
Thanks!
Best,
--Hans
