Re: suggestion to avoid erroneous lines in findmnt/lslocks/...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 06, 2012 at 10:15:33AM +0200, Karel Zak wrote:
> I'll fix it to use iscntrl() and \x?? hex (to be consistent our
> another outputs).

Fixed:

 - mount(8) uses '?' like coreutils for control chars (note that
   listing mode in mount(8) is in maintenance mode, use findmnt(8) if
   you want something better)

 - \x<code> is used in findmnt, lsblk, partx, ... for control and non-printable
   chars

 - in the raw and export (NAME=data) output are also replaced already existing
   \x<code> sequences (aaa\x20bbb --> aaa\x5cx20bbb).

   This is not used in the default output to keep it human readable (\x?? is
   pretty common in /dev/disk/by-*).


I have also fixed the way how lib/tt.c counts cells, it's possible
that old findmnt, lsblk, ... versions have a problem with some languages
(e.g JP) where more than one cell is necessary to print one multibyte.


    Karel

--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux