12-12-2005
Hi friends ,
I got the solution to my problem. i feel to discuss it in the form, so that others will be benifitted ...
At cmd prompt I just have to write two lines
EDITOR=vi;
export EDITOR
Now, crontab -e will open a vi editor for me. :-)
Chow.
Aru
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
LDBEDIT(1) User Commands LDBEDIT(1)
NAME
ldbedit - Edit LDB databases using your preferred editor
SYNOPSIS
ldbedit [-?] [--usage] [-s base|one|sub] [-b basedn] [-a] [-e editor] [-H LDB-URL] [expression] [attributes...]
DESCRIPTION
ldbedit is a utility that allows you to edit LDB entries (in tdb files, sqlite files or LDAP servers) using your preferred editor. ldbedit
generates an LDIF file based on your query, allows you to edit the LDIF, and then merges that LDIF back into the LDB backend.
OPTIONS
-?, --help
Show list of available options, and a phrase describing what that option does.
--usage
Show list of available options. This is similar to the help option, however it does not provide any description, and is hence shorter.
-H <ldb-url>
LDB URL to connect to. For a tdb database, this will be of the form tdb://filename. For a LDAP connection over unix domain sockets,
this will be of the form ldapi://socket. For a (potentially remote) LDAP connection over TCP, this will be of the form ldap://hostname.
For an SQLite database, this will be of the form sqlite://filename.
-s one|sub|base
Search scope to use. One-level, subtree or base.
-a, -all
Edit all records. This allows you to apply the same change to a number of records at once. You probably want to combine this with an
expression of the form "objectclass=*".
-e editor, --editor editor
Specify the editor that should be used (overrides the VISUAL and EDITOR environment variables). If this option is not used, and neither
VISUAL nor EDITOR environment variables are set, then the vi editor will be used.
-b basedn
Specify Base Distinguished Name to use.
-v, --verbose
Make ldbedit more verbose about the operations that are being performed. Without this option, ldbedit will only provide a summary
change line.
ENVIRONMENT
LDB_URL
LDB URL to connect to. This can be overridden by using the -H command-line option.)
VISUAL and EDITOR
Environment variables used to determine what editor to use. VISUAL takes precedence over EDITOR, and both are overridden by the -e
command-line option.
VERSION
This man page is correct for version 4.0 of the Samba suite.
SEE ALSO
ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)
AUTHOR
ldb was written by Andrew Tridgell.
If you wish to report a problem or make a suggestion then please see the : http://ldb.samba.org/ web site for current contact and
maintainer information.
This manpage was written by Jelmer Vernooij and updated by Brad Hards.
Samba 3.5 06/18/2010 LDBEDIT(1)