2009/10/19 Jason Axelson <bostonvaul...@gmail.com>: > Look for step 6: > > Even though the path to pdflatex is in the shell's $PATH environmental > variable, textext.py needs the full path, as applications get their > value of $PATH from ~/.MacOSX/environment.plist. Another solution is > to make sure that ~/.MacOSX/environment.plist has /usr/texbin in PATH.
It's strange that apparently the only two ways to set PATH properly for non-terminal applications is either to hardcode it into the application source code (!!) or modify an ugly XML file (environment.plist) on a per-user basis. Why couldn't Apple just let the /etc/paths.d/* and /etc/paths method work for all programs? :/ What a pain! Abel: > Do you have any suggestions as to 'first steps' with the > command line? > After all of this, I feel it would be well worth while to become > further acquainted, but I've yet to find a good means of > introduction . . . There are lots of Bash tutorials on the web which are interesting (bash is the default shell program that you use in the terminal), but the best thing is experience. I'd suggest playing around with some very unixy programs that can be piped together and operate via the command line, for example the netpbm suite of image manipulation tools... e.g, a small script I wrote which extracts a preset area from a screenshot, scales it to the ratio provided as a parameter, quantises it down to 512 colours or less, then after converting it to a PNG, compresses it with two different programs (which actually works in this case :D): ;;;; bmptopnm $1.bmp | pamcut -left 96 -top 58 -width 640 -height 400 | pamscale -verbose -nomix $2 | pnmquant 512 | pnmtopng > $1.png optipng -o7 $1.png advpng -z -4 $1.png ;;;; The pipe | operator between two commands means "take the output of the first program and pass it to the second as input", like "strings `which ls`|sort|more" will list all the textual strings in the ls program, sort them alphabetically and page them onscreen. So... really the best thing is to pick a task that's extremely tedious to do from the Finder, but possible with simple shell commands, and incrementally muddle through it. Best of luck, Oisín --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to mnemosyne-proj-users@googlegroups.com To unsubscribe from this group, send email to mnemosyne-proj-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en -~----------~----~----~----~------~----~------~--~---
