Yes. I’ll second this. Having the same issue. Is there a better way to resolve the issue, as it is stated in the commit message?
Best,
Farhan
> On Mar 22, 2018, at 9:13 AM, Rob McBroom <mailinglist0(a)skurfer.com> wrote:
>
> After the last update, I noticed some garbled Quick Look previews in my Downloads folder.
>
> <Screen Shot 2018-03-22 at 9.06.59 AM.png>
>
> I’m pretty sure it results from this commit:
>
> https://github.com/textmate/textmate/commit/fd827fb8179cd74e553680d605d2172…
>
> As you can see form the image, it doesn’t seem to affect all files, but I would argue that no application should claim Quick Look support for every file in existence.
>
> --
> Rob McBroom
> http://www.skurfer.com/
After the last update, I noticed some garbled Quick Look previews in my
Downloads folder.
I’m pretty sure it results from this commit:
https://github.com/textmate/textmate/commit/fd827fb8179cd74e553680d605d2172…
As you can see form the image, it doesn’t seem to affect all files,
but I would argue that no application should claim Quick Look support
for every file in existence.
--
Rob McBroom
http://www.skurfer.com/
Hi all -
Something's gone wonky with my Javascript bundle (and only that one, as far as I can tel)l. Every time I hit cmd-/ to comment/uncomment some text, it uses an unindented block comment instead of the double-slash single line comment I expect. ("/* */", rather than "// ")
So:
" this line"
becomes
"/* this line*/"
when what I want and expect is
" // this line"
I suspect this has to do with some way I've edited the language bundle incorrectly. Does anyone know
A) how I could fix this particular issue, or
B) how I could remove all my changes to the Javascript bundle and revert simply to the repo version?
Cheers,
Evan
I’m been starting to use go-to-definition commands more and more in TextMate. One thing that would be really nice is if there was a way to navigate back to the location where I invoked go-to-definition. I quite often look up the source code of a symbol that I’m using with the help of go-to-definition and then need to get back to where I was coding. If go-to-definition opens a new file it’s pretty easy to get back to the previous location by just closing the newly opened file. But if the definition is in the same file it’s not that easy to get back. One idea would be set a mark when go-to-definition is invoked, then use Jump To Next/Previous Mark. The problem with that is that there might be different marks, like marks set by compiling the code. These marks will now interfere with go-to-definition marks. It’s also quite difficult to build up a stack, allowing to navigate backwards and forwards with these marks. Since navigating between marks will, I think, in the order they’re located in the document, not the order they were created or any other user defined order.
Ideally this would be a built in feature in TextMate, making it possible to navigate backwards and forwards regardless if the “mate” command, the Jump to Line or any other feature was used to navigate the code.
--
/Jacob Carlborg
Hi all,
I can’t push/pull using the Mercurial bundle, I get the following error:
“abort: no suitable response from remote hg!” (In a tool tip.)
It works fine on the command line and other commands, like commit and diff, works fine from TextMate.
Any ideas about how to debug this?
Cheers,
Tuk
macOS 10.13.1
I've also tried changing the shebang of gen_html to so it uses ruby 2.4.2 (from Homebrew) and the result is the same. Anyone else hitting this? Any workaround?
[266/740] Generate ‘/Users/dfelicia/build/TextMate/Applications/TextMate/TextMate.app/Contents/Resources/Contributions.html’…
FAILED: /Users/dfelicia/build/TextMate/Applications/TextMate/TextMate.app/Contents/Resources/Contributions.html
bin/gen_html > /Users/dfelicia/build/TextMate/Applications/TextMate/TextMate.app/Contents/Resources/Contributions.html~ -h Applications/TextMate/templates/header.html -f Applications/TextMate/templates/footer.html Applications/TextMate/about/Contributions.md Applications/TextMate/references.md && mv /Users/dfelicia/build/TextMate/Applications/TextMate/TextMate.app/Contents/Resources/Contributions.html~ /Users/dfelicia/build/TextMate/Applications/TextMate/TextMate.app/Contents/Resources/Contributions.html
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/erb.rb:861:in `eval': (erb):18: syntax error, unexpected &, expecting end-of-input (SyntaxError)
; ></p>
^
from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/erb.rb:861:in `block in result'
from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/erb.rb:862:in `result'
from bin/gen_html:29:in `expand_tpl'
from bin/gen_html:114:in `block in <main>'
from bin/gen_html:114:in `open'
from bin/gen_html:114:in `<main>'
[275/740] Compile xib ‘Applications/TextMate/resources/English.lproj/MainMenu.xib’…
ninja: build stopped: subcommand failed.
I tried completely cleaning up, and also worked around the annoying ns/ns.h issue that was previously reported to this list, but the results is the same:
rm -rf ~/build
rm -rf ~/github/local/textmate
cd ~/github/local
git clone https://github.com/textmate/textmate.git
cd textmate
git submodule update --init
sed -i.bak 's%<ns/ns.h>%"/Users/dfelicia/github/local/textmate/Frameworks/ns/src/ns.h"%g' /Users/dfelicia/github/local/textmate/Frameworks/OakFoundation/src/OakFoundation.mm
./configure
ninja
Hi,
I'm trying to fix the textmate2 port in MacPorts. It fails to build on OS X 10.10 and earlier, and I think the reason is that the code uses Objective-C lightweight generics, a feature introduced in the 10.11 SDK. So I would like to instruct the build to use the 10.11 SDK, but I can't figure out how to do that. Usually I would set environment variables:
CFLAGS='-isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk'
CPPFLAGS='-isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk'
CXXFLAGS='-isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk'
LDFLAGS='-Wl,-syslibroot,/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk'
OBJCFLAGS='-isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk'
OBJCXXFLAGS='-isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk'
But textmate's configure script isn't an autotools one and it doesn't appear to honor these environment variables. So how can I tell the build system I want to use a different SDK? I see that the configure script explicitly passes CC and CXX to bin/gen_build. Do I need to modify the configure script to also explicitly pass the other environment variables or is there an easier way that doesn't involve modifying the build system?
Dear all,
When parsing large amount of text from textmate2 to the terminal, it sometimes happens that strange parsing errors occur.
Line breaks, white space, or symbols are arbitrarily not send correctly to terminal.
For example; this line in textmate:
col <- ifelse(…
ended up like this in terminal:
col <col <cse(...
Hence, whenever I want to run multiple lines of code, I end up with errors, which makes it very difficult to work with textmate in combination with terminal.
I use the following command to parse the selected text to the terminal:
#!/bin/bash
[[ -f "${TM_SUPPORT_PATH}/lib/bash_init.sh" ]] && . "${TM_SUPPORT_PATH}/lib/bash_init.sh"
rawText="$(cat | sed 's/ / /g;')"
#rawText="`cat`"
osascript -e 'on run(theCode)' \
-e 'tell application "Terminal" to activate' \
-e 'tell application "Terminal"' \
-e 'do script theCode in window 1' \
-e 'end tell' \
-e 'end run' -- "$rawText”
Thanks for any help and advice!
