09-13-2008
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Redhat 9
I want to change my default text editor from vi to pico.
When I look in the .bash_profile or .bashrc I do not see the EDITOR variable. So how do I change the default permanently? (1 Reply)
Discussion started by: Tony Empire
1 Replies
2. AIX
For some reason something has changing in my AIX environment where when I type:
ACLEDIT filename
...I get:
3002-104 acledit: EDITOR environment variable must be full pathname
I know I need to reset the EDITOR variables path to /usr/bin/vi but I can't remember the syntax anyone? (2 Replies)
Discussion started by: heprox
2 Replies
3. Solaris
Hi all
I am new to this forum (just registered)
I need help from you guys
Even if it is a basic question please don't hesitate to answer.Any answer will be helpful to me
I am unable to get the previously entered commands by pressing uparrow
When i enered uparrow it is giving ^[[A
I got... (2 Replies)
Discussion started by: oracle_sri
2 Replies
4. Solaris
hi guys , i need some help
i want to set cron job for every sunday , of each month so any body plz help or this proble :confused: (1 Reply)
Discussion started by: Kbharat20
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
6. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
7. Solaris
I am setting the size using "stty columns 120" . But I still get the prompt saying "terminal too wide " when I am in vi.
is there any time limit for this setting?
how to set the column size to 120 permanently?
Thanks in advance,
Devi (4 Replies)
Discussion started by: pvkdevi
4 Replies
8. UNIX for Dummies Questions & Answers
Guys,
Can somebody help in setting vi as the default editor in zsh shell.
I know that in ksh and bourne we can achieve the setting through .profile file.
I want to replicate the behavior of ksh in zsh where on command prompt when one presses escape the screen acts as a vi.
And one can use all... (1 Reply)
Discussion started by: yabhi_22
1 Replies
9. UNIX for Dummies Questions & Answers
Hi ,
Below is the content of my .profile
$cat .profile
# Workstation users: Make changes to your .profile file in your home dir.
. /.profile
set -o vi
PS1=$
But anytime I login I have to source "set -o vi" separately.Please suggest (8 Replies)
Discussion started by: ramesh12621
8 Replies
10. UNIX Desktop Questions & Answers
Hello All,
Last night I installed OpenSuSE 12.1 (i586) on a HP Mini 110 laptop. And I selected GNOME as my Desktop during install...
So I was trying to customize some things about the desktop, for example adding the Maximize/Minimize/Close options to the titlebar of a window.
I did this... (2 Replies)
Discussion started by: mrm5102
2 Replies
LEARN ABOUT DEBIAN
shell-quote
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)