unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vinicius Jose Latorre <viniciusjl@ig.com.br>
To: Seiji Zenitani <zenitani@mac.com>
Cc: emacs-devel@gnu.org
Subject: Re: OS X: load-path on self-contained build
Date: Wed, 01 Aug 2007 18:46:48 -0300	[thread overview]
Message-ID: <46B0FF48.9000500@ig.com.br> (raw)
In-Reply-To: <B93907C1-D235-49AB-BB94-422A9447B98C@mac.com>


Done.

Patch applied in trunk and Emacs 22 branch.


Seiji Zenitani wrote:
> Hi,
>
> Could anyone please deal with the below patch?  According to the CVS, 
> that part was written by Dr. Andrew Choi 5 years ago (revision 1.9, 
> Fri Aug 16 02:30:21 2002 UTC).  I noticed that comment strings (/* ... 
> */) near the relevant lines should reflect the change, too.
>
> Seiji Zenitani
> zenitani@mac.com
>
> On 2007/07/15, at 18:11, Seiji Zenitani wrote:
>> On 2007/07/10, at 18:01, Richard Stallman wrote:
>>
>>> Would someone please fix this, then ack?
>>
>>
>> The attached patch (by R. Yoshitake; GPL) works fine for me.
>> Is there any potential side-effects?
>>
>>
>> Seiji Zenitani
>> zenitani@mac.com
>>
>>
>> --- src/mac.c.orig  2007-04-20 09:26:45.000000000 -0400
>> +++ src/mac.c       2007-06-09 18:54:42.000000000 -0400
>> @@ -5331,12 +5335,12 @@
>>        q[0] = '\0';
>>        strcpy (p, app_bundle_pathname);
>> -      strcat (p, "/Contents/Resources/lisp");
>> +      strcat (p, "/Contents/Resources/site-lisp");
>>        if (stat (p, &st) == 0 && (st.st_mode & S_IFMT) == S_IFDIR)
>>     strcat (q, p);
>>        strcpy (p, app_bundle_pathname);
>> -      strcat (p, "/Contents/Resources/leim");
>> +      strcat (p, "/Contents/Resources/lisp");
>>        if (stat (p, &st) == 0 && (st.st_mode & S_IFMT) == S_IFDIR)
>>     {
>>       if (q[0] != '\0')
>> @@ -5345,7 +5349,7 @@
>>     }
>>        strcpy (p, app_bundle_pathname);
>> -      strcat (p, "/Contents/Resources/site-lisp");
>> +      strcat (p, "/Contents/Resources/leim");
>>        if (stat (p, &st) == 0 && (st.st_mode & S_IFMT) == S_IFDIR)
>>     {
>>       if (q[0] != '\0')

  reply	other threads:[~2007-08-01 21:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  3:54 OS X: load-path on self-contained build Seiji Zenitani
2007-07-10 22:01 ` Richard Stallman
2007-07-15 22:11   ` Seiji Zenitani
2007-07-16 15:49     ` Richard Stallman
2007-07-23 22:30     ` Richard Stallman
2007-07-30 20:48     ` Richard Stallman
2007-07-31  2:13     ` Seiji Zenitani
2007-08-01 21:46       ` Vinicius Jose Latorre [this message]
2007-08-01 22:06         ` Seiji Zenitani
2007-08-01 22:23           ` Vinicius Jose Latorre
2007-08-01 22:40             ` Glenn Morris
2007-08-01 23:13               ` Vinicius Jose Latorre
2007-08-02  0:08                 ` Vinicius Jose Latorre
2007-08-06 16:33     ` Richard Stallman
2007-08-06 18:08       ` Glenn Morris

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=46B0FF48.9000500@ig.com.br \
    --to=viniciusjl@ig.com.br \
    --cc=emacs-devel@gnu.org \
    --cc=zenitani@mac.com \
    /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).