I'm using TextMate mostly for XHTML/CSS work.
I recently switched to a Mac Pro from a Mac Mini and now have a
proper Apple UK keyboard.
unfortunately the # is lurking under opt+3 and I find that an awkward
key combo for such an often used character.
I've tried using TextPander with some success but it won't expand a
snippet when the caret is not in empty space, so getting h3#header1
requires some jiggling.
are there any snippets or shortcuts I'm missing in TM that will
append a # to an element in CSS without me having to contort my
fingers to get option+3 so often?
TIA
Hi,
Anybody make Markdown Extra <http://www.michelf.com/projects/php-
markdown/> work with TextMate? Not sure if other people think the
extra syntax is helpful, but I do.
As this is written in PHP, I'm not sure how it can be implemented.
Another possibility is to use Maruku <http://maruku.rubyforge.org/>,
which is written in Ruby. Anyone here have any needs to these
Markdown add-ons? I'm now trying Textile now, but prefer Markdown.
Takaaki
--
Takaaki Kato
http://samuraicoder.net
Hi,
I'm looking for a way to export all the text from my .tex files, or
just one -
(actually I want to use it to create tagcrowds of my work >> http://
www.tagcrowd.com/ - to give it a try and for some designing touches)
I wonder if there is some way to do this, something like picking all
content that fits a certain scope like "string" - or something and
export it into a pure plaintext file.
I agree this feature would probably not be able to export \footnote's
and \marginnote's but anyway -
Do you have any idea if there already is something like this - or if
it is possible at all?
Thanks a lot - and enough for today
flo
Hi,
I've got a problem..
Using the instructions from the manual and from the mailing list, I
hit the Info-button in my project drawer (without having any file
selected) and set the
TM_LATEX_MASTER to
> /Users/flo/Desktop/DiplomArbeit/070627_da_draft01/da_draft01.tex
From now on, whenever I hit "Typeset and Preview" I get the
following error in my Preview-WIndow:
> Error locating external viewer: ‘/Users/flo/Desktop/DiplomArbeit/
> 070627_da_draft01/da_draft01.tex’
I've tried saving my masterfile "da_draft..." as relative and
absolute path, but both showed the same error.
In my external viewer, PDFView everything is fine and gets properly
compiled.
Why is this so? And is there something I do wrong? Anyway to fix this?
Thanks
Flo
I've got a couple questions:
Can it parse the document and generate a list of completions based on
what you've typed?
(Thomas' completion command does this very well.)
Can it do this on unsaved documents?
How are these rules defined? (the easier this is the better)
Hello,
I'm curious why these instructions <http://macromates.com/textmate/
manual/bundles#getting_more_bundles> direct the User to create a
local svn repo in the Apple System's (/) Library area as opposed to
the User's (~) Library area. Is there a reason that it must be
installed at the System level instead of the User's "Application
Support" hierarchy?
Cheers,
DK
On Aug 15, 2007, at 08:00, Alex Ross wrote:
> I agree that prefixing all re's is not ideal.
>
> So, we have five options:
>
> 1. Match all raw strings unambiguously as regular expressions. We
> will sometimes have false-positives.
>
> 2. Match raw strings that are arguments to methods from the re
> module. We will sometimes not match raw strings that are regular
> expressions, but can be pretty well guaranteed to never have a
> false-positive.
>
> 3. Require some prefix to a raw string to "turn on" regular
> expression matching. This has an extremely high probability of
> removing false-positives and false-negatives, but at the cost of
> additional CRUFT.
>
> 4. A combination of 2. and 3. Match raw strings that are arguments
> to re.compile and raw strings prefixed with (?#) as regular
> expressions, but no others.
>
> 5. Don't match re's at all.
>
> It would seem there is no perfect option. I propose that we put it
> to a vote, and perhaps appeal to our BDFL Allan.
>
> –Alex
>
> My vote would be for 4, but I'll add two more options:
>
> 6. Parse r' and r''' but not r" and r""" (or vice-versa) as regexes.
>
> 7. Parse the "r" prefix, but not the "R" prefix, as regexes.
>
> The last option is probably the simplest. I don't think I've ever
> seen the "R" prefix in use and didn't even know it was an option
> until I just read the spec moments ago.
>
> j.
>
6. and 7. are really variations of 3 - which 'special' prefix do you
use to turn highlighting on or off, and what is it's default state?
I have incorporated them below.
>> The last option is probably the simplest. I don't think I've ever
>> seen the "R" prefix in use and didn't even know it was an option
>> until I just read the spec moments ago.
>>
>
> I've never seen 'R' in use either, but I'm sure somebody, somewhere is
> doing it. I think 6,7 are going to be too confusing.
I think that it's no more confusing than having r'(?# as the lead
prefix, having R' instead, or having r' turning regex highlighting
ON, and R' disabling it. It also has the benefit that it's easier to
read, and since there doesn't seem to be a standardized common-use of
R', making it the 'I'm not a regex raw string' marker is reasonable.
> And adding a no-op "signal" to raw strings that will later be used as
> regexes just to turn on some coloring seems very unPythonic in that:
>
> It is ugly.
> It is implicit.
> It adds complexity.
> It detracts from readability.
> It is not the obvious way to do it.
Partially true - but this is not a language definition, nor Python
code, but something different - a highlighter FOR Python. The
underlying code that makes up Python is very unpythonic.... and it
certainly will make it MORE readable in TextMate, as then it will be
highlighted correctly!
I vote for 4 as well. Method number 2 will cover the most common use
cases of regexes, and will keep the regex using folk (like me) happy,
without highlighting non-regex raw strings, and keep that group
happy. Part 3 is more touchy...
Once we start to get to the edge cases, such as feeding in a raw
string defined in one line into an re.compile in another line, either
we:
a - Never highlight - keep raw string users happy, annoy regex
users quite a bit,
b - Highlight when a prefix turns it on - obscure and a bit ugly,
but keeps raw string users happy, annoy regex users much less, but
still a little,
c - Highlight by default, but adding a prefix can turn it OFF, e.g.
R instead of r - again, obscure and a bit ugly; annoys raw string
users slightly, keep regex users happy, or
d - Always highlight all raw strings as regexes - annoy raw string
users, keep regex users happy - which is what we have now.
I use regexes quite a bit, but I could foresee a case where I might
want a raw string non-highlighted. If we change it at all, I would
vote for 4c.
Nick
Hi
(I'm preparing a talk so I am actively testing
and running into problems, sorry...)
Again on the issue LaTeX Watch-Beamer:
could someone please reproduce the following issue:
- save a file containing only
\documentclass[10pt]{beamer}
\begin{document}
aa
\end{document}
- invoke LaTeX Watch
- modify something (add "bb") and save
- check what's happening: on my computer,
the .aux and .pdf files are refreshed twice
a second! in other words, LaTeX Watch
continually updates even if I change nothing
(after the first change and save)
I guess this is a conflict with the pgf package.
But how? This is especially annoyng in
case of errors since the requst to show the log
is repeated every second or so...
Thanks,
Piero
I just need to vent on a quirk that keeps tripping me up.
I can bring focus to the drawer. I can navigate up and down with arrow keys.
I can even select all files with cmd-a,
yet, if I hit return on a highlighted file (intending to open it) it inserts
a new line in the focused tab.
?? is it me, or is that inconsistent ??
--
dc
-----
David Clark
Database Developer
Institute for Community Inclusion (http://www.communityinclusion.org/)
david.clark(a)umb.edu
(617) 287-4318
On 8/16/07, Tobias Jung <newsgr(a)tobiasjung.net> wrote:
> At 15:31 Uhr -0400 15.08.2007, Charilaos Skiadas wrote:
> > this Applescript was utilizing the dictionary that Transmit had
> > set. In other words, Transmit has told AppleScript that it
> > understands words like "upload", "current session" etc. I guess
> > YummyFTP doesn't understand some of these words.
>
> Thank you; now it's obvious to me why it doesn't work.
>
> Kind regards,
> Tobias
>
Im sure you can ask developer (as license owner) to add AppleScript
support you need. At least they can tell you is it planned or not. Or
point you to workaround of any kind...
