Sponsored Content
Full Discussion: Vi issue with solaris
Operating Systems Solaris Vi issue with solaris Post 302464592 by DGPickett on Wednesday 20th of October 2010 01:19:18 PM
Old 10-20-2010
I would choose sed or ex in a script. The vi is too screen oriented for script life, unless you are into firing your optical neurons a lot, usually not a cash deliverable.

Do you need to know what happened inside vi using the $? 0/1 behavior?

BTW, I have a vi wrapper I call vix:
  • for (some) xterms, it saves my scroll history: drives the on screen text up by screen size lines, then calls vi
  • for ksh command editing, set -o vi/viraw, export $EDITOR=~/bin/vix: always returns 0 so my output is not discarded by ksh.
Code:
#!/usr/bin/ksh

(
 stty -a | sed '
        s/^/ /
        t a
        :a
        s/.* rows = \([1-9][0-9]*\).*/\1/
        t
        d
        ' | read zr

# echo $zr >&2

 if [ "$zr" = "" ]
 then
  zr=25
 fi

 while [ "$zr" != -1 ]
 do
  zr=$(( $zr - 1 ))
  echo >/dev/tty
  done

 vi "$@"

 exit 0
)

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris 10 auth issue

Very strange one, we've got a recently build server (Sol10 via JET flash). Bascially you can ssh to it fine, but telnet will allow entry of username, but will then feed in a carriage return on the passwd field, this also happens on any auth type command, ie passwd on a user account will also... (4 Replies)
Discussion started by: itsupplies
4 Replies

2. Solaris

CDE Issue In Solaris 10

Hi All, I have solaris 10 on X86 and I need to connect this through X-Manager or similar software. I have googled a lot and tried the following : root@sol10x86 # ps -ef |grep dtlogin root 1825 4718 0 13:38:50 pts/1 0:00 grep dtlogin root@sol10x86 # svcs cde-login STATE ... (2 Replies)
Discussion started by: pintu_asim
2 Replies

3. Solaris

Solaris Issue

Hi, I am having a serious problem with a Solaris 2.6 box. Whenever I try and tar a large directory I get this error:tar: write error: unexpected EOF My own research shows that I might have to enable tarring large files by this command: fsadm -o largefiles <mountpoint> My box does not... (8 Replies)
Discussion started by: mojoman
8 Replies

4. Solaris

du -sh issue in solaris 10

i have 30 file systems on my production system and my system is responding too slow and / is 99% full is there any way i can run the du -sh only on root file systems and skip all the SAN file systems as the system is unable to do du -sdh * / as it would try to run du on all the SAN/NAS file... (5 Replies)
Discussion started by: fugitive
5 Replies

5. Solaris

Printing Issue On Solaris 10

Synopsis: Solaris 10 SunFire v880 with two networked HP laser printers set up through HPPI. Test page will print through HPPI but can't print to them us the lp command. When using the lp command it just hangs and causes the Samba process to fail. We have a SunFire v880 running Solaris 10. $$... (1 Reply)
Discussion started by: KenLynch
1 Replies

6. UNIX for Dummies Questions & Answers

grep issue (Solaris)

Can anyone explain this (i.e. why the 2nd grep does not find anything)?: -bash-3.00$ cat tmp.log sftp> chdir /home/test-dir sftp> mget thosefiles*.txt File "/home/test-dir/thosefiles*.txt" not found. -bash-3.00$ grep "s*.txt" tmp.log sftp> mget thosefiles*.txt File... (4 Replies)
Discussion started by: dhebden
4 Replies

7. Solaris

Solaris 11 disk issue

I have 2 disks in my system.I recently added a zpool to the disk, but today I changed my mind and deleted the zpool , zpool destroy -f extra The zpool is now deleted and I want to partition the disk, so I delete the only partition on the disk. Now when I run format again, format... (13 Replies)
Discussion started by: cbtshare
13 Replies

8. Solaris

Solaris version issue

Hi Friends, I am new in solaris. yesterday i installed solaris in VM. now while installing weblogic setup(.bin) its giving me Invalid argument error. after some google i have two points in my mind 1) i am using solaris on intel machine. thats why i am facing this issue. If answer is yes... (3 Replies)
Discussion started by: Vishal Baghla
3 Replies

9. Shell Programming and Scripting

X Forwarding issue on Solaris 11

Hello All , Need assistance in finding out a solution for X Forwarding issue IBM applications requires X Forwarding . Server X11 works fine when i try xclock but not this application . On a different server with the same OS it is working . Need inputs . OS Version : Solaris 11 with updated... (1 Reply)
Discussion started by: ajayram_arya
1 Replies

10. Solaris

Cipher issue on Solaris 11.4

Hi, Our most of servers are on Solaris 11.2 (with no SRU). Recently I upgraded one of them to Solaris 11.4. It has to go in multiple steps, as it can not jump fro 11.2 to 11.4 in one go. After upgrading, I can not login to server with SecureCRT and it through error key exchange failed: cipher... (1 Reply)
Discussion started by: solaris_1977
1 Replies
shell_builtins(1)														 shell_builtins(1)

NAME
shell_builtins, case, for, foreach, function, if, repeat, select, switch, until, while - shell command interpreter built-in commands The shell command interpreters csh(1), ksh(1), and sh(1) have special built-in commands. The commands case, for, foreach, function, if, repeat, select, switch, until, and while are commands in the syntax recognized by the shells. They are described in the Commands section of the manual pages of the respective shells. The remaining commands listed in the table below are built into the shells for reasons such as efficiency or data sharing between command invocations. They are described on their respective manual pages. | Command | Shell alias |csh, ksh bg |csh, ksh, sh break |csh, ksh, sh case |csh, ksh, sh cd |csh, ksh, sh chdir |csh, sh continue |csh, ksh, sh dirs |csh echo |csh, ksh, sh eval |csh, ksh, sh exec |csh, ksh, sh exit |csh, ksh, sh export |ksh, sh false |ksh fc |ksh fg |csh, ksh, sh for |ksh, sh foreach |csh function |ksh getopts |ksh, sh glob |csh goto |csh hash |ksh, sh hashstat |csh history |csh if |csh, ksh, sh jobs |csh, ksh, sh kill |csh, ksh, sh let |ksh limit |csh login |csh, ksh, sh logout |csh, ksh, sh nice |csh newgrp |ksh, sh nohup |csh notify |csh onintr |csh popd |csh print |ksh pushd |csh pwd |ksh, sh read |ksh, sh readonly |ksh, sh rehash |csh repeat |csh return |ksh, sh select |ksh set |csh, ksh, sh setenv |csh shift |csh, ksh, sh source |csh stop |csh, ksh, sh suspend |csh, ksh, sh switch |csh test |ksh, sh time |csh times |ksh, sh trap |ksh, sh true |ksh type |ksh, sh typeset |ksh ulimit |ksh, sh umask |csh, ksh, sh unalias |csh, ksh unhash |csh unlimit |csh unset |csh, ksh, sh unsetenv |csh until |ksh, sh wait |csh, ksh, sh whence |ksh while |csh, ksh, sh Bourne Shell, sh, Special Commands Input/output redirection is now permitted for these commands. File descriptor 1 is the default output location. When Job Control is enabled, additional Special Commands are added to the shell's environment. In addition to these built-in reserved command words, sh also uses: : No effect; the command does nothing. A zero exit code is returned. .filename Read and execute commands from filename and return. The search path specified by PATH is used to find the directory con- taining filename. C shell, csh Built-in commands are executed within the C shell. If a built-in command occurs as any component of a pipeline except the last, it is exe- cuted in a subshell. In addition to these built-in reserved command words, csh also uses: : Null command. This command is interpreted, but performs no action. Korn Shell, ksh, Special Commands Input/Output redirection is permitted. Unless otherwise indicated, the output is written on file descriptor 1 and the exit status, when there is no syntax error, is zero. Commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. In addition to these built-in reserved command words, ksh also uses: * : [ arg ... ] The command only expands parameters. * .file [ arg ..Read the complete file then execute the commands. The commands are executed in the current shell environment. The search path specified by PATH is used to find the directory containing file. If any arguments arg are given, they become the posi- tional parameters. Otherwise, the positional parameters are unchanged. The exit status is the exit status of the last com- mand executed. the loop termination test. intro(1), alias(1), break(1), cd(1), chmod(1), csh(1), echo(1), exec(1), exit(1), find(1), getoptcvt(1), getopts(1), glob(1), hash(1), his- tory(1), jobs(1), kill(1), ksh(1), let(1), limit(1), login(1), logout(1), newgrp(1), nice(1), nohup(1), print(1), pwd(1), read(1), read- only(1), set(1), sh(1), shift(1), suspend(1), test(1B), time(1), times(1), trap(1), typeset(1), umask(1), wait(1), chdir(2), chmod(2), creat(2), umask(2), getopt(3C), profile(4), environ(5) 29 Jun 2005 shell_builtins(1)
All times are GMT -4. The time now is 10:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy