Hi,
is there a possibility to change or turn of the smart quote function
of textmate?
Since I need to write some german TeXt i would like to have the
„German Anführungszeichen“ instead of “English quotes”.
Having a mac gives me the great advantage of typing those quotes but
TextMate does to much here and generates „“” which
is a bit annoying.
Any suggestions?
Thanks
Christoph
~~~~~
Christoph Biela
cbiela(a)gmail.com
Does anyone out there have easy access to a PPC machine where they
could compile app-cmigrep from godi (it's an OCaml thing)? I'd like
to include it in Support/bin as a universal app to support the new
swank code completion for OCaml.
-David
Is anybody using TextMate to write Docbook? If so, I'd appreciate any
information about how to set up the tools to manage the various XSL
transformations.
Thanks,
Noel
--
Noel Rappin
noelrappin(a)alumni.brandeis.edu
I'm new to TextMate and am already recommending it to my students, but I don't
understand the conventions for Scope Selectors.
Let's say I want to color all div tags in HTML red. I've tried variations on
"entity.tag.div" in Prefs > Fonts & Colors without success. I've a basic
familiarity with RegExp, and it looks like Bundle grammar supports RegExp, but I
can't see where syntax coloring might be defined in the HTML Bundle either.
(For the record, I also can't figure out how to duplicate a Theme--say, if I
want to tweak a version of the default Theme but keep the original too.)
Thanks for any help getting me going in the right direction.
jon
I just downloaded and installed the latest "cutting edge" version of
TextMate. Just after I restarted TextMate to bring up the new version
however suddenly I faced a kernel panic, and had to cold-restart my
computer.
Is there anyone else who experienced something like this?
Anyone,
In version (Version 1.5.4 (1360)) of textmate there is a new
XHTML1.1 template. The problem I now have is that when you run Tidy
from the HTML bundle on a XHTML1.1 document it converts the document
to XHTML1.0 strict. This is a little odd. Additionally it does not
do this well because the resulting XHTML1.0 Strict document is not
valid. Iit leaves the (version="-//W3C//DTD XHTML 1.1//EN") attribute
from the original XHTML1.1 document templet. So, you end up with
some odd non-valid document. I love html tidy but maybe I'm doing
something wrong. I don't know how to change it so that HTML tidy is
nicer to XHTML1.1 documents. The XML bundle version of tidy works
well for now, but its not that same because I have to select in
manually. I can't just press (opt, shift, H).
If anyone has fixed up how they have Tidy cleanup an XHTML1.1
document please share.
Thanks you for your help!
- Ethan
i must be missing an obvious thing here, but whats the easiest way to
find the path to the current document you are editing?
i know of "reveal in project" but the full path? i would expect a
right click to bring up some way to find this.
interestingly running pwd as a command inside a doc returns "/"
using ^S to search, opens up a search bar. it would be neat if this
were like a command input area ala vi ... to run commands in the cwd.
thanks!
/dc
(counting the days for japanese support in TM!)
-------------------------------------------
David "DC" Collier
mailto:dc@pikkle.com
+81 (0)80 6521 9559
skype: callto://d3ntaku
-------------------------------------------
Pikkle 株式会社
http://www.pikkle.com
-------------------------------------------
--
-------------------------------------------
David "DC" Collier
mailto:dc@pikkle.com
+81 (0)80 6521 9559
skype: callto://d3ntaku
-------------------------------------------
Pikkle 株式会社
http://www.pikkle.com
-------------------------------------------
The current situation
A major goal of all the scoping standardizationstuff we do in the
syntaxes is to make it really easy so make a single theme that can be
used for any language.
Unfortunately, the reality is that languages are really complex and
it takes work to make a theme look good in more than a few languages.
And then more work to keep that theme looking good as the languages
syntaxes are updated and improved.
So, what do we have?
We have a handful of deep themes and a whole hugh mess of really good
looking shallow themes.
the deep themes are constantly updated and work in most every
language. The shallow themes are usually never updated and only work
in a few languages and break on most edge cases like deeply nested
embedded source.
The future
Themes are going to be even more important in the next major release
of TextMate. Themes will be more than just style, they will really
start making inroads into real functionality.
We'll be able to color things like the current selection, the current
line, merge conflicts, tab triggers, placeholders, etc... probably
even more.
[see http://pastie.textmate.org/39665]
This means that themes are going to become much more important to the
way you use the application than ever before.
Which means that it's going to become that much more difficult to
make a theme that really works for more than a few people and keep it
updated.
Tweaked Theme Versions instead of new Themes!
I think we need to move away from a Theme-as-style type of mentality
and more to a Theme-as-functionality type of thinking.
I've put a lot of work into my Brilliance Black theme, but frankly a
lot of people think it's really ugly.
Why is it so ugly? Mostly just my color choices. People all have
different tastes.
Also, it's totally unusable on a dark CRT or LCD.
I've made a few versions of my Brilliance Black theme. Brilliance
Dull, Brilliance White, Brilliance BBS, etc…
The advantage of doing a version of an existing deep theme is that
you get a new style without having to do all the coding of the random
edge cases. It looks pretty without losing any theme-based
functionality.
ShapeShifter
Have you ever user ShapeShifter? There are all these OS themes that
you can use to change the look of the chrome on all the windows and
dock and whatever else on your system. There's also a new tool you
can use to make a tweaked version of an existing theme. You can apply
core image tweaks to all of the images in the theme and save out a
tweaked version of a theme.
I think TextMate should do the same thing.
Start with a good deep base theme like Twilight and tweak the colors.
Then save the recipe of how you tweaked that theme.
The advantage is that when Twilight is updated, all of your tweaked
themes based off of it are also updated since they're just recipes
instead of actually different themes.
And you can make really creative new versions of themes without
having to do all the work of figuring out all the crazy edge cases
and junk.
thomas Aylott — subtleGradient — CrazyEgg — sixteenColors
http://blog.circlesixdesign.com/download/utw-rpc-autotag/
The Autotag bundle for Wordpress\TM has been updated to include a new
interface, better fuzzy matching, progress reporting, header endpoint
checking and more. The bundle automates tag suggestions and
insertions in blog posts for Wordpress blogs using Ultimate Tag
Warrior. It requires the UTW-RPC plugin available at the above
address, which adds xmlrpc capabilities to Ultimate Tag Warrior
without having to hack any files.
Thanks,
Brett
