From: "d.henman" <dhenman@gmail.com>
To: <emacs-devel@gnu.org>
Cc: eliz@gnu.org, Angelo Graziosi <angelo.graziosi@alice.it>
Subject: Re: cygwin emacs gtk2 problem fix
Date: Tue, 08 Jul 2008 12:03:14 +0900 [thread overview]
Message-ID: <20080708120314.3780@blackhawk> (raw)
In-Reply-To: Your message of Tue, 08 Jul 2008 00:41:46 +0200 <48729BAA.9090102@alice.it>
Thanks for the confirmation that the fix works for you as well.
As to your question:
"> Now the question is: could that be done at level of source code?"
I am not familiar with the source code, though I did try something like the following in "../lisp/startup.el", thinking it might work.
Ideally I7d use the below (if (and ...)) structure, but I don't now how to determine the toolkit emacs was built with. I simply wrote "x-toolkit" to illustrate.
(if (and (string= system-type "cygwin") (string= x-toolkit "gtk2"))
(setenv "G_SLICE" "always-malloc"))
but, since I don't know how to find the toolkit used I just used the below:
(if (string= system-type "cygwin")
(setenv "G_SLICE" "always-malloc"))
But, this did not work. emacs just crashed. I guess startup.el is called after doing some processing with the toolkit.
Regards,
Darel Henman
Angelo Graziosi <angelo.graziosi@alice.it> wrote:
> d.henman wrote:
>
> > I have found a simple fix to for the cygwin emacs gtk2 problem,
> > as mentioned in the etc/PROBLEM file.
> > [...]
> >
> > + $ export G_SLICE=always-malloc
> > + $ emacs
>
> Confirmed. It works just fine!
>
> Now the question is: could that be done at level of source code?
>
>
> Cheers,
> Angelo.
next prev parent reply other threads:[~2008-07-08 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 22:41 cygwin emacs gtk2 problem fix Angelo Graziosi
2008-07-08 3:03 ` d.henman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-07 0:32 d.henman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080708120314.3780@blackhawk \
--to=dhenman@gmail.com \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.