Ok, I’m feeling a little dumb here. I understand from various posts scattered around that you can install and upgrade styles and so on for MacTeX via something called i-Installer, instead of getting the zip file and building the cls files etc and installing it by hand. (Not that I ever upgraded LaTeX when I was on linux either, but…)
So anyway, this being a mac, I have a feeling it is easy to do and yet I can’t seem to figure out how to upgrade the memoir class.
Any tips?
well I found a list of TeX packages available through i-installer, but memoir isn’t listed among them.
How do you upgrade the memoir package? Does it have to be done by hand?
i-Installer is more intended to keep the whole thing updated, rather than individual parts like the classes. I had to do it by hand, which involved fixing things up a bit afterwords. The old hyperref wasn’t compatible with the new class, et cetera.
Hm, that’s a nuisance. Do you happen to have notes on what all you needed to install? memoir, hyperref, anything else?
I didn’t write it all down, no. I think I needed kvoptions.sty, too. Which was in the oberdiek macro collection.
But, before you go through all of that trouble, have you tried just running pdflatex in nonstopmode? Do this:
pdflatex -interaction nonstopmode <filename.tex>If that makes a good PDF, then alias the command so you do not have to type all of that in every time.
alias pdflatex='pdflatex -interaction nonstopmode'You’ll need to add that to your shell environment file, which depends on what shell you use. For me, that is ~/.profile, using Bash.
argh 
I already did the manual update of memoir and hyperref.
after texhash and updmap, I’m now getting different errors, too.
Missing \endcsname inserted
followed by
Extra \endcsname
(grr)
Maybe I’ll nuke and reinstall MacTeX, and just accept that ifpdf error, or comment out the ifpdf commands. It seemed to produce a good PDF, as far as I could tell - didn’t inspect it closely, but nothing jumped out as being wrong. Besides, I’m always going to be using pdflatex for these documents…
What a nuisance. :-p
I was going to add, if you start messing around with upgrades, make sure to back up your old classes somewhere safe so you can restore – but it looks like I am too late. 
And yes, I am pretty sure the ifpdf warning is very minor. It is just getting declared twice somewhere, so all of the PDF meta-data functions still work. The PDF itself is fine – it just an annoying bug of duplication. nonstopmode is fine for stuff that comes out Scrivener anyway. Interactive mode is more useful when you’ve hand-coded the LaTeX file and you need to spot typos. So far, I haven’t seen an invalid LaTeX file yet.
Oh well, I just re-ran the MacTeX installer, and it fixed it right up 
I’ve actually never tried upgrading LaTeX before, I have always just done the “install it and leave it” thing. Set it and forget it…
At any rate, the ifpdf thing is minor so I’m not going to worry about it further. I’ll just be waiting for fletcher’s 6x9 xslt file for lulu format PDFs… 
I really should preface some of my more cavalier comments with a bunch of
[size=117]“I am insane geekgirl, who tears things apart because it is fun to fix them!”[/size]
…disclaimers.
Sorry you had to go through all of that hassle!
Haha 
You know, I used to be the same way. That’s why I jumped right in and tried the upgrade. But after a while I found I preferred to have most things that I use day to day Just Work. If it’s broken, I’ll get my hands dirty, but for the most part I like having things Just Work.
I’ll still hand-code LaTeX, or write scripts because doing things by hand is boring, or spend a few hours tweaking text configuration files until things are just as I want them, but sometimes it’s nice for well-designed software to do something for you.
That said, my appreciation of OS X is both that it Just Works and that I can screw around with unix to my heart’s content, all on the same computer! I do some software development myself, but it’s all perl/apache server type stuff, so I like being able to do that on my slick little powerbook 
Maybe should mention that TextMate’s default keybinding for “Edit in TextMate…” (Cmd-Ctrl-E) is currently blocked by Scrivener’s keystroke for entering one of the screen writing modes, and that it can be changed in the global system settings. I realise this is documented in the TextMate readme for setting it up, but it is one of those things that someone might not realise there ever was a keystroke in the first place.
It’s been a while since I worked on the guide to using MultiMarkdown with Scrivener.
I’ve put what I have up on my new site:
fletcherpenney.net/Using_MultiMa … _Scrivener
Also, I welcome anyone and everyone to edit the copy on my scratchpad:
fletcherpenney.net/scratchpad/Us … _Scrivener
Fletcher
I just tried to download that file and got the following error:
Is there anywhere else I can get a copy?
That’s an old link, the new one is right above your post
http://fletcherpenney.net/Using_MultiMarkdown_with_Scrivener
Actually, that’s not the same link. I’m looking for the example ScrivenerAndMultiMarkdown.zip document to download.
Can you give me an explicit url for that document?
It’s the same thing - just moved to the web rather than a standalone document.
If you want a sample document in Scrivener, then check out the MMD sample document, also on my website:
Can you be a little more specific? I’ve read about a dozen pages there and haven’t found anything other than the MultiMarkdown.zip release itself.
I was looking for something ending in .zip and overlooked the link right in the middle of the page to this file:
Hi Fletcher,
I’m new to this Scrivener/MMD/LaTex thing so I’ll be asking a lot and contributing little (in terms of solving other people’s problems).
But maybe I can make up for that by doing some collecting of solutions. In one of your posts you mention a Wiki, which seems to me the right place for that:
Following this link however doesn’t get me to a Wiki. Can you help me out?
Thanks, Richard
I believe that statement is obsolete. There was a time when Fletcher’s entire web site was run by wiki based software; I never tested to see if it was editable by the public, though.