Hi, Do you recommend we do the same in the cat manual page, regarding filenames?
Or for that matter, in hundreds of other manual pages. Unix does whitespace-seperated tokenization, nearly everywhere, so I do not think this needs to be documented. Florian Viehweger <[email protected]> wrote: > Hi, > > this is a diff mentioning double quotes for using passphrases > containing whitespaces. > > Additionally adding a comma to a sentence for better clarity. > > Comments? > > Thanks! > > Index: ifconfig.8 > =================================================================== > RCS file: /daten/openbsdmirror/cvs/mirror/src/sbin/ifconfig/ifconfig.8,v > retrieving revision 1.384 > diff -u -p -u -p -r1.384 ifconfig.8 > --- ifconfig.8 27 Jun 2022 16:27:03 -0000 1.384 > +++ ifconfig.8 22 Aug 2022 21:50:59 -0000 > @@ -1302,13 +1302,15 @@ A station will always use the group ciph > Set the WPA key and enable WPA. > The key can be given using either a passphrase or a full length hex key, > starting with 0x. > -If a passphrase is used the > +If a passphrase is used, the > .Cm nwid > or > .Cm join > option must first be specified, since > .Nm > will hash the nwid along with the passphrase to create the key. > +If a passphrase contains one or more whitespaces, it can be surrounded > +by double quotes. > .It Cm -wpakey > Delete the pre-shared WPA key and disable WPA. > .It Cm wpaprotos Ar proto,proto,... > > > > -- > greetings, > > Florian Viehweger >
