Came in yesterday to find that pdflatex had written a 256GB .log file (only stopped because that filled the space on my ssd… and dropbox was studiously uploading to my shared pals folders :-) ).
I had closed the typesetting window, saying yes to the resulting “kill processes dialog” (pdflatex was in an endless loop trying to process an errant latex script), but that doesn’t kill pdflatex (as can be seen in the activity monitor). You can end up with multiple pdflatex instances all ownerless, and only killing them manually works to end them.
Textmate obviously can’t kill processes spawned by bundles in case they are supposed to be continuing, but perhaps shutting the latex TypeSetting bundle could ensure that closing the typesetting window/ending watching could send a kill/quit signal to pdflatex?
I'am updating/ organizing all my snippets and commands, because I want to
use git in order to "sync" my bundles between my Macs.
Digging into the Package Content, it seems that the Bundle Editor does not
update the [name].tmSnippet or [name].tmCommand when changing it's name! It
keeps the initial name (so sometimes untitled).
I assume this is not intended to be! Am I right this is a bug?
Can I for the time being change the name via Finder without any
View this message in context: http://textmate.1073791.n5.nabble.com/Bundle-editor-does-not-update-name-co…
Sent from the textmate users mailing list archive at Nabble.com.
Tweets can give the link to another site, for example, the wiki.
> From: fukurokujo <fukurokujoe(a)googlemail.com>
> we could make some kind of wiki or repository for TextMate tips and a bot for twitter that tweets them once in a while.
> That way everyone could look at the whole list, contribute and gets informed about new or random ones.
>> On 13 Feb 2016, at 12:32, Elia Schito <elia(a)schito.me> wrote:
>> Just for the record I still have access to the tm2tips Twitter account if anyone's interested in reviving it.
>> Elia Schito
>> On 12 Feb 2016, at 13:18, George McGinley Smith <george(a)gsgd.co.uk <mailto:email@example.com>> wrote:
>>> There was this tumblr a while back, but seems to have fallen by the wayside ? http://tm2tips.tumblr.com/ <http://tm2tips.tumblr.com/>
>>> On 12 February 2016 at 02:33, Carpii UK <carpii.uk(a)gmail.com <mailto:firstname.lastname@example.org>> wrote:
>>> For me, the problem with tweets is they're too short to provide anything useful, at l least in terms of TextMate tips
>>> Likewise the mailing list isn't really an appropriate arena for them.
>>> New TM users are very unlikely to search the mailing list archive to find tips, so it would only be helping the userbase who were subscribed at the time of posting
>>> I'd much rather see a wiki, which everyone can contribute to, and develop it into a good TM guide.
>>> Right now the docs are a little outdated and ambiguous, with many articles referencing TextMate 1 (but not always making this clear)
>>> On 12 February 2016 at 00:16, Music <akakie(a)gmail.com <mailto:email@example.com>> wrote:
>>> If you go for tweets, please announce that on the list. I'm not a great fan of tweets, but a daily hint sounds interesting.
>>>> On Feb 11, 2016, at 8:54 AM, Phil Schumm <pschumm(a)uchicago.edu <mailto:firstname.lastname@example.org>> wrote:
>>>> On Feb 11, 2016, at 10:34 AM, Tim Bates <timothy.c.bates(a)gmail.com <mailto:email@example.com>> wrote:
>>>>> why not tweet it? That way it?s discoverable by many more people, will help promote Textmate, and won?t take over this list
>>> Kind regards,
** Steps to Reproduce: **
1. Open a directory/project with one or more files
2. Rename any file from inside TextMate
3. Click on "Go > Go to File" or press CMD-T
4. Search for the old filename
5. Search for the new filename
** Expected Result: **
The old filename should not appear in the "Go to File" box, when searched.
The new filename should appear in the "Go to File" box, when searched.
** Actual Result: **
The old filename appears in the "Go to File" box, when searched.
The new filename does not appear in the "Go to File", when searched.
** Environment: **
- OSX 10.11.12 (El Capitán)
- TextMate 2.0-beta.8.5
- Code working in: PHP (tested with php files)
Would someone like to put out a Hint of the Day on this list? I’d appreciate it. Could include changes and improvements too. I know it would be some work, and wold require tracking old hints, but they could be accumulated in a web page for our reading.
Or maybe the others on the list would hate it.
Thanks to all the help from this list: my GitHub Markdown bundle now supports (in some form) all the functionality in GitHub Flavoured Markdown and has a preview feature that displays them all. Check it out:
I’m interested in working on what’s required to get this as an “official” bundle; what would that require? I’m happy to make changes and fix issues that may block this being changed.
When pressing CMD-SHIFT-D in a PHP-file (Jump to Included File), only files
with an absolute path to the file are recognized:
Tooltip error: file not found.
Also when pressing ESC when the CMD-SHIFT-D pop-up tooltip is active, the
following error occurs:
Failure running "Jump to include File"
Command return status code 1
I'am using TM 2.0 beta 8.6 and OSX 10.11.3n (also happens with TM beta 8.5)
View this message in context: http://textmate.1073791.n5.nabble.com/Jump-to-included-file-does-not-work-f…
Sent from the textmate users mailing list archive at Nabble.com.
TextMate looks terrific! Thanks Allan for making it available under the
GNU General Public License! I installed the binary and it works for me,
but I'd like to build it from source, and I'm having a bit of trouble
At https://github.com/textmate/textmate I see the following instructions:
In the simplest case you would run:
$ git clone https://github.com/textmate/textmate.git
$ cd textmate
$ git submodule update --init
$ ./configure && ninja
I did all the prerequisites using homebrew without apparent problems:
$ brew install ragel boost multimarkdown hg ninja capnp
$ brew install proctools
But the last step in building TextMate (./configure && ninja) fails for
[445/1150] Compile ‘Applications/commit/src/commit.mm’…
FAILED: xcrun clang++ -include
/Users/alpha/build/TextMate/Shared/PCH/prelude.mm -c -pipe -fPIC
-gdwarf-2 -m64 -mmacosx-version-min=10.7 -funsigned-char
-D'NULL_STR="\uFFFF"' -DREST_API='"https://api.textmate.org"' -Wall
-Wwrite-strings -Wformat -Winit-self -Wmissing-include-dirs
-Wno-parentheses -Wno-sign-compare -Wno-switch -IShared/include
-fcolor-diagnostics -DNDEBUG -Os -DCOMPILE_DATE=\"`date +%Y-%m-%d`\"
-fvisibility=hidden -std=c++1y -stdlib=libc++ -fobjc-abi-version=3
-fobjc-arc -fobjc-call-cxx-cdtors -o
/Users/alpha/build/TextMate/Applications/commit/src/commit.o -MMD -MF
Applications/commit/src/commit.mm:1:10: fatal error:
'CommitWindow/CommitWindow.h' file not found
1 error generated.
[445/1150] Run test ‘/Users/alpha/bu...TextMate/Frameworks/scm/test_scm’…
ninja: build stopped: subcommand failed.
It's strange because the reportedly missing file is apparently present
(if not exactly where ninja seems to be looking for it):
$ find . -name "CommitWindow.h"
I didn't think I would need to set any of the variables:
builddir — location of built files. Defaults to ~/build/TextMate.
identity — for Apple’s codesign. Defaults to ad-hoc signing, which
does not use an identity at all.
boostdir — location of boost includes. By default it will search
various locations including MacPorts and Homebrew.
sparsedir — location of sparsehash includes. By default it will
search various locations including MacPorts and Homebrew.
CC and CXX — C and C++ compiler.
so I didn't, but maybe I need to set boostdir manually?
Any advice on this, or is this a bona fide bug in the build process
(seems unlikely)? I've never filed an issue in github. Is that how I
would go about reporting a bug?