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
