From: Ian Dunn <dunni@gnu.org>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ENWC Development
Date: Tue, 28 Feb 2017 21:49:42 -0500 [thread overview]
Message-ID: <87inntogmx.fsf@escafil> (raw)
In-Reply-To: <6eb0f39a-6ed0-d54c-c13c-2d3b4296c522@gmail.com> ("Clément Pit-Claudel"'s message of "Mon, 27 Feb 2017 14:50:34 -0500")
Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
>
> With this added scanning worked: I got a list of wireless networks!
>
Hurray!
> Some small requests: Instead of throwing and error, could enwc automatically
> figure out (possibly by prompting me) what my wired and wireless interfaces are?
>
I like this idea. Here's how I imagine it:
1. Set the default values of the interfaces to an empty string or nil
2. If unset during enwc-setup, use ip or ifconfig (or other customizable program) to determine the available interfaces and prompt the user for each one
It's probably possible to automate it more, but I don't see much benefit. In all likelihood, it'd be easier and more accurate to collect the interfaces and present them to the user for selection.
What do you think?
> Also: sorting the list of networks by clicking a header should ideally not
> scroll it (currently, sorting by e.g. Essid will sometimes scroll all but two or
> three networks out of the screen).
>
Reproduced. This is an issue with tabulated-list-mode. I'll see what I can do.
--
Ian Dunn
next prev parent reply other threads:[~2017-03-01 2:49 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 [this message]
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=87inntogmx.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).