kdeconnect-cli broadcast option

[Aleix Pol]

No need to make it the default, it can be a separate argument, so you
either pass "-d devicename" or "--all".

Aleix

On Fri, Mar 18, 2016 at 3:06 PM, Achilleas Koutsou
<achilleas.k at gmail.com> wrote:
> Oh yes, of course. That's what I was thinking about too. I understand it
> might cause issues to do it by default when there's only one device. I was
> simply describing a (perhaps common) use case, when I was referring to the
> one device scenario.
>
> On Fri, 18 Mar 2016 at 16:03 Aleix Pol <aleixpol at kde.org> wrote:
>>
>> On Fri, Mar 18, 2016 at 2:55 PM, Achilleas Koutsou
>> <achilleas.k at gmail.com> wrote:
>> > I've recently been using a script to broadcast messages to all my
>> > connected
>> > devices. It basically iterates through "kdeconnect-cli -a --id-only" and
>> > runs the command I supplied.
>> >
>> > This isn't tedious, or even bothersome, but I was thinking it might be
>> > nice
>> > to have it as a built-in option. I was thinking this would also be
>> > useful
>> > for people who want to run a command (send ping, share file, etc) from
>> > the
>> > command line and only have one device paired. It's strange to have to
>> > lookup
>> > the device id, then run the command with the id to perform an action
>> > when
>> > all you have paired is that one device.
>> >
>> > What do you think? Is this useful?
>> > I presume it's a rather simple implementation as well, if you don't mind
>> > me
>> > taking a stab at it.
>>
>> That could make sense, provided we think it through.
>>
>> Maybe it would make more sense as a --all-paired-devices argument,
>> rather than just doing if there's the one paired device?
>>
>> Aleix
>> _______________________________________________
>> KDEConnect mailing list
>> KDEConnect at kde.org
>> https://mail.kde.org/mailman/listinfo/kdeconnect
>
>
> _______________________________________________
> KDEConnect mailing list
> KDEConnect at kde.org
> https://mail.kde.org/mailman/listinfo/kdeconnect
>