LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > LinuxQuestions.org > LQ Suggestions & Feedback
User Name
Password
LQ Suggestions & Feedback Do 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


Reply
  Search this Thread
Old 07-12-2013, 04:12 PM   #1
Firerat
Senior Member
 
Registered: Oct 2008
Distribution: Debian Jessie / sid
Posts: 1,471

Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
no [spoiler] BBcode tags


There are times when I decide to myself that a section of something I have posted is excessively long.
I usually wrap these with [spoiler] BBcode, which presents the reader with a button to unhide the content.

Makes for scrolling past large blocks of text ( some long log for instance ) much faster

I checked with BB code and it is not featured.

Any chance we can have spolier tags?
or did I just miss something ?

Cheers
 
Old 07-12-2013, 04:14 PM   #2
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 6,860

Rep: Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958Reputation: 1958
I've not seen those but they sound interesting for both the purpose Firerat uses them for and their [presumed] original purpose also.
 
Old 07-12-2013, 04:43 PM   #3
ntubski
Senior Member
 
Registered: Nov 2005
Distribution: Debian, Arch
Posts: 3,239

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Quote:
Originally Posted by Firerat View Post
Makes for scrolling past large blocks of text ( some long log for instance ) much faster
[CODE][/CODE] tag boxes get their own scrollbars so they don't take up much space. This has the advantage of not requiring JavaScript to work.
 
1 members found this post helpful.
Old 07-12-2013, 05:07 PM   #4
Firerat
Senior Member
 
Registered: Oct 2008
Distribution: Debian Jessie / sid
Posts: 1,471

Original Poster
Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
Hi ntubski, I see what you are saying
here is the post which prompted my request

I used code boxes, which made !little impact

going to press a js button now
 
Old 07-12-2013, 09:56 PM   #5
ntubski
Senior Member
 
Registered: Nov 2005
Distribution: Debian, Arch
Posts: 3,239

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Quote:
Originally Posted by Firerat View Post
here is the post which prompted my request

I used code boxes, which made !little impact
Oh, you have multiple boxes with none of them being large enough to get scrollbar'd. Here is the "spoiler" stuff all in one box:

Code:
sudo dp<tab><tab>

# gets you something like this

dpkg                     dpkg-genchanges          dpkg-scansources
dpkg-architecture        dpkg-gencontrol          dpkg-shlibdeps
dpkg-buildflags          dpkg-gensymbols          dpkg-source
dpkg-buildpackage        dpkg-maintscript-helper  dpkg-split
dpkg-checkbuilddeps      dpkg-mergechangelogs     dpkg-statoverride
dpkg-cross               dpkg-name                dpkg-trigger
dpkg-deb                 dpkg-parsechangelog      dpkg-vendor
dpkg-depcheck            dpkg-preconfigure        dprofpp
dpkg-distaddfile         dpkg-query               dput
dpkg-divert              dpkg-reconfigure         
dpkg-genbuilddeps        dpkg-scanpackages     

# and 

sudo dpkg<tab><tab><tab>

sudo dpkg --
--abort-after                  --ignore-depends=              --refuse-downgrade
--add-architecture             --install                      --remove
--admindir=                    --instdir=                     --remove-architecture
--assert-multi-arch            --list                         --root=
--assert-working-epoch         --listfiles                    --search
--audit                        --log=                         --selected-only
--auto-deconfigure             --merge-avail                  --set-selections
--clear-avail                  --no-act                       --skip-same-version
--clear-selections             --no-debsig                    --status
--compare-versions             --no-force-                    --status-fd
--configure                    --no-triggers                  --status-logger=
--debug=                       --path-exclude=                --triggers
--extract                      --path-include=                --triggers-only
--force-                       --print-architecture           --unpack
--force-help                   --print-avail                  --update-avail
--forget-old-unavail           --print-foreign-architectures  --version
--get-selections               --purge                        
--help                         --record-avail
Perhaps not ideal, as you have to do extra work to distinguish the intervening comments, but it's effective for a big log file. What you posted isn't really all that big, so it doesn't help very much.

Alternate solution: post it to your LQ blog, and just put a link in the thread.
 
Old 07-12-2013, 11:33 PM   #6
Firerat
Senior Member
 
Registered: Oct 2008
Distribution: Debian Jessie / sid
Posts: 1,471

Original Poster
Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
Quote:
Originally Posted by ntubski View Post
Oh, you have multiple boxes with none of them being large enough to get scrollbar'd. Here is the "spoiler" stuff all in one box:

Code:
sudo dp<tab><tab>

# gets you something like this

dpkg                     dpkg-genchanges          dpkg-scansources
dpkg-architecture        dpkg-gencontrol          dpkg-shlibdeps
dpkg-buildflags          dpkg-gensymbols          dpkg-source
dpkg-buildpackage        dpkg-maintscript-helper  dpkg-split
dpkg-checkbuilddeps      dpkg-mergechangelogs     dpkg-statoverride
dpkg-cross               dpkg-name                dpkg-trigger
dpkg-deb                 dpkg-parsechangelog      dpkg-vendor
dpkg-depcheck            dpkg-preconfigure        dprofpp
dpkg-distaddfile         dpkg-query               dput
dpkg-divert              dpkg-reconfigure         
dpkg-genbuilddeps        dpkg-scanpackages     

# and 

sudo dpkg<tab><tab><tab>

sudo dpkg --
--abort-after                  --ignore-depends=              --refuse-downgrade
--add-architecture             --install                      --remove
--admindir=                    --instdir=                     --remove-architecture
--assert-multi-arch            --list                         --root=
--assert-working-epoch         --listfiles                    --search
--audit                        --log=                         --selected-only
--auto-deconfigure             --merge-avail                  --set-selections
--clear-avail                  --no-act                       --skip-same-version
--clear-selections             --no-debsig                    --status
--compare-versions             --no-force-                    --status-fd
--configure                    --no-triggers                  --status-logger=
--debug=                       --path-exclude=                --triggers
--extract                      --path-include=                --triggers-only
--force-                       --print-architecture           --unpack
--force-help                   --print-avail                  --update-avail
--forget-old-unavail           --print-foreign-architectures  --version
--get-selections               --purge                        
--help                         --record-avail
Perhaps not ideal, as you have to do extra work to distinguish the intervening comments, but it's effective for a big log file. What you posted isn't really all that big, so it doesn't help very much.

Alternate solution: post it to your LQ blog, and just put a link in the thread.
I do not have a blog
no intention of having
one

so F off ya knob
 
Old 07-13-2013, 05:58 AM   #7
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,361
Blog Entries: 55

Rep: Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547
Quote:
Originally Posted by Firerat View Post
so F off ya knob
The language you used is unwarranted and unacceptable. Inform yourself about the LQ Rules you agreed to adhere to when you signed up for the account: http://www.linuxquestions.org/linux/rules.html and do not do that again.
 
Old 07-13-2013, 11:44 AM   #8
ntubski
Senior Member
 
Registered: Nov 2005
Distribution: Debian, Arch
Posts: 3,239

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Quote:
Originally Posted by Firerat View Post
I do not have a blog
no intention of having
one
If the word "blog" upsets you, you could use the wiki instead. The downside is that wiki accounts are separate from LQ so an extra step is needed.
 
Old 07-13-2013, 11:51 AM   #9
Firerat
Senior Member
 
Registered: Oct 2008
Distribution: Debian Jessie / sid
Posts: 1,471

Original Poster
Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
Quote:
Originally Posted by ntubski View Post
If the word "blog" upsets you, you could use the wiki instead. The downside is that wiki accounts are separate from LQ so an extra step is needed.
You are offering solutions which simply do not fit the problem.
why do you not see this?
 
Old 07-13-2013, 03:18 PM   #10
ntubski
Senior Member
 
Registered: Nov 2005
Distribution: Debian, Arch
Posts: 3,239

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Quote:
Originally Posted by Firerat View Post
You are offering solutions which simply do not fit the problem.
why do you not see this?
I see the problem differently. I don't think it's a good idea to hide useful info behind a mouse click, but if you really want to, putting it behind a link seems as good as a button.

The post you linked to doesn't seem that long to me: I scroll past with 2 taps of the space bar. For the long log file case, a [CODE][/CODE] box seems like the best solution (and the monospace font is usually more appropriate for a log file anyway).


Anyway, it probably doesn't cost much to enable a [spoiler] tag, even though I doubt I'll find any use for it myself.
 
Old 07-13-2013, 03:41 PM   #11
Firerat
Senior Member
 
Registered: Oct 2008
Distribution: Debian Jessie / sid
Posts: 1,471

Original Poster
Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
Quote:
Originally Posted by ntubski View Post
I see the problem differently. I don't think it's a good idea to hide useful info behind a mouse click, but if you really want to, putting it behind a link seems as good as a button.
Linking is a bit of a faff, first have to go off and create the content, much easier to just wrap with spoiler tags

Quote:
Originally Posted by ntubski View Post
The post you linked to doesn't seem that long to me: I scroll past with 2 taps of the space bar. For the long log file case, a [CODE][/CODE] box seems like the best solution (and the monospace font is usually more appropriate for a log file anyway).
It is not really the best example, it just happened that I wanted to make it easier for people to just skip over it.
this post on forum.cyanogenmod.com is a better example a post from many many moons ago.


Quote:
Originally Posted by ntubski View Post
Anyway, it probably doesn't cost much to enable a [spoiler] tag, even though I doubt I'll find any use for it myself.
No, I didn't think it would cost much either
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Allowed BBCode in social groups Kenny_Strawn LQ Suggestions & Feedback 2 09-01-2010 11:23 PM
[SOLVED] BBCode replacement technique in PHP - using regular expressions vharishankar Programming 12 07-13-2009 01:15 AM
After Editing Tags with JuK - XMMS do not display tags correctly Artik Linux - Software 0 07-23-2005 06:55 AM
use BBCode in PHP script Boby Programming 2 08-22-2004 12:01 PM
BBCode and Smiley button issue revived... sewer_monkey LQ Suggestions & Feedback 2 06-27-2002 10:22 AM

LinuxQuestions.org > Forums > LinuxQuestions.org > LQ Suggestions & Feedback

All times are GMT -5. The time now is 03:25 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration