public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Emacs problems after dbus (?) update
Date: Sat, 03 Dec 2011 18:30:00 -0000	[thread overview]
Message-ID: <4EDA4D77.4050804@cornell.edu> (raw)
In-Reply-To: <CAK-n8j68ZL_+OrXXV8Lkoifh--+mtnp3O1=QDvkXEzE=3E+BJg@mail.gmail.com>

On 12/3/2011 10:17 AM, Jim Reisert AD1C wrote:
> On Sat, Dec 3, 2011 at 4:42 AM, Ken Brown wrote:
>
>>> (emacs:3380): GLib-GObject-WARNING **: Two different plugins tried to
>>> register 'BasicEngineFc'.
>>
>> Try removing /etc/pango/pango.modules .  See
>>
>>   http://cygwin.com/ml/cygwin-xfree/2011-11/msg00047.html
>
> Ken, that did fix the problem.  Why did this just start happening
> (after the last update), and what's the long-term fix?  At least if it
> comes back, I know what to do.

This is just a minor glitch, related to the fact that Yaakov is 
gradually updating some packages that were updated long ago in Ports. 
[It's minor because emacs actually worked fine, in spite of all the 
warnings].  I'm sure he will get this all sorted out.

> I don't use Gnome - is there a way to uninstall the whole package,
> including Pango?

emacs-X11 is built using the gtk toolkit.  This is the upstream default 
for emacs, and I don't want to do something special for Cygwin unless 
there's a good reason.  So emacs-X11 requires libgtk, which requires 
libpango.

Ken

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      reply	other threads:[~2011-12-03 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03  6:45 Jim Reisert AD1C
2011-12-03 14:24 ` Ken Brown
2011-12-03 16:25   ` Jim Reisert AD1C
2011-12-03 18:30     ` Ken Brown [this message]

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=4EDA4D77.4050804@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-xfree@cygwin.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.
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).