Hello,
I looked around for quite some while now, but everything I found online did
either not apply for TextMate 2 any more or did just not help me to solve my
problem.
I am using:
- OSX 10.9 (latest updates installed)
- TeXLive 2009 (now also 2013)
- latest LaTeX bundle (reinstalled just before)
What happens:
- I open a file that compiles just fine from terminal using pdflatex in
TextMate 2.
- I hit command+r
- The HTML output window opens ans says (twice in different font size, one
on top of other): "Error: Could not open to check for packages." And in a
second line it continues: "This is most likely a problem with
TM_LATEX_MASTER".
- The main TextMate window then also said: "Failure running 'Typeset&View
(PDF)'. Command returned status code 1."
Some more info:
- I do try to compile a simple file, no includes or imports... So I guess I
do not need TM_LATEX_MASTER, do I?
- The LaTeX bundle is set up to use pdflatex.
- Using "defaults write com.macromates.textmate latexDebug 1" does not cause
any additional outputs within TextMates GUI, nor in the Console.
What else did I try:
- I completely reset all TextMate settings (by deleting several folders and
files as suggested somewhere in the net) -- this changed a LOT, my TextMate
was certainly not the same any longer... but error remained the same.
If anybody has ANY idea what the most likely totally braindead and stupid
thing is that I do not see... please let me know... you'd be my personal
hero and I will worship you for weeks... ;)
Thanks,
Florian
--
View this message in context: http://textmate.1073791.n5.nabble.com/TextMate-2-LaTeX-Error-Could-not-open…
Sent from the textmate users mailing list archive at Nabble.com.
I’d like to highlight conflict markers (“<<<<<<< HEAD”, “=======”, …)
across all file types.
I created a small bundle with an injection grammar for this, but it only
works correctly for plain text. It seems that in most source grammars
other rules take precedence (e.g. in Ruby “=======” has the scope
“keyword.operator.assignment.ruby”) and therefore the injection grammar
won’t get applied.
Is there any way to solve this?
Stefan
As you probably know, I'm trying to write a new AsciiDoc bundle from the ground up. When I created this bundle, my tmLanguage file was named untitled.tmLanguage even though I have entered AsciiDoc in the bundle editor as the name of the language grammar. My question is, how can I rename this file asciidoc.tmLanguage? (If I do it directly in the Finder, TextMate simply loses track of the file altogether and thinks I no longer have a language grammar.) m.
--
matt neuburg, phd = matt(a)tidbits.com, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
And here it is:
https://github.com/mattneub/AsciiDoc-TextMate-2
I would like to thank everyone (meaning Allan in particular) for so much hand-holding. I truly couldn't have done it without you.
(That's partly because, even after all this time, the state of documentation on how to write a grammar is startlingly inadequate; if I have time, I intend to write a public document providing some lessons learned.)
In conclusion I would like to repeat some suggestions about possible improvements to grammars, that would have helped me a lot:
* "exclude" in addition to the existing "include". This would allow me to include a batch of rules by a single name and then exclude the few that should _not_ be included.
* Peekahead. This is the setext problem, but it arises in a lot of areas of AsciiDoc. Despite concerns over speed and the problems of backtracking, it might be that the mere ability to examine _just the next line_ might all by itself be helpful without slowing things down too much, i.e. no, the next line is not a match for the "next" pattern, so *this* line is not a match for the "begin" pattern, and on we go to the next line.
* "include" should limit the search. You will recall that the problem I had is this (because AsciiDoc paragraphs can consist of multiple lines):
This (1) is a paragraph *consisting of
multiple lines* and containing a stretch of bold.
This (2) is a paragraph with * an asterisk in it.
This (3) is another paragraph with * an asterisk in it.
Now, I can sort of pick out the paragraphs here by the fact that they are bounded by more than one return character. But if I code my "bold" rule as a begin-end rule, it picks up not only the bold in the paragraph 1 but (wrongly) a bold stretching from paragraph 2 to paragraph 3, _even if "bold" is an include within "paragraph"_. Indeed, TextMate extended the containing "paragraph" to include both 2 and 3 just in order to allow the "bold" to grow. Therefore I just had to give up and pick out neither. But what TextMate was doing here seems wrong to me and it would be nice if it wouldn't do that.
Still, what I ended up with is more than acceptable and definitely useful. Now that I can edit my books with it, I am able to move forward and adopt TextMate 2 full-time! m.
--
matt neuburg, phd = matt(a)tidbits.com, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
Hi.
I'm using the default bundle for Java and would like to modify it so that the console output is displayed as plain text in a tool tip, as Venkat is doing here:
http://www.youtube.com/watch?v=7vYr12vlwrA#t=329
When I edit the Compile & Run Menu Action to show the output in tool tip and set the format to text the console output is indeed shown in a tool tip but it's shown as HTML. How do prevent TextMate from generating HTML in this case?
Thanks in advance!
/ Fredrik
Lets say I search for all periods (.) in a paragraph. I can do this using
OPTION+CMD+F, which places multiple carets over each period. Is there a
keyboard shortcut to remove the multiple carets and to get back to just one
caret?
Thanks
Ross
In the Find Dialog, you can toggle regex with Cmd-Option-R. Seems like we
used to be able to toggle Ignore case with Cmd-Option-I, but this no longer
works. That keyboard sequence toggles invisible characters.
Are there shortcuts for the other items in the Find Dialog?
Here's a list of includes from one of the inline patterns in the AsciiDoc grammar I'm writing:
{ include = '#double_bold'; },
{ include = '#double_italic'; },
{ include = '#double_literal'; },
{ include = '#double_unquoted'; },
{ include = '#double_quote'; },
{ include = '#single_bold'; },
{ include = '#single_italic'; },
{ include = '#single_literal'; },
{ include = '#single_literal_nopassthru'; },
{ include = '#single_unquoted'; },
{ include = '#superscript'; },
{ include = '#characters'; },
But it happens that that list is almost the same as the #inline group I've already defined. I could reduce this to a single include! There's just one problem: we must not include ourselves, i.e. #subscript; we crash if we do, and anyway it's wrong (this pattern is not in any way recursive). Thus I request that the grammar should allow me to talk like this:
{ include = '#inline'; },
{ exclude = '#subscript'; },
This is not just to make the list shorter; it also makes the list more correct and coherent, because I'm allowed to say (and see) exactly the truth: "include everything except yourself".
Thanks for thinking about this - m.
--
matt neuburg, phd = matt(a)tidbits.com, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
Is it possible to set the default theme for a given folder by setting the
.tm_properties file? I know I've seen reference to it but I also think I
remember hearing that this wasn't implemented yet. I'm VERY interested in
either:
- Per directory defaulting of Theme (via above .tm_properties or any
other method)
- Per grammer/language defaulting of Theme
If these features aren't currently available I'd like to put my vote in for
them ... they seems quite generally applicable to the populations use-cases
and I would imagine (speaking completely out of school) them to not be
terribly hard to implement? Here's me hoping anyway.
Ken
