Allan Odgaard wrote:
> On 30. Jul 2007, at 22:26, Dushan Mitrovich wrote:
>
>>> Where do you see the `-`? The `-` in the lower right side is a symbol
>>> list. The column is just next to the `Line: xx` on the lower left. If
>>> you open a new document, you should see "Line: 1 Column: 1"
>>> (assuming you open a new document wihtout any templates.
>> What I see is this: "Line: 1 Column: _", followed by a pale
>> vertical bar, followed by a pale colored disk with the white letter "L".
>
> And this is even when you place the caret in the upper left corner, i.e.
> at column one?
Yes, even then.
<snip>
> I’ll update the manual. This command is gone. But there is a “Create
> HTML From Document” which you can run, Show Web Preview (Window menu)
> and then print from there.
>
> If you do this a lot, you can go to the bundle editor and change the
> output for the command to Show as HTML and give it a key equivalent.
> Then printing (colored) is just two keys instead of one.
Okay, I'll try that.
BTW, I'd like to thank you and compliment you for the clarity of your
instructions (to someone else, earlier) on how to get the 'End' and
'Home' keys to work as in the non-OSX world. Since I much prefer the
keyboard to the mouse, these instructions were a treat. I notice, tho,
that there are still some apps that disregard that, such as in Firefox
and Thunderbird. I suppose their structure is too different to notice
the key mapping.
- Dushan
Paul McCann <paul.mccann(a)adelaide.edu.au> wrote:
> Gack: I don't think you want to be grabbing latex just to get some
> printing functionality in place! If you're interested in producing
> beautiful technical documents on the other hand...
For beautiful technical documents, including equations, plots, etc., I
do use a full latex program - it would never occur to me to use a text
editor for that. What I do expect from a text editor is to be able to
write and print out a letter, for example, containing pure ASCII, that I
can mail off. Yes, occasionally snail-mail is still appropriate :).
> The link mentioned earlier in this thread *is* out of date: the
> "Typeset and View (PDF)" command in the latex bundle almost certainly
> isn't what was being referred to: it is --unsurprisingly-- only useful
> on a latex source file. I do have a recollection of some printing
> scripts being developed using "enscript", a formatting utility that
> comes with OS X. Here's one that lingers in my bundle, and
> occasionally proves useful. Make a new command with...
> =======================================================================
> Save: Current File
> Command(s):
> #!/bin/bash
> # close stderr
> exec 2<&-
> # set options here
> enscript_opt="-2Gr --line-numbers -o -"
> tempfile="/tmp/texmate-print.$$.pdf" # note: "$$" is the current pid
> pstopdf_opt="-i -o $tempfile"
> # create the pdf and open it
> enscript $enscript_opt | pstopdf $pstopdf_opt
> open $tempfile
> rm $tempfile
>
> Input: Entire Document
> Output: Discard
> =======================================================================
>
> You'll probably want to play with the enscript options to get the
> output to your liking, but it's very malleable.
Thanks for this command script, Paul. I've not tried making any
commands yet, but this is a chance to learn how.
- Dushan
Hello everyone,
I'm new to the group...I ABSOLUTELY LOVE TM. But I have one recurring
problem that is starting to irritate me.
9 out of 10 times when I start Textmate, I get some (unknown) font that I
don't want. Changing the font setting in preferences has NO effect.
Anti-aliasing on/off seems to work, but changing the font does nothing.
But then 1 out of 10 times when I start it, TM uses my font setting and I'm
a happy camper and afraid to ever close TM.
I've not spent a lot of time messing around trying to figure out the
problem...I'm also new to Mac and feel like a fish out of water doing
anything.
So I thought I'd ask if anyone knows what is going on...and how I can get TM
to use my font choice all the time.
Thanks,
John
Well, there are a few obvious points that (most) everyone wants, better
performance on networked files for example. There are (approximately)
five such Really Obvious(tm) requests (hey, I won't say what they
are--after all, they're Really Obvious(tm), right?), and even for those
that don't affect me personally, it's pretty obvious they need to be
taken care of.
Past that, what _I'd_ like (yes, I'm unique, and possibly completely out
of touch with the rest of the universe :-) ) is--simplicity. I'd like
Alan to concentrate a significant part of his design and programming
prowess on making TM not more powerful, but more obvious.
My canonical example of this is the whole keybindings issue. Currently,
dealing with keybindings in TM involves searching through bundles, using
the Keyboard and Mouse Preferences Panel, and using a keybinding utility
such as KBE. This is just too much info for my little head. I'd like it
all in one place, and if not in one place, at least simpler.
My belief is that TM is currently at a level where (for me)
concentrating on increasing uniformity and simplicity would in real
terms _add_ features to the application, because I suspect that there is
a lot of power I'm not using because I don't have the time to consider
the special cases or esoteric knowledge needed to use already existing
features.
So my real request for TM2 is--don't worry too much about new stuff.
Concentrate on making TM easier to use (keybindings as described above;
optional help strings for bundle items and a streamlined bundle editor;
UI improvements; etc.), and I'll still feel my money is well spent.
(This may have something to do with age. At 43, the days when I both had
the time and the desire to learn about cool "new" features, keybindings,
etc, are long gone. In the last five years, the only truly worthwhile UI
innovation I've come across are: The technique that Quicksilver and
Launchbar use for identifying commands/files, and that TM uses when
moving between files, i.e. type in a not-necessarily-contiguous
substring of a name to identify a command/file/whatever; And
tab-completion in TM. And the second could easily be subsumed in the first.)
Just my $0.02,
Ken
On Aug 2, 2007, at 6:45 PM, John Yates wrote:
> Curious...what is the font of choice for TM users?
My font of choice is Anonymous; very clear and readable on my aging
eyes.
I may just be being a berk here, but I don't seem to be able to get
the URL associations to play ball. I'm editing text in three different
wikis, each with a different format. My config looks like this:
{
URLAssociations = {
'mail.google.com/' = 'mail';
'macromates.com/blog/' = 'markdown';
'blacktree.cocoaforge.com/forums/' = 'bbcode';
'trac.' = 'trac';
'wiki.' = 'twiki';
'doe.caribou.lan' = 'markdown';
};
}
Whenever I edit the contents of a textarea in TM it's opened into a
file named title-of-page.safari. I consequently need to manually
switch the syntax highlighting. Is there something wrong with my
config?
I've restarted TM and Safari, to no effect. Do I need to prod
something else to get the input manager to take notice of changes to
the plist file? I'm using the Safari beta (3.0.2).
On a related note, can you use regular expressions in the
URLAssociations setup, or do you have to specify an exact match?
Cheers,
Graham
Howdy.
Since TextMate seems to be like 80% LaTeX users. I feel a burning need
to use latex.
Can one of you LaTeX gurus condescend to learn me what's up?
Maybe a few links to how to get started with latex and latex in
textmate specifically.
Do you have to be a nerd to be able to use it?
thomas Aylott — subtleGradient — CrazyEgg — sixteenColors
I don't know how many people use the Smarty bundle, but I've made some
major improvements. Highlighting now includes support for all
assignment, arithmetic, and logical operators. It also properly colors
all PHP variables, functions and constants.
I also updated the snippets to take advantage of tab stops, and
selected text, and includes almost all the options for each
function/modifier.
Finally, I updated the menu structure.
Also, I patched the HTML and PHP syntax so a block like:
{php}
$var
{/php}
will get properly highlighted as PHP and not as HTML. (Don't apply
these patches unless you really use Smarty, since Smarty is by default
disabled in the HTML syntax and this will undo that)
Any, comments, suggestions, etc. are welcome.
- Brian
I've played some with the SQL bundle but i wonder how to auto-select a
db/config per project.
I've got multiple configurations in my config for the MySQL bundle
But i need to click the config-item that i want to use and if i switch
project i need to click the other configuration first before i can
select a query and run it.
I've tried MYSQL_DB in my project property but that didn't work out...
Regards J.
Hi All,
I'm working on an all new version of the Latex and View command. See my
earlier message for you you can switch to this branch of the svn repository
if you'd like to beta test. I'm hoping to commit a major new version
today. I've attached a screenshot of the configuration window.
Whats missing?
Is the wording on the options for opening the viewer clear?
Here is another big question I've been thinking about. Since all of these
new configuration settings will be stored along with the standard TextMate
prefereces in a preferences file, how much backward compatibility should
this new version try to maintain?
The current Latex and View command has grown organically over the life of
TextMate and there are lots of environment variables that have been added
over time, some that are semi-redundant even.
TM_LATEX_PROGRAM
TM_LATEX_COMPILER
TM_LATEX_VIEWER
TM_LATEX_ERRLVL
TM_LATEX_OPTIONS
All of the above can/will be replaced with the new interface, and I think we
should make a break and do away with these.
TM_LATEX_MASTER
This one is more interesting. We currently have two ways to specify a
master/root file. Using this variable, or using the TexShop %!TEX directive
embedded directly in the file. The TexShop way seems clearly superior to me
since it allows for more flexibility than a single environment variable per
directory or project. So my proposal is that the environment variable goes
away.
TEX_PSTRICKS
Since we can automatically detect when we should use latex instead of
pdflatex this is redundant and should go away.
As I mentioned above, TexShop allows authors to embed directives right in
their source file that specify a master file, there are others as well. I
propose that we use that same set of directives and allow the following
in-file settings to take precedence over the preferences set in the
preference dialog box:
TS-options -- command line options passed to the latex engine
TS-program -- the typesetting engine to use just for this file
encoding -- how the file is encoded, I don't really know what to do with
this one. Anybody?
I've looked at the TexShop documentation and I think this is it, are there
other %!TEX directives I'm missing?
Thanks,
Brad
--
Brad Miller
Assistant Professor, Computer Science
Luther College
