Hi,
I've got favorites for “lib” and “LIB” set, pointing to two different
locations. That works fine when I switch the file browser to the
favorites (with the heart shape icon), but in the command-shift-O
dialog, I only see one of them.
I know I can rename the favorites and probably will do that, but
shouldn't these two views into the favorites list behave similarly, at
least when I have no subfolders?
Christopher
Is it possible to change the key combination used for completion? Escape is a very far reach given how commonly I use completion. If not, I'll just have to resort to keyremap4macbook.
Thanks,
Connor
On Jan 30, 2012, at 6:00 AM, textmate-request(a)lists.macromates.com wrote:
> Date: Mon, 30 Jan 2012 11:10:32 +0000
> From: "ld(a)ldaley.com" <ld(a)ldaley.com>
> To: "TextMate users" <textmate(a)lists.macromates.com>
> Subject: [TxMt] Re: TM Bundle for Java - Improved Java Properties
> grammar
> Message-ID: <6ACE76A4-AF40-4943-AA54-0805C2990BDA(a)ldaley.com>
> Content-Type: text/plain; format=flowed
>
> On 29 Jan 2012, at 6:15, John Joyce wrote:
>
>> Hello List,
>> After ages of consternation with viewing Java Properties files that
>> had multiline values in KVPs not properly syntax colored, I have
>> created a better language grammar for Java Properties.
>>
>> It does several things...
>> First it captures comments of course.
>> Then single-line KVPs
>> Then KVPs with dangling spaces or tabs between the key and the = sign.
>> (These stand out awesomely during fast scrolling to find where they
>> are and fix them)
>> Then multi-line-value KVPs.
>>
>> One can never be 100% sure of these things, but I feel fairly
>> confident with it because the multi-line-value KVPs I have dealt with
>> are actually HTML emails stored in KVPs. :)
>>
>> By the way, it looks best in Sunburst them.
>>
>> Please consider it for inclusion.
>
> If you submit a pull request for
> https://github.com/textmate/java.tmbundle I'll happily include it.
>
> Thanks!
>
> LD.
Submitted pull request.
Thanks,
John Joyce
Oddity:
My cursor ist placed after the "h" in the tag that should become "h1". The tag has been produced using "Insert open/close tag with current word" but without anything selected. I just typed the "h".
when typing the "1" the snippet inserts weird stuff underneath, where the text "Headline 1" is (see second screenshot).
could someone with a little more expertise have a look at the snippet and possibly fix it? I have no idea why that happens.
Thanks,
Thomas
Hello List,
After ages of consternation with viewing Java Properties files that had multiline values in KVPs not properly syntax colored, I have created a better language grammar for Java Properties.
It does several things...
First it captures comments of course.
Then single-line KVPs
Then KVPs with dangling spaces or tabs between the key and the = sign. (These stand out awesomely during fast scrolling to find where they are and fix them)
Then multi-line-value KVPs.
One can never be 100% sure of these things, but I feel fairly confident with it because the multi-line-value KVPs I have dealt with are actually HTML emails stored in KVPs. :)
By the way, it looks best in Sunburst them.
Please consider it for inclusion.
zipped for your unzipping pleasure.
Thanks,
John Joyce
Sorry if this has been covered, but I couldn’t find a mention of it.
Is there a “Filter Through Command” in TextMate 2 (8998)? Was it re-implimented as a bundle item or something? I can’t find it and the old shortcut doesn’t seem to bring it up.
--
Rob McBroom
<http://www.skurfer.com/>
Dear Sir or Madam:
http://jpfly.com/woaint.php?fuducampID=38
Thu, 26 Jan 2012 8:40:39
______________
" At the commencement of winter, Artichoke plants should be protected against frost, which sometimes destroys them in our climate" (c) Kailene vtk5945
On 24/01/2012, at 20.54, Dirk Günther wrote:
> I use the LaTeX grammar and I have defined my own shortverb
> command [...] What should I do that |c| in \tabular{...} is not defined as
> verbatim?
As Allan suggested, I think that you need to have a rule in the LaTeX
grammar that will match the column specification part of the tabular
environment. Instead of writing a completely new rule, I tried changing the
relevant existing rule, copied below. The only difference is in the begin
match. I also tried adding your rule for scoping anything between pipes as
verbatim, and this change to the tabular rules seems to do what you want -
anything in the column spec is not scoped as verbatim. Hope that helps!
-Daniel Grady
{ begin = '(?x)
(?:\s*) # Optional whitespace
((\\)begin) # Marker - Function
(\{) # Open Bracket
(array|tabular[xy*]?)
(\}) # Close Bracket
(\s*\{.*\})? # Column specification
(\s*\n)? # Match to end of line absent of content
';
captures = {
1 = { name = 'support.function.be.latex'; };
2 = { name = 'punctuation.definition.function.latex'; };
3 = { name = 'punctuation.definition.arguments.begin.latex'; };
4 = { name = 'variable.parameter.function.latex'; };
5 = { name = 'punctuation.definition.arguments.end.latex'; };
6 = { name = 'variable.columnspec.tabular.latex'; };
};
contentName = 'meta.data.environment.tabular.latex';
end = '(?x)
(?:\s*) # Optional whitespace
((\\)end) # Marker - Function
(\{) # Open Bracket
(\4) # Previous capture from begin
(\}) # Close Bracket
(?:\s*\n)? # Match to end of line absent of content
';
name = 'meta.function.environment.tabular.latex';
patterns = (
{ match = '\\';
name = 'punctuation.definition.table.row.latex';
},
{ begin = '(?:^|(?<=\\\\))(?!\\\\|\s*\\end\{(?:tabular|array))';
end = '(?=\\\\|\s*\\end\{(?:tabular|array))';
name = 'meta.row.environment.tabular.latex';
patterns = (
{ match = '&';
name = 'punctuation.definition.table.cell.latex';
},
{ begin = '(?:^|(?<=&))((?!&|\\\\|$))';
end = '(?=&|\\\\|\s*\\end\{(?:tabular|array))';
name = 'meta.cell.environment.tabular.latex';
patterns = ( { include = '$base'; } );
},
{ include = '$base'; },
);
},
{ include = '$base'; },
);
}
Setup:
Some text here {Some text here {some more text here}} Some text here
1. Place cursor after the first } but before the second }
2. Press Ctrl-Up.
My understanding is that the cursor should jump to just after the first {,
instead it lands just before the second {.
Cheers,
David.
