On Aug 20, 2009, at 2:21 AM, Peter Dyballa wrote: > > Am 20.08.2009 um 01:29 schrieb Adam M. Goldstein: > >> Any ideas about how I can use Emacs.app to edit documents and >> preserve >> the links? > > > The problem with hard links can be solved with a bit of customisation: > > '(backup-by-copying-when-linked t) > > Setting this variable to non-nil makes GNU Emacs copy the original > file and leave this copy as backup. Now one of the hard links will > get edited. >
This works. Thanks! > OTOH with LaTeX you don't need to keep so many "copies" around. > LaTeX searches for input files along a set of paths, each named. > TEXMFHOME describes where your private files are stored, the command > 'kpsexpand \$TEXMFHOME' (on the command line) will reveal the root > of a file system branch where you can store your own files, for > example in $TEXMFHOME/tex/latex/mine. > What I want to do is create a library of parts of syllabi, so that each semester I can generate syllabi that are the same in certain sections. If I see a change I want to make, say, to some remarks about late papers, and it applies to, say, 3 syllabi for 3 sections of the same class, I don't want to have to make the changes in all three. Also I want to be able to teach different versions of the same class, each with its own description, set of readings, etc., and be able to re-use those parts in different years. So, I have one master library directory, which is accessed by LaTeX from each syllabus directory (there's one for each section, each semester). So, the importance of all this is that I would like to be able, in principle, to pick up the entire structure, including the library, and move it to any unix-like machine, and run LaTeX on it w/o making any other changes. In particular, I don't want to have to change the variable you talk about below. I can't even really specify relative paths because because (and I am pretty sure this make the difference) the path from each syllabus folder to the library folder will be different depending on the class, year, etc. Maybe the thing to do is to determine what $TEXMFHOME is, and be prepared to drop the library files in there, even if I move to a new machine. Well, maybe I won't have access to that on another machine? For now I am using the hard links. ------------------ Adam M. Goldstein PhD, MSLIS -- agoldst...@iona.edu a.m.goldst...@mac.com http://www.iona.edu/faculty/agoldstein -- (914) 637-2717 -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Emacs-app-dev- mailing list Emacs-app-dev-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
