On 15 Aug 2014, at 19:16, riki wrote:
> […] In the following code:
>
> […] I checked scope as you suggested. I got storage modifier scope
> […] but not for allocatable.
The issue is not related to your custom theme but rather the Fortran
grammar.
The Fortran - Modern grammar includes Fortran - Punchcard. This grammar
has a rule for ‘meta.specification.fortran’. In this rule, a new
context is started, and only Punchcard rules are included into that
context, this is line 69 in the (Punchcard) grammar which is:
patterns = ( { include = '$self'; } );
If we change this to instead include the Modern grammar then it works:
patterns = ( { include = 'source.fortran.modern'; } );
There are other places where Punchcard includes Modern (it actually
includes $self + Modern, but here $self is redundant since Modern
includes Punchcard).
I do not know about this Modern vs Punchcard, it seems that if Punchcard
is made to include Modern (as it already does) the two grammars should
just be combined into a single one, which would make parsing more
trapsnarent.
Just upgraded to TextMate 2 (have not used TextMate in a while, glad to be back :-)
I’m also starting to try and due Rails development in TextMate. The Rails Bundle is dated, and so is only partially usable. I would like to start “fixing” that in my spare time. One thing, though, that would be nice, is the ability to edit Ruby code in the Bundle Editor. The files show up, but I cannot click on them. The only way I can edit is “mate …” from the command line the files I want to modify.
Not a big deal, but would be nice.
Is there any way to show the SVN new/modified/deleted lines on the editor, just like the Modific plugin (https://github.com/gornostal/Modific)?
I mean, some kind of line badges/colors to highlight the changes.
Thanks,
Rubén
Hello Everyone,
I've been participating in a thread on GitHub
(https://github.com/deplorableword/textmate-solarized/issues/52) that
has identified the selection of text in the Solarized Dark theme as a
real issue. It seems that implementation of
selectionForeground/selectionBackground may be one solution for the
frustrating issue. I wanted to see if there was a wider desire for a
solution to this problem here, and perhaps if there was more support for
the implementation of selectionForeground/selectionBackground.
Thanks,
Alex
I found a strange behavior that I believe is a bug. I am using 2.0-alpha.9503 on OS 10.9.1.
First I redefined the keyboard shortcut for "Comment Line" in the system Preferences. This command is from the "Source" bundle and appears as alternative shortcut to the default ⌘/ in the bundle menu (I used ⌘- in order to avoid the rather clumsy command for german keyboard layout).
Right after that both shortcuts work fine. After closing and reopening TextMate, only the default shortcut ⌘/ works, the new shortcut is now ignored.
When I select Bundles -> Source -> Comments I can see that the commands are still set correctly. After that, both shortcuts work again, until I close TextMate and open it again: the new shortcut is ignored until the menu selecting Bundles -> Source -> Comments is opened up, after that it works till closing TextMate again.
I was struggling some time with this issue, without solution. Now after testing for writing this bug report, at least there is a simple workaround. But maybe it can be resolved. I also tried changing the Bundle "Source" itself, but that didn't do the trick either.
Martin
I've found this great BlurMate plugin today for TM2.
https://github.com/cliffrowley/blurmate
It works great, I just wonder since it's just a few lines of code,
why background blurring is not included in TM2 already?
I always loved the blur in Terminal and thought that TM2 is not capable of it.
Found the plugin just by accident.
Some way to set the blur using "defaults" for example would be nice.
On 15 Aug 2014, at 18:37, riki wrote:
> Please find herewith my custom theme.
> […]
I do not see any issue here.
I saved your theme and switched to it. Then changed langauge to Fortran
— Modern and entered ‘recursive’. This keyword is shown in bold
and with a slight color change (rather subtle though).
The rule in my Fortran grammar does btw not include as many keywords as
yours. Did you edit the grammar? Did you verify that you get the storage
scope (using ⌃⇧P)?
In a .tex file, typing sec + tab prints code for a section header and label. Very handily, the label for the section header syncs with the actual section header the first time the section is typed. However, thereafter, if the section header changes, the label doesn't change. Is it possible to always have the label change whenever the section header changes?
Many thanks
Ross
Hi,
We’re writing a booking (currently LaTeX) and I’d like to be able to use TM themes in the code listings.
Any solutions for that?
We’re using LaTeX packages “listings” + “color” to do the syntax highlighting. It allows statements such as this:
\definecolor{codegreen}{rgb}{0,0.6,0}
\definecolor{codegray}{rgb}{0.5,0.5,0.5}
\definecolor{codepurple}{rgb}{0.58,0,0.82}
\definecolor{backcolour}{rgb}{0.95,0.95,0.92}
\lstdefinestyle{mystyle}{
backgroundcolor=\color{backcolour},
commentstyle=\color{codegreen},
keywordstyle=\color{magenta},
numberstyle=\tiny\color{codegray},
stringstyle=\color{codepurple},
basicstyle=\footnotesize,
breakatwhitespace=false,
breaklines=true,
captionpos=b,
keepspaces=true,
numbers=left,
numbersep=5pt,
showspaces=false,
showstringspaces=false,
showtabs=false,
tabsize=2
}
Pretty basic… Anyone seen anything better (pygments?) Or even a way to convert themes to this style?
Thank you, and best wishes,
tim