Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: set EDITOR=vi -> default editor not setting for cron tab
Top Forums Shell Programming and Scripting set EDITOR=vi -> default editor not setting for cron tab Post 302235701 by amaltemara on Friday 12th of September 2008 12:45:41 PM
Old 09-12-2008
Lightbulb check VISUAL env variable
I had the same problem, check and see if the VISUAL env. variable is set to something other than vi.

Code:
set | grep VISUAL

If so, then that's overriding the EDITOR variable.

Many ways to fix...


Add to your ~/.bash_profile (or /etc/profile, or /etc/profile.d/SOME_FILE)
Code:
export VISUAL=vi

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Changing default editor

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

How to set path for the EDITOR variable?

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

where can i set editor option to yes

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

cron tab setting

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

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

6. 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

7. Solaris

How to set VI editor column size on 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

Default editor in zsh

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

Problem with setting vi as my default editor in ksh

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

GNOME Desktop - Setting missing from dconf-editor?

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 OSX

locale::codes::langfam

Locale::Codes::LangFam(3pm)				 Perl Programmers Reference Guide			       Locale::Codes::LangFam(3pm)

NAME

       Locale::Codes::LangFam - standard codes for language extension identification

SYNOPSIS

	  use Locale::Codes::LangFam;

	  $lext = code2langfam('apa');		       # $lext gets 'Apache languages'
	  $code = langfam2code('Apache languages');    # $code gets 'apa'

	  @codes   = all_langfam_codes();
	  @names   = all_langfam_names();

DESCRIPTION

       The "Locale::Codes::LangFam" module provides access to standard codes used for identifying language families, such as those as defined in
       ISO 639-5.

       Most of the routines take an optional additional argument which specifies the code set to use. If not specified, the default ISO 639-5
       language family codes will be used.

SUPPORTED CODE SETS

       There are several different code sets you can use for identifying language families. A code set may be specified using either a name, or a
       constant that is automatically exported by this module.

       For example, the two are equivalent:

	  $lext = code2langfam('apa','alpha');
	  $lext = code2langfam('apa',LOCALE_LANGFAM_ALPHA);

       The codesets currently supported are:

       alpha
	   This is the set of three-letter (lowercase) codes from ISO 639-5 such as 'apa' for Apache languages.

	   This is the default code set.

ROUTINES

       code2langfam ( CODE [,CODESET] )
       langfam2code ( NAME [,CODESET] )
       langfam_code2code ( CODE ,CODESET ,CODESET2 )
       all_langfam_codes ( [CODESET] )
       all_langfam_names ( [CODESET] )
       Locale::Codes::LangFam::rename_langfam  ( CODE ,NEW_NAME [,CODESET] )
       Locale::Codes::LangFam::add_langfam  ( CODE ,NAME [,CODESET] )
       Locale::Codes::LangFam::delete_langfam  ( CODE [,CODESET] )
       Locale::Codes::LangFam::add_langfam_alias  ( NAME ,NEW_NAME )
       Locale::Codes::LangFam::delete_langfam_alias  ( NAME )
       Locale::Codes::LangFam::rename_langfam_code  ( CODE ,NEW_CODE [,CODESET] )
       Locale::Codes::LangFam::add_langfam_code_alias  ( CODE ,NEW_CODE [,CODESET] )
       Locale::Codes::LangFam::delete_langfam_code_alias  ( CODE [,CODESET] )
	   These routines are all documented in the Locale::Codes::API man page.

SEE ALSO

       Locale::Codes
	   The Locale-Codes distribution.

       Locale::Codes::API
	   The list of functions supported by this module.

       http://www.loc.gov/standards/iso639-5/id.php
	   ISO 639-5 .

AUTHOR

       See Locale::Codes for full author history.

       Currently maintained by Sullivan Beck (sbeck@cpan.org).

COPYRIGHT

	  Copyright (c) 2011-2012 Sullivan Beck

       This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.16.2							    2012-10-11					       Locale::Codes::LangFam(3pm)
All times are GMT -4. The time now is 11:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy