In the File Browser sidebar when I open a "project" (a directory), TextMate
always shows the same state where some directories are expanded (to
multiple levels) and others are not. Is there any rhyme or reason about why
TextMate remembers this particular state?
It's a bother to have to close things up each time I open a project.
I would even be happy with the File Browser starting with no directories
open.
I've tried doing
defaults write com.macromates.TextMate.preview disableFolderStateRestore
-bool YES
but that seems to have no effect.
I've tried opening or closing some "tabs" (open files) and then closing the
project. That has no effect.
I'm on Mac OS X 10.11.4. TextMate version 2.0-beta.9.
BTW, after recently upgrading to the above version of TextMate (from
previous beta version), the problem was solved for a while, but now it is
happening again.
Thanks,
--ErikN
How does one go about debugging values and the like in TextMate?I’m trying to iterate through rows and see the values associated with my iteration. Is there a special output area that code prints to, like a console or something?
Hi,
seems odd, but I really do not know what marks are and how to set them (and
how many)? It seems related to the keybinding setMark.
In the latest release version 2.0-beta.9.1 the jump to next/previous mark
shortcuts have been changed to F3/⇧F3. So I was wondering how to set them ;)
and what is the difference with bookmarks?
regards,
feek
--
View this message in context: http://textmate.1073791.n5.nabble.com/What-are-marks-an-how-to-set-tp29938.…
Sent from the textmate users mailing list archive at Nabble.com.
Ah, thank you very much for that input. I will resend there.
On 4/18/16, 3:21 PM, "Jacob Carlborg" <textmate-dev-bounces+jjbernitt=gmail.com(a)lists.macromates.com on behalf of doob(a)me.com> wrote:
>On 2016-04-18 12:12, Joshua Bernitt wrote:
>> Hey all!
>>
>> I think this is the correct mailing list for this question;
>
>I recommend the general mailing list instead. There's barely any traffic
>at all in this mailing list.
>
>--
>/Jacob Carlborg
>
>_______________________________________________
>textmate-dev mailing list
>textmate-dev(a)lists.macromates.com
>http://lists.macromates.com/listinfo/textmate-dev
Hello
I use a lot of variables with @ in their names like
\rput@temp but a double-click on \rput@temp selects only
rput or temp. With TM1 I had the possibilities to
change but how can I do with TM2?
Thanks,
Best Regards,
Alain
Hi everyone,
I want to fold the following 'code'
# Section 1 ----
for (i in 1:30) {
y = i+1
}
# Section 2 ----
# a comment
x = y + 1
y = y^2
if (foo) {
a = b
for (j in 1:3) {
b = b + 1
}
}
# Section 3 ----
b = c
to fold in the following way:
- "sections" in the code are defined by #something----, everything
between two section titles should fold when the folding marker of the
title line is clicked
- blocks are defined with { (and a few other markers) and should fold
as expected.
With the following rules I can almost make it work
{
foldingStartMarker = '\{';
foldingStopMarker = '\}';
foldingIndentedBlockStart = '^#(.*?)\-{4,}';
foldingIndentedBlockIgnore = '^(?!#(.*?)\-{4,})';
}
the blocks fold, respecting nesting, the sections fold up to the next
section, *except* for section 1; there, the `for` block is not
indented and is at the same level as the section, therefore folding at
section 1 only folds until the start of the for block, not all the way
down to section 2.
It looks like I am searching for a way to the `foldingIndentedBlock`
rule to take precedence over the `foldingStartMarker` rule. Is it
possible?
To make it easy to take a stab at it, I created a new bundle and a
test file (the language is "testing") which you can get there:
https://dl.dropboxusercontent.com/u/1047321/Test.zip
PS: having comments which define sections in the code seems like a
general use case. The syntax is in that particular example is defined
in the R language by the RStudio IDE. This IDE is becoming common
enough that I am receiving code formatted this way a lot.
Thanks in advance for your help!
Good day,
I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text. I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
--
Josh Bernitt
Sent with Airmail
I was thinking that the context menu that shows up when you press
keyboard shortcut for a bundle command that is overloaded (multiple
commands for a single keyboard shortcut) can be quite long, especially
for the git commands.
What if we (I or someone) adds a text input field to the menu which
filters the menu items. And example of this can be found in Xcode [1].
Would that be a good idea?
[1] http://blog.manbolo.com/2012/05/24/filtered1.png
--
/Jacob Carlborg
I've been working for quite a while with trying to rewrite the grammar
for the D bundle to be more accurate to the official grammar. The
grammar for D is quite complex, that in the combination with the syntax
for grammars in TextMate doesn't allow any good ways to reuse or compose
rules making it very difficult to describe a grammar. I know it's
possible to reuse rules with the repository, but that seems to be mostly
useful when matching with "begin" and "end".
For example, this is the grammar for a function declaration from the
official D grammar:
FuncDeclaration:
StorageClasses(opt) BasicType FuncDeclarator FunctionBody
AutoFuncDeclaration
AutoFuncDeclaration:
StorageClasses Identifier FuncDeclaratorSuffix FunctionBody
FuncDeclarator:
BasicType2(opt) Identifier FuncDeclaratorSuffix
FuncDeclaratorSuffix:
Parameters MemberFunctionAttributes(opt)
TemplateParameters Parameters MemberFunctionAttributes(opt)
Constraint(opt)
Each of these parts/rules of the grammar consists of several other
rules, many levels deep.
It would be really nice if the TextMate grammar syntax allowed, somehow,
to define rules, or parts of a rule, which the other rules can be
composed of, similar to above.
Or is there a way to already do something similar with the current syntax?
--
/Jacob Carlborg
