unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Noé Lopez via Emacs development discussions." <emacs-devel@gnu.org>
To: rms@gnu.org
Cc: dunni@gnu.org, emacs-devel@gnu.org, noelopez@free.fr
Subject: Re: [PATCH] [ELPA] Implement connman in enwc
Date: Tue, 02 Apr 2024 15:06:03 +0200	[thread overview]
Message-ID: <87le5voqx0.fsf@xn--no-cja.eu> (raw)
In-Reply-To: <E1rrQVB-0007lL-3l@fencepost.gnu.org> (message from Richard Stallman on Mon, 01 Apr 2024 18:51:41 -0400)

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> Could you please tell us in a few lines what ENWC does?

Hi,

ENWC is an emacs package who's purpose is to display and manage internet
connections through diffent backends. That means listing available wi-fi
networks and connecting to them from emacs. On gnu/linux backends this
is usually NetworkManager, wicd or connman (maybe other packages
exist). AFAIK these packages interface with the linux kernel to manage
these connections, and they all provide a D-BUS interface for
applications that want to manage wifi, this is ENWC's use case.

From what I can see, ENWC has been created in 2013, then rebooted in
2017 by Ian Dunn but abandoned again since, though in a working state
for NetworkManager, the ConnMan back-end has not been updated.

        https://mail.gnu.org/archive/html/emacs-devel/2012-12/msg00368.html
        https://mail.gnu.org/archive/html/emacs-devel/2017-02/msg00583.html

As of right now ENWC is hosted on savannah and is inactive since the
reboot in 2017.

       https://savannah.nongnu.org/projects/enwc

And to answer your 2012 question, it uses mostly asynchronous requests,
except for when connecting, but that should be easily fixable.

       https://mail.gnu.org/archive/html/emacs-devel/2012-12/msg00391.html

> Also, what connman support does, concretely?

ConnMan support makes the package compatible with another back-end, my
patch only finishes the work that was started a few years ago.



  reply	other threads:[~2024-04-02 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 22:10 [PATCH] [ELPA] Implement connman in enwc Noé Lopez via Emacs development discussions.
2024-04-01 22:51 ` Richard Stallman
2024-04-02 13:06   ` Noé Lopez via Emacs development discussions. [this message]
2024-04-04 22:42     ` Richard Stallman
2024-04-04 22:42     ` Richard Stallman
2024-04-05 20:00       ` Noé Lopez via Emacs development discussions.
2024-04-08 22:30         ` Richard Stallman
2024-04-14 13:01           ` Noé Lopez via Emacs development discussions.
2024-09-27 17:34 ` Joseph Turner
2024-09-28 11:03   ` Noé Lopez via Emacs development discussions.
2024-09-28 18:15     ` Joseph Turner

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=87le5voqx0.fsf@xn--no-cja.eu \
    --to=emacs-devel@gnu.org \
    --cc=dunni@gnu.org \
    --cc=noe@xn--no-cja.eu \
    --cc=noelopez@free.fr \
    --cc=rms@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).