01-10-2011
Quote:
Originally Posted by
fpmurphy
Jlovi, you started off with a purported problem with ksh93 on AIX. Now you are talking about Konsole on Fedora/KDE using readline. What exactly are you trying to achieve, under what shell and on what platform? You need to spell it out for us!
My stations is a Fedora/KDE system, I use Konsole in order to connect to an AIX server, using ssh. The script runs on the AIX server. You were talking of terminal issues, that's why I mentionned my workstation. And "read line" is in two words
.
However, I'm a bit skeptical about a terminal issue since it works in ksh88, but not in ksh93. Looks like a specific bug or feature. IMHO, ksh93 is not as stable as ksh88, as I get something coredumps in ksh93 for things that work in ksh88.
Currenly my script works perfectly in ksh88 but I have experimental code that requires ksh93 (for keybinding), that's why I'd like to make it work with this latest version of ksh.
Last edited by jlovi; 01-10-2011 at 03:24 PM..
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi.
i´m working in bash and am trying to create a Perl daemon that controls bash´s behavior. this is actually in preparation for a later project i´ll be working on.
basically, i´m looking for a way to have the Perl daemon tell bash what to do. i already have a small daemon that simply prints... (2 Replies)
Discussion started by: deryk
2 Replies
2. Shell Programming and Scripting
I'm getting rather frustrated with an interactive script I'm writing.
The script is divided up, with section for setting variable at the top, then functions (which make up most of the script) then basically a line at the end which calls the first function- the program moves between the... (5 Replies)
Discussion started by: alexop
5 Replies
3. Shell Programming and Scripting
in a ksh script, i want to process
some string variables using awk,
and then i want to go on using this variables
in the same ksh (out of awk lines)
can anybody send me a very simple example about this? (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies
4. Shell Programming and Scripting
Hi all,
I'm having a rather peculiar problem involving parameter passing with declared functions in my shell script. Hope to get some advice here.
A brief description of my code is as follows:
However, I'm not getting the results I wanted. If I pass in $rdir, I'm going to end up... (4 Replies)
Discussion started by: rockysfr
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I was trying to customize this archaic HP-UX box. only shell available is ksh and that too seems to be pretty old and doesn't completely conform to what I read on the web about ksh. Anyway here are my issues:
- I wanted to have a dynamic title on xterm or dtterm. I put the following lines... (2 Replies)
Discussion started by: anurags
2 Replies
6. UNIX for Advanced & Expert Users
As you are probably aware, $# indicates the number of parameters passed into a korn shell script. But this appears to hang around for
sunsequent runs...????
A simple script:-
#!/usr/bin/ksh
echo "#parameters $#"
echo "\$1 $1"
echo "\$2 $2"
I run the script with 0 parameters (all fine)
#... (7 Replies)
Discussion started by: gsw_aix
7 Replies
7. Shell Programming and Scripting
Hello,
I would like to understand this... I'm using ksh and doing
(( z = y - 1 ))
if y=34, then the result for z is 33, but if y=034 the result is z=27. Why??
Thanks (15 Replies)
Discussion started by: fbg
15 Replies
8. Shell Programming and Scripting
Hi All,
I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data.
If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But... (9 Replies)
Discussion started by: DILEEP410
9 Replies
9. Shell Programming and Scripting
Hi,
I have a strange problem with arrays in Perl.
That is to say, for me it is strange and perhaps there is a special reason for it that I do not know of.
Not a real Perl Ace.
This is the program, as an example:
#!/usr/bin/perl -w #-d
use strict;
my $pu;
my $pu_list_cmd;
my... (2 Replies)
Discussion started by: ejdv
2 Replies
LEARN ABOUT OPENSOLARIS
print
print(1) User Commands print(1)
NAME
print - shell built-in function to output characters to the screen or window
SYNOPSIS
ksh
print [-Rnprsu [n]] [arg]...
ksh93
print [-Renprs] [-f format] [-u fd] [string...]
DESCRIPTION
ksh
The shell output mechanism. When no options are specified, or when an option followed by ' a - is specified, or when just - is specified,
the arguments are printed on standard output as described by echo(1).
ksh93
By default, print writes each string operand to standard output and appends a NEWLINE character.
Unless, the -r, -R, or -f option is speciifed, each character in each string operand is processed specially as follows:
a Alert character.
Backspace character.
c Terminate output without appending NEWLINE. The remaining string operands are ignored.
E Escape character (ASCII octal 033).
f FORM FEED character.
NEWLINE character.
Tab character.
v Vertical tab character.
\ Backslash character.
x The 8-bit character whose ASCII code is the 1-, 2-, or 3-digit octal number x.
OPTIONS
ksh
The following options are supported by ksh:
-n Suppresses new-line from being added to the output.
-r-R Raw mode. Ignore the escape conventions of echo. The -R option prints all subsequent arguments and options other than -n.
-p Cause the arguments to be written onto the pipe of the process spawned with |& instead of standard output.
-s Cause the arguments to be written onto the history file instead of standard output.
-u [ n ] Specify a one digit file descriptor unit number n on which the output is placed. The default is 1.
ksh93
The following options are supported by ksh93:
-e Unless -f is specified, process sequences in each string operand as described above. This is the default behavior.
If both -e and -r are specified, the last one specified is the one that is used.
-f format Write the string arguments using the format string format and do not append a NEWLINE. See printf(1) for details on how to
specify format.
When the -f option is specified and there are more string operands than format specifiers, the format string is reprocessed
from the beginning. If there are fewer string operands than format specifiers, then outputting ends at the first unneeded for-
mat specifier.
-n Do not append a NEWLINE character to the output.
-p Write to the current co-process instead of standard output.
-r Do not process sequences in each string operand as described above.
-R
If both -e and -r are specified, the last one specified is the one that is used.
-s Write the output as an entry in the shell history file instead of standard output.
-u fd Write to file descriptor number fd instead of standard output. The default value is 1.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 Output file is not open for writing.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
echo(1), ksh(1), ksh93(1), printf(1), attributes(5)
SunOS 5.11 27 Mar 2008 print(1)