From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Ian Dunn <dunni@gnu.org>, emacs-devel@gnu.org
Subject: Re: ENWC Development
Date: Wed, 15 Feb 2017 20:29:26 -0500 [thread overview]
Message-ID: <91c64d10-75c6-a813-6425-bd4c49a146d4@gmail.com> (raw)
In-Reply-To: <87inoblzns.fsf@escafil>
On 2017-02-15 19:58, Ian Dunn wrote:
> 3. Finally, I'd appreciate help testing enwc. I run NetworkManager
> myself, so that's likely to get the most testing, but I'd hate to see
> the others fall into disrepair. Even something simple such as
> running a few commands and telling me it didn't work would be
> helpful. If anyone would like to take it a step further and maintain
> one of the backends, that'd be even better.
Hi Ian,
I use Network Manager. I just installed enwc from ELPA. My first instinct was to run M-x elwc, which caused a "enwc-do-scan: Symbol’s function definition is void: nil" message to appear. Looking at the code, I gathered that I had to run enwc-setup first (why doesn't M-x enwc do that automatically? I saw that in fact this should be done from my .emacs, but I don't want to ENWC in all Emacs sessions). Running enwc-setup printed "enwc-setup: No usable backend found.", and then a series of "Error running timer ‘enwc-update-mode-line’: (void-function nil)" messages.
It seems that the dbus call for network manager in enwc-setup returns nil for me.
Cheers,
Clément.
next prev parent reply other threads:[~2017-02-16 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 0:58 ENWC Development Ian Dunn
2017-02-16 1:21 ` Clément Pit-Claudel
2017-02-16 2:21 ` Ian Dunn
2017-02-27 19:50 ` Clément Pit-Claudel
2017-03-01 2:49 ` Ian Dunn
2017-03-01 3:07 ` Clément Pit-Claudel
2017-03-01 3:36 ` raman
2017-02-16 1:29 ` Clément Pit-Claudel [this message]
2017-02-16 9:10 ` Live System User
-- strict thread matches above, loose matches on Subject: below --
2017-03-14 1:06 Ian Dunn
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=91c64d10-75c6-a813-6425-bd4c49a146d4@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=dunni@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.