Hi All,
Just a quick report in hopes of helping someone else facing this problem:
Textmate binds Cmd-Opt-Ctrl DownArrow to scrollLineDown. I use this keystroke and it's counterpart for scrollLineUp frequently.
After upgrading from Snow Leopard to Mountain Lion I started getting a system alert sound (beep, pop, funk, as set in System Prefs) when using this keystroke and no scrollLineDown action in TextMate.
Long story short is that Xcode 4 eats that keystroke even when it's not running.
Fix is to open XCode, open Preferences > Key Bindings, and set the key binding for 'Jump to Previous Counterpart' to something other than Ctrl-Cmd DownArrow. This causes the inferred key binding for 'Jump to Previous Counterpart in Assistant Editor' to change from Cmd-Opt-Ctrl DownArrow to Opt NewKeystroke.
For example, setting 'Jump to Previous Counterpart' to 'F19' causes 'Jump to Previous Counterpart in Assistant Editor' to change from Cmd-Opt-Ctrl DownArrow to Opt F19.
I needed to reboot before it took effect, but that ended up doing the trick :)
Might also work in Lion, I'm not sure what version of Xcode that shipped with.
Hope that's a help to someone in future :)
Best,
Steve
In brief, does anyone know the font that's used for the Markdown Bundle's Preview window?
And the different (serif'd) font used to print the preview? Can it be changed?
tia, DW
Hi,
The MediaWiki bundle in TextMate 2 has a feature that when I type:
Line1
Line2
It automatically reindents to:
Line1
Line2
Despite that I explicitly typed the two spaces.
I find this rather annoying. I'm trying to turn this feature off.
The only thing about indentation I can find is in the bundle, Settings:
Folding:
foldingIndentedBlockStart = '^=+\s+';
foldingIndentedBlockIgnore = '^(?!=+\s+)';
But even when I remove these lines, the feature is still there. Anyone
has an idea what may cause this behaviour and turn it off?
I'm also fine with any option that turns off auto-indenting off
globally, like there was in the Preferences for TextMate 1 (I usually
find it more annoying than useful).
Thanks,
Freek
First I created a plain-text doc with some Markdown "markup"; my default font is Monaco. Then I used Bundles > Markdown > Preview, and got a very nice window created with some unkown (to me) sans-serif font. I used cmd-P to print this, and was surprised to find the printout used some strange (to me) serif'd font. Same of course if I opted to print to pdf.
So as an experiment I tried adding my own <style> ... </style> containing Verdana to the doc. Unsurprisingly the html was ignored by Markdown > Preview, still had the nice ss font in that window, and print still used the strange serif'd font. No surprises there really.
Next, I could get the html handled by using Bundles > HTML > Open Doc in Running Browser(s). No surprises there.
Finally I tried altering Preferences > Fonts & Colors. This affected the source doc of course, but again made no difference to Markdown Preview or to Print.
So what are the mysterious fonts used by Markdown Preview and Print? I'd like to know what the "nice" sans-serif font used by Preview is, the only clue I can offer is that a capital M has sloping sides.
But above all, what is this mysterious serif'd font used when I print the Preview window, and can I replace it?
David Whitford
On 05.11.2012, at 21:00, textmate-request(a)lists.macromates.com wrote:
> Bottom line: I enjoy much faster TeXing when adding the apparently superfluous extra-line at the beginning. For principal reasons I would like to get rid of this extra line, and understand what is going on.
This is a bundle problem, if I pdflatex your example (the TeXLive 2011 version), it compiles correctly.
I usually separate my documentclass from the packages I frequently load as they are usually the same while the documentclass depends on the specific document. E. g. I would sometimes use scrbook instead of scrartcl or the cls file from the journal I intend to publish in. Furthermore, I am loading my standard packages as a package (change the file extension from .tex to .sty and load your standard packages via \usepackage{file}). The advantage is that you can modularize your standard includes file further, e. g. you can load hyphenations.tex via that .sty file while this is not possible if you use \input (\input does not allow nested uses of \input).
> A final remark: Is there a way to adjust some preferences of the speedier LaTeX bundle? For instance: I would like to have the typesetting window not to be kept open (very annoying); I would like not to have activated the reading bar in Skim.
What do you mean by »reading bar« in Skim?
Max
Dear Hans,
I have a hard time following your explanation, especially of the word »bundle«, because I'm not certain whether that refers to LaTeX packages or one of TextMate's LaTeX bundles. The initial problem you describe has *nothing* to do with TextMate: it appears your file was saved in the wrong encoding (not applemac), so latex cannot decipher non-ASCII characters such as umlaute or accented characters. By default, TextMate and pretty much all other editors use UTF8, hence my advice to *change* the argument for when you load the inputenc LaTeX package to UTF8:
\usepackage[utf8]{inputenc}
If you comment out this usepackage command, pdflatex will not be able to correctly render non-ASCII characters (e. g. ä, ö and ü).
Unfortunately the problem with the example code you've included is that it cannot be used to detect problems with file encodings. But the mail you've sent indicates that it's just a file encoding problem that's easy to solve (e. g. the umlaut for »für« was not copied correctly from your text editor). I think what you've been missing is Step 2 below.
I recommend you the following:
(0) Open the problematic .tex file in TextMate
(1) Change \usepackage[applemac]{inputenc} to \usepackage[utf8]{inputenc}.
(2) Select Save As from the File menu and make sure that UTF8 as file encoding is selected. Then proceed to save the file as text.tex someplace else. This way any experiment with LaTeX will not destroy work.
(3) Try to compile the document.
Note that if you load other LaTeX files via \include{filename.tex} or \input{filename.tex}, check that the other files are also all saved in the correct encoding, UTF8!
If it doesn't work out, please include the content of test.log (in general: [document name].log) in your next post.
Max
On 28.10.2012, at 21:00, textmate-request(a)lists.macromates.com wrote:
> When trying to typeset a letter, where my preamble looks different and has the following line in it:
>
> \usepackage[applemac]{inputenc}
>
> the typesetting window will claim a problem with respect to this line:
>
> "inputenc.sty:40: [...]"
>
> When I comment out the \usepackage-line in the source, typesetting proceeds successfully (and VERY fast), though all special characters get omitted (to be able to use German umlaute like ?, etc is what the inputenc package should provide for).
I suspect your file has been saved as UTF8 (which you should use if at all possible anyway). So change the inputenc argument to
\usepackage[utf8]{inputenc}
and recompile. In my experience, UTF8 works best, but if you have cross-platform collaborators, you may need to work in latin1. I would strongly discourage you from using applemac encoding this day and age.
Max
Hi,
I will appreciate tremendously if you help me with my problem.
I built Textmate 2 in my Mac (OSX 10.8.2). I have TeX Distribution
TeXLive-2012 installed. When I try to compile a LaTeX file I get the
following error:
Failure running “Typeset & View (PDF)”.
Typeset & View (PDF):4: undefined method `+' for nil:NilClass
(NoMethodError)
Do you have any suggestions?
Best,
Bogac
--
View this message in context: http://textmate.1073791.n5.nabble.com/Textmate-2-LaTeX-tp25947.html
Sent from the textmate users mailing list archive at Nabble.com.
Hi,
This is probably an easy question. I'm using Mads Hartmann Jensen
whitespace bundle (git clone
https://github.com/mads379/Whitespace.tmbundle.git) that "adds the
scopes invalid.illegal.whitespace.trailing to all trailing whitespace
and invalid.illegal.whitespace.mixed to all occurrences of mixed
spaces/tabs". This shows up fine in some themes (all the core themes
work) but not some other themes, specifically solarized (light). How
would I add a background colour to solarized to reflect that? I tried a
couple of things but not got it to work. Any pointers gratefully
received.
Thanks
Alex
--
-------------------------
http://zero-dev.co.uk
alex(a)zero-design.info
mob. +44 (0) 785 216 7005
Hi,
as you sure now there a couple of (forked) LaTeX bundles providing speedier TeXing than TM’s standard (bundled?) LaTeX bundle.
Alex Ross (lasersox)’ bundle was first, now there are Adam Strzelecki (nanoant)’s, as well as Paul Hagstrom’s. You can find them, respectively, here:
https://github.com/lasersox/latex.tmbundlehttps://github.com/nanoant/LaTeX.tmbundlehttps://github.com/paulhagstrom/LaTeX.tmbundle
Now, while they seem indeed to be significantly faster than the standard LaTeX bundle, with all three of them I run into the following (presumably very same) problems:
When there is a line with an \input command in the tex-file, like:
"\input{praewide_TM}"
there shows up in the typesetting window an (apparently) error. The error message is not very verbose, just a line noting:
"praewide_TM.tex:1: \documentclass[a4paper]{".
("praewide_TM.tex" is the name of my preamble-file, which is supposed to get linked in; praewide_TM.tex contains, among other things, the line "\documentclass[a4paper]...". This works with TM’s LaTeX standard bundle as expected. It also works with TeXShop, for instance.)
I take it to be an error message (it nowhere says "error", or something to that effect), but if some such line shows up in the typesetting window, then there is no pdf output produced. If I manage to get rid of any of these lines noting some input, then tex’ing succeeds and a pdf output is indeed produced.
When trying to typeset a letter, where my preamble looks different and has the following line in it:
\usepackage[applemac]{inputenc}
the typesetting window will claim a problem with respect to this line:
"inputenc.sty:40: [...]"
When I comment out the \usepackage-line in the source, typesetting proceeds successfully (and VERY fast), though all special characters get omitted (to be able to use German umlaute like ä, etc is what the inputenc package should provide for).
So, is there a problem with the speedier LaTeX bundles as regards the preamble’s structure or content of the files to be tex’ed?
Sorry, I cannot really analyze or actually make sense of this behaviour, so I was hoping for some enlightment through the mailing-list.
Thanks for any hints about how to tackle this. I really would love to use the speedier bundles.
Best,
--Hans
