unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steven Tamm <steventamm@mac.com>
Cc: emacs-devel@gnu.org
Subject: Re: Enhanced Carbon Emacs (version 2.1, emacs 21.3.50.4) : trying to save as mac-roman
Date: Tue, 25 Feb 2003 23:32:51 -0800	[thread overview]
Message-ID: <8355F9AF-495C-11D7-A793-00039390AB82@mac.com> (raw)
In-Reply-To: <DDD614B3-48FB-11D7-99BD-0030654C30A8@fsa.ulaval.ca>


[-- Attachment #1.1: Type: text/plain, Size: 2925 bytes --]

The binary distributions of GNU Emacs on versiontracker are woefully 
out of date.  I had an email conversation with the guy who posted the 
"Enhanced Version" and we sort of agreed to disagree.  In any case, the 
version you have is almost 3 months old and many, many bugs have been 
fixed.

If you do not need to specialized LaTeX support in the "enhanced" 
version I would suggest pulling down the CVS,  following the directions 
at savannah:  See http://savannah.gnu.org/cvs/?group=emacs .  Once you 
have that, and assuming you have installed the OSX developer tools, all 
you have to do is follow the directions in the mac/INSTALL, which 
contains the three commands you need to execute in the terminal.

The bigger question is what to do about the binary distributions of 
21.3 that are floating around with bugs that people report.  The ones 
on versiontracker all do the wrong thing, either include more than what 
is needed (like this one with TeX stuff), or less than what is needed, 
or install in the wrong place, like in /usr/bin.   I'm kind of 
regretting the whole make-package script.

-Steven

On Tuesday, February 25, 2003, at 12:01  PM, Antoine Gautier wrote:

> Hi all,
>
> Here is a copy of a post I made on gnu.emacs.help, I am beginning to 
> suspect that I either found a bug or that my installation is flawed.
>
> I just installed Enhanced Carbon Emacs (version 2.1, emacs 21.3.50.4)
> on mac os X 10.2.4, and I have no succes trying to save mac-roman
> encoded files (saving as latin1 works fine).
>
> I tried adding a number of things to my .emacs, such as
>
> (prefer-coding-system 'mac-roman-mac)
> (set-buffer-file-coding-system 'mac-roman-mac)
> (set default-buffer-file-coding-system 'mac-roman-mac)
>
> with no result. The files do get saved, but are unreadable by other mac
> apps. Even re-opening them with emacs I get a bunch of ????'s (only
> accentuated characters such as é, à, ô, etc. come out OK : 'été' gets 
> saved as 'é?é').
>
> Trying to set the coding from emacs (c-x ret f mac-roman) does not 
> help either.
>
> For some odd reason I can correctly open mac-roman files, but saving
> them does not work.
>
> Also : whenever I lauch emacs.app I get the following message on 
> console.app :
>
> ## Component Manager: attempting to find symbols in a component alias 
> of type (regR/carP/x!bt)
>
> but lauching terminal.app does that too.
>
> Maybe it has to do with the many emacs's installed in /usr/bin (?)
>
> Any help will be greatly appreciated !
>
> Regards,
>
>
> Antoine Gautier
>
> Faculté des Sciences de l'administration
> Université Laval
> internet : http://www.fsa.ulaval.ca/personnel/gautiera/
> courriel : antoine.gautier@fsa.ulaval.ca
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel

[-- Attachment #1.2: Type: text/enriched, Size: 2982 bytes --]

The binary distributions of GNU Emacs on versiontracker are woefully
out of date.  I had an email conversation with the guy who posted the
"Enhanced Version" and we sort of agreed to disagree.  In any case,
the version you have is almost 3 months old and many, many bugs have
been fixed.  


If you do not need to specialized LaTeX support in the "enhanced"
version I would suggest pulling down the CVS,  following the
directions at savannah:  See http://savannah.gnu.org/cvs/?group=emacs
.  Once you have that, and assuming you have installed the OSX
developer tools, all you have to do is follow the directions in the
mac/INSTALL, which contains the three commands you need to execute in
the terminal.


The bigger question is what to do about the binary distributions of
21.3 that are floating around with bugs that people report.  The ones
on versiontracker all do the wrong thing, either include more than
what is needed (like this one with TeX stuff), or less than what is
needed, or install in the wrong place, like in /usr/bin.   I'm kind of
regretting the whole make-package script.


-Steven


On Tuesday, February 25, 2003, at 12:01  PM, Antoine Gautier wrote:


<excerpt>Hi all,


Here is a copy of a post I made on gnu.emacs.help, I am beginning to
suspect that I either found a bug or that my installation is flawed.


I just installed Enhanced Carbon Emacs (version 2.1, emacs 21.3.50.4)

on mac os X 10.2.4, and I have no succes trying to save mac-roman

encoded files (saving as latin1 works fine).


I tried adding a number of things to my .emacs, such as


(prefer-coding-system 'mac-roman-mac)

(set-buffer-file-coding-system 'mac-roman-mac)

(set default-buffer-file-coding-system 'mac-roman-mac)


with no result. The files do get saved, but are unreadable by other mac

apps. Even re-opening them with emacs I get a bunch of ????'s (only

accentuated characters such as é, à, ô, etc. come out OK : 'été' gets
saved as 'é?é').


Trying to set the coding from emacs (c-x ret f mac-roman) does not
help either.


For some odd reason I can correctly open mac-roman files, but saving

them does not work.


Also : whenever I lauch emacs.app I get the following message on
console.app :


## Component Manager: attempting to find symbols in a component alias
of type (regR/carP/x!bt)


but lauching terminal.app does that too.


Maybe it has to do with the many emacs's installed in /usr/bin (?)


Any help will be greatly appreciated !


Regards,



Antoine Gautier 


Faculté des Sciences de l'administration

Université Laval 

internet :
<underline><color><param>1A19,1A19,FFFE</param>http://www.fsa.ulaval.ca/personnel/gautiera/</color></underline>

courriel : antoine.gautier@fsa.ulaval.ca

_______________________________________________

Emacs-devel mailing list

Emacs-devel@gnu.org

http://mail.gnu.org/mailman/listinfo/emacs-devel

</excerpt>

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2003-02-26  7:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 20:01 Enhanced Carbon Emacs (version 2.1, emacs 21.3.50.4) : trying to save as mac-roman Antoine Gautier
2003-02-25 22:38 ` Hans-Peter Binder
2003-02-25 23:20   ` Antoine Gautier
2003-02-26  7:32 ` Steven Tamm [this message]
2003-02-26 23:51   ` Antoine Gautier
2003-02-27  9:59     ` Hans-Peter Binder
2003-02-27 15:40       ` Ovidiu Predescu
     [not found] <E18oBMx-0006TS-00@monty-python.gnu.org>
2003-02-27  2:14 ` Enhanced Carbon Emacs (version 2.1, emacs 21.3.50.4) : Guillaume Lessard
2003-02-27  9:17   ` Juanma Barranquero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8355F9AF-495C-11D7-A793-00039390AB82@mac.com \
    --to=steventamm@mac.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).