Sponsored Content
The Lounge What is on Your Mind? Should We Keep or Drop the Bottom Toolbar? Post 302682013 by bakunin on Sunday 5th of August 2012 07:37:25 AM
Old 08-05-2012
Quote:
Originally Posted by Neo
So, i think we are unique in that we really try to think about our members and insure they have a choice on what features to enable and disable.
Amen to that! This is what sets apart our forum from the myriads of others, IMHO.

Quote:
Originally Posted by vernalbrat
And, if not, then we can click on 'minimize toolbar'. I say, let's keep it.
In principle this is true, but there is always the performance argument: any new feature will cost resources in one or other way while introducing a new (if slight) risk of making something break. To keep the forum as fast and reliable as possible Neo tries to determine not only if the people are annoyed by it or not, but also, if the effort matches the positive effect. If not enough people really use this or any other feature (even a minority might be "enough" in this sense) then it makes sense not to offer an opt-out but to deinstall it.

bakunin
This User Gave Thanks to bakunin For This Post:
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HP-UX toolbar help

Hi all, I am trying to set some icons in the toolbar thingy (HP-UX 10.2). I used the Toolboxes->Personal to help me setup, but it put the program icon in the personal toolbox folder. So I dragged it out to the Desktop. Now I've a link on a Desktop. Any ideas on how to create directly on to... (2 Replies)
Discussion started by: nitin
2 Replies

2. UNIX and Linux Applications

Showing all open programs on your bottom toolbar

http://i255.photobucket.com/albums/hh133/COKEDUDEUSF/toolbar.jpg Take a look at my picture to understand what I'm talking about. I have a bunch of programs open right now and I can't see the name of the programs on my toolbar. Is there hopefully a way to see all open programs on your toolbar... (1 Reply)
Discussion started by: cokedude
1 Replies

3. What is on Your Mind?

Change Toolbar to Opt In?

Hey! I'm thinking we should change the toolbar to "opt in" and have it off for members by default? But then, the would not have toolbar access to the code tag videos, etc. so then I thought to make it "opt in" after say 30 posts. That way, the toolbar will show to all new users with less... (5 Replies)
Discussion started by: Neo
5 Replies
SHELL-QUOTE(1p) 					User Contributed Perl Documentation					   SHELL-QUOTE(1p)

NAME
shell-quote - quote arguments for safe use, unmodified in a shell command SYNOPSIS
shell-quote [switch]... arg... DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands or files with embedded white space or shell globbing characters safely. Here are a few examples. EXAMPLES
ssh preserving args When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and passes them to "$SHELL -c". This doesn't work as intended: ssh host touch 'hi there' # fails It creates 2 files, hi and there. Instead, do this: cmd=`shell-quote touch 'hi there'` ssh host "$cmd" This gives you just 1 file, hi there. process find output It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote: eval set -- `find -type f -print0 | xargs -0 shell-quote --` debug shell scripts shell-quote is better than echo for debugging shell scripts. debug() { [ -z "$debug" ] || shell-quote "debug:" "$@" } With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can. save a command for later shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are things the user can't pass through), you can do something like this: user_switches= while [ $# != 0 ] do case x$1 in x--pass-through) [ $# -gt 1 ] || die "need an argument for $1" user_switches="$user_switches "`shell-quote -- "$2"` shift;; # process other switches esac shift done # later eval "shell-quote some-command $user_switches my args" OPTIONS
--debug Turn debugging on. --help Show the usage message and die. --version Show the version number and exit. AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions. AUTHOR
Roderick Schertler <roderick@argon.org> perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)
All times are GMT -4. The time now is 04:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy