inxi output: no code tags, please!

[Pjotr]

Some forum helpers ask help seekers to provide their inxi -Fxz output between code tags. I don't think that's a good idea, because then you need to use scroll bars to find your way through that output....

When no code tags are being used, you can see all information at one glance. Much easier!

[gm10]

I hope you're just 2 days late...

[catweazel]

I hope you're just 2 days late...

Or his account's been hacked.

[karlchen]

Does the output below really look better ...

karl@unimatrix0 ~ $ inxi -Fxz
System: Host: unimatrix0 Kernel: 4.4.0-145-generic i686 bits: 32 compiler: gcc v: 5.4.0 Desktop: Xfce 4.12.3
Distro: Linux Mint 18.1 Serena base: Ubuntu 16.04 xenial
Machine: Type: Desktop Mobo: N/A model: N/A serial: <filter> BIOS: American Megatrends v: 080015 date: 10/09/2009
CPU: Topology: Dual Core model: Intel Atom 330 bits: 64 type: MT MCP arch: Bonnell rev: 2 L2 cache: 512 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 12799
Speed: 1600 MHz min/max: N/A Core speeds (MHz): 1: 1600 2: 1600 3: 1600 4: 1600
Graphics: Device-1: NVIDIA C79 [ION] vendor: ZOTAC driver: nouveau v: kernel bus ID: 03:00.0
Display: server: X.Org 1.18.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz
OpenGL: renderer: NVAC v: 3.3 Mesa 18.0.5 direct render: Yes
Audio: Device-1: NVIDIA MCP79 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:08.0
Sound Server: ALSA v: k4.4.0-145-generic
Network: Device-1: NVIDIA MCP79 Ethernet vendor: ZOTAC driver: forcedeth v: kernel port: d080 bus ID: 00:0a.0
IF: enp0s10 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: AzureWave AW-NE785 / AW-NE785H 802.11bgn
driver: ath9k v: kernel port: ec00 bus ID: 04:00.0
IF: wlp4s0 state: up mac: <filter>
Drives: Local Storage: total: 149.05 GiB used: 9.70 GiB (6.5%)
ID-1: /dev/sda vendor: Samsung model: HM160HI size: 149.05 GiB
Partition: ID-1: / size: 47.12 GiB used: 9.70 GiB (20.6%) fs: ext4 dev: /dev/sda7
ID-2: swap-1 size: 5.05 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors: System Temperatures: cpu: 84.0 C mobo: N/A gpu: nouveau temp: 60 C
Fan Speeds (RPM): N/A
Info: Processes: 193 Uptime: 1h 44m Memory: 1.72 GiB used: 479.0 MiB (27.3%) Init: systemd runlevel: 5 Compilers:
gcc: 5.4.0 Shell: bash v: 4.3.48 inxi: 3.0.33

... than the formatted text in the code box below?

Code: Select all

karl@unimatrix0 ~ $ inxi -Fxz
System:    Host: unimatrix0 Kernel: 4.4.0-145-generic i686 bits: 32 compiler: gcc v: 5.4.0 Desktop: Xfce 4.12.3 
           Distro: Linux Mint 18.1 Serena base: Ubuntu 16.04 xenial 
Machine:   Type: Desktop Mobo: N/A model: N/A serial: <filter> BIOS: American Megatrends v: 080015 date: 10/09/2009 
CPU:       Topology: Dual Core model: Intel Atom 330 bits: 64 type: MT MCP arch: Bonnell rev: 2 L2 cache: 512 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 12799 
           Speed: 1600 MHz min/max: N/A Core speeds (MHz): 1: 1600 2: 1600 3: 1600 4: 1600 
Graphics:  Device-1: NVIDIA C79 [ION] vendor: ZOTAC driver: nouveau v: kernel bus ID: 03:00.0 
           Display: server: X.Org 1.18.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz 
           OpenGL: renderer: NVAC v: 3.3 Mesa 18.0.5 direct render: Yes 
Audio:     Device-1: NVIDIA MCP79 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:08.0 
           Sound Server: ALSA v: k4.4.0-145-generic 
Network:   Device-1: NVIDIA MCP79 Ethernet vendor: ZOTAC driver: forcedeth v: kernel port: d080 bus ID: 00:0a.0 
           IF: enp0s10 state: down mac: <filter> 
           Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: AzureWave AW-NE785 / AW-NE785H 802.11bgn 
           driver: ath9k v: kernel port: ec00 bus ID: 04:00.0 
           IF: wlp4s0 state: up mac: <filter> 
Drives:    Local Storage: total: 149.05 GiB used: 9.70 GiB (6.5%) 
           ID-1: /dev/sda vendor: Samsung model: HM160HI size: 149.05 GiB 
Partition: ID-1: / size: 47.12 GiB used: 9.70 GiB (20.6%) fs: ext4 dev: /dev/sda7 
           ID-2: swap-1 size: 5.05 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 84.0 C mobo: N/A gpu: nouveau temp: 60 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 193 Uptime: 1h 44m Memory: 1.72 GiB used: 479.0 MiB (27.3%) Init: systemd runlevel: 5 Compilers: 
           gcc: 5.4.0 Shell: bash v: 4.3.48 inxi: 3.0.33

Which inxi output is easier to read?

[Pjotr]

Which inxi output is easier to read?

Without code tags: not so nice, agreed. But definitely easier to read, without the bloody scroll bars (both vertical and horizontal!).

[Moem]

I hope you're just 2 days late...

Two days late and a € short.

[gm10]

I hope you're just 2 days late...

Two days late and a € short.

Haha, I did not see that one coming.

[Pjotr]

Well, not much approval yet (*cough*)....

But I know what I like to see, when I'm helping somebody. So if need be, I'll fight the war against the evil scroll bars on my own.

[Moem]

I can't stop you from that, but I'll continue to add the code tags, and encourage newcomers to do so as well. The advantage of formatting (blockquotes) outweighs the 'evil' scrollbars.

On my small screen, I see only a vertical scrollbar in Karlchen's example.

[Pjotr]

I'll continue to add the code tags

Please don't in the threads where I'm the one who is asking for the inxi -Fxz output....

[Moem]

That's asking a lot. I'm not sure I'll be able to agree to that. After all, the request to add the code tags to long output is even in the forum guidelines.

[karlchen]

Request: inxi output: no code tags, please!
Answer: No inxi output unless between code tags.

[MrEen]

For my oldish eyes, formatted is better. I'll admit I miss stuff either way, but karlchen's soon-to-overheat cpu is easier for me to spot in the formatted output.

I have seen some people posting their inxi output without code tags and yet it is still somewhat well formatted. I'm uncertain how they accomplished that.

[karlchen]

<side issue> The joy of Zotac passive cooling. I have been expecting the CPU to go up in fire for the past 9 years now. </side issue>

[gm10]

Does anyone have access to the theme files? Just add a button to the codebox linked to some simple javascript $('.codebox code').css('max-height','none'); and everybody is happy.

[h2-1]

To make inxi output readable, just use the -y width option: inxi [options] -y 80

Note that legacy inxi (pre 3.x) line width handling was really crude and hacked, so it's narrow width handlers weren't very reliable.

This makes a nice what I consider 'forum friendly' output. Note that inxi will do this itself if the terminal window open is under 90 columns wide. There's a definite valid point when the line width is greater than the code box width, so you have to scroll left to right AND top to bottom, that I agree is really hard to process and read.

I find the non code formatted inxi output really difficult to read.

Code: Select all

System:
  Kernel: 4.17.0-17.3-liquorix-amd64 x86_64 bits: 64 compiler: gcc 
  v: 7.3.0 Desktop: Xfce 4.12.4 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.18.3 Distro: Debian GNU/Linux buster/sid 
Machine:
  Type: Desktop System: Gigabyte product: X470 AORUS ULTRA GAMING v: N/A 
  serial: <filter> 
  Mobo: Gigabyte model: X470 AORUS ULTRA GAMING-CF v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F2 date: 03/14/2018 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ 
  rev: 2 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 81590 
  Speed: 2144 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1612 2: 1589 
  3: 1726 4: 1759 5: 2457 6: 1910 7: 1653 8: 1614 9: 1887 10: 1572 11: 2488 
  12: 2161 
Graphics:
  Device-1: NVIDIA GT218 [GeForce 210] vendor: Gigabyte driver: nvidia 
  v: 340.107 bus ID: 09:00.0 chip ID: 10de:0a65 
  Display: x11 server: X.Org 1.20.0 driver: nvidia 
  resolution: 1280x1024~60Hz, 1280x1024~60Hz 
  OpenGL: renderer: N/A v: N/A direct render: N/A 
Audio:
  Device-1: NVIDIA High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:0be3 
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 0b:00.3 chip ID: 1022:1457 
  Sound Server: ALSA v: k4.17.0-17.3-liquorix-amd64 
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: 5.4.0-k 
  port: f000 bus ID: 06:00.0 chip ID: 8086:1539 
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.98 TiB used: 729.10 GiB (35.9%) 
  ID-1: /dev/sda vendor: Intel model: SSDSC2BW180A4 size: 167.68 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: DC32 scheme: MBR 
  ID-2: /dev/sdb vendor: Western Digital model: WD1003FZEX-00MK2A0 
  size: 931.51 GiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 1A01 temp: 35 C scheme: GPT 
  ID-3: /dev/sdc vendor: Western Digital model: WD1001FALS-00E8B0 
  size: 931.51 GiB speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 0K05 temp: 42 C scheme: GPT 
Partition:
  ID-1: / size: 58.81 GiB used: 14.74 GiB (25.1%) fs: ext4 dev: /dev/sda2 
  ID-2: /home size: 47.94 GiB used: 17.38 GiB (36.3%) fs: ext4 dev: /dev/sdb7 
  ID-3: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb1 
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A gpu: nvidia temp: 58 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 384 Uptime: 5d 19h 51m Memory: 31.43 GiB used: 9.11 GiB (29.0%) 
  Init: systemd v: 239 runlevel: 5 Compilers: gcc: 8.1.0 alt: 5/6/7/8 
  Shell: bash v: 4.4.23 running in: xfce4-terminal pinxi: 3.0.33-1

[Flemur]

inxi -Fxz | fmt --width=60

Code: Select all

System:
  Host: lemurator Kernel: 4.14.109-1-MANJARO x86_64 bits:
  64 compiler: gcc v: 8.2.1 Desktop: Fluxbox 1.3.7 Distro:
  Manjaro Linux
Machine:
  Type: Desktop System: eMachines product: ET1831 v:
  N/A serial: <filter> Mobo: eMachines model: EMCP73VT-PM
  serial: <filter> BIOS: AMI v: P01-A1 date: 09/14/2009
  ...

[h2-1]

it's easier to do inxi [options] -y 80, the output gets weird at less than 80 I found. fmt is a neat trick though, never seen that one. Plus piping will drop the colors unless you specify a specific color via -c

I do tend to wince though when very wide screened outputs are pasted into forum code boxes.