From: Glenn Morris <rgm@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 25301@debbugs.gnu.org, mwolson@gnu.org
Subject: bug#25301: 26.0.50; erc: peculiar error, emacs not compiled with dbus support
Date: Wed, 04 Jan 2017 16:11:41 -0500 [thread overview]
Message-ID: <odd1g2jzsi.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20161230181504.GB1350@protected.rcdrun.com> (Jean Louis's message of "Fri, 30 Dec 2016 21:15:04 +0300")
Jean Louis wrote:
> My emacs is compiled withou dbus support. And erc is a built-in, and
> it complains "peculiar error, emacs not compiled with dbus support". I
> guess if there is no dbus, then erc, that is a built-in shall not
> complain on that. It blocks the emacs for short time.
>
> It could detect the dbus support, and simply not do those whatever
> benefits of dbus are there.
I don't use erc, but AFAICS the only part of it that uses dbus is
erc-desktop-notifications, which needs dbus to work at all.
erc-desktop-notifications does not seem to be enabled by default,
so it seems to me that you should simply stop doing whatever it is that
you do that tries to use it.
> Features:
> (help-fns radix-tree cus-edit mailclient shadow mailalias emacsbug
> misearch multi-isearch mm-archive message dired dired-loaddefs rfc822
> mml mml-sec epa gnus-util rmail rmail-loaddefs mailabbrev gmm-utils
> mailheader mm-decode mm-bodies mm-encode network-stream starttls
> url-http tls gnutls mail-parse rfc2231 url-gw nsm subr-x puny
> url-cache url-auth epg erc-track erc-spelling flyspell ispell
> erc-services erc-ring erc-desktop-notifications notifications dbus xml
next prev parent reply other threads:[~2017-01-04 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 18:15 bug#25301: 26.0.50; erc: peculiar error, emacs not compiled with dbus support Jean Louis
2017-01-04 21:11 ` Glenn Morris [this message]
2017-01-04 23:31 ` Jean Louis
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=odd1g2jzsi.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25301@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=mwolson@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.