cli: use infintive form of verb, interfaces -> interface

We use the infinitive, or basic form, in configure context, as do most
other network vendors, so let's do the same in admin exec context.

Also, drop the 'name' qualifier, it is not needed in configure context
so we shouldn't have to use it in admin exec either.

Signed-off-by: Joachim Wiberg <[email protected]>

Author: troglobit

doc/networking.md

@@ -562,7 +562,7 @@ In addition to basic status shown in the interface overview, detailed
 LAG status can be inspected:
 
 ```
-admin@example:/> show interfaces name lag0
+admin@example:/> show interface lag0
 name                : lag0
 index               : 25
 mtu                 : 1500
@@ -582,7 +582,7 @@ out-octets          : 2142
 Same aggregate, but in LACP mode:
 
 ```
-admin@example:/> show interfaces name lag0
+admin@example:/> show interface lag0
 name                : lag0
 index               : 24
 mtu                 : 1500
@@ -624,7 +624,7 @@ Member ports provide additional status information:
 Example member port status:
 
 ```
-admin@example:/> show interfaces name eth7
+admin@example:/> show interface eth7
 name                : eth7
 index               : 8
 mtu                 : 1500
@@ -755,7 +755,7 @@ The speed and duplex status for the links can be listed as shown
 below, assuming the link operational status is 'up'. 
 
 ```
-admin@example:/> show interfaces name eth1
+admin@example:/> show interface eth1
 name                : eth1
 index               : 2
 mtu                 : 1500
@@ -769,7 +769,7 @@ ipv6 addresses      :
 in-octets           : 75581
 out-octets          : 43130
 ...
-admin@example:/> show interfaces name eth4
+admin@example:/> show interface eth4
 name                : eth4
 index               : 5
 mtu                 : 1500
@@ -827,7 +827,7 @@ require auto-negotiation to be enabled.
 Ethernet packet statistics[^6] can be listed as shown below.
 
 ```
-admin@example:/> show interfaces name eth1
+admin@example:/> show interface eth1
 name                : eth1
 index               : 2
 mtu                 : 1500
@@ -1525,10 +1525,10 @@ currently supported, namely `ipv4` and `ipv6`.
 [^3]: For example, IPv4 groups are mapped to MAC multicast addresses by
     mapping the low-order 23-bits of the IP address in the low-order 23
     bits of the Ethernet address 01:00:5E:00:00:00.  Meaning, more than
-	one IP multicast group maps to the same MAC multicast group.
+    one IP multicast group maps to the same MAC multicast group.
 [^4]: A YANG deviation was previously used to make it possible to set
     `phys-address`, but this has been replaced with the more flexible
-	`custom-phys-address`.
+    `custom-phys-address`.
 [^5]: MAC bridges on Marvell Linkstreet devices are currently limited to
     a single MAC database, this may be a problem if the same MAC address
     appears in different MAC bridges.

doc/wifi.md

@@ -27,10 +27,10 @@ Wi-Fi support is primarily tested with Realtek chipset-based adapters.
 ## Configuration
 
 Add a supported Wi-Fi network device. To verify that it has been
-detected, look for `wifi0` in `show interfaces`
+detected, look for `wifi0` in `show interface`
 
 ```
-admin@example:/>  show interfaces
+admin@example:/>  show interface
 INTERFACE       PROTOCOL   STATE       DATA
 lo              loopback   UP
                 ipv4                   127.0.0.1/8 (static)
@@ -52,7 +52,7 @@ see the result read the operational datastore for interface `wifi0` or
 use the CLI
 
 ```
-admin@infix-00-00-00:/> show interfaces name wifi0
+admin@infix-00-00-00:/> show interface wifi0
 name                : wifi0
 type                : wifi
 index               : 3
@@ -119,11 +119,11 @@ admin@example:/config/interface/wifi0/> leave
 
 The Wi-Fi negotiation should now start immediately, provided that the
 SSID and pre-shared key are correct. You can verify the connection by
-running `show interfaces` again.
+running `show interface` again.
 
 
 ```
-admin@example:/> show interfaces
+admin@example:/> show interface
 INTERFACE       PROTOCOL   STATE       DATA
 lo              loopback   UP
                 ipv4                   127.0.0.1/8 (static)
@@ -139,14 +139,14 @@ admin@example:/>
 
 ## Troubleshooting Connection Issues
 
-Use `show wifi scan wifi0` and `show interfaces` to verify signal strength
+Use `show wifi scan wifi0` and `show interface` to verify signal strength
 and connection status. If issues arise, try the following
 troubleshooting steps:
 
 1. **Verify signal strength**: Check that the target network shows "good" or "excellent" signal
 2. **Check credentials**: Verify the preshared key in `ietf-keystore`
 3. **Review logs**: Check system logs with `show log` for Wi-Fi related errors
 4. **Regulatory compliance**: Ensure the country-code matches your location
-5. **Hardware detection**: Confirm the adapter appears in `show interfaces`
+5. **Hardware detection**: Confirm the adapter appears in `show interface`
 
 If issues persist, check the system log for specific error messages that can help identify the root cause.

src/klish-plugin-infix/xml/infix.xml

@@ -441,14 +441,12 @@
   </COMMAND>
 
   <!-- https://www.cisco.com/c/en/us/td/docs/wireless/access_point/mob_exp/83/cmd-ref/me_cr_book/me_ports_and_interfaces_cli.html -->
-  <COMMAND name="interfaces" help="Show interface info">
+  <COMMAND name="interface" help="Show interface info, default an overview of all">
     <SWITCH name="optional" min="0" max="1">
-      <COMMAND name="name" help="Show detailed info about NAME">
-        <PARAM name="name" ptype="/IFACES" help="Interface." />
-      </COMMAND>
+      <PARAM name="ifname" ptype="/IFACES" help="Interface name" />
     </SWITCH>
     <ACTION sym="script" in="tty" out="tty" interrupt="true">
-        show interface "$KLISH_PARAM_name" |pager
+      show interface "$KLISH_PARAM_ifname" |pager
     </ACTION>
   </COMMAND>