Sorry I missed your response Allan, I set up my dead keys with a program
called Ukelele:
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ukelele
The first keystroke sets up a state that modifies the output of the
following keystroke (essentially each dead key you set up creates an
entirely new keyboard mapping of your choice). If the second keystroke
is not specified in the alternate mapping, the default value is used.
Garrett
textmate-request(a)lists.macromates.com wrote:
> Re: TM2 with dead keys
Hi,
I'm using TextMate Version 2.0 (9090) and found a minor but annoying bug.
Steps to reproduce:
Open up a folder
Open two files (two tabs)
Highlight text in your current tab (should be bright highlighting)
Switch to other tab, switch back (now it will be dull highlighting)
To fix you just have to command-tab to a different app and back. Seems like
changing tabs correctly dulls the tab you are changing from, but does not
brighten the tab you are changing to. Keep up the good work!
Cheers,
Andrew
Hi,
in TM 1.x it was possible to highlight the current line. In TM2 I can see a nice gutter effect which is feasible for almost all cases but I'm sometimes editing plain text tables with rather long lines and here it'd be nice to have a visual indicator for the current line to be able to read long lines better.
Thanks,
--Hans
Hi,
TM2 regularly crashes during redo. I can't consistently reproduce, except that it seems to happen when I redo more than once in quick succession, or redo directly after undoing. I have TM2 configured to send crash reports, but thought it would be a good idea to throw it out here, especially if others are experiencing the same issue.
Adam
Hi,
what is the new syntax to access the ui.rb and exit_codes.rb
files, and in general items from the Bundle Support bundle?
I mean, what should I use (in a ruby script) instead of
require ENV["TM_SUPPORT_PATH"] + "/lib/ui.rb"
which does not seem to work? maybe it's just matter of
setting a shell variable, but can't figure out how.
Thanks
Piero
I'm using TM Version 1.x (build 1631).
Some of the characters (in text mode) are not displayed "normally" (i.e.,
the way they have been). For example, the character - (minus) creates a red
highlight where is appears. Let's say I'm writing -- enable SSL -- in a
middle of a sentence, the -- enable SSL -- part is highlighted in red for
no apparent reasons (I haven't changed my setup). Also, the sign > is
changed to > with an underscore.
Any idea why this is happening? Might have changed something without
knowing it?
Thanks in advance.
I use command + arrow up / down quite a bit to navigate to the top and bottom of my tex files. I noticed that when I switch to an existing file, command + arrow up gets me to the top but command + arrow down gets me down the file but not to the bottom of the file. Or, if I do first the command + arrow down, nothing happens. I need to reiterate command + arrow up, to the top, then command + arrow down, to get to the bottom. This happens with all files except the very short ones. Is this something seen by others, and is there a solution?
-- Gildas Hamel