From: Ian D <dunni@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Network Manager
Date: Fri, 14 Dec 2012 11:25:30 -0500 [thread overview]
Message-ID: <87bodwfvnp.fsf@gnu.org> (raw)
Answers to next round of questions:
> Maybe your code could protect the respective D-Bus call with
> `dbus-ignore-errors'. With this, wired connections might be visible at
> least.
To use ENWC in wired mode, press 'W'. I probably should have put
that in the commentary.
> What about `dbus-call-method-asynchronously'? The handler could update
> the enwc buffer, and you aren't blocked during scan.
I've tried that, but here's the problem with at least Wicd (Not
so certain about NetworkManager): The "Scan" function for Wicd
takes a parameter `sync'. This is `t' if the user wants a
synchronous call, and `nil' otherwise. The issues I ran into
before were with this, and `dbus-call-method-asyncronously'
doesn't really help with it.
If `sync' is `nil', then the function returns `t', and goes
into the background, but doesn't provide a way to see when the
scan is finished. It returns immediately, so
`dbus-call-method-asynchronously' doesn't help. If I try using
`dbus-call-method-asynchronously' with `sync' as `t', then it
just doesn't return until another call to "Scan" is made, which
then compromises the return results
> Is it asynchronous? That is, can one go on editing while it makes a
> connection?
This part, there are no problems with (Again, not much testing
with NetworkManager). For Wicd, it begins connecting to the
network, and disappears into the background. For both of them
(assuming that NetworkManager doesn't block during connection),
the mode line string then switches to `[*%]', and will switch
to the signal strength if it connects, or `[0%]' if it is not
connected. This allows the user to keep an eye on the connection
status.
Ian D
next reply other threads:[~2012-12-14 16:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 16:25 Ian D [this message]
2012-12-16 9:07 ` Network Manager Michael Albinus
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 18:45 Ian D
2013-01-22 18:24 ` Stefan Monnier
2013-01-22 18:32 ` Ian D
2012-12-17 12:39 Ian D
2012-12-14 14:01 Ian D
2012-12-14 14:29 ` Michael Albinus
2012-12-15 16:08 ` Michael Albinus
2012-12-13 22:56 Ian D
2012-12-14 8:31 ` Bastien
2012-12-14 8:55 ` Michael Albinus
2012-12-14 9:33 ` Bastien
2012-12-13 21:38 Ian D
2012-12-13 21:47 ` Bastien
2012-12-13 21:58 ` Ian D
2012-12-13 22:19 ` Bastien
2012-12-18 17:45 ` Christian Lynbech
2012-12-13 21:51 ` Ian Bryant
2012-12-13 22:22 ` Xue Fuqiao
2012-12-14 8:21 ` Michael Albinus
2012-12-14 13:45 ` Ian D
2012-12-14 23:11 ` Stefan Monnier
2012-12-14 15:23 ` Richard Stallman
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=87bodwfvnp.fsf@gnu.org \
--to=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 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).