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.
I was posting in the hardware forum the other day and it can be difficult to know what information to include when you're not sure where the problem might be. At the same time it is quite annoying to scroll through posts with hundreds of lines of unnecessary code.
Is it possible to make collapsible parts of a post so you could add output from several commands/files and then people could click on a "plus" next to the filename to see the output if they feel it is relevant?
This would make posts easier to read, and you could add more information without being afraid of scaring people away.
I think the quote and code boxes can be collapsible. That would not require much coding. IN fact, I think a tiny bit of Javascript or CSS would do the trick.
I can see the point and usefulness of the idea were it used intellegently.
Most people who post huge amounts of data, do not use the "code" vb code though (which is limited in size already). Instead the post the entire load into the main body of the message.
It strikes me that the idea requires a user to think to use it, and know how to use it best (the title or first line in front of the [+] would need to be informative for eg.) ... users have enough trouble just writing informative titles.
OTOH:
Reverse the idea: expanding boxes...
perhaps a quote or code box could display only the first two or three lines by default... but can be expanded to a popup (say) or just to full length at a click? These boxes then occupy less space.
Doesn't solve the "here is my syslog in the main body" post though.
OTOH:
Reverse the idea: expanding boxes...
perhaps a quote or code box could display only the first two or three lines by default... but can be expanded to a popup (say) or just to full length at a click? These boxes then occupy less space.
Yes this is more or less what I had in mind. I know the boxes are already limited in size, but I would prefer expanding boxes to these minipages that steal the scroll focus when I'm trying to get further down the page
Quote:
Originally Posted by Simon Bridge
Doesn't solve the "here is my syslog in the main body" post though.
Well, no. You can't guarantee that people will use it, but perhaps if enough people start out more will follow if they like the idea?
I think for posts > a certain word count, you can make it automatically collapsed by displaying just a short summary (or the first few lines). And then give the users to expand it if necessary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.