BlueFreeBSD: width

grahamperrin

Daemon

Reaction score: 368
Messages: 1,221

Please, can you allow BlueFreeBSD (first screenshot below) to run as wide as FreeBSD light?

1622703078846.png

1622703108256.png

Thank you.
 

drhowarddrfine

Son of Beastie

Reaction score: 2,205
Messages: 4,202

Designers will tell you that text shouldn't be any wider than 75 characters--up to 100. And I agree.
 
OP
grahamperrin

grahamperrin

Daemon

Reaction score: 368
Messages: 1,221

danger@ at your leisure, would you like to make the widths consistent for the two styles? I imagine that the (greater) width of FreeBSD light will be preferable. Thanks.

drhowarddrfine with respect, I believe that a 100-character limit will not suit the types of content that are sometimes found in FreeBSD Forums. Code blocks should be not so limited, and so on.
 

kpedersen

Son of Beastie

Reaction score: 1,866
Messages: 2,746

Code blocks should be not so limited, and so on.
Code blocks should absolutely be limited to less than 80 chars wide. As a respectful nod towards our PDP-11/vt100 forefathers ;)

Yes, I know it pretty much excludes Java and C++ developers but that is beyond the point!
 
OP
grahamperrin

grahamperrin

Daemon

Reaction score: 368
Messages: 1,221

I shouldn't detract from the wish for consistency, but here goes:

git -C /usr/ports pull --ff-only && git -C /usr/src pull --ff-only
echo "" ; date ; uname -sr ; echo "shell: $SHELL" ; echo "" ; git -C /usr/ports pull --ff-only && echo "" ; git -C /usr/src pull --ff-only && set freebsdmaingitcommitcount="`git -C /usr/src rev-list --first-parent --count HEAD`" && echo "freebsd/main (FreeBSD-CURRENT) Git commit count: $freebsdmaingitcommitcount" && set freebsdmaingithash="`git -C /usr/src rev-list --max-count=1 HEAD`" && echo "freebsd/main Git hash: $freebsdmaingithash" && echo "<https://cgit.freebsd.org/src/commit/?id=$freebsdmaingithash>" && echo "– in context: <https://cgit.freebsd.org/src/log/?qt=range&q=$freebsdmaingithash>"
cd /usr/src && make -j2 buildworld && make -j2 buildkernel KERNCONF=GENERIC-NODEBUG
bectl create n"$freebsdmaingitcommitcount"-"$freebsdmaingithash"-a && bectl activate n"$freebsdmaingitcommitcount"-"$freebsdmaingithash"-a && bectl list -c creation


Alternatively (misusing a code block to represent a command):

Code:
echo "" ; date ; uname -sr ; echo "shell: $SHELL" ; echo "" ; git -C /usr/ports pull --ff-only && echo "" ; git -C /usr/src pull --ff-only && set freebsdmaingitcommitcount="`git -C /usr/src rev-list --first-parent --count HEAD`" && echo "freebsd/main (FreeBSD-CURRENT) Git commit count: $freebsdmaingitcommitcount" && set freebsdmaingithash="`git -C /usr/src rev-list --max-count=1 HEAD`" && echo "freebsd/main Git hash: $freebsdmaingithash" && echo "<https://cgit.freebsd.org/src/commit/?id=$freebsdmaingithash>" && echo "– in context: <https://cgit.freebsd.org/src/log/?qt=range&q=$freebsdmaingithash>"

Tested in a handful of browsers, I like that a command will run full width and wrap.

One browser (not mainstream) has trouble with the horizontal scroll bar, IMHO not reason enough to limit the width of code blocks.
 

kpedersen

Son of Beastie

Reaction score: 1,866
Messages: 2,746

Heh, to be fair, those commands should be split into new lines via '\'

Even if the text field was 1000 characters, it would be pretty manky to read!
 
Top