My file filters in .tm_properties don't work any more.
I removed all other .tm_properties files and tried a .tm_properties
with just the two lines
excludeFiles = "*"
includeFiles = ""
and it has no effect. All files in the same folder are still displayed.
But it works for a different user with the same TM version on the same computer.
Other settings like "tabSize" are no problem at all.
I started TM 1.5 a few days ago by accident. Maybe this caused the problem.
TM 9286
OSX 10.7.4
- Philipp
Hi,
I'm finding the new calculated gutter themes quite jarring (build 9287). Would it be possible to have an option to revert to the old default gutter theme?
Adam
Hello, I recently used the Bundle Editor, and I noticed that the search
functionality (CMD-F) tends to work once and then never again, but is
somewhat unreliable (e.g. I was able to get it to work again once if I
closed the bundle editor then opened it again, but that only worked
sometimes)
I'm on a Macbook Pro 3,1 running 10.8.
-E
It's very common for CJK users to handling files with different
encodings. I want Textmate to show current file's encoding in the
status bar, and it will be better if I can convert a file's encoding
with a mouse click in Textmate.
It's also will be nice to show the current file's line endings in
status bar, eg (DOS / UNIX), and let user be able to convert it from
on to another in Textmate.
--
Yuan Jiang
http://blog.vetcafe.nethttp://twitter.com/sleetdrop
On Aug 18, 2012, at 7:17 PM, Gerd Knops wrote:
>>> - Right now it seems injection appends to the patterns. Would it be possible to also have 'early injection' where the new patterns are prepended to the patterns? I am experimenting with special comment sections like /*H: */, and can't seem to do this with injection. (Another example application: Headerdoc/Docbook comments /** */ etc).
>> I am not following why this would work for appending but not prepending… this is because you want to replace the _entire_ comment rule? As opposed to inject the grammar into the comment?
> Right. Here is a simple example: I like to use line comments '//' that begin at the start of the line as code separators, so I draw the line background in a different color, so basically
>
> match = "^//.*\n?";
>
> This doesn't work with injections, because the 'regular' grammar already gobbles up any '//', so the injected grammar never sees it.
>
> Similar for docbook comments: an injected grammar never sees the '/**' comments.
As for DocBook, you can inject into ‘comment.block’ and make the grammar:
{ patterns = (
{ begin = '\G\*';
end = '(?=\*/)';
name = 'text.docbook';
patterns = ( … );
},
);
}
Here \G anchors to the start of the parent match, i.e. directly after ‘/*’.
I don’t disagree on maybe changing the order of append/prepend, but there is a good case to be made for keeping as much parsing as possible in the original grammar.
By doing it that way, my rule above works with all comment types and can safely be injected into ‘comment.block’ rather than having to specify a list of source scopes that use ‘/* … */’ comments (i.e. if injected into ‘source’ you’d suddenly have rules for matching such comments in languages that do not support them).
The line comment rule, I am not sure if there is a case for changing how our “canonical” line rule should be made, perhaps matching ‘//’ with a look-ahead so that this can be re-parsed (and tested with ^) by the injected rule, or perhaps injected rules should run on the _entire_ scope, rather than start at where the ‘begin’ stopped.
My goal is to keep this generalized, so your injected rule to add a scope to line comments without leading whitespace would not just add a rule for double-slash comments (as not all languages may support this, and having to provide a list of which do, in the injection scope selector, fails to exploit the semantic value of scoping).
> Another example is leading whitespace: I like to have leading tabs highlighted with alternating light backgrounds, like so:
>
> <PastedGraphic-2.png>
>
> I would LOVE to use injection for that, unfortunately many definitions eat up leading space. So my only recourse is to write custom language grammars for ALL languages I want to have this feature (eg ALL languages I use), start with my rules (so they get first dib), then include the actual language.
I fear though that if you were to inject the whitespace rule you would break these definitions that also parse the whitespace, as many do things like: ‘^\s*«keyword»’ — I think either way, we need to “fix” these grammars to (generally) not parse the leading whitespace (I’m actually not sure why so many rules do this, and in some languages it’s *clearly* a bug, for example PHP’s ‘return’ keyword has the leading whitespace included not only in the match, but also the scope, meaning word selection/movement is wrong (as that leading whitespace is assigned the ‘keyword’ character class).
I just checked my own preferences and found that in addition to the bashrc
path contents, there is one more entry in TM's PATH variable, namely
/Users/[your user name]/Library/Application
Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/bin
Yes, there is a whitespace in between "Bundle" and "Support".
I actually don't remember whether it was there before I added my bashrc
paths, or if I appended it for any other reason, sorry. But you could try
that.
--
View this message in context: http://old.nabble.com/kpsewhich%E2%80%9D-to-PATH-in-TextMate%27s-Shell-Vari…
Sent from the textmate users mailing list archive at Nabble.com.
mtozsu wrote:
>
> But it is not clear what the variable name I should add should be (I tried
> TM_PATH and it did not work)
>
I may be wrong but try to simply name it PATH add the content of your
.bashrc path variable.
--
View this message in context: http://old.nabble.com/kpsewhich%E2%80%9D-to-PATH-in-TextMate%27s-Shell-Vari…
Sent from the textmate users mailing list archive at Nabble.com.
Hi,
to reproduce simply
- select a grammar which defines folding markers etc.
- type something which can be folded
- place the cursor just before the greyed three points indicator
- press e.g. ↩
it ends up like that:
[the problem - I can't even do an 'undo' and if I try to remove these CTRL char weird things happen]
or
- place the cursor just after the three point indicator and start typing
- nothing to see but the typed chars are stored within the folded block
Cheers,
--Hans
I updated from build 9270 to build 9275 last night, and it just crashes on launch every time, even if I opt not to restore windows.
I'm running 10.7.4 on a 2009 Mac Pro (4-core).
Crashlog: http://pastebin.com/3j47akHY
Reverting to build 9270 leaves me with a working editor once more.
Does anybody have any ideas what could be causing this? Unfortunately, it dies before showing the changelog, so I have no clues from that (I assume it's in the repo somewhere, but I haven't found where yet :)
Thanks
--
John Yeates
Hi,
I'm on 10.7.4 TM2 [9278] and any Bundle commands - invoked by mouse (via Bundle menu or status bar) - don't work. I only can execute commands via key equivalents.
Unfortunately I can't downgrade.
Any thoughts?
Cheers,
--Hans