mac-emacs-users Mailing List for Emacs for Mac OS 8/9 (Page 3)
Brought to you by:
akochoi
Menu
▾
▴
mac-emacs-users
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
(3) |
May
(2) |
Jun
(1) |
Jul
(9) |
Aug
(1) |
Sep
(2) |
Oct
(3) |
Nov
(1) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
(3) |
Apr
(5) |
May
(1) |
Jun
|
Jul
(7) |
Aug
|
Sep
(8) |
Oct
(9) |
Nov
(20) |
Dec
(25) |
| 2002 |
Jan
(11) |
Feb
(8) |
Mar
(16) |
Apr
(33) |
May
(56) |
Jun
(55) |
Jul
(16) |
Aug
(26) |
Sep
|
Oct
(19) |
Nov
(3) |
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(7) |
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Nozomu A. <na...@ma...> - 2002-08-08 02:30:30
|
Hello, On Wednesday, August 7, 2002, at 10:19 PM, Peter Ilberg wrote: > I'm having trouble running gnu-prolog in inferior-prolog-mode. > It seems to work except that I'm not getting a prompt in > emacs 21.3.50. It works in "terminal" emacs that comes with > OS X 10.1.4/5. I tried "run-prolog" and got a prompt. It seems fine for me. Please try (setq process-connection-type t) in your .emacs. I'm not sure this fix your problem because its default value changed to be "t" on the CVS repository since 2002/06/29. BUT when process-connection-type is t, we do not sometimes get right result from sub-process (the final parts of the output of the subprocess may be lost -- This is pseudo-tty problem). e.g. auctex, M-x grep. On the other hand, when process-connection-type is nil, some interactive subprocess cannot work as we expected (but it's not a bug). e.g. job-control is disabled in shell-mode (M-x shell / tcsh), no prompt in inferior-prolog-mode. To fix pseudo-tty problem, I am trying to find workaround for the bug of the pseudo-tty on MacOSX in vain. Anyone have a suggestion? Regards, --- Nozomu Ando |
|
From: William M. <mcc...@ea...> - 2002-08-07 21:37:20
|
In addition to the problem every one else describes, which I fixed by downloading emacs from cvs and recompiling, I have another new problem: my auctex command to bring up an xdvi window after texing a file no longer works. It claims to run xdvi, but the window never appears. My command includes the -sourceposition option (to make xdvi go to the place in the dvi file corresponding to the current cursor position in the emacs file). If I eliminate that option, then the problem goes away; the xdvi window appears as usual. Stranger, if I subsequently, in the same session, ask emacs to execute the original command with -sourceposition, it asks me if I want to kill the current xdvi, and then the original command miraculously starts working again. Regards, Bill McCallum |
|
From: Jeffrey P. <tha...@te...> - 2002-08-07 21:22:45
|
> Heya ppl! > > > I'm having a bit of trouble and was hoping someone could point me in > the right direction to go track it down meself. > > I pulled the cvs current a couple days ago, configured, built & > installed the code, but execution give me the very descriptive error > "Fatal error (6).Abort". I started having Emacs crash on me on startup (if I run from the command line, I get a Fatal Error - illegal instruction). I don't think anything in the application changed, so it might have been some security update from Apple or something. I re-downloaded the source, built it over again from scratch, and it seems to work now... You might try building again... -Jeffrey |
|
From: Michael P. W. <mpw...@ea...> - 2002-08-07 21:21:00
|
This is getting interesting :) Glad I said something. At 3:15 PM -0600 8/7/02, Andrew Choi wrote: > > [...] WRT, the security update, I think the problem might be in the >> whole unexec process. That is where a preliminary emacs (just >> compiled C code) reads in a bunch of lisp and then spits itself out >> as an executable (so I doesn't take too long to load up). I have >> found that when I try to run update_prebinding, it complains that it >> cannot update Emacs. Since update_prebinding is what the installer >> does when it says "Optimizing" I assumed that unexec might not be >> spitting out the right prebinding. However, older versions of emacs >> I had lying around seemed to still work after the update so I could >> be barking up the wrong tree. >> >> Maybe the author of the unexmacosx.c code has an idea? >> >> -Steven > >Hi Steven, > >I wrote unexmacosx.c but I don't know if the problem originated there. > >When I installed the Security Update, I didn't notice it running >update_prebinding! That would certainly cause the problem, because it >seems to change a few libraries. > >If other people experience the same problem, perhaps they can try >running > > update_prebinding -root / > >manually. Otherwise, rebuilding Emacs will certainly make it work >again. > >Andrew. > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Mac-emacs-users mailing list >Mac...@li... >https://lists.sourceforge.net/lists/listinfo/mac-emacs-users -- http://radio.weblogs.com/0108194/ |
|
From: Andrew C. <ak...@sh...> - 2002-08-07 21:15:29
|
> [...] WRT, the security update, I think the problem might be in the > whole unexec process. That is where a preliminary emacs (just > compiled C code) reads in a bunch of lisp and then spits itself out > as an executable (so I doesn't take too long to load up). I have > found that when I try to run update_prebinding, it complains that it > cannot update Emacs. Since update_prebinding is what the installer > does when it says "Optimizing" I assumed that unexec might not be > spitting out the right prebinding. However, older versions of emacs > I had lying around seemed to still work after the update so I could > be barking up the wrong tree. > > Maybe the author of the unexmacosx.c code has an idea? > > -Steven Hi Steven, I wrote unexmacosx.c but I don't know if the problem originated there. When I installed the Security Update, I didn't notice it running update_prebinding! That would certainly cause the problem, because it seems to change a few libraries. If other people experience the same problem, perhaps they can try running update_prebinding -root / manually. Otherwise, rebuilding Emacs will certainly make it work again. Andrew. |
|
From: Steven T. <ste...@ma...> - 2002-08-07 20:19:44
|
I hit the exact same problem. After the security update I had to recompile from scratch or else I got Fatal Error (10). I assumed -nw was the problem (probably falsely), but hopefully the patch I posted to the mac-emacs-devel list will fix that. WRT, the security update, I think the problem might be in the whole unexec process. That is where a preliminary emacs (just compiled C code) reads in a bunch of lisp and then spits itself out as an executable (so I doesn't take too long to load up). I have found that when I try to run update_prebinding, it complains that it cannot update Emacs. Since update_prebinding is what the installer does when it says "Optimizing" I assumed that unexec might not be spitting out the right prebinding. However, older versions of emacs I had lying around seemed to still work after the update so I could be barking up the wrong tree. Maybe the author of the unexmacosx.c code has an idea? -Steven On Wednesday, August 7, 2002, at 01:00 PM, Amos wrote: >>>>>> On Wed, 7 Aug 2002 13:42:51 -0400, >>>>>> Michael P Wilson <mpw...@ea...> (mpw) writes: > > mpw> I pulled the cvs current a couple days ago, configured, built & > mpw> installed the code, but execution give me the very descriptive > error > mpw> "Fatal error (6).Abort". > > Did you install the latest Mac OS X security update since the CVS > build? I noticed something quite similar after installing that OS > X update. My guess at the time was that Emacs didn't care for the > change in libraries. So I figured it was time to suck down another > CVS update and redo the build. Things have been peachy since.... > > -- > Amos > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Mac-emacs-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mac-emacs-users |
|
From: Michael P. W. <mpw...@ea...> - 2002-08-07 20:09:58
|
I think Steve's response has got it nailed. I wasn't executing with "-nw". The last update I pulled for OSX was a few days before anyway. Sure does sound like the type of thing emacs would bellyache over ;) At 3:00 PM -0500 8/7/02, Amos wrote: > >>>>> On Wed, 7 Aug 2002 13:42:51 -0400, >>>>>> Michael P Wilson <mpw...@ea...> (mpw) writes: > >mpw> I pulled the cvs current a couple days ago, configured, built & >mpw> installed the code, but execution give me the very descriptive error >mpw> "Fatal error (6).Abort". > >Did you install the latest Mac OS X security update since the CVS >build? I noticed something quite similar after installing that OS >X update. My guess at the time was that Emacs didn't care for the >change in libraries. So I figured it was time to suck down another >CVS update and redo the build. Things have been peachy since.... > >-- >Amos > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Mac-emacs-users mailing list >Mac...@li... >https://lists.sourceforge.net/lists/listinfo/mac-emacs-users -- http://radio.weblogs.com/0108194/ |
|
From: Amos <amo...@ut...> - 2002-08-07 20:00:13
|
>>>>> On Wed, 7 Aug 2002 13:42:51 -0400, >>>>> Michael P Wilson <mpw...@ea...> (mpw) writes: mpw> I pulled the cvs current a couple days ago, configured, built & mpw> installed the code, but execution give me the very descriptive error mpw> "Fatal error (6).Abort". Did you install the latest Mac OS X security update since the CVS build? I noticed something quite similar after installing that OS X update. My guess at the time was that Emacs didn't care for the change in libraries. So I figured it was time to suck down another CVS update and redo the build. Things have been peachy since.... -- Amos |
|
From: Michael P. W. <mpw...@ea...> - 2002-08-07 17:44:04
|
Heya ppl! I'm having a bit of trouble and was hoping someone could point me in the right direction to go track it down meself. I pulled the cvs current a couple days ago, configured, built & installed the code, but execution give me the very descriptive error "Fatal error (6).Abort". Is there a com-line option to do some kind of full trace on startup that I can pipe off to a file to figure out what's going on? I'm pretty used to posix-based systems, but OS-X is different enough in some strange places that it's throwing me for a loop. TIA, Mike Point me to TFM that I may R it. -- http://radio.weblogs.com/0108194/ |
|
From: Peter I. <pet...@ni...> - 2002-08-07 13:19:58
|
Hello! I'm having trouble running gnu-prolog in inferior-prolog-mode. It seems to work except that I'm not getting a prompt in emacs 21.3.50. It works in "terminal" emacs that comes with OS X 10.1.4/5. This sounds quite similar to a recent post to the list from Brian Marick. He ran into the same issue with Ruby. I didn't find a solution to his problem in the mailing list archives, so I was wondering if this has been resolved offline? I've downloaded/compiled emacs-21.3.50 from savannah.gnu.org, and gprolog-1.2.13 from gprolog.inria.fr. In order to get the environment variables I've set up an applescript that runs a shell script which in turn launches Emacs.app from tcsh. This way I can launch emacs from the dock and have the correct (tcsh) environment variables. I've also setq prolog-program-name to "gprolog" which is in the path. When I M-x run-prolog in emacs-21.3.50 the subprocess is (apparently) launched correctly and prints its banner info but no prompt. It's waiting for input however. If I type append([1,2,3],[4,5],X). the result appears but, again, not prompt. This works fine using the "terminal" emacs that comes with OS X (20.7 I believe). I've also had the same problem with free_bp199, another prolog system, before replacing it with gprolog hoping that it would fix the problem. Thanks in advance, Peter -- Peter Ilberg <pet...@ni...> |
|
From: Andrew C. <ak...@sh...> - 2002-08-04 00:08:37
|
> [...] That's as far as I can get. Why is ange-ftp not used by > default anymore? I had never looked in to how remote file editing > actually worked, it always just worked. Any ideas? Hi Clay, Tramp has been part of the CVS version for about a month now. If you follow the discussion on the emacs-devel mailing list (subscribe through http://savannah.gnu.org/projects/emacs/), you will notice that there are still some bugs to be ironed out for it. Changes to it are committed to the CVS as recently as today. I've been able to use the latest version (18:00 mountain time, August 3) with some success but there still seem to be some bugs. If this feature is important to you, please contribute by testing the new code and sending bug reports to emacs-devel. I believe there is also a list specifically for tramp (please check its web page). Also it is advisable for people who update their version from the CVS regularly to read emacs-devel to keep track of recent changes made to Emacs and its packages. Andrew. |
|
From: Clay J. <cla...@ma...> - 2002-08-03 13:36:25
|
I downloaded the source from CVS a couple of days ago, and everything went fine. My only issue is I cannot open remote files. When I try to open: /user@host:/path/to/file Emacs tries to use tramp (did it always?), and I get a 'sm' mode error. When I add the following line to my .emacs file: (setq tramp-default-method "ftp") which is supposed to forward all requests to ange-ftp, I get: symbol's value as variable is void: ange-ftp-name-format When I issue: m-x load-library and then: ange-ftp I get: Wrong type argument: stringp, (t -1 -1 -1 (0 0) (0 0) -1 "d?????????" nil ...) That's as far as I can get. Why is ange-ftp not used by default anymore? I had never looked in to how remote file editing actually worked, it always just worked. Any ideas? Thanks, Clay |
|
From: John P. W. <jp...@sh...> - 2002-07-29 01:50:41
|
Rodney Sparapani <rsp...@mc...> wrote: > cd /Users/rodney/cvs/emacs/man; makeinfo tramp.texi > tramp.texi:25: Unknown command `copying'. > tramp.texi:50: Unmatched `@end'. > makeinfo: Removing output file `../info/tramp' due to errors; use > --force to preserve. > make[1]: *** [../info/tramp] Error 2 > make: *** [info] Error 2 > > Apparently, @copying and therefore @end copying are not texinfo > commands. If you > comment these out with @c, then make install completes. They work in GNU texinfo 4.2, but not earlier versions. -- John Paul Wallington |
|
From: Gregg R. <ar...@ea...> - 2002-07-27 22:39:32
|
On Saturday, July 27, 2002, at 04:08 PM, Nozomu Ando wrote: > Do you have GNU-Fonts? > Doh! Bless you. (But in my defense, I did verify that mac-emacs picks up fonts from the standard OS X font search paths, specifically from /Users/<uid>/Library/Fonts, and that the system fonts and my private fonts have latin 1 glyphs. Emacs just refused to use them. But now I observe that glyphs for codepoints > 127 come from the gnu fonts even when I've set a mac font (try Zapfino) as the face. I.e. it looks like emacs won't use the upper half of the latin 1 glyphs from the mac fonts, substituting glyphs from the gnu fonts. Strikes me as odd; I suppose it has something to do with font encoding vectors or truetype machinations. Can anyone enlighten me as to what's happening? And esp. how to get at the full set of glyphs in the mac system fonts?) BTW, I put the gnu fonts in /Users/<myid>/Library/Font; I'd suggest a note covering this in the README. Heartfelt thanks for all the suggestions - the internet to the rescue once again! -gregg |
|
From: Nozomu A. <na...@ma...> - 2002-07-27 21:08:52
|
Hi, On Sunday, July 28, 2002, at 03:01 AM, Gregg Reynolds wrote: > Does anybody know of some kind of configuration dump that would write > out all my emacs config settings (e.g. the various faces, fontsets, > encodings, etc.) for easy comparison to a system that works? At this > point it has become clear to me that the problem must be something > completely simple and obvious, along the lines of "make sure the power > cable is plugged in" and I just can't see it. I am using emacs-21.3.50 on MacOSX 10.1.5. It can display accented characters with no "~/.emacs". But GNU-Fonts is need to be installed. Do you have GNU-Fonts? http://prdownloads.sourceforge.net/mac-emacs/GNU-Fonts.sea.bin I hope this helps. --- Nozomu Ando |
|
From: Patrick G. <gun...@ir...> - 2002-07-27 19:50:32
|
Gregg Reynolds <ar...@ea...> writes: > Thanks, but no go. Are you using OS X 10.1.5, Yes. > emacs 21.3.50? No. I have Enricos enriched emacs. I think (I don't feel like booting my iBook now :) it is something like 21.1.x. > Also, I've got a bunch of fink stuff installed in /sw, but when I > renamed that directory to remove it from the path nothing changed, > so I don't think anything in there is interfering. This should do no harm. > Does anybody know of some kind of configuration dump that would write > out all my emacs config settings (e.g. the various faces, fontsets, > encodings, etc.) for easy comparison to a system that works? At this not that I know of. So, you have an incorrect display of the Hello-file (C-h H)? I had this, too but after Andrew suggested the lines I wrote in the last mail; this file was (for the german-needed chars) ok. Strange that you say that mozilla has also problems with the display of latin1 chars. Patrick -- I'll fade into the darkness |
|
From: Gregg R. <ar...@ea...> - 2002-07-27 18:00:10
|
On Saturday, July 27, 2002, at 08:00 AM, Patrick Gundlach wrote: > > then give these lines in your .emacs a try. At least it works for me > (german umlauts etc.) > > (set-frame-font "fontset-mac") > (set-keyboard-coding-system 'mac-roman) > Thanks, but no go. Are you using OS X 10.1.5, emacs 21.3.50? Also, I've got a bunch of fink stuff installed in /sw, but when I renamed that directory to remove it from the path nothing changed, so I don't think anything in there is interfering. Does anybody know of some kind of configuration dump that would write out all my emacs config settings (e.g. the various faces, fontsets, encodings, etc.) for easy comparison to a system that works? At this point it has become clear to me that the problem must be something completely simple and obvious, along the lines of "make sure the power cable is plugged in" and I just can't see it. Thanks, Gregg |
|
From: Rodney S. <rsp...@mc...> - 2002-07-27 17:35:02
|
Gang: I had trouble with the latest code via CVS. It was failing due to the non-existence of the directory mac/Contents/. Instead it created ../mac/Contents. So, I created this directory by hand, and make completes fine. But, then make install fails: cd /Users/rodney/cvs/emacs/man; makeinfo tramp.texi tramp.texi:25: Unknown command `copying'. tramp.texi:50: Unmatched `@end'. makeinfo: Removing output file `../info/tramp' due to errors; use --force to preserve. make[1]: *** [../info/tramp] Error 2 make: *** [info] Error 2 Apparently, @copying and therefore @end copying are not texinfo commands. If you comment these out with @c, then make install completes. But, I didn't get an Emacs.app in /Applications. I can open Emacs.app from the mac directory (and everything works great! Thanks Andrew!). But, when I try copying it to /Applications, Emacs doesn't open with either open or clicking. What am I doing wrong? Rodney On Friday, July 26, 2002, at 02:06 PM, mac-emacs-users- re...@li... wrote: Hi Gregg, The font problem had been fixed quite a while ago after the release of the patch for Emacs 21.1. The Mac OS X code has been merged into the main CVS tree so the latest version of the code can be obtained from Emacs CVS repository, which includes this bug fix. The current version is 21.3.50. For information on how to use the CVS, see: http://savannah.gnu.org/cvs/?group=emacs <SNIP> Andrew. |
|
From: Patrick G. <pg...@le...> - 2002-07-27 13:02:00
|
Gregg Reynolds <ar...@ea...> writes: Hi, > Thanks, but no luck. But I'm not sure I've understood you; "font" and then give these lines in your .emacs a try. At least it works for me (german umlauts etc.) (set-frame-font "fontset-mac") (set-keyboard-coding-system 'mac-roman) > This is incredibly, unbelievably frustrating. Is there some way I can > blame MS? Very likely. Patrick -- I'll fade into the darkness |
|
From: Gregg R. <ar...@ea...> - 2002-07-27 10:34:18
|
On Saturday, July 27, 2002, at 01:06 AM, Lennart Staflin wrote: > On Fri, 26 Jul 2002, Gregg Reynolds wrote: >> [..], but I still don't see accented characters. [..] > > I had to set the default font to "fontset-mac" to see the Latin-1 > characters. Thanks, but no luck. But I'm not sure I've understood you; "font" and "fontset" are different animals, aren't they? I tried setting the default face to "fontset-mac", and the encoding to "mac", "mac-roman", etc. to no avail. This is incredibly, unbelievably frustrating. Is there some way I can blame MS? -gregg |
|
From: Lennart S. <le...@ly...> - 2002-07-27 06:06:33
|
On Fri, 26 Jul 2002, Gregg Reynolds wrote: > [..], but I still don't see accented characters. [..] I had to set the default font to "fontset-mac" to see the Latin-1 characters. //Lennart |
|
From: Gregg R. <ar...@ea...> - 2002-07-26 17:49:28
|
On Friday, July 26, 2002, at 08:33 AM, Andrew Choi wrote: > Hi Gregg, > > The font problem had been fixed quite a while ago after the release of > the patch for Emacs 21.1. The Mac OS X code has been merged into the > main CVS tree so the latest version of the code can be obtained from > Emacs CVS repository, which includes this bug fix. The current > version is 21.3.50. For information on how to use the CVS, see: > Dear Andrew, Thanks for the quick reply, and for the work on mac-emacs. I've got 21.3.50 running now, but I still don't see accented characters. The fact that they don't seem to work anywhere else either (less v. 340, Mozilla 1.0, TextEdit) leads me to believe I somehow changed a system setting of some sort. Or maybe OS X 10.1.5 is buggy. (I'm pretty sure accented glyphs were working at some point in the past.) Anybody suggestions? Thanks, Gregg |
|
From: Andrew C. <ak...@sh...> - 2002-07-26 13:37:08
|
> Relatively new to OS X, runnning mac-emacs 21.1 on OS X 10.1.5, I > seem to have lost my latin 1 glyphs. Tried everything. Desperate. > Mule stuff like set-input-method seems to work ok, but I get blank > boxes instead of accented glyphs. Today I also noticed on a Mozilla > 1.0 that some latin 1 glyphs were not displaying, so maybe this is > an OS X question rather than an emacs question. Can anybody help? > > (P.S. A logo idea: dress the Gnu in a tartan pattern and call him > McEmacs.) > > Thanks, > > G. Reynolds Hi Gregg, The font problem had been fixed quite a while ago after the release of the patch for Emacs 21.1. The Mac OS X code has been merged into the main CVS tree so the latest version of the code can be obtained from Emacs CVS repository, which includes this bug fix. The current version is 21.3.50. For information on how to use the CVS, see: http://savannah.gnu.org/cvs/?group=emacs This version contains a GNU head icon. If you like the icon in the classic version better, a larger, color version is available at http://members.shaw.ca/akochoi/emacs/Emacs.icns To use it, simply replace the file with the same name in mac/Emacs.app/Contents/Resources/ by this one. I have received various suggestions to name the program in the past. But I don't think I should nor could give it a new name: the program is simply just `Emacs'. Think of it as having earned the right to carry that name :-). Andrew. |
|
From: Gregg R. <ar...@ea...> - 2002-07-26 11:35:55
|
Relatively new to OS X, runnning mac-emacs 21.1 on OS X 10.1.5, I seem to have lost my latin 1 glyphs. Tried everything. Desperate. Mule stuff like set-input-method seems to work ok, but I get blank boxes instead of accented glyphs. Today I also noticed on a Mozilla 1.0 that some latin 1 glyphs were not displaying, so maybe this is an OS X question rather than an emacs question. Can anybody help? (P.S. A logo idea: dress the Gnu in a tartan pattern and call him McEmacs.) Thanks, G. Reynolds G. Reynolds |
|
From: Steven T. <ste...@ma...> - 2002-07-23 16:32:38
|
An external program, starttls, required for this and can be found at ftp://ftp.opaopa.org/pub/elisp/starttls-0.9.tar.gz This program requires OpenSSL which is included with OSX 10.1, but for some reason is missing header files. This link shows how to get it running (i.e. place the header files in the right place): http://iharder.sourceforge.net/macosx/openssh3.html Once I got the header files in the right place it compiled. -Steven On Tuesday, July 23, 2002, at 01:40 AM, dm...@dm... wrote: > * ha...@Pr... [2002-07-22 22:59:16] >> When I try to send email from emacs I get the error message: >> >> 503 5.7.0 encryption too weak 0 less than 39 >> >> Anyone know how to do this? I am able to send email using Entourage >> or the >> OS X Mail program, so maybe I should try to send mail from emacs via >> one of >> those programs? >> >> Sending email used to work fine for me but my sttp server (at >> Princeton) is >> now requiring authorization that appears to use that encryption. > > Simon Josefsson has some support for starttls in Emacs. See > http://www.josefsson.org/emacs-smtp-starttls.html. Perhaps this will > provide what you need - I use this with an iPlanet Messaging Server > and it works fine. > |
1 message has been excluded from this view by a project administrator.
