Well, my email to Chandler was returned to me so here goes my
improvements to the MEL bundle. I find them very useful and that they
round out the MEL support.
Changes:
* parsing for the function statements to catch 'global proc' and
'proc' better
* preference to allow function names to be put into the symbol list
* moved global out of keyword.control.mel to keyword.other.mel
* made all scopes point to mel
Take what you want and feel free to point out where I made errors.
Thanks,
Dan
> On Sep 11, 2006, at 8:31 AM, Max Lein wrote:
> Just send them to me (or the list) when you are done. These can
> easily be included. The custom one are a bit more difficult:
Will do.
> This won't be very easy to do, we'll have to figure out the best way
> to do it in terms of making sure the user stays up to date with newer
> versions of the bundle. We could tell you how to edit the language
> grammar to add these things, but that's not very easy to do and
> results in the user having local modifications to the bundle which
> might result in them not seeing any official changes that happen to
> the grammar.
Ok, I'm no expert, but I figure this is what many, many people want
to do. Perhaps you could just list these commands in a separate file
and include that file appropriately?
> One thing that can be done now, is that you can create a new language
> that basically has the extra commands, and then includes the latex
> language, and you would be using that new language instead. I could
> offer a template language and tell you what you need to edit where.
> However, I would consider that only a temporary fix, because my
> understanding is that the next major version of TextMate will have
> tools that will make this customization process a lot easier/
powerful.
That would be great.
> That's exactly why I advocate the use of \( \).
>
> (we could actually make it so that pressing the dollar sign produces
> the \( \) pair instead ;). )
;-)
> I meant it was not possible without editing the language grammar.
> However I did add yesterday marginpar as a separate scope. It is
> meta.paragraph.margin.latex (not meta.paragraph.marginpar.latex as I
> mentioned in my last email).
True. Again, another quick and dirty hack by me ;-)
> Can input do selective includes, like via \includeonly? [http://
> www.eng.cam.ac.uk/help/tpl/textprocessing/teTeX/latex/latex2e-html/
> ltx-245.html]
> I was actually thinking, that one could simply duplicate the include
> drag command, and have a new one with input. Now, when you drag a
> file, you would be getting a menu with two options, and selecting one
> of them (with arrows or 1/2 numbers) would do the corresponding
> thing. We could do the same thing for graphics,
Nah, I think those people who want to change it, can do so easily.
> I was just looking at: http://authors.aps.org/revtex4/auguide.ps
> Section 6.4 explicitly mentions using \[, \] for unnumbered
> equations. And nowhere is it mentioned that \(, \) should not be used
> (though it does mention $).
Well, we do what we are used to in the end ;-)
I use align, because I got used to the way it, ahem, aligns formulas.
> The AMS-LaTeX guidelines do make it clear that both options are fine:
> [ftp://ftp.ams.org/pub/tex/doc/amsmath/short-math-guide.pdf]
>
> The only thing they discurage is the use of the eqnarray environment.
> They also recommend not using $$..$$
>
> Working on it. Actually the grammar will undergo a series of changes
> in the next couple of weeks probably.
Great :-)
You can also (ab)use me as a beta tester.
> I've just added command for part, chapter, paragraph, subparagraph.
> The triggers now are:
Thanks a lot.
> Also, all these commands now create the (fold) (end) comments
> described earlier, so they would fold and that should keep Jenny
happy.
Even better!
> Further, they have been designed so that you could execute them with
> a selection, and then they would wrap around that selection.
You thought of everything ;-)
> I would do: select the second part of the formula: press cmd-x, move
> down until out of the environment, type eq (or the right shortcut)
> followed by cmd-{ to generate a new equation environment, and then
> press cmd-v.
No sure, but that's what in principle the closing tag feature should
be for ...
> Alternatively, you can again select the second part of the formula,
> use ctrl-cmd-down arrow to move it out, and then use shift-ctrl-cmd-W
> to wrap it in a new environment.
I gotta give this a try.
> That is a good idea. Please suggest a list of specific howto topics.
> I'll see if I can also do a screencast demonstrating a typical
> complete workflow.
Yes, this would complement written documentation nicely.
> I guess that's why we have the outline at the very beginning, which
> links to the subsequent sections. In the first draft of the help
> there was such a thing, but then it was removed. We were trying to
> keep the size of the LaTeX file a small as possible, so that users
> could actually read the entire thing.
I don't think this is something you can keep up with the increasing
complexity. Thus, I don't think it's a good idea to constrain
yourself in such a way.
Instead, you could design one section to be read thoroughly and then
let the rest be what it is: a manual.
> How about a cheatsheet instead? A single page containing all the
> necessary information, in the form of a pdf?
Sounds like a good start. Refer to the appropriate sections in the
Help as well, then people can go on reading.
> Allan and I both agree with that. This is something that's missing.
> However, a lot of the customization of the LaTeX bundle should be
> done via the LaTeX Configuration file instead. What kinds of
> customizations did you have in mind? Things like creating a new
> snippet or a new command, or changing a current command? Or more deep
> things related to the syntax?
I would say both. Take a look what I did, I hacked your bundle to get
the functionality I want -- at the expense that it might break in the
future.
So I would actually do both -- if time permits.
> > For me, the most helpful kind of documentation is one that explains
> > by example (e. g. Samba by Example). So I would suggest to write
> > HowTo sections on `Getting Started', `Big LaTeX Projects',
> > `Customizing The LaTeX Bundle'. I would be willing to make
> > additions of my own.
>
> I take it you have seen the posts here: http://skiadas.dcostanet.net/
> afterthought/list-of-my-textmate-pages/
> They are a bit outdated I must say, need some new ones. Not sure if
> they count as HowTo's.
No, I haven't. You should definitely link them in your help.
Max
After installing the latest LaTeX bundle, I have noticed that *all*
labels are now included in the drop-down menu in the bottom instead
of just the section labels. Since I usually have 40+ citations in my
papers and notes, the drop-down menu has been rendered unusable.
Is there any way to fix this?
Max
Begin forwarded message:
> From: Andy Hunt <andy(a)pragmaticbookshelf.com>
> Date: September 12, 2006 8:28:26 AM EDT
> To: announce(a)lists.pragprog.com
> Subject: [Bookshelf] Textmate: Power Editing for the Mac
>
> We're very pleased to announce that our latest title, "Textmate:
> Power Editing for the Mac", is now available (in BETA) at
> pragmaticprogrammer.com/titles/textmate
>
> TextMate is a full-featured text editor available for Mac OS X that
> can greatly enhance your text manipulation skills. TextMate is
> actually a thin shell over a personalized team of robot ninjas ready
> to do your bidding. Let's face it, who doesn't want their very own
> team of robot ninjas?
>
> With TextMate you can do your normal work, but signal the ever-
> watchful ninjas as you go. At your command, they will launch into
> action, slicing through text, building repetitive structures of data
> in the blink of an eye, and much more. They will even post to your
> blog, handle your IRC conversations, and read your email.
>
> Inside this book you will learn how to teleport instantly to the
> exact line of the file you need to be on, edit the data with the
> briefest incantations of power, and banish the end result to the land
> of your choosing. It's magic, as you can plainly see.
>
> Leave the days of dull work behind. Learn your spells, gain access to
> your team of robot ninjas, and you too will be able to edit text so
> effortlessly that everyone watching over your shoulder will be forced
> to ask, "Wait, how did you do that?"
>
> With this book, you'll
>
> * Learn the preferred editor for Rails application development
> * Use built-in automations for HTML, Ruby, or over 30 other languages
> * Manage all the files in your projects
> * Fly through your files with easy navigation techniques
> * Master quick and dirty text editing with strong regular expression
> integration
> * Teach TextMate new languages and actions that will save you times.
>
> TextMate is a modern, powerful tool for programmers, web designers,
> and anyone else who regularly needs to work with text files on Mac OS
> X. TextMate focuses on pragmatic automation, which means it will save
> you time--time that's always in short supply. See how your lowly text
> editor can become a hard working member of your staff.
>
> Available now in BETA at pragmaticprogrammer.com/titles/textmate
>
> For more information on our popular BETA book program, please see
> http://www.pragmaticprogrammer.com/starter_kit/faqs/beta_faq.html
>
> --------------------
> Coming soon in Beta:
>
> * Rails For Java Programmers, by Stuart Halloway and Justin Gehtland
>
> Recently released:
>
> * From Java to Ruby: Things Every Manager Should Know, by Bruce Tate
> * Agile Retrospectives: Making Good Teams Great, by Esther Derby and
> Diana Larsen, Foreword by Ken Schwaber
> * Google Web Toolkit: Taking the Pain out of Ajax by Ed Burnette
>
> --------------------
>
> Enjoy, and thanks for your continued support!
>
> Andy and Dave
> www.PragmaticProgrammer.com
>
>
> _______________________________________________
> Pragmatic Bookshelf Announcements
> http://lists.pragprog.com/mailman/listinfo/announce
>
--
The moral of the story is this: don't assume that someone asking you
a question is an idiot -- especially if the question is about the
intricacies of SPARC DCTI couples. http://blogs.sun.com/roller/page/
bmc/20050125#solaris_10_revealed
OK. The title is terrible... Sorry...
This is a feature request. When I search
a word in a file with ⌃S, I would like some
warning (either a sound, or so...) when the
search starts again from the beginning of the file
I hope I make myself clear... :D
Thanks in advance :)
Howdy all,
Is anyone using the MEL Bundle? I've started using it at work and I
have a couple of simple changes for it. What's the best method of
submitting those changes so that they can be put into the repository
by a qualified commiter?
Dan
I sometimes find myself reformating big chunks of code (html) and
then i usually build a little scratch macro, and then i just hit shift
+command+m lots of times to go through the code. while this works, is
there an easy way to say something like "do this until end of file"
or simmilar?
perhaps make the macro dependant on finding the next text string of
something until the end or something?
andreas
Hi,
I've been experiencing this for quite a while now but until now had
no time to dig into the matter: With "Check Spelling as You Type" I'm
experiencing abysmal typing speed problems when working on LaTeX
documents. It only happens when I'm working some in already existing
paragraphs, *not* when typing at the end of the document. I can
actually see single letters appearing one after another in slow-
motion. Very annoying! Once I turn off "Check Spelling as You Type"
everything's back to normal, but it lacks a lot of convenience ... It
this a known problem? Does anybody else experience these problems, too?
(I'm working on a 12" PB (1st gen., 867 mhz) maxed out with 1.12 GB
RAM. It's plain text with a bit of markup so the machine *should* be
up to it ...!)
Christian
Hi All [Brad Choate in particular, I imagine],
I was wondering about the status of MT Category support in the blogging
bundle. Given the pedigree of the bundle's author (!) I would imagine
this would be a pretty important feature...
Yours,
Andrew
Hi all,
I was wondering about the status of 'full' support for folding in
python? The current implementation based on blank lines, spaces, etc.,
doesn't quite work for me. I understand that the 'folding engine' as it
is can't really handle python's indentation model -- but is some support
in the cards?
Andrew
