From Peter_Dyballa at Web.DE Thu Jan 5 22:05:10 2006 From: Peter_Dyballa at Web.DE (Peter Dyballa) Date: Thu, 5 Jan 2006 14:05:10 +0100 Subject: [macemacsjp-english 422] System/Library/Printers/Libraries/convert Message-ID: <7E71C250-B47F-4FCA-9318-6AEEE822E3C8@Web.DE> Hello! I was looking a bit closer on that programme to find out why it failed for so many of my text files. And the answer is: it can only handle MacRoman plain text input! Brain damaged? is an exquisite trade mark. OK, it's really not easy to distinguish between the hundred or more 7 and 8 bit text encodings, but UTF-8 is a very fine input encoding which probably (I actually have no proof for this) has every 7 or 8 bit encoding incorporated as some subset. So it is a promising text input format. Should we create some bug reports that convert cannot convert ISO Latin or UTF-8 encoded texts? We must mention then the Apple Scripts / Library/Scripts/Printing\ Scripts/Convert\ To\ PDF.scpt /Library/ Scripts/Printing\ Scripts/Convert\ To\ PostScript.scpt as sources ... One work-around would be to retrieve from Emacs the buffer's or selection's text encoding and use iconv in a *lossy* way to convert to MacRoman: iconv -c -f ?from actual encoding? -t MACROMAN ?buffer or selection? > /tmp/`id -u`/tmp.out /System/Library/Printers/Libraries/convert -f /tmp/`id -u`/tmp.out - i text/plain -j application/pdf -P ?path to PPD file? | lpr [-P?set default printer?] rm /tmp/`id -u`/tmp.out iconv *has* to work lossy, otherwise it would not produce any output. iconv has to be lossy because MacRoman contains so many useless mathematical characters, quotation and diacritical marks, that you lose anyway some characters when coming from ISO Latin encodings. The other and better work-around is to htmlize in Emacs first and then invoke convert (the Aquamacs Emacs way): /System/Library/Printers/Libraries/convert -f /tmp/`id -u`/ htmlize.out -i text/html -j application/pdf -P ?path to PPD file? | lpr [-P?set default printer?] rm tmp/`id -u`/htmlize.out (A bit weird is that convert seems to fail when the file names are not enclosed inside double quotation marks. Anyone else found that?) I'm again (still!) astonished how well htmlize.el works! Is there really any reason *not* to make HTML the standard output format before sending it to the printer? (It might be worth to have a personal style sheet made up from some user specific system and Emacs defaults like font and font size, font colours, background ... and, damned, it's too early to write: next year!) Anyway: anyone experienced in MS Losedows?! Before I die I wish to get experienced and my own brain damaged. -- Greetings Pete "Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration." -Donald Knuth From david.reitter at gmail.com Thu Jan 5 22:12:24 2006 From: david.reitter at gmail.com (David Reitter) Date: Thu, 5 Jan 2006 13:12:24 +0000 Subject: [macemacsjp-english 423] Re: System/Library/Printers/Libraries/convert In-Reply-To: <7E71C250-B47F-4FCA-9318-6AEEE822E3C8@Web.DE> References: <7E71C250-B47F-4FCA-9318-6AEEE822E3C8@Web.DE> Message-ID: <0CBCCBD4-79C4-4DAC-8A0D-00CE94AF9D39@gmail.com> On 5 Jan 2006, at 13:05, Peter Dyballa wrote: > > I'm again (still!) astonished how well htmlize.el works! Is there > really any reason *not* to make HTML the standard output format > before sending it to the printer? (It might be worth to have a > personal style sheet made up from some user specific system and Emacs > defaults like font and font size, font colours, background ... and, > damned, it's too early to write: next year!) Note that I have extended htmlize in Aquamacs to support fonts and choose an appropriate font size. So if you want to reproduce this outside out Aquamacs, better grab the htmlize from the source. We should probably limit our efforts on printing since we have a viable solution in Aquamacs right now, and a viable solution via Ghostscript and the preview package in Carbon Emacs Package. The ultimate solution will use the proper system APIs, and that will be easiest once the Cocoa port is stable and integrated with Emacs 23. -- D From hduan at ucsd.edu Sat Jan 7 04:16:06 2006 From: hduan at ucsd.edu (Huaiyu Duan) Date: Fri, 6 Jan 2006 11:16:06 -0800 Subject: [macemacsjp-english 424] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> Message-ID: <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> Hi, I'm just wondering when the option to disable anti-aliasing will be restored. I'm still using the 205-10-09 version. The most import thing about emacs, in my mind, is that it is a good editor, although other fancy stuff could be useful too. To be a good editor, it should display the texts in a way appealing to the user, otherwise people may not even want to look at it. -Huaiyu On Dec 10, 2005, at 2:02 PM, Huaiyu Duan wrote: > It used to work well, but now there is no way to turn off anti- > aliasing. Seiji suggested to disable font-smoothing. However, monaco > font looks terrible without smoothing. Here is an article explaining > why anti-aliasing is not a good idea for monaco font. Hope it can be > fixed in the next version. > http://daringfireball.net/2003/03/antialiasing > > -Huaiyu From Peter_Dyballa at Web.DE Sat Jan 7 09:27:10 2006 From: Peter_Dyballa at Web.DE (Peter Dyballa) Date: Sat, 7 Jan 2006 01:27:10 +0100 Subject: [macemacsjp-english 425] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> Message-ID: Am 06.01.2006 um 20:16 schrieb Huaiyu Duan: > I'm just wondering when the option to disable anti-aliasing will be > restored. I'm still using the 205-10-09 version. When I put (setq mac-allow-anti-aliasing nil) in my .emacs file the fonts look very ugly, although with sharp edges. (The same case for Aquamacs Emacs.) Or do you something different? -- Greetings Pete A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. From nandff at gmail.com Sat Jan 7 23:44:41 2006 From: nandff at gmail.com (Nozomu Ando) Date: Sat, 7 Jan 2006 23:44:41 +0900 Subject: [macemacsjp-english 426] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> Message-ID: <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> Which font do you use for ascii character? To check this, please move the cursor to the `ugly' character and type C-u C-x = If that displays -apple-monaco-medium-r-normal--12-120-72-72-m-120-iso10646-1 then put (setq mac-allow-anti-aliasing nil) in you .emacs If your font is -apple-monaco-medium-r-normal--12-120-72-72-m-120-mac-roman then put (setq mac-allow-anti-aliasing t) in you .emacs And then, with Terminal, please do % defaults write org.gnu.Emacs AppleAntiAliasingThreshold 14 and restart your Emacs. (14 is only an example. please choose your favorite threshold) I'm not sure this is a solution to your problem. Hope this helps, --- Nozomu Ando From zenitani at gmail.com Sun Jan 8 13:30:14 2006 From: zenitani at gmail.com (Seiji Zenitani) Date: Sun, 8 Jan 2006 13:30:14 +0900 Subject: [macemacsjp-english 427] Re: anti-aliasing problem still exists in the Dec '05 Message-ID: <19b4247f0601072030mb7f66d8t@mail.gmail.com> > I'm just wondering when the option to disable anti-aliasing will be > restored. I'm still using the 2005-10-09 version. I've restored the menu in our CVS code. It will be back in the next release. Note that the menu is identical to the following .emacs line: (setq mac-allow-anti-aliasing nil) as repeatedly quoted in [macemacsjp-english 401] [macemacsjp-english 425]. -- Seiji From jsmgage at mac.com Mon Jan 9 00:36:21 2006 From: jsmgage at mac.com (John Gage) Date: Sun, 8 Jan 2006 16:36:21 +0100 Subject: [macemacsjp-english 428] PSGML Message-ID: <0ABDAFC7-3FE0-4690-AE57-D57DEF617C03@mac.com> Does anyone know how to activate PSGML in the .emacs.el file? Once activated, does PSGML work in this environment? Thanking you, John Gage From hduan at ucsd.edu Mon Jan 9 03:42:11 2006 From: hduan at ucsd.edu (Huaiyu Duan) Date: Sun, 8 Jan 2006 10:42:11 -0800 Subject: [macemacsjp-english 429] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> Message-ID: <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> I tried what you have said with the 2005-12-04 version. The character coding is -apple-monaco-medium-r-normal--12-120-72-72-m-120-iso10646-1. However, the method you mentioned doesn't work well. I would like the monaco fonts to be displayed in a way as in the OSX's Terminal. They are much fuzzier in the current carbon emacs than in the Terminal. If you turn off the the font smoothing using the command you mentioned or in the System Preferences, the monaco fonts will look too thin. -Huaiyu On Jan 7, 2006, at 6:44 AM, Nozomu Ando wrote: > Which font do you use for ascii character? > To check this, please move the cursor to the `ugly' character and > type C-u C-x = > > If that displays > -apple-monaco-medium-r-normal--12-120-72-72-m-120-iso10646-1 > then put (setq mac-allow-anti-aliasing nil) in you .emacs > > If your font is > -apple-monaco-medium-r-normal--12-120-72-72-m-120-mac-roman > then put (setq mac-allow-anti-aliasing t) in you .emacs > > And then, with Terminal, please do > % defaults write org.gnu.Emacs AppleAntiAliasingThreshold 14 > and restart your Emacs. > (14 is only an example. please choose your favorite threshold) > > > I'm not sure this is a solution to your problem. > > Hope this helps, > --- > Nozomu Ando From hduan at ucsd.edu Mon Jan 9 03:47:41 2006 From: hduan at ucsd.edu (Huaiyu Duan) Date: Sun, 8 Jan 2006 10:47:41 -0800 Subject: [macemacsjp-english 430] Re: anti-aliasing problem still exists in the Dec '05 In-Reply-To: <19b4247f0601072030mb7f66d8t@mail.gmail.com> References: <19b4247f0601072030mb7f66d8t@mail.gmail.com> Message-ID: Then it probably won't work either. I don't know the details of Carbon Emacs. The apparent symptoms can be summarized as follows. The version of the last October can display the monaco fonts gracefully. The current version either display the fonts too thick if nothing is done, or too thin if smoothing threshold is raised. The variable mac- allow-anti-aliasing has no effect at all. -Huaiyu On Jan 7, 2006, at 8:30 PM, Seiji Zenitani wrote: >> > > I've restored the menu in our CVS code. It will be back in the next > release. > > > Note that the menu is identical to the following .emacs line: > > (setq mac-allow-anti-aliasing nil) > > as repeatedly quoted in [macemacsjp-english 401] [macemacsjp- > english 425]. > > > -- Seiji > > From nandff at gmail.com Mon Jan 9 04:13:29 2006 From: nandff at gmail.com (Nozomu Ando) Date: Mon, 9 Jan 2006 04:13:29 +0900 Subject: [macemacsjp-english 431] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> Message-ID: <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> Hmm... My Carbon Emacs without anti-aliasing and Terminal seems to use the same font... Are you using Terminal with anti-aliasing on? (mine is off) How about selecting fontset-mac of Emacs' font by Shift mouse-1 then select Fontset -> mac: 16-dot meduim with (setq mac-allow-anti-aliasing nil) ? From jfrederich at gmail.com Mon Jan 9 04:19:58 2006 From: jfrederich at gmail.com (Jens Frederich) Date: Sun, 8 Jan 2006 20:19:58 +0100 Subject: [macemacsjp-english 432] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> Message-ID: <9B6803A8-DDE9-4C99-9AFC-D1AB9C22A154@gmail.com> On 08.01.2006, at 20:13, Nozomu Ando wrote: > Hmm... My Carbon Emacs without anti-aliasing and Terminal seems to > use the same > font... Are you using Terminal with anti-aliasing on? (mine is off) > > How about selecting fontset-mac of Emacs' font by > Shift mouse-1 then select Fontset -> mac: 16-dot meduim > > with > (setq mac-allow-anti-aliasing nil) > doen't work !!! > ? > _______________________________________________ > macemacsjp-english mailing list > macemacsjp-english at lists.sourceforge.jp > http://lists.sourceforge.jp/mailman/listinfo/macemacsjp-english From nandff at gmail.com Mon Jan 9 04:37:23 2006 From: nandff at gmail.com (Nozomu Ando) Date: Mon, 9 Jan 2006 04:37:23 +0900 Subject: [macemacsjp-english 433] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> Message-ID: <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> Is there any your favorite in these screenshots? http://homepage.mac.com/nand/macosx/antialiasing.html From hduan at ucsd.edu Tue Jan 10 03:50:03 2006 From: hduan at ucsd.edu (Huaiyu Duan) Date: Mon, 9 Jan 2006 10:50:03 -0800 Subject: [macemacsjp-english 434] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> Message-ID: It displays well on your machine. Here are some pictures grabbed from my screen. Fuzzy: http://physics.ucsd.edu/~hduan/tmp/fuzzy.png Thin: http://physics.ucsd.edu/~hduan/tmp/thin.png Just right: http://physics.ucsd.edu/~hduan/tmp/good.png Picture of a terminal: http://physics.ucsd.edu/~hduan/tmp/term.png All the emacs sessions have set mac-allow-anti-aliasing nil. I think that I might know where the problem is. When I checked the font in the new Carbon Emacs with "C-u C-x =", it displays -apple-monaco-medium-r-normal--12-120-72-72-m-120-iso10646-1 The old one has -apple-monaco-medium-r-normal--12-120-75-75-m-120-mac-roman I use xlsfonts to check the fonts under X11. None of the fonts have resx/resy=72 except a few Chinese fonts. I'm wondering how I can force new Carbon Emacs to use resx/resy=75. -Huaiyu On Jan 8, 2006, at 11:37 AM, Nozomu Ando wrote: > Is there any your favorite in these screenshots? > > http://homepage.mac.com/nand/macosx/antialiasing.html From hduan at ucsd.edu Tue Jan 10 04:04:20 2006 From: hduan at ucsd.edu (Huaiyu Duan) Date: Mon, 9 Jan 2006 11:04:20 -0800 Subject: [macemacsjp-english 435] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> Message-ID: OK, resx/resy may not be the problem. With mac-allow-anti-aliasing set as t, the old Carbon Emacs also display fuzzy fonts, while it has no effect at all on the new ones. There got to be some change in the font display part that introduces this annoying bug. -Huaiyu On Jan 9, 2006, at 10:50 AM, Huaiyu Duan wrote: > It displays well on your machine. Here are some pictures grabbed from > my screen. > > Fuzzy: > http://physics.ucsd.edu/~hduan/tmp/fuzzy.png > > Thin: > http://physics.ucsd.edu/~hduan/tmp/thin.png > > Just right: > http://physics.ucsd.edu/~hduan/tmp/good.png > > Picture of a terminal: > http://physics.ucsd.edu/~hduan/tmp/term.png > > All the emacs sessions have set mac-allow-anti-aliasing nil. > > I think that I might know where the problem is. When I checked the > font in the new Carbon Emacs with "C-u C-x =", it displays > -apple-monaco-medium-r-normal--12-120-72-72-m-120-iso10646-1 > The old one has > -apple-monaco-medium-r-normal--12-120-75-75-m-120-mac-roman > I use xlsfonts to check the fonts under X11. None of the fonts have > resx/resy=72 except a few Chinese fonts. I'm wondering how I can > force new Carbon Emacs to use resx/resy=75. > > -Huaiyu From zenitani at gmail.com Tue Jan 10 23:44:19 2006 From: zenitani at gmail.com (Seiji Zenitani) Date: Tue, 10 Jan 2006 23:44:19 +0900 Subject: [macemacsjp-english 436] Re: PSGML In-Reply-To: <0ABDAFC7-3FE0-4690-AE57-D57DEF617C03@mac.com> References: <0ABDAFC7-3FE0-4690-AE57-D57DEF617C03@mac.com> Message-ID: <8FD5E531-EF90-447B-B57C-94A1F6B35082@gmail.com> Hi, According to the psgml's README, > Put the following line in your .emacs: > > (autoload 'sgml-mode "psgml" "Major mode to edit SGML files." t) > (autoload 'xml-mode "psgml" "Major mode to edit XML files." t) Because I'm not a psgml user, I'm not sure whether it works fine or not. -- Seiji On 2006/01/09, at 0:36, John Gage wrote: > Does anyone know how to activate PSGML in the .emacs.el file? Once > activated, does PSGML work in this environment? > > Thanking you, > > John Gage > > > _______________________________________________ > macemacsjp-english mailing list > macemacsjp-english at lists.sourceforge.jp > http://lists.sourceforge.jp/mailman/listinfo/macemacsjp-english From nandff at gmail.com Wed Jan 11 02:45:56 2006 From: nandff at gmail.com (Nozomu Ando) Date: Wed, 11 Jan 2006 02:45:56 +0900 Subject: [macemacsjp-english 437] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> Message-ID: <4e698fda0601100945v33dbe7a7n12dae5cf6cfaf8e3@mail.gmail.com> Did you try selecting fontset-mac as I mentioned before? > Shift mouse-1 then select Fontset -> mac: 16-dot meduim Its ascii font should be -apple-monaco-medium-r-normal--12-120-72-72-m-120-mac-roman It looks identical with prior version, at least for me. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.sourceforge.jp/mailman/archives/macemacsjp-english/attachments/20060111/759da668/attachment.htm From hduan at UCSD.EDU Thu Jan 12 02:12:12 2006 From: hduan at UCSD.EDU (Huaiyu Duan) Date: Wed, 11 Jan 2006 09:12:12 -0800 Subject: [macemacsjp-english 438] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <4e698fda0601100945v33dbe7a7n12dae5cf6cfaf8e3@mail.gmail.com> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> <4e698fda0601100945v33dbe7a7n12dae5cf6cfaf8e3@mail.gmail.com> Message-ID: <0115F02D-7DE0-4176-BE99-60CDEB94C99D@ucsd.edu> I tried, and it didn't work. For my case, the old version uses -apple- monaco-medium-r-normal--12-120-75-75-m-120-mac-roman, and new version uses the same font as yours. Notice the difference in resx/resy parameters which are changed from 75 to 72. -Huaiyu On Jan 10, 2006, at 9:45 AM, Nozomu Ando wrote: > Did you try selecting fontset-mac as I mentioned before? > > > Shift mouse-1 then select Fontset -> mac: 16-dot meduim > > Its ascii font should be -apple-monaco-medium-r- > normal--12-120-72-72-m-120-mac-roman > > It looks identical with prior version, at least for me. > From nandff at gmail.com Thu Jan 12 22:05:32 2006 From: nandff at gmail.com (Nozomu Ando) Date: Thu, 12 Jan 2006 22:05:32 +0900 Subject: [macemacsjp-english 439] Re: anti-aliasing problem still exists in the Dec '05 version In-Reply-To: <0115F02D-7DE0-4176-BE99-60CDEB94C99D@ucsd.edu> References: <10C46461-2643-45EA-BABE-DD3DB85E29A5@ucsd.edu> <37EB16B1-3055-475E-9298-1CE7200FF40C@ucsd.edu> <4e698fda0601070644m3d181662ie44e45dcb0b34fab@mail.gmail.com> <91A210F3-FC3F-49BC-87E7-D8652FA3234E@ucsd.edu> <4e698fda0601081113w43697ef8u1a7209370bcddd6a@mail.gmail.com> <4e698fda0601081137q71c85e36xc85a781a586e833d@mail.gmail.com> <4e698fda0601100945v33dbe7a7n12dae5cf6cfaf8e3@mail.gmail.com> <0115F02D-7DE0-4176-BE99-60CDEB94C99D@ucsd.edu> Message-ID: <4e698fda0601120505g35d4306ft932e13c44b513666@mail.gmail.com> The font rendering code of CVS HEAD have been changed. Your problem might be fixed in the next Zenitani-san's distribution. (But I'm not sure because I can not reproduce your problem.) Regards, Nozomu Ando -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.sourceforge.jp/mailman/archives/macemacsjp-english/attachments/20060112/27ac192a/attachment.htm From gnn at neville-neil.com Sat Jan 14 12:10:25 2006 From: gnn at neville-neil.com (George V. Neville-Neil) Date: Sat, 14 Jan 2006 11:10:25 +0800 Subject: [macemacsjp-english 440] Control-g (keyboard-quit) is not heard by carbon emacs under load Message-ID: Hi, I've been having a problem where if a network connection or some long running process in Carbon Emacs gets stuck I get the spinning color wheel but cannot get Emacs to respond to keyboard quit (aka control-g). If Carbon Emacs has not run away but is just mildly busy then keyboard-quit works. Is this a known issue? I ahve not seen anything in the FAQ or the mail archives on this. This most often happens with stale IMAP connections (those that are messed up by a NAT gateway closing the port) in wanderlust. Thanks, George From j.m.figueroa at ed.ac.uk Sat Jan 14 21:10:44 2006 From: j.m.figueroa at ed.ac.uk (Jose Figueroa-O'Farrill) Date: Sat, 14 Jan 2006 12:10:44 +0000 Subject: [macemacsjp-english 441] Control-g (keyboard-quit) is not heard by carbon emacs under load In-Reply-To: References: Message-ID: <17352.59972.580156.24246@castalia.local> >>>>> "George" == George V Neville-Neil writes: George> Hi, George> I've been having a problem where if a network connection or some long George> running process in Carbon Emacs gets stuck I get the spinning color George> wheel but cannot get Emacs to respond to keyboard quit (aka George> control-g). If Carbon Emacs has not run away but is just mildly busy George> then keyboard-quit works. Is this a known issue? I ahve not seen George> anything in the FAQ or the mail archives on this. This most often George> happens with stale IMAP connections (those that are messed up by a NAT George> gateway closing the port) in wanderlust. I have experienced the very same problem (in my case with VM) both in Carbon Emacs and on Aquamacs. I'd love to be able to solve it. Jos? From alex at gnu.org Sun Jan 15 22:59:22 2006 From: alex at gnu.org (Alex Schroeder) Date: Sun, 15 Jan 2006 14:59:22 +0100 Subject: [macemacsjp-english 442] Compiling Emacs Message-ID: This is a question unrelated to the precompiled binaries. I'm on Mac OS 10.3.9 and want to compile emacs from CVS myself. make clean ./configure --with-carbon --with-carbon-app make bootstrap But I get undefined symbols at the end: ld: warning suggest use of -bind_at_load, as lazy binding may result in errors or different symbols being used symbol _acosl used from dynamic library /usr/lib/libstdc++.6.dylib(single module) not from earlier dynamic library /usr/lib/libSystem.B.dylib(ld64.o) symbol _tanl used from dynamic library /usr/lib/libstdc++.6.dylib(single module) not from earlier dynamic library /usr/lib/libSystem.B.dylib(ld64.o) (many more) ld: Undefined symbols: _HICopyAccessibilityActionDescription referenced from QuickTime expected to be defined in Carbon _HICopyAccessibilityRoleDescription referenced from QuickTime expected to be defined in Carbon _LLCStyleInfoCheckForOpenTypeTables referenced from QuickTime expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuickTime expected to be defined in ApplicationServices What am I missing? Alex. -- http://www.emacswiki.org/alex/ From Peter_Dyballa at Web.DE Sun Jan 15 23:31:44 2006 From: Peter_Dyballa at Web.DE (Peter Dyballa) Date: Sun, 15 Jan 2006 15:31:44 +0100 Subject: [macemacsjp-english 443] Re: Compiling Emacs In-Reply-To: References: Message-ID: Am 15.01.2006 um 14:59 schrieb Alex Schroeder: > What am I missing? Isn't there a subdirectory mac with a shell script make-package? That's the proper way ... besides the README and INSTALL files. The Japanese Carbon Emacs uses a Makefile that probably even manages to configure. (I didn't look so deep into it, but what would the Makefile be worth when it would be overwritten by configure?) -- Mit friedvollen Gr??en Pete Stau ist nur hinten bl?d, vorne geht's! From zenitani at mac.com Mon Jan 16 02:34:21 2006 From: zenitani at mac.com (Zenitani Seiji) Date: Mon, 16 Jan 2006 02:34:21 +0900 Subject: [macemacsjp-english 444] Re: Compiling Emacs In-Reply-To: References: Message-ID: <10559335.1137346461310.JavaMail.zenitani@mac.com> On 2006.01.15, at 23:00, Alex Schroeder wrote: >This is a question unrelated to the precompiled binaries. I'm >on Mac OS 10.3.9 and want to compile emacs from CVS myself. > >make clean >./configure --with-carbon --with-carbon-app >make bootstrap > I use the below options in the makefile. Nothing special. ./configure \ --prefix=/Applications/Emacs.app/Contents/Resources \ --with-carbon --without-x ; \ make bootstrap How about trying with the latest XCode (2.2)? -- Seiji From alex at gnu.org Mon Jan 16 07:16:39 2006 From: alex at gnu.org (Alex Schroeder) Date: Sun, 15 Jan 2006 23:16:39 +0100 Subject: [macemacsjp-english 445] Re: Compiling Emacs In-Reply-To: <10559335.1137346461310.JavaMail.zenitani@mac.com> (message from Zenitani Seiji on Mon, 16 Jan 2006 02:34:21 +0900) References: <10559335.1137346461310.JavaMail.zenitani@mac.com> Message-ID: > How about trying with the latest XCode (2.2)? I'm glad to see that I don't need any of the special stuff -- a simple ./configure call with the correct parameters in the top level directory is enough. As for the "latest" XCode -- I don't know what XCode I have. As I said in my first mail, I use Panther (10.3.9). The web page says: "Xcode 2.2 will run on Mac OS X 10.4 (Tiger) on a Macintosh with either a PowerPC or an Intel processor. It will not install or run on earlier versions of Mac OS X." I think I'm stuck with Version 1.5. (Actually I don't know how to check what version I have; I've found the installer for 1.5 in my Applications directory, to be honest.) Oh well. Since I'm only doing minor checks (I'm working on Rmail), I will try to build an Emacs for X11 instead. That should be enough for the testing I have in mind. :) Alex. -- http://www.emacswiki.org/alex/ From zenitani at mac.com Tue Jan 31 19:48:54 2006 From: zenitani at mac.com (Seiji Zenitani) Date: Tue, 31 Jan 2006 19:48:54 +0900 Subject: [macemacsjp-english 446] Carbon Emacs for Intel Mac Message-ID: Hi, Carbon Emacs for Intel Mac is contributed by an anonymous programmer. Take a look at it. http://macemacsjp.sourceforge.jp/package/ If it works fine, I'll put it to my web page. -- Seiji