From: Ian Dunn <dunni@gnu.org>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ENWC Development
Date: Wed, 15 Feb 2017 21:21:43 -0500 [thread overview]
Message-ID: <878tp6naj5.fsf@escafil> (raw)
In-Reply-To: <933e7e36-2c24-231d-d2f0-c407250117a0@gmail.com> ("Clément Pit-Claudel"'s message of "Wed, 15 Feb 2017 20:21:02 -0500")
Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> 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).
>
As I mentioned, the ELPA version is out of date at the moment (and apparently non-functional), but this is a great point.
ENWC isn't in a state to be released right now, a fact that I didn't make clear, and I'm sorry for that. Right now, the only feature I have working on my machine is scanning and displaying access points.
Thank you Clément, both for your help and your quick response. Would it be too much trouble to try it from the hg repo on Savannah? ( hg clone http://hg.savannah.nongnu.org/hgweb/enwc/ ) Same question for anyone else interested, and I understand if you choose not to.
Also, if anyone wants to help with the design or development, feel free to shoot me an email.
--
Ian Dunn
next prev parent reply other threads:[~2017-02-16 2:21 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 [this message]
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
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
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=878tp6naj5.fsf@escafil \
--to=dunni@gnu.org \
--cc=cpitclaudel@gmail.com \
--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 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).