public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thanasis <thanasis@asyr.hopto.org>
To: gentoo-user@lists.gentoo.org
Cc: Mick <michaelkintzios@gmail.com>
Subject: Re: [gentoo-user] heads-up: 2011-05-01 baselayout news
Date: Mon, 02 May 2011 13:26:27 +0300	[thread overview]
Message-ID: <4DBE86D3.5060701@asyr.hopto.org> (raw)
In-Reply-To: <201105021105.50173.michaelkintzios@gmail.com>

on 05/02/2011 01:05 PM Mick wrote the following:
> Another thing I found, is some incongruity about the file in which the $EDITOR 
> and $PAGER should be defined.
>
> The migration guide says:
>
> "The EDITOR variable is no longer found in /etc/rc.conf. Both EDITOR and PAGER 
> are set by default in /etc/profile. You should change this as needed in your 
> ~/.bashrc (or equivalent) file or create */etc/env.d/99editor* and set the 
> system default there."
>
> On the other hand the /etc/profile file seems to recommend /etc/profile.d/
>
> "# You should override these in your ~/.bashrc (or equivalent) for per-user
> # settings.  For system defaults, you can add a new file in /etc/profile.d/.
> export EDITOR=${EDITOR:-/bin/nano}
> export PAGER=${PAGER:-/usr/bin/less}"
>
> Which one is the authoritative place to define a system wide editor?
All above are consistent. The system default is set in a file like
/etc/env.d/99editor
I use eselect (app-admin/eselect) to set the system defaults.
eg I have:
# cat /etc/env.d/99editor
# Configuration file for eselect
# This file has been automatically generated.
EDITOR="/usr/bin/vi"
VISUAL="/usr/bin/vi"

But on a per user basis, a user should define those environment
variables in his ~/.bashrc or ~/.bash_profile (or equivalent) shell
initialization files.



  reply	other threads:[~2011-05-02 10:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02  9:03 [gentoo-user] heads-up: 2011-05-01 baselayout news Thanasis
2011-05-02  9:11 ` Thanasis
2011-05-02  9:31   ` Mick
2011-05-02 17:11     ` Mark Knecht
2011-05-02 17:36       ` Mick
2011-05-02 17:55         ` Mark Knecht
2011-05-03  2:23         ` William Hubbs
2011-05-02 18:02       ` Neil Bothwick
2011-05-02 18:16         ` Mark Knecht
2011-05-02 18:48           ` Neil Bothwick
2011-05-02 18:54             ` Mark Knecht
2011-05-02 22:07               ` Mark Knecht
2011-05-03  5:07                 ` Mick
2011-05-02 19:00       ` Felix Leif Keppmann
2011-05-02 10:18   ` Dale
2011-05-02  9:43 ` Mick
2011-05-02 10:05   ` Mick
2011-05-02 10:26     ` Thanasis [this message]
2011-05-02 10:50       ` Mick
2011-05-02 11:25         ` Thanasis
2011-05-02 11:52         ` Alex Schuster
2011-05-02 12:35           ` Mick
2011-05-05  8:25             ` Alex Schuster
2011-05-05  9:06               ` Alan McKinnon
2011-05-05 19:57               ` Mick
2011-05-02 10:06   ` Thanasis
2011-05-03  0:16   ` [gentoo-user] " walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DBE86D3.5060701@asyr.hopto.org \
    --to=thanasis@asyr.hopto.org \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=michaelkintzios@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox