LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Message:
You should include as much detail as possible in your message, including exact error messages (where applicable) and what you have done so far. The more detail you include the more we can help. You should also use the board's search feature to ensure that the question has not already been asked.
something along the lines of:
Quote:
To improve the readability of your post wrap commands or command output ( error messages and the like ) with [code][/code] 'tags'
example:
[code]
SomeCommand arg1 arg2 /path/to/somefile
bash: SomeCommand: command not found
[/code]
This preserves 'white space' and forces the use of a fixed width font
for convenience highlight the command/output and click the # button
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by Firerat
The question is "how do we fix this?"
That is a good question. Unfortunately I don't think appending to that message will help the issue (nor is it a scalable solution). I'd suggest 1) educating the member who didn't use the code tag about it, along with suggesting that they edit their post to include them. 2) If that doesn't work, report the post so the code tags can be added by a mod.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
Quote:
Originally Posted by ntubski
I would suggest:
Change the icon to something that is more obviously code, have the actual word "code" on the button perhaps.
Putting aside the aesthetics of putting a word in a button that small, as that exact button is used in every CKEditor instance around the web I think a change would actually be a net loss.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.