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
Hi-
I have some java code that won't indent properly, and I would like to update
the syntax so it correctly identifies the end brace.
Simplified code looks like this:
package foo;
public class Foo
{
public static void main(String[] args)
{
new Transaction()
{
@Override
public void run() throws Rollback
{
System.out.println("In Main");
}
}.execute();
}
}
The problem is that the "}.execute();" line should have ended the "new
Transaction() {" block- but it doesn't. Whatever is trying to match the end
brace doesn't like the .execute() at the end.
Where/how might I be able to fix this?
Thank you,
-jamie
--
View this message in context: http://old.nabble.com/Change-java-indent--tp34273612p34273612.html
Sent from the textmate users mailing list archive at Nabble.com.
Just a thank you note for the on-going development of TM2, most recently the addition of the bundle menu to the bottom status bar by Elia Schito, full screen added to window and view (Jesse B. Hannah), and other improvements which make work so much more pleasurable.
--Gildas
On OS X 10.8:
* Invoking from command line does not get back to the prompt
* "Save" does not work anymore (no error, but the 'document change'
indicator in the menu title keeps showing), and any attempt to quit
the app prompts the "Do you want to save the changes you made in the
document ?" pop up
Anybody gets the same issues?
r9270 seemed ok.
BTW, is there an easy way to revert back to a nightly build or regular
version from the update window?
Cheers,
Manu
I'm looking for advice on the best way to hack minimal Vim support into TM2. I'm not looking to support all of Vim, but just a subset of what might be referred to as Vim normal mode.
Desired behavior
===
Until Vim mode is activated, TM2 should behave as normal. Once activated, all the <meta>*-<key> combinations will continue to work as normal TM2 commands, but non-meta key combinations will be interpreted as Vim commands.
Entering Vim normal mode
---
Traditionally, Vim normal mode is entered via hitting the escape key. Since most people won't want Vim behavior, there needs to be a toggle that enables Vim so that the escape key will work. This prevents existing TM2 escape behavior changing for those who don't want the optional Vim behavior.
Additionally, it is not uncommon for Vim users to remap the Vim normal mode entry trigger to something like "jj". This should be supported so that users can have the escape key retain it's traditional TM2 use.
Vim normal mode
---
I would like to support the full range of Vim commands for motion, deleting, and changing of text short of entering command mode i.e. ":<command>"
Vim command mode
---
No support, but maybe a subset later.
Vim search mode
---
I don't think this needs support, however it would be handy for '/' to map to opening the find dialog.
Approaches
===
I've spent a little time trying to figure out how to modify TM2 for Vim support and I'm not sure which direction I should go.
1) Hard code it right into TM2. It looks like I could start with OakTextView:keydown and branch off to a Vim interpreter if Vim is enabled. I think this is probably the easiest and most flexible approach.
2) Create a TM2 plugin/bundle that does most of the work, and modify TM2 just enough to provide the support that such a plugin/bundle would need. This approach worries, me because I'm not sure how much modification TM2 would need to expose all the required interface to the plugin system. Do TM2 plugins work the same as TM1 plugins? Is the TM2 plugin API in flux?
Thoughts?
I've been spoiled using all my TextMate macros and snippets in Mail in recent years. Unfortunately, after upgrading to Mountain Lion, Edit in TextMate is no longer working in TM 1.5.11 (1634) with Mail.app v6.0.
IIRC for past Mac OS upgrades, I've fixed this by re-installing Edit in TextMate via the TextMate bundle, making sure /Library/InputManagers is owned by root, then setting Mail.app to launch in 32-bit mode to enable InputManagers. But now in Mountain Lion I don't see the option under Mail > Get Info to launch Mail in 32-bit mode anymore.
1) Does anyone have a workaround for TM1?
2) Does TM2 (which I've not installed yet) have an upgrade/replacement for Edit in TextMate?
Thanks--jon
______________________________
It's not too late to catch up to the 21st century
Digital Curation online certificate
http://DigitalCuration.UMaine.edu
I'm looking for advice on the best way to hack minimal VIM support into TM2. I'm not looking to support all of VIM, but just a subset of what is known as Command Mode.
Desired behavior
---
Until Vim Command Mode is activated, TM2 should behave as normal. Once activated, all the <meta>*-<key> combinations will continue to work as normal TM2 commands, but non-meta key combinations will be interpreted as VIM commands.
Entering Vim Command Mode
---
Traditionally, Vim command mode is entered via hitting the escape key. Since most people won't want this feature, there needs to be a toggle that enables the Vim behavior so that the escape key would work. This prevents existing TM2 escape behavior changing for those who don't want the optional Vim behavior.
Additionally, it is not uncommon for VIM users to remap the Vim Command Mode entry trigger to something like "jj". This should be supported so that users can optionally have escape key can retain it's traditional TM2 use.
Vim Command Mode
---
I envision a basic set of Vim motion and selection commands:
Character movement:
k or up arrow - up
j or down arrow - down
h or left arrow - left
l or right arrow - right
Word movement:
e - to end of word as defined by current syntax (this is different from standard VIM behavior and should be reconsidered)
E - to end of a whitespace-delimited word
b - to beginning of word as defined by current syntax (this is different from standard VIM behavior and should be reconsidered)
--
Hans Stimer
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
I have read the threads about indentation problems and requests, and they don't seem to apply to my situation. I have somehow gotten TM2 so if I just hit return and type it indents every single line, no matter what, for Text and Python...
#!/usr/bin/env python
import sys
import time
import re
This even happens if I open a new blank plain text document and type:
asdf
asdf
asdf
asdf
I tried enabling and disabling the disable autoindent option in those two bundles, but nothing seems to change the behavior.
I have TM2.0, build 9147.
Thanks!
Seconded!
> On 9 Aug 2012, at 12:01, Rolf Langenhuijzen wrote:
>
>> Well, to me TM is money well spent, I'd renew my license any day.
>
> I would as well. Open-Sourcing it is *incentive* to pay for it, not
> vice-versa. It's the best of both worlds: lots of eyes on the little
> nit-picky problems, but someone who can dedicate their time to
> maintaining the larger vision and direction of the project, vet the
> contributed code for quality, and make sure there are regular dependable
> releases.
Am 10.08.2012 um 03:02 schrieb Allan Odgaard <mailinglist(a)textmate.org>
> Is this files with spaces?
Some of the directories in the path contain spaces, the actual file name does not. For instance, one of the files is called
/Users/max/Dropbox/research/piezoelectric effetcts in graphene (DL 2011)/top-current/section_3.tex
Thanks for fixing the bug!
Max
I've been using the TODO bundle for a long time in conjunction to help writing my research papers.
I've noticed that with Textmate 2, clicking in links of items in the Todo window (which covers the lower half of the window after pressing ctrl + shift + T) results in a »File Does not Exist« error message, although the link displayed points to the correct file. E. g. if you copy and paste the link into Safari, it will open a Finder window with the correct file selected.
To my knowledge, I have installed the latest version of the »official« Todo bundle (last updated in 2010, the one you can find at github.com/textmate/todo.tmbundle). I have also tried newer branches to no avail. The same version of the bundle under Textmate 1.5 works just fine.
Can someone point me in the right direction? My machine runs 10.8.0.
Thanks!
Max
This is some weird behavior. I've installed the Blogging bundle. Put in
my blog details like this:
blog_name http://admin@my_blog_url/xmlrpc.php
I successfully fetched posts. Once. Then it started failing with this
message:
Error: Bad login/pass combination. (403)
I deactivated all my Wordpress plugins. Same error. I went into
Keychain, deleted the password; tried fetching posts again (pasting the
PW into the dialogue box), and it works -- until...
I try fetching my blog's Categories, and get the following error:
Received exception: XMLRPC:: FaultException
XMLRPC:: FaultException: Bad login/pass combination.
[Several more lines of information, but I don't know how to capture
it!]
...And from that moment on, trying to Fetch Posts -- pasting the PW into
the dialogue box because the PW is no longer in the Keychain -- fails
with the "Bad login/pass" error. Can anyone help me figure out what on
earth is going on?
TIA,
Mark
Using:
TM 1.5.10 (1631)
Blogging & Multimarkdown bundles
OS X 10.6.8
WordPress 3.4.1
> On 7 Aug 2012, at 05:51, Max Lein wrote:
>
>> To my knowledge, I have installed the latest version of the »official« Todo bundle (last updated in 2010, the one you can find at github.com/textmate/todo.tmbundle). I have also tried newer branches to no avail. The same version of the bundle under Textmate 1.5 works just fine.
>
> You probably need to install the avian version: https://github.com/avian/todo.tmbundle though you should be able to install this bundle from the preferences pane as it's an official one.
Thanks for the link, I've installed the version of the TODO bundle specific to Avian and removed the old bundle. Unfortunately, that hasn't fixed my problem. Is there any way I can track down this problem any further?
Max
Hi,
when opening a file with Cmd-T it is opened in the editor. Now when
going to the Document (Cmd-Ctrl R, Go/Current Document), TextMate will
jump into the subfolder (instead of staying in the top folder. Any way
to configure TextMate2 so it will stick with the top folder (the one I
opened with mate) and not open the sub folder? Alternatively Keyboard
shortcuts to navigate the folder hierachy (going one folder up)?
A rails project with its 2-3 level deep directory structure it is
easier to see where I am when I now the folder (app/controllers, which
lib directory etc)
Christian
How and where do I define multi-language spelling? I use the LaTeX bundle and type different languages in my documents. I would like to define a scope for French, for instance, using \begin{french} and \end{french} as markers.
David Howden suggested a while back “to add to the grammar (creating scopes for different languages) and then set the languages for those scopes in the tm_properties file.” I would like to learn how to do that. I don't know regex (only very minimally) and where to define such scope. Thanks for pointers.
--Gildas
Hello:
In TextMate there was a "Fonts & Colors" preference panel where I could select which specific colours to use per syntax context. I can't find any such panel in TM2.
How do I adjust the colours so as to end up with my own scheme?
dZ.
