From MacOSX-TeX@email.esm.psu.edu Wed Jun 8 19:55:07 2005
Received: from engremail2.engr.psu.edu ([130.203.201.116]) by ENGRMAIL1.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
Wed, 8 Jun 2005 19:55:07 -0400
Received: from email.esm.psu.edu ([130.203.247.204]) by engremail2.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
Wed, 8 Jun 2005 19:55:05 -0400
Date: Wed, 8 Jun 2005 20:00:13 -0400
Message-ID: <5613.19361@email.esm.psu.edu>
Subject: MacOSX-TeX Digest #1397 - 06/08/05
From: "TeX on Mac OS X Mailing List"
To: "TeX on Mac OS X Mailing List"
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Sender:
Precedence: List
List-Software: LetterRip Pro 4.05 (0531) by LetterRip Software, LLC.
List-Subscribe:
List-Digest:
List-Unsubscribe:
X-LR-SENT-TO: mail.engr.psu.edu
Return-Path: MacOSX-TeX@email.esm.psu.edu
X-OriginalArrivalTime: 08 Jun 2005 23:55:05.0268 (UTC) FILETIME=[7E243740:01C56C85]
MacOSX-TeX Digest #1397 - Wednesday, June 8, 2005
PPC to Intel
by "Rodrigo Banuelos"
Re: [OS X TeX] PPC to Intel
by "Justin Walker"
[ANN] BibDesk 1.1
by "Adam R.Maxwell"
Re: [OS X TeX] PPC to Intel
by "Bruno Voisin"
Re: [OS X TeX] PPC to Intel
by "Gerben Wierda"
Re: [OS X TeX] PPC to Intel
by "Peter Dyballa"
Re: [OS X TeX] PPC to Intel
by "Fernando Pereira"
Re: [OS X TeX] [ANN] BibDesk 1.1
by "Michael S. Hanson"
Font problem?
by "Fran=E7ois G. Schmitt"
Re: [OS X TeX] Font problem?
by "Aaron Jackson"
Re: [OS X TeX] Font problem?
by "Herbert Schulz"
Re: [OS X TeX] [ANN] BibDesk 1.1
by "Adam Maxwell"
customizing menu shortcut keys in TeXShop
by "Charles Chapman Pugh"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Herbert Schulz"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Johan Almqvist"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Chris Goedde"
customizing menus in TeXShop
by "Charles Chapman Pugh"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Bob Kerstetter"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Herbert Schulz"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Herbert Schulz"
Re: [OS X TeX] Font problem?
by "Peter Dyballa"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Bob Kerstetter"
Re: [OS X TeX] customizing menu shortcut keys in TeXShop
by "Bob Kerstetter"
Re: [OS X TeX] PPC to Intel
by "Maarten Sneep"
Re: [OS X TeX] PPC to Intel
by "mark oilcan"
Re: [OS X TeX] PPC to Intel
by "Bob Kerstetter"
----------------------------------------------------------------------
Subject: PPC to Intel
From: "Rodrigo Banuelos"
Date: Tue, 7 Jun 2005 20:17:27 -0500
...and so the question, for those who know best, will the transition
from PowerPC to Intel be painless, as far as TeX (and all the related
apps
that we so cherish) is concerned?
Rodrigo Banuelos
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Justin Walker"
Date: Tue, 7 Jun 2005 18:38:47 -0700
On Jun 7, 2005, at 18:17, Rodrigo Banuelos wrote:
> ...and so the question, for those who know best, will the transition
> from PowerPC to Intel be painless, as far as TeX (and all the related
> apps
> that we so cherish) is concerned?
Ha! It will be as painless as possible :-}. Most of the pain will be
borne by developers, as they learn to live with the unliveableXXXXXnew
architecture. For higher-layer code, such as Cocoa based apps (e.g.,
TeXShop), "it should just work", depending on how much or little skanky
code lies beneath.
For the Unix-flavored stuff, like teTeX, I should think that will
indeed just work, since those bridges have been long-since crossed
(this code runs on all manner of architectures, OS's, ...).
There will certainly be rough spots, and the early adopters of the Macs
with Intel Inside (shudder) will see growing pains. That should soon
pass, though. There has been a significant amount of work put into
this already, and Apple has been working on this, in one form or
another, for the past 12-15 years, so I don't expect serious issues
once shipments to real end users begin in ernest.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-at-Large
/~\ The ASCII
\ / Ribbon Campaign
X Help Cure HTML Email
/ \
----------------------------------------------------------------------
Subject: [ANN] BibDesk 1.1
From: "Adam R.Maxwell"
Date: Tue, 7 Jun 2005 22:07:40 -0700
The BibDesk development team is pleased to announce that version 1.1 =20
is available for download at . =20
There are some major changes in this version, so it should probably =20
be considered a beta release; as usual with beta releases, don't use =20
it to overwrite the only copy of your .bib file!
Items using the BibTeX crossref field are now searchable and =20
sortable, and inherited fields are displayed in the main pubs list =20
and the editor. Please see the online help for notes on editing =20
(preferences, new menu items, and drag-and-drop).
Any problems should be reported on the SourceForge Tracker at .
Complete release notes follow:
Changes since 1.0
New Features
=95 Crossref support implemented (RFE 1175264).
=95 The "add publication from..." items now have autocompletion =20
enabled when editing (RFE 1213519)
=95 Added a preference option for cleaning TeX commands or braces =20=
from format strings for AutoFile and auto cite key generation
=95 The Macro editing list now has type-ahead find, so you can =20
select an item in the list by typing part of its title (handy for =20
looking up definitions)
=95 RIS value of a publication is now accessible from AppleScript
Bugs Fixed
=95 Online version checking should be more effective; previous =20
versions considered 1.0RC2 to be newer than 1.0
=95 Refer to the correct anchor in the Help for help buttons (bug =20=
#1213603).
=95 Undefined fields are now handled correctly in AppleScript. =20
Fields are added if necessary, and an empty string is returned if the =20=
value is undefined. 'All fields' will now return all defined fields, =20=
not just non-empty fields.
=95 Copy and Cut menu items should now be disabled when there is no =20=
selection
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Bruno Voisin"
Date: Wed, 8 Jun 2005 11:38:47 +0200
Le 8 juin 05 =E0 03:17, Rodrigo Banuelos a =E9crit :
> ...and so the question, for those who know best, will the transition
> from PowerPC to Intel be painless, as far as TeX (and all the =20
> related apps
> that we so cherish) is concerned?
Depends on which TeX you're thinking about:
- For Textures, painful: it seems Rosetta, which will allow PowerPC =20
apps to run on Pentium, won't support Classic. Of course, there's =20
always the possibility that Textures runs on OS X, eventually...
- For other TeXs, depends on whether they're optimized to use G4 or =20
G5 specific functions, that Rosetta won't support. If you look at the =20=
doc , you'll see that Rosetta is =20
actually a G3 emulator, not more. For example telling, as Apple does, =20=
to a scientist that Rosetta won't be good at FFT is like telling a =20
cook that an oven won't be good at heating food. Thus it feels like =20
Rosetta will be pretty much useless, except for the most basic tasks.
It's safer to assume that TeX apps won't actually require the Rosetta =20=
emulation, and be ported instead to the Pentium (=3D become Universal =20=
Binaries). If one is to believe Apple's doc and marketing blurb, for =20
Cocoa apps (TeXShop, iTeXMac, ...) the porting should be easy, and =20
for Carbon apps (OzTeX, CMacTeX, ...) a bit more difficult but still =20
manageable.
That's only frontends, though, and that leaves of matter of the TeX =20
engines (TeX, pdfTeX, XeTeX, ...). On this I've no idea. It depends, =20
I imagine, on some sort of support of the new platform by gcc. It =20
might also be an issue for OzTeX, which includes its own TeX binaries =20=
compiled with another compiler (for the Modula-2 language IIRC).
Regarding the lack of support of Classic, which Apple seems to =20
confirm , I feel personally very upset: Phil =20
Schiller from Apple has the attitude of telling "Hardly anybody uses =20
Classic anymore, so it's very low on our priority list". Very well. I =20=
don't use Classic to do any new stuff, but I appreciate the =20
possibility of opening my old files from 15 years ago, written using =20
MacWrite, MacDraw/Claris Draw, Claris Resolve (and Textures), and =20
copying/reusing some of their content. Or using fonts in Mac OS 9 =20
format (like my Lucida and MathTime fonts) under OS X.
Warning: I'm no developer, thus I may be completely wrong. And there =20
are issues that puzzle me: for example, the Pentium doesn't support =20
64-bit code, right? What will happen, then, of applications for which =20=
a lot of the recent development efforts went precisely into =20
supporting 64-bit addressing for the G5?
Bruno Voisin=
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Gerben Wierda"
Date: Wed, 8 Jun 2005 12:25:32 +0200 (CEST)
> ...and so the question, for those who know best, will the transition
> from PowerPC to Intel be painless, as far as TeX (and all the related
> apps
> that we so cherish) is concerned?
Regarding the backend most people use on Mac OS X: I have already a repor=
t
that TeX Live compiles fine on an Intellimac. In howfar i-Installer is
portable I do not know yet (because that depends in howfar Apple has good
ports for the Mac OS X 10.2 frameworks i-Installer uses) but normally it
should just work. Unless someone pays $999 for me to use an evaluation
system for the coming 2 years I will not have access to an Intellimac
soon. But it is likely I will buy an Intellimac if they produce somethin=
g
good.
What might happen is that I have to drop support for Mac OS X 10.2 accros=
s
the board. Dropping 10.2 might enable me to support autehticating proxies
etc, so it is also a potential good thing.
I am likely going to work on getting Apple to produce an improved
Installer engine for 10.5 Leopard, so what might happen is that
i-Installer would disappear entirely and be replaced by Apple's own.
(Here's to hoping that is going to happen)
Relax all, we have a year of hammering this out before the first systems
are out there.
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Peter Dyballa"
Date: Wed, 8 Jun 2005 13:02:33 +0200
Am 08.06.2005 um 03:17 schrieb Rodrigo Banuelos:
> ...and so the question, for those who know best, will the transition
> from PowerPC to Intel be painless, as far as TeX (and all the related
> apps
> that we so cherish) is concerned?
>
Yes and No!
The No refers to Vanderpool, a hardware extension Intel is going to
bring to us probably next year. It does make the CPU virtual, i.e. the
applications get the feeling that they have their own 'private' CPU to
which they are bound to. This too means that Vanderpool allows the use
of more than one operating system at the same time -- no Soft or
Virtual PC or Classic or VMware. Now imagine an OS independent TeX
server -- applications send work to it, other applications fetch the
server's work!
FAT binaries could be very lean ...
--
Greetings
Pete
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Fernando Pereira"
Date: Wed, 8 Jun 2005 10:15:15 -0400
On Jun 8, 2005, at 5:38 AM, Bruno Voisin wrote:
> That's only frontends, though, and that leaves of matter of the TeX
> engines (TeX, pdfTeX, XeTeX, ...). On this I've no idea. It
> depends, I imagine, on some sort of support of the new platform by
> gcc.
gcc on Intel gets a lot more development effort than on PPC, since
it's the compiler of choice for all open-source dvelopment on Linux
and *BSD. So, if anything, gcc on the new Macs will be ahead of where
gcc for PPC would be.
> Warning: I'm no developer, thus I may be completely wrong. And
> there are issues that puzzle me: for example, the Pentium doesn't
> support 64-bit code, right? What will happen, then, of applications
> for which a lot of the recent development efforts went precisely
> into supporting 64-bit addressing for the G5?
You can buy Intel Xeon CPUs with 64 bit support already. Most people
I know prefer 64 bit CPUs from AMD at the moment (that's what I've
been buying for my compute servers), but Intel is catching up fast.
-- F
----------------------------------------------------------------------
Subject: Re: [OS X TeX] [ANN] BibDesk 1.1
From: "Michael S. Hanson"
Date: Wed, 8 Jun 2005 12:04:21 -0400
On Jun 8, 2005, at 1:07 AM, Adam R.Maxwell wrote:
> The BibDesk development team is pleased to announce that version 1.1
> is available for download at .
>
> Any problems should be reported on the SourceForge Tracker at
> .
For some reason I cannot get through to the above link, so I'm
reporting my problems with version 1.1 below. Note that v1.0 seems to
work fine, and I have rolled back to that version for now.
Copied from the crash reporter:
> Date/Time: 2005-06-08 11:56:09 -0400
> OS Version: 10.3.8 (Build 7U16)
> Report Version: 2
>
> Command: BibDesk
> Path: /Applications/BibDesk.app/Contents/MacOS/BibDesk
> Version: ??? (???)
> PID: 1124
> Thread: Unknown
>
> Link (dyld) error:
>
> dyld: /Applications/BibDesk.app/Contents/MacOS/BibDesk can't open
> library: /usr/lib/libgcc_s.1.dylib (No such file or directory, errno
> =3D 2)
Thanks in advance for addressing this issue.
-- Mike
----------------------------------------------------------------------
Subject: Font problem?
From: "Fran=E7ois G. Schmitt"
Date: Wed, 8 Jun 2005 18:15:54 +0200
Hi,
I have installed TeXShop 1.40 on a system 10.3.9 and have the following
problem.
Everything used to work fine, but recently I had to reinstal the
system, and then I reinstalled TeXShop and all the indicated files.
And now it refuses to work, for an unknown reason. The problem does not
seem to be linked to TeXShop since IteXMac gives the same result: the
problem seems to be with TeTeX or with fonts.
At the end of the compilation of my file I obtain the following output,
repeated several times before an almost blank pdf file is generated:
------------------------------
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
cmex10
/usr/local/teTeX/bin/powerpc-apple-darwin-current/mktexpk: line 1:
basename: command not found
mktexpk: /var/tmp/texfonts/pk/ljfour/public/cm/ already exists.
/usr/local/teTeX/share/texmf/web2c/mktexupd: Missing argument(s).
/usr/local/teTeX/share/texmf/web2c/mktexupd: line 1: basename: command
not found
Try ` --help' for more information.
warning: kpathsea: mktexpk output
`/var/tmp/texfonts/pk/ljfour/public/cm/' instead of a filename.
kpathsea: Appending font creation commands to missfont.log.
)
(see the transcript file for additional information)
Warning: /usr/local/teTeX/bin/powerpc-apple-darwin-current/pdflatex
(file cmex1
0): kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+57/600
--dpi 657 cmmi10
/usr/local/teTeX/bin/powerpc-apple-darwin-current/mktexpk: line 1:
basename: command not found
mktexpk: /var/tmp/texfonts/pk/ljfour/public/cm/ already exists.
/usr/local/teTeX/share/texmf/web2c/mktexupd: Missing argument(s).
/usr/local/teTeX/share/texmf/web2c/mktexupd: line 1: basename: command
not found
Try ` --help' for more information.
warning: kpathsea: mktexpk output
`/var/tmp/texfonts/pk/ljfour/public/cm/' instead of a filename.
Font cmex10 at 600 not found
------------------------------
Thanks for any info to help fix this problem.
Francois Schmitt
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Font problem?
From: "Aaron Jackson"
Date: Wed, 8 Jun 2005 12:30:55 -0400
On Jun 8, 2005, at 12:15 PM, Fran=E7ois G. Schmitt wrote:
> Hi,
>
> I have installed TeXShop 1.40 on a system 10.3.9 and have the=20
> following problem.
>
> Everything used to work fine, but recently I had to reinstal the=20
> system, and then I reinstalled TeXShop and all the indicated files.=20=
> And now it refuses to work, for an unknown reason. The problem does=20
> not seem to be linked to TeXShop since IteXMac gives the same result:=20=
> the problem seems to be with TeTeX or with fonts.
How did you install tex? You seem to be missing the cmextra fonts, but=20=
I think they are part of the base install.
Aaron
> At the end of the compilation of my file I obtain the following=20
> output, repeated several times before an almost blank pdf file is=20
> generated:
> ------------------------------
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi=20
> 600 cmex10
> /usr/local/teTeX/bin/powerpc-apple-darwin-current/mktexpk: line 1:=20
> basename: command not found
> mktexpk: /var/tmp/texfonts/pk/ljfour/public/cm/ already exists.
> /usr/local/teTeX/share/texmf/web2c/mktexupd: Missing argument(s).
> /usr/local/teTeX/share/texmf/web2c/mktexupd: line 1: basename: command=20=
> not found
> Try ` --help' for more information.
> warning: kpathsea: mktexpk output=20
> `/var/tmp/texfonts/pk/ljfour/public/cm/' instead of a filename.
> kpathsea: Appending font creation commands to missfont.log.
> )
> (see the transcript file for additional information)
> Warning: /usr/local/teTeX/bin/powerpc-apple-darwin-current/pdflatex=20
> (file cmex1
> 0): kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+57/600=20
> --dpi 657 cmmi10
> /usr/local/teTeX/bin/powerpc-apple-darwin-current/mktexpk: line 1:=20
> basename: command not found
> mktexpk: /var/tmp/texfonts/pk/ljfour/public/cm/ already exists.
> /usr/local/teTeX/share/texmf/web2c/mktexupd: Missing argument(s).
> /usr/local/teTeX/share/texmf/web2c/mktexupd: line 1: basename: command=20=
> not found
> Try ` --help' for more information.
> warning: kpathsea: mktexpk output=20
> `/var/tmp/texfonts/pk/ljfour/public/cm/' instead of a filename.
> Font cmex10 at 600 not found
> ------------------------------
> Thanks for any info to help fix this problem.
> Francois Schmitt
>
> --------------------- Info ---------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Post:
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Font problem?
From: "Herbert Schulz"
Date: Wed, 8 Jun 2005 11:35:22 -0500
On Jun 8, 2005, at 11:15 AM, Fran=E7ois G. Schmitt wrote:
> Hi,
>
> I have installed TeXShop 1.40 on a system 10.3.9 and have the =20
> following problem.
>
> Everything used to work fine, but recently I had to reinstal the =20
> system, and then I reinstalled TeXShop and all the indicated =20
> files. And now it refuses to work, for an unknown reason. The =20
> problem does not seem to be linked to TeXShop since IteXMac gives =20
> the same result: the problem seems to be with TeTeX or with fonts.
> At the end of the compilation of my file I obtain the following =20
> output, repeated several times before an almost blank pdf file is =20
> generated:
> ------------------------------
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi =20=
> 600 cmex10
> ...
Howdy,
How did you re-install ``all the indicated files''? Was it via i-=20
installer or directly from teTeX/TeXLive? It looks like the system is =20=
not finding the Computer Modern .pfb files. That could just be that =20
you need to run `sudo texhash' in Terminal or maybe worse.
Good Luck,
Herb Schulz
(herbs@wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] [ANN] BibDesk 1.1
From: "Adam Maxwell"
Date: Wed, 08 Jun 2005 09:40:38 -0700
On Wednesday, June 08, 2005, at 09:05AM, Michael S. Hanson =
wrote:
>
>On Jun 8, 2005, at 1:07 AM, Adam R.Maxwell wrote:
>
>> The BibDesk development team is pleased to announce that version 1.1
>> is available for download at .
>>
>> Any problems should be reported on the SourceForge Tracker at
>> .
>
> For some reason I cannot get through to the above link, so I'm
>reporting my problems with version 1.1 below. Note that v1.0 seems to
>work fine, and I have rolled back to that version for now.
Yes, this is a known problem; the new Xcode release must have broken =
something. Apparently BibDesk 1.1 works fine on 10.3.9, but is broken on =
10.3.8 and 10.2.x. Sorry, I'll try to rebuild it tonight, but I no longer =
have a pre-10.3.9 Panther install around to test against, and testing =
against Jaguar is such a hassle that I only do it if there's a Jaguar-only =
bug.
Previous versions are always available from the project page at =
.
Adam
>
>Copied from the crash reporter:
>
>> Date/Time: 2005-06-08 11:56:09 -0400
>> OS Version: 10.3.8 (Build 7U16)
>> Report Version: 2
>>
>> Command: BibDesk
>> Path: /Applications/BibDesk.app/Contents/MacOS/BibDesk
>> Version: ??? (???)
>> PID: 1124
>> Thread: Unknown
>>
>> Link (dyld) error:
>>
>> dyld: /Applications/BibDesk.app/Contents/MacOS/BibDesk can't open
>> library: /usr/lib/libgcc_s.1.dylib (No such file or directory, errno
>> =3D 2)
>
> Thanks in advance for addressing this issue.
>
> -- Mike
>
>--------------------- Info ---------------------
>Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
>TeX FAQ: http://www.tex.ac.uk/faq
>List Post:
>
>
>
>
----------------------------------------------------------------------
Subject: customizing menu shortcut keys in TeXShop
From: "Charles Chapman Pugh"
Date: Wed, 8 Jun 2005 11:01:50 -0700
Hello.
In the help files for TeXShop 2.03, there are directions for
customizing the menu shortcut keys. You go the file
KeyEquivalents.plist whose location is
~/Library/TeXShop/Menus/KeyEquivalents.plist
and then you modify it, save the result, and that should do it. An
example is given in the KeyEquivalents.plist file, which is indeed
located as it should be. The example is commented out because it is
a "crazy redefinition," which among other things removes the keyboard
command Apple-W from the close operation in the file menu.
Well, after trying to emulate the example file, I got no change in
the menus or shortcuts, so, as an experiment, I duplicated the crazy
part and removed its commenting-out brackets, saved the result, quit
TexShop for good measure, started it back up, opened a file, and the
menus were unchanged. Apple-W still closed things up.
What am I missing?
Best, Charles Pugh
Here is what the KeyEquivalents.plist file looks like after the
changes I made.
-->
10
Edit
Find
1
u
4
Comment
X
Indent
Z
Uncomment
y
Unindent
w
-->
File
6
10
Edit
Find
1
u
4
Comment
X
Indent
Z
Uncomment
y
Unindent
w
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Herbert Schulz"
Date: Wed, 8 Jun 2005 13:31:34 -0500
On Jun 8, 2005, at 1:01 PM, Charles Chapman Pugh wrote:
> Hello.
>
> In the help files for TeXShop 2.03, there are directions for
> customizing the menu shortcut keys. You go the file
> KeyEquivalents.plist whose location is
>
> ~/Library/TeXShop/Menus/KeyEquivalents.plist
>
>
> and then you modify it, save the result, and that should do it. An
> example is given in the KeyEquivalents.plist file, which is indeed
> located as it should be. The example is commented out because it
> is a "crazy redefinition," which among other things removes the
> keyboard command Apple-W from the close operation in the file menu.
>
> Well, after trying to emulate the example file, I got no change in
> the menus or shortcuts, so, as an experiment, I duplicated the
> crazy part and removed its commenting-out brackets, saved the
> result, quit TexShop for good measure, started it back up, opened a
> file, and the menus were unchanged. Apple-W still closed things up.
>
> What am I missing?
>
> Best, Charles Pugh
> ...
Howdy,
Hmmm... When I try to open that default (original) .plist file in my
plist editor (PlistEdit Pro - a very nice reliable application that
does binary as well as text plists) I get an error:
There was an error reading the property list file (The file /Users/
herbs/Library/TeXShop/Menus/KeyEquivalents.plist could not be opened
because an error occurred parsing the file.
XML parser error:
Encountered unexpected character - on line 56
Old-style plist parser error:
Malformed data byte group at line 1; invalid hex
).
So it looks as though there is a problem with the plist xml although
I don't know what it is.
Good Luck,
Herb Schulz
(herbs@wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Johan Almqvist"
Date: Wed, 8 Jun 2005 20:47:09 +0200
On Jun 8, 2005, at 20:31, Herbert Schulz wrote:
> On Jun 8, 2005, at 1:01 PM, Charles Chapman Pugh wrote:
>> In the help files for TeXShop 2.03, there are directions for
>> customizing the menu shortcut keys. You go the file
>> KeyEquivalents.plist whose location is
>>
>> ~/Library/TeXShop/Menus/KeyEquivalents.plist
>>
>>
>> and then you modify it, save the result, and that should do it.
>> An example is given in the KeyEquivalents.plist file, which is
>> indeed located as it should be. The example is commented out
>> because it is a "crazy redefinition," which among other things
>> removes the keyboard command Apple-W from the close operation in
>> the file menu.
>>
>> Well, after trying to emulate the example file, I got no change in
>> the menus or shortcuts, so, as an experiment, I duplicated the
>> crazy part and removed its commenting-out brackets, saved the
>> result, quit TexShop for good measure, started it back up, opened
>> a file, and the menus were unchanged. Apple-W still closed things
>> up.
>
> Hmmm... When I try to open that default (original) .plist file in
> my plist editor (PlistEdit Pro - a very nice reliable application
> that does binary as well as text plists) I get an error:
>
> There was an error reading the property list file (The file /Users/
> herbs/Library/TeXShop/Menus/KeyEquivalents.plist could not be
> opened because an error occurred parsing the file.
> XML parser error:
> Encountered unexpected character - on line 56
> Old-style plist parser error:
> Malformed data byte group at line 1; invalid hex
> ).
>
> So it looks as though there is a problem with the plist xml
> although I don't know what it is.
I don't think nested comments are allowed, so try removing the last
part of the big comment at the top:
[...]Since nobody would actually want to do this, the example is
commented out;
use it as a guide and add similar definitions which are not
bracketed inside the
comment symbols
[comment block ends here]
(The explanation of the comment symbols is probably the culprit)
-Johan
--
Johan Almqvist
johan@almqvist.net
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Chris Goedde"
Date: Wed, 8 Jun 2005 13:50:08 -0500
On Jun 8, 2005, at 1:01 PM, Charles Chapman Pugh wrote:
> Hello.
>
> In the help files for TeXShop 2.03, there are directions for
> customizing the menu shortcut keys. You go the file
> KeyEquivalents.plist whose location is
>
> ~/Library/TeXShop/Menus/KeyEquivalents.plist
>
>
> and then you modify it, save the result, and that should do it. An
> example is given in the KeyEquivalents.plist file, which is indeed
> located as it should be. The example is commented out because it is a
> "crazy redefinition," which among other things removes the keyboard
> command Apple-W from the close operation in the file menu.
>
> Well, after trying to emulate the example file, I got no change in the
> menus or shortcuts, so, as an experiment, I duplicated the crazy part
> and removed its commenting-out brackets, saved the result, quit
> TexShop for good measure, started it back up, opened a file, and the
> menus were unchanged. Apple-W still closed things up.
>
> What am I missing?
>
> Best, Charles Pugh
I've had the exact same experience in TeXShop, and a few months ago
asked the very same question on this list, with no real answer. As far
as I can tell, this feature is broken in TeXShop. Or perhaps as Herb
Schulz suggests, the xml in the default plist file is defective.
Chris Goedde
----------------------------------------------------------------------
Subject: customizing menus in TeXShop
From: "Charles Chapman Pugh"
Date: Wed, 8 Jun 2005 12:05:43 -0700
Hello.
I think the suggestion about extra uses of the commenting-out code
was the key. Removed everything enclosed in the commenting-out
brackets, and the "crazy redefinition" now works. So I'll be off to
emulationville.
Thanks, Charles Pugh
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Bob Kerstetter"
Date: Wed, 8 Jun 2005 14:10:25 -0500
If you use TextEdit or remove the comments, but leave the crazy
redefinition, the file opens in the PLIST editor and totally screws
up the TeXShop functions, from an Apple standard point of view.
Here are the contents of the file with the comments removed.
PLEASE READ THIS: I would not use these definitions since they change
Apple standards, but this shows what the file format looks like if
you want to define keyboard shortcuts.
To quote Herb Schulz: "Good Luck" :)
File
6
10
Edit
Find
1
u
4
Comment
X
Indent
Z
Uncomment
y
Unindent
w
On Jun 8, 2005, at 1:50 PM, Chris Goedde wrote:
> On Jun 8, 2005, at 1:01 PM, Charles Chapman Pugh wrote:
>
>
>> Hello.
>>
>> In the help files for TeXShop 2.03, there are directions for
>> customizing the menu shortcut keys. You go the file
>> KeyEquivalents.plist whose location is
>>
>> ~/Library/TeXShop/Menus/KeyEquivalents.plist
>>
>>
>> and then you modify it, save the result, and that should do it.
>> An example is given in the KeyEquivalents.plist file, which is
>> indeed located as it should be. The example is commented out
>> because it is a "crazy redefinition," which among other things
>> removes the keyboard command Apple-W from the close operation in
>> the file menu.
>>
>> Well, after trying to emulate the example file, I got no change in
>> the menus or shortcuts, so, as an experiment, I duplicated the
>> crazy part and removed its commenting-out brackets, saved the
>> result, quit TexShop for good measure, started it back up, opened
>> a file, and the menus were unchanged. Apple-W still closed things
>> up.
>>
>> What am I missing?
>>
>> Best, Charles Pugh
>>
>
> I've had the exact same experience in TeXShop, and a few months ago
> asked the very same question on this list, with no real answer. As
> far as I can tell, this feature is broken in TeXShop. Or perhaps as
> Herb Schulz suggests, the xml in the default plist file is defective.
>
> Chris Goedde
>
> --------------------- Info ---------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Post:
>
>
>
Bob Kerstetter
http://homepage.mac.com/bkerstetter/
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Herbert Schulz"
Date: Wed, 8 Jun 2005 14:11:40 -0500
On Jun 8, 2005, at 1:47 PM, Johan Almqvist wrote:
>
> I don't think nested comments are allowed, so try removing the last
> part of the big comment at the top:
>
> [...]Since nobody would actually want to do this, the example is
> commented out;
> use it as a guide and add similar definitions which are not
> bracketed inside the
> comment symbols
> [comment block ends here]
>
> (The explanation of the comment symbols is probably the culprit)
>
> -Johan
>
Howdy,
I tried to delete that nested comment and there still is a problem.
You might get rid of all of the comments that appear before the
actual code you wish to be read. You can always re-generate the
original (faulty) plist file by simply running TeXShop after removing
what you have from that folder.
I'm sure it will always take a restart of TeXShop to re-bind the
keyboard if it is working at all.
Good Luck,
Herb Schulz
(herbs@wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Herbert Schulz"
Date: Wed, 8 Jun 2005 14:18:39 -0500
On Jun 8, 2005, at 2:10 PM, Bob Kerstetter wrote:
> If you use TextEdit or remove the comments, but leave the crazy
> redefinition, the file opens in the PLIST editor and totally screws
> up the TeXShop functions, from an Apple standard point of view.
> ...
Howdy,
Yep... I tried it too and it worked; i.e., Cmd-W was gone, etc. Then
I just threw out that mess, restarted TeXShop and got the default
(faulty) .plist file back.
Now you're free to mess any keybindings up (and even recover)
although you may not be very happy with the results.
Good Luck,
Herb Schulz
(herbs@wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Font problem?
From: "Peter Dyballa"
Date: Wed, 8 Jun 2005 21:30:53 +0200
Am 08.06.2005 um 18:15 schrieb Fran=E7ois G. Schmitt:
> /usr/local/teTeX/bin/powerpc-apple-darwin-current/mktexpk: line 1:=20
> basename: command not found
>
This looks very bad! The command `basename=B4 is usually found in=20
/usr/bin. I think you need to fix your ~/.MacOSX/environment.plist and=20=
your environment. Could you check ~/.MacOSX/environment.plist and open=20=
Terminal and invoke there 'env | grep -i path'?
But the actual problem is that TeX thinks you haven't installed the PS=20=
versions of Computer Modern fonts, so it tries to create the PK fonts=20
at the right size.
So solve this: what is 'updmap --listmaps' showing in Terminal?
--
Greetings
Pete
Government is actually the worst failure of civilized man. There has
never been a really good one, and even those that are most tolerable
are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Bob Kerstetter"
Date: Wed, 8 Jun 2005 14:34:37 -0500
On Jun 8, 2005, at 2:18 PM, Herbert Schulz wrote:
> Now you're free to mess any keybindings up (and even recover)
> although you may not be very happy with the results.
Well, the cool thing is this: if you delete KeyEquivalents.plist,
TeXShop rebuilds it, including the villainous comments, on its next
startup.
Bob Kerstetter
http://homepage.mac.com/bkerstetter/
----------------------------------------------------------------------
Subject: Re: [OS X TeX] customizing menu shortcut keys in TeXShop
From: "Bob Kerstetter"
Date: Wed, 8 Jun 2005 14:36:18 -0500
Aaaah. I read your note too quickly. You had already noted the re-
creation of the file.
On Jun 8, 2005, at 2:34 PM, Bob Kerstetter wrote:
>
> On Jun 8, 2005, at 2:18 PM, Herbert Schulz wrote:
>
>
>> Now you're free to mess any keybindings up (and even recover)
>> although you may not be very happy with the results.
>>
>
> Well, the cool thing is this: if you delete KeyEquivalents.plist,
> TeXShop rebuilds it, including the villainous comments, on its next
> startup.
>
> Bob Kerstetter
> http://homepage.mac.com/bkerstetter/
>
> --------------------- Info ---------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Post:
>
>
>
Bob Kerstetter
http://homepage.mac.com/bkerstetter/
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Maarten Sneep"
Date: Wed, 8 Jun 2005 22:09:51 +0200
On 8 Jun 2005, at 12:25, Gerben Wierda wrote:
>> ...and so the question, for those who know best, will the transition
>> from PowerPC to Intel be painless, as far as TeX (and all the related
>> apps that we so cherish) is concerned?
>
> Regarding the backend most people use on Mac OS X: I have already a
> report
> that TeX Live compiles fine on an Intellimac.
I would expect the 'Intellimac' (first time I hear this name) to be
the same as Darwin/x86, which itself is not dissimilar from FreeBSD/
x86. The latter certainly has TeX running (... checks on shell
servers owned by his ISP, whoops, it's there, but it is _old_), and I
guess someone has TeXLive compiled on Darwin (eithe PPC or x86). I'd
be very surprised if it didn't compile.
> In howfar i-Installer is
> portable I do not know yet (because that depends in howfar Apple
> has good
> ports for the Mac OS X 10.2 frameworks i-Installer uses) but
> normally it
> should just work.
>
> What might happen is that I have to drop support for Mac OS X 10.2
> accross
> the board. Dropping 10.2 might enable me to support autehticating
> proxies
> etc, so it is also a potential good thing.
Don't forget that the intellimac is still one to two years into the
future. 10.2 will be four to five years old by then, which should
mean the number of users depending on 10.2 is reduced even further.
> I am likely going to work on getting Apple to produce an improved
> Installer engine for 10.5 Leopard, so what might happen is that
> i-Installer would disappear entirely and be replaced by Apple's own.
> (Here's to hoping that is going to happen)
(Cheers!)
> Relax all, we have a year of hammering this out before the first
> systems
> are out there.
Agreed. And with software such as TeX, that has been ported a the
number of systems that can only be described as 'staggering', I don't
think there is any reason to worry.
Maarten
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "mark oilcan"
Date: Wed, 8 Jun 2005 14:57:06 -0700 (PDT)
--- Maarten Sneep wrote:
> On 8 Jun 2005, at 12:25, Gerben Wierda wrote:
>=20
> >> ...and so the question, for those who know best, will the
> transition
> >> from PowerPC to Intel be painless, as far as TeX (and all the
> related
> >> apps that we so cherish) is concerned?
> >
> > Regarding the backend most people use on Mac OS X: I have already a
> =20
> > report
> > that TeX Live compiles fine on an Intellimac.
>=20
> I would expect the 'Intellimac' (first time I hear this name) to be =20
Personally, I would prefer Macintel as I don't particularly see any
reason to associate the word "intelligent" with a Mac using an Intel
cpu. Not that it's a big deal or anything....
Mark A
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around=20
http://mail.yahoo.com=20
----------------------------------------------------------------------
Subject: Re: [OS X TeX] PPC to Intel
From: "Bob Kerstetter"
Date: Wed, 8 Jun 2005 17:40:05 -0500
On Jun 8, 2005, at 4:57 PM, mark oilcan wrote:
>
>
> --- Maarten Sneep wrote:
>
>
>> On 8 Jun 2005, at 12:25, Gerben Wierda wrote:
>>
>>
>>>> ...and so the question, for those who know best, will the
>>>>
>> transition
>>
>>>> from PowerPC to Intel be painless, as far as TeX (and all the
>>>>
>> related
>>
>>>> apps that we so cherish) is concerned?
>>>>
>>>
>>> Regarding the backend most people use on Mac OS X: I have already a
>>>
>>
>>
>>> report
>>> that TeX Live compiles fine on an Intellimac.
>>>
>>
>> I would expect the 'Intellimac' (first time I hear this name) to be
>>
>
> Personally, I would prefer Macintel as I don't particularly see any
> reason to associate the word "intelligent" with a Mac using an Intel
> cpu. Not that it's a big deal or anything....
I was pretty impressed with the "little boy-ish" attitude of the
Intel CEO during the WWDC keynote. He seemed genuinely excited about
this. Intel is possibly looking forward to working with a fun
company. MS and Dell are okay, but they are also business-grey-
boring. Apple is business-color-cool.
I don't know, but maybe Intel is pushing the envelope and maybe IBM
has lost its edge. I used to work for IBM. At the time (1980-89) a
lot of the staff were star trek-ish futuristic smart---I mean one of
my colleagues programmed the fuel flow simulator for the Saturn V in
assembly language and fortran---and it was not unusual to work with
this caliber of people in both hardware and software. I get the
impression that is not the case any longer. They appear to be
becoming sort of a software service company. I really don't know what
happens at IBM these days when it comes to hardware development, but
Apple is obviously not impressed.
Bob Kerstetter
http://homepage.mac.com/bkerstetter/
----------------------------------------------------------------------
End of MacOSX-TeX Digest
--------------------- Info ---------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
& FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Post: