On 10/11/2005, at 12.12, Andreas Wahlin wrote:

It's a great thing, problem is though, it's somewhat slow (I suppose there's nothing to do about that) but when I constantly press an arrow key, it never updates.

It updates 1.5 seconds after last “change”. But it'll be instant for non-mutating changes (when I add a cache for the extracted list of symbols).

I'd like to see encoding down there in the status bar as well, I don't really know why actually, but all other editors have it :)

See Erics recent reference to Hyatts “all other modern browsers” :)

There are two reasons why I don't want to put it there, despite it being oft requested:

1) people should use utf-8, especially with TM's tight shell integration, this is important because the commands that need to work on files (like svn diff, TODO, PyMate/RubyMate (showing script output) etc.) can't possibly know about encodings, and utf-8 is the only encoding which can be recognized with near certainty, and is the only encoding which is ASCII compatible and can represent all typeable characters.

2) changing the encoding in TM is done _when saving_ -- that is, TextMate uses unicode internally, but offers the capability to *convert* this when saving the buffer, thus that choice should be made in the save dialog (i.e. if I were to offer it in the status bar, the proper thing to do would then also be to disallow typing of characters not supported by the current encoding, but I really do not feel like this, when utf-8 is the silver bullet, has been recommended by IETF etc. for 7+ years, the iso-8859 people/committee I think have stated that they no longer work on that set of encodings because of utf-8 etc.).

The faster we phase out all legacy encodings, the better -- and I'm playing an active role trying to promote utf-8 (despite this not always being popular)!

On 10/11/2005, at 13.07, Andreas Wahlin wrote:

Perhaps we could get a warning dialog or something in those cases?

Yes, I actually considered adding an “encoding wizard” for when TM can't detect the (utf-8) encoding.

But it's a little down on the list…

On 10/11/05, Luc Heinrich luc@honk-honk.com wrote:

On 10 nov. 05, at 11:28, Matt Mower wrote: class Foo def initialize end end

class Bar def initialize end end

Ah, I haven't seen this because I haven't yet opened a file with two classes defined inside. The SubEthaEdit styling is certainly very nice and if Allan can do it I'd be very glad to see that (or something even better) included.

M

-- Matt Mower :: http://matt.blogs.it/

On Nov 10, 2005, at 9:03 AM, Luc Heinrich wrote:

On 10 nov. 05, at 11:28, Matt Mower wrote:

...

...and the symbol popup is great.

Well, it's a good start yes, but it's pretty much close to useless, for me at least :p

A simple Ruby example:

class Foo def initialize end end

class Bar def initialize end end

The symbol popup for this file will show: <TxM_symbol_popup.png>

When it should at least show something like: Foo::initialize Bar::initialize

Or better: Foo initialize Bar initialize

Or even better, like SubEthaEdit with cute little icons :) <SEE_symbol_popup.png>

Looking forward to see what the next updates will bring us... Can I also have SubEthaEdit's superior block editing ? Please ? ;)

You can get pretty close to the same thing already. You won't have the nice icons, but you will have class and or def to set apart the class declarations from the method definitions. Note, this example is for Python not Ruby so you will have to translate the scope names to their ruby equivalents...

First go open up your language in the Bundle editor and create a new preferences. The contents of this new preference should be { showInSymbolList = '1'; }

Now the critical part is to set the scope: In python I set the scope to: source.python declaration.function, declaration.class

Now close the bundle editor.

With those definitions Here's what my symbols menu looks like for a file with multiple classes....

---

For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate

On 11/11/2005, at 11.35, Matt Mower wrote:

I did this in my Python Bundle changing "source.python" to "source.ruby". It sort of works in that I now see def <function_name>( <params> ) instead of just the function name. I don't get class <ClassName>.

Any ideas?

declaration.class should also work for Ruby (the entire line, just the class name has scope entity.name.class.ruby, you can see the scope with ctrl-shift P, and the scope selector is a bit like a CSS selector, see [1] for more info) -- but in the current ruby syntax, there's a problem correctly marking up classes/modules when they have no leading indent (because of the first rule in the grammar, which eats the keyword), I've re-arranged the rule on the repository (so will work in next build).

[1] http://macromates.com/blog/archives/2005/07/06/introduction-to- scopes/