What are code tags?
Quote:
Thanks, LT |
Quote:
Code:
This text is in a code box (at least that is my term -- seems logical). You can wrap text in code tags two ways. One is to highlight the text and then click the hash (#) icon at the top of the edit box. (This isn't available on the "Quick Reply" box.) The other way is to type them in manually. If you don't know how to do that, hit the quote button on the bottom of this post, and look at what is between square brackets before and after the text in the code box above. (Assuming you don't want to actually respond to this post, I think you can just hit the back button on your browser after you have finished taking a look. If that screws up, just close the tab!) As an example of a screwed up posting, this is what a routing table looks like w/o the code tags: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 209.244.XX.XX 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 192.168.2.0 192.168.1.XX 255.255.255.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 209.244.XX.XXX 0.0.0.0 UG 0 0 0 ppp0 And this is with code tags: Code:
Kernel IP routing table |
Good info., nice post, thanks.
One addition: there seems to be a persistent bug* in the interaction between Konqueror (though ver. 3.5.8) & LQ that causes the horizontal scroll bars inside posts to be useless -- they scroll only about 10 or 50 pixels & almost always trigger horizontal scroll bars in the main browser window. Once any single post in a thread is "too wide" then all posts in the thread are too wide to read comfortably. The only cure is to switch to Opera, lynx, or even Firefox. Or not bother w/ the thread. The only cure while composing a post is to insert "hard" new lines in the post in otherwise unnatural places. Like this. I implore all posters who use "Code:" blocks & anything else that triggers horizontal scrolling, to limit their lines to roughly the same 72 characters that were available on punch cards. * I suspect the bug is in the CSS that LQ inherits from vBulletin, as I have the same problem on other vBulletin powered fora. |
Quote:
|
Of course it is, & I believe the correct procedure would be to file a bug report
-- only the last time I tried @ LQ, the bug reporter either wouldn't work for me. I think it would be equally appropriate to file w/ KDE & vBulletin. |
Quote:
|
I've moved this to LQ WS&F as it's something Jeremy may need to be aware of. He is very keen on LQ being as accessible to as many people as possible and especially for it work (as far as possible) on various browsers.
|
Quote:
|
Jeremy checks this forum regularly and will see anything that is new since he last checked. He is far less likely to see it in another forum or tacked onto the end of a different thread. So, yes.
|
I do indeed read every single thread in this forum. We're planning an upgrade in the near future. If that doesn't fix the bug we'll fix it ourselves and push it back upstream. Thanks.
--jeremy |
Code:
Kernel IP routing table |
Quote:
|
Now that LQ had just done a code upgrade, I thought this might be a good time to check if the problem with horiontal scrollbars with Konquorer had ever been solved. (See post #3 on this thread)
Also, when I went to post this, there was no "quick reply" box on this page. Is that a bug in the new software? I haven't noticed the problem on other pages. EDIT: That's really strange ... After posting this, the "quick reply" box appeared. Sounds like one of those "fun" subtle bugs. |
Scrolling: http://www.linuxquestions.org/questi...32#post3345132
As for the QRB, it's disabled for threads that have not gotten a reply in a certain amount of time. --jeremy |
FWIW, scrolling is still broken.
At least in KDE/Konq. 3.5.3 -- not sure about 3.5.8 ... (KDE 3.5.3 is what comes in SimplyMEPIS 6.0, which is based on Ubuntu Dapper 6.06 LTS repos, & so it has another 7 months to "live". I'm waiting for 8.0 to be stable before I upgrade.) |
All times are GMT -5. The time now is 02:53 AM. |