Hi,
using the Perl gramar, if I have the cursor on a package name, like
Time::Mo|ment, (| is the cursor) and I try to get help, it should try to
get help on Time::Moment but right now it only uses Moment.
I had this problem with TM1 also but I fixed it by including : in the
definition of the "word". I don't know if this is still the way to do it on
TM2 or if there is a better way.
Suggestions?
Thanks,
--
Pedro Melo
@pedromelo
http://www.simplicidade.org/
xmpp:melo@simplicidade.org
mailto:melo@simplicidade.org
The search and replace window has a serious bug: the text in the search and in the replace text fields is not updated as you type, meaning whatever was in these fields from the last search is displayed properly. But if you edit the text in one of the fields, it is not updated. Functionality-wise, everything still seems to work, meaning that the text you’ve entered blindly in the search field still is what TextMate searches for and the text in the replace text field is what the search term will be replaced with.
Also, if you do a search all, the first time you press the button Search All, the Replace All button remains grayed out. Only after pressing Search All a second time does the Replace All button become active.
Does anyone else have the same problem?
Max
Hi all,
As of only very recently, I get the following drop-down error box when I
try to typeset a LaTeX document:
| Failure running "Typeset & View (PDF)".
|
| Typeset & View (PDF):4: undefined method `+' for nil:NilClass
(NoMethodError)
I think it was working until 1-2 updates ago.
Andrew
Is there a way to have TextMate remember the tab settings for a specific
file? I seem to recall that TextMate 1 did this.
I have a file with a .txt extension that I would like to always be set to
indent size 2 with soft tabs.
In my default .tm_properties file I have the a [ text.plain ] section that
sets the defaults to 8 and no soft tabs so I assume that this is why the
file is always opened with these settings. I would like to make this one
file an exception, but it is not part of any particular "project" just a
one off file.
I suppose I could add an entry in my default .tm_properties file for each
specific exception to the rule, but was hoping there might be a way that
wouldn't involve this.
Thanks.
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.
