TextMate February 2012

textmate@lists.macromates.com

75 participants
122 discussions

by Lewy

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.

14 years, 2 months

Re: textmate Digest, Vol 45, Issue 50

by Erik Ebsen

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 > > >

14 years, 2 months

TM2 crash report

by Lewy

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

14 years, 2 months

[TM2] XML Tidy

by bugswatter

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.

14 years, 2 months

Re: working with SVN

by Lewy

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

14 years, 2 months

working with SVN

by Lewy

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

14 years, 2 months

[TM2 9092] if window of a favorite project is minimized ...

by Hans-Jörg Bibiko

... 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

14 years, 2 months

TM2 with rbenv

by 姜源

I find this url to use rbenv in textmate, http://uberfork.com/post/12280974742/integrate-rbenv-with-textmate but it doesn't work for textmate2 Anyone knows how to config rbenv to with with textmate2 ?

14 years, 2 months

Re: TM2: Latex\Watch Document problem

by Philipp Kühl

> in TM2 I have the problem that the dialog that says > "LaTeX Watch: Compiling document" never disappears. > If I force quit the Cocoadialog things work just fine, > but it is annoying to have to force quit > the process every time I Watch a new document. My workaround is preventing TM from starting the dialog. I don't really have an idea of what I'm doing but commenting out the following lines for the watch document command in the bundle editor seems to kill the dialog while keeping the rest of watch document alive: #nice -n 20 CocoaDialog progressbar --indeterminate --title 'LaTeX Watch' --text 'LaTeX Watch: Compiling document' </dev/console &>/dev/null & #progressbar_pid=$(jobs -p %%) #disown %% watch_script_opts="--textmate-pid $PPID" # --progressbar-pid $progressbar_pid"

14 years, 2 months

How to make Go > Current Document work like in TM1?

by John Yeates

When I selected Go > Current Document (Cmd-Ctrl-R) in TextMate 1, it would highlight the current document in the file list, expanding any folders as needed. In TextMate 2, it still works this way — *IF* the folder containing the document is already expanded, so all it needs to do is scroll. If the folder is not expanded, TM2 opens the folder, so the drawer now only shows a subset of the project I'm working on. Example: > folder1 v folder2 file1 file2 > folder3 If I am editing file2 and press Cmd-Ctrl-R, the highlight moves to file2, correctly. In the case where folder2 was not expanded, though, I would see this after pressing Cmd-Ctrl-R: file1 file2 …and I would no longer be able to access folder1 and folder3 from the file list without using the dropdown at the top. I would also no longer have an overview of the SCM status of the entire project. How can I set TM2 to work the old, non-annoying way, where it just expands folders as needed and doesn't change the root? Thanks -- John Yeates

14 years, 2 months

← Newer
1
2
3
4
5
6
7
...
13
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

TextMate February 2012