[OS X TeX] New Macros, new Engines, new TeXShop versions, and all that
herbs at wideopenwest.com
Sun Feb 21 18:19:52 CET 2010
On Feb 21, 2010, at 10:52 AM, David Messerschmitt wrote:
> On Feb 21, 2010, at 8:18 AM, Richard Koch wrote:
>> I have been listening to the discussion about regenerating TeXShop/Macros for new releases.
>> I don't want to reach into users personal Macros (or personal Templates or whatever)
>> and add new items. That's because in the reverse situation I don't want anybody mucking with
>> my personal stuff.
> Thanks for your ongoing efforts to improve TexShop! I was thinking how this could be more transparent on upgrade too.
> Your suggestion is OK, but I would suggest the following alternative design philosophy: Make upgrade _completely_ transparent for naive or lazy users who are happy with the packaged distribution, and place the burden of manual changes only on users who desire something different from the packaged distribution.
> Here is a scheme that would achieve this (perhaps not carefully enough thought out):
> Two folders -- default macros and user macros. The default macro folder would be automatically upgraded. By convention, the user macro folder could include three types of files: (a) additions, (b) replacements (same name), and (c) removals (signaled by some agreed convention like the same name with the word "remove" prepended). Texshop at startup would determine which macros or versions of macros were desired. In this scheme you would be blindly adding new default macros with each upgrade, but this seems benign -- the burden would be on the unusual user not wanting that macro to add a new file to remove it.
> David Messerschmitt
> Electrical Engineering and Computer Sciences
> University of Californa at Berkeley
I don't like anything to happen blindly! If the user really is lazy I don't see what motivates them to do anything like make a list of items they don't want, etc. Having new items just put in a separate folder makes sense to me. Then I decide if/what I want and don't want. Also, this process would have to happen at every startup of TeXShop when you rarely need it at all.
(herbs at wideopenwest dot com)
More information about the macostex-archives