Thomas Haller 0055d8ed58 cli: don't fail removing non-existing option (pt1) ... Part 1, which addresses the issue for simple properties that have a plain remove-by-value function. Rationale: Removing a value/index that does not exist should not be a failure. Woule you like: $ nmcli connection modify "$PROFILE" autoconnect no $ nmcli connection modify "$PROFILE" autoconnect no Error: autoconnect is already disabled So, why would it be a good idea to fail during $ nmcli connection modify "$PROFILE" -vpn.data ca $ nmcli connection modify "$PROFILE" -vpn.data ca Error: failed to remove a value from vpn.data: invalid option 'ca'. Generally, it should not be an error to remove an option, as long as the option itself is valid. For example, $ nmcli connection modify "$PROFILE" -vlan.ingress-priority-map bogus should fail, but $ nmcli connection modify "$PROFILE" -vlan.ingress-priority-map 1:5 should succeed even if there was nothing to remove.		2019-03-25 09:12:32 +01:00
..
c-list
c-rbtree
c-siphash
n-acd
nm-utils	shared: don't implement nm_utils_parse_inaddr() based on nm_utils_parse_inaddr_bin()	2019-03-25 09:12:32 +01:00
systemd	shared/systemd: fix gettid() compat implementation shadowing function from glibc	2019-03-11 18:17:12 +01:00
meson.build	shared: add "shared/nm-libnm-core-utils.h" utils	2019-03-25 09:12:32 +01:00
nm-common-macros.h
nm-dbus-compat.h
nm-default.h	all: goodbye libnm-glib	2019-03-19 17:15:15 +01:00
nm-dispatcher-api.h
nm-ethtool-utils.c
nm-ethtool-utils.h
nm-libnm-core-utils.c	libnm: move parsing VLAN priority mapping to "shared/nm-libnm-core-utils.h"	2019-03-25 09:12:32 +01:00
nm-libnm-core-utils.h	cli: don't fail removing non-existing option (pt1)	2019-03-25 09:12:32 +01:00
nm-meta-setting.c
nm-meta-setting.h
nm-test-libnm-utils.h	all: goodbye libnm-glib	2019-03-19 17:15:15 +01:00
nm-test-utils-impl.c	all: goodbye libnm-glib	2019-03-19 17:15:15 +01:00
nm-version-macros.h.in