Sponsored Content
Top Forums Programming Open Source What editor does everyone use? Post 302531565 by linuxadmin on Friday 17th of June 2011 07:36:16 AM
Old 06-17-2011
is there any editor to run from there itself

it should run the Shell / perl from the editor itself..

and it should give the Output there itself , as in eclipse
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Vi editor ?

Hello everybody, My question is: how to add /tmp/work at the end of line in vi editor. my file looks like: cp file1 cp file2 cp file3 **** I need to add " /tmp/work" at the end of each line. I tried this :%s/$/" /tmp/work" and this :%s/$/\ /tmp/work\/ but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies

2. HP-UX

instead VI editor - which one?

I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one? thx (6 Replies)
Discussion started by: diamond
6 Replies

3. UNIX for Advanced & Expert Users

vi editor

Hi, how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before. for exemple if in my file i have line 1 line 2 I want to have : start line 1 end start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies

4. UNIX Desktop Questions & Answers

best editor

We work on AIX 5L We use vi as text editor (only scripts to create and modifiy). What do you think of emacs ? Where can I find it ? Do you know better text editor for scripts ? Thank you for all answers. (1 Reply)
Discussion started by: annemar
1 Replies

5. HP-UX

vi editor

I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work. how can I enable them. thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies

6. UNIX for Dummies Questions & Answers

Pasting text in VI editor from a different editor

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

7. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

Hi All, I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by set EDITOR=vi it does not open a vi editor , rather it do as below..... ///////////////////////////////////////////////////// $ set... (6 Replies)
Discussion started by: aarora_98
6 Replies

8. Solaris

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :Licen

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

9. Shell Programming and Scripting

About vi editor

How can ` character be printed on vi editor ? empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies

10. Shell Programming and Scripting

Not able to use @ in VI editor

Hello All, Need one Help for one issue. I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it. It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies
DBI::Shell(3)						User Contributed Perl Documentation					     DBI::Shell(3)

NAME
DBI::Shell - Interactive command shell for the DBI SYNOPSIS
perl -MDBI::Shell -e shell [<DBI data source> [<user> [<password>]]] or dbish [<DBI data source> [<user> [<password>]]] DESCRIPTION
The DBI::Shell module (and dbish command, if installed) provide a simple but effective command line interface for the Perl DBI module. DBI::Shell is very new, very experimental and very subject to change. Your milage will vary. Interfaces will change with each release. TO DO
Proper docs - but not yet, too much is changing. "/source file" command to read command file. Allow to nest via stack of command file handles. Add command log facility to create batch files. Commands: load (query?) from file save (query?) to file Use Data::ShowTable if available. Define DBI::Shell plug-in semantics. Implement import/export as plug-in module Clarify meaning of batch mode Completion hooks Set/Get DBI handle attributes Portability Emulate popular command shell modes (Oracle, Ingres etc)? COMMANDS
Many commands - few documented, yet! help /help chistory /chistory (display history of all commands entered) /chistory | YourPager (display history with paging) clear /clear (Clears the current command buffer) commit /commit (commit changes to the database) connect /connect (pick from available drivers and sources) /connect dbi:Oracle (pick source from based on driver) /connect dbi:YourDriver:YourSource i.e. dbi:Oracle:mysid Use this option to change userid or password. current /current (Display current statement in the buffer) do /do (execute the current (non-select) statement) dbish> create table foo ( mykey integer ) dbish> /do dbish> truncate table OldTable /do (Oracle truncate) drivers /drivers (Display available DBI drivers) edit /edit (Edit current statement in an external editor) Editor is defined using the enviroment variable $VISUAL or $EDITOR or default is vi. Use /option editor=new editor to change in the current session. To read a file from the operating system invoke the editor (/edit) and read the file into the editor buffer. exit /exit (Exits the shell) get /get (Retrieve a previous command to the current buffer) go /go (Execute the current statement) Run (execute) the statement in the current buffer. This is the default action if the statement ends with / dbish> select * from user_views/ dbish> select table_name from user_tables dbish> where table_name like 'DSP%' dbish> / dbish> select table_name from all_tables/ | more history /history (Display combined command and result history) /history | more option /option [option1[=value]] [option2 ...] /option (Displays the current options) /option MyOption (Displays the value, if exists, of MyOption) /option MyOption=4 (defines and/or sets value for MyOption) perl /perl (Evaluate the current statement as perl code) quit /quit (Leaves shell. Same as exit) redo /redo (Re-execute the previously executed statement) rhistory /rhistory (Display result history) rollback /rollback (rollback changes to the database) For this to be useful, turn the autocommit off. /option autocommit=0 table_info /table_info (display all tables that exist in current database) /table_info | more (for paging) trace /trace (set DBI trace level for current database) Adjust the trace level for DBI 0 - 4. 0 off. 4 is lots of information. Useful for determining what is really happening in DBI. See DBI. type_info /type_info (display data types supported by current server) AUTHORS and ACKNOWLEDGEMENTS The DBI::Shell has a long lineage. It started life around 1994-1997 as the pmsql script written by Andreas Konig. Jochen Wiedmann picked it up and ran with it (adding much along the way) as dbimon, bundled with his DBD::mSQL driver modules. In 1998, around the time I wanted to bundle a shell with the DBI, Adam Marks was working on a dbish modeled after the Sybase sqsh utility. Wanting to start from a cleaner slate than the feature-full but complex dbimon, I worked with Adam to create a fairly open modular and very configurable DBI::Shell module. Along the way Tom Lowery chipped in ideas and patches. As we go further along more useful code and concepts from Jochen's dbimon is bound to find it's way back in. COPYRIGHT
The DBI::Shell module is Copyright (c) 1998 Tim Bunce. England. All rights reserved. Portions are Copyright by Jochen Wiedmann, Adam Marks and Tom Lowery. You may distribute under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file. perl v5.8.0 2002-11-29 DBI::Shell(3)
All times are GMT -4. The time now is 11:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy