Hi everyone,
I am running Debian potato and am having a problem with .bashrc. It works
fine as root but does not get executed when I log in as a user. The default
.bashrc contains one alias command (the rest are commented out). When I type
'alias' (under the regular user ac
Many thanks for the tip about .bash_profile. Sure enough, the lines that
execute .bashrc were commented out.
Regards,
Larry
I'm confused as to how debian handles the .bashrc file. In my user
directory, I have a .bashrc file that reads
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files for examples
# If running interactively, then:
if [ "$PS1" ]; the
hi
I wanted to knw how to print a file which is
in text on screen whenever i log in
that is printing a quote everytime i login
or printing a quote in my mail everytime i send
a mail.
pl. lemme knw the syntax for this
thanx
avinash[A
Get your FREE Email at http://mailcity.lycos.com
Get your PE
I've been running Debian for about 3 days now (been running RedHat for 5
years+). I've read through several docs, but haven't found (if I did find
it, I must've read right past it) answers to a couple of problems.
1) When I log in, my .bashrc isn't executed. Here
Hi all,
does anyone know which (and where) is the *system-wide* .bashrc file?
Thanks in advances
Bruno
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Hello list
I have a .bashrc file in my home dir, whose content is shown as follows.
But every time I log into the system, I have to source this file by hand.
$ which scala
/usr/bin/scala
$ cat .bashrc
#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="$HOME/.s
[please type enter after +/- 70 characters]
On Thu, Jul 12, 2001 at 10:20:52AM -0500, Larry W. Irwin Sr. wrote:
> I am running Debian potato and am having a problem with .bashrc. It
> works fine as root but does not get executed when I log in as a user. The
> default .bashrc contains
On Thursday, July 12, 2001 8:51 AM, [EMAIL PROTECTED] spoke:
> On Thu, Jul 12, 2001 at 10:20:52AM -0500, Larry W. Irwin Sr. wrote:
> > [...] having a problem with .bashrc. It works fine as
> > root but does not get executed when I log in as a
> > user.
> maybe
On Thu, Jul 12, 2001 at 10:20:52AM -0500, Larry W. Irwin Sr. wrote:
> Hi everyone,
>
> I am running Debian potato and am having a problem with .bashrc. It works
> fine as root but does not get executed when I log in as a user. The default
> .bashrc contains one alias comman
On Thu, Jul 12, 2001 at 10:20:52AM -0500, Larry W. Irwin Sr. wrote:
> Hi everyone,
>
> I am running Debian potato and am having a problem with .bashrc.
> It works fine as root but does not get executed when I log in as
> a user. The default .bashrc contains one alias co
On Thu, Jul 12, 2001 at 10:24:22AM -0700, Greg Wiley wrote:
> On Thursday, July 12, 2001 8:51 AM, [EMAIL PROTECTED] spoke:
> > On Thu, Jul 12, 2001 at 10:20:52AM -0500, Larry W. Irwin Sr. wrote:
> > > [...] having a problem with .bashrc. It works fine as
> > > roo
om-
mands (like alias defs) are in .bashrc so they
will be run at term start.
> Since I am not a gdm/kdm user, I cannot tell how it works there, but the
> idea shoudl be the same, I guess.
The problem with ~/.xsession for kdm is that
you lose the session selection capability of
the login a
the right environment settings.
>
> Right, just make sure your bash-specific com-
> mands (like alias defs) are in .bashrc so they
> will be run at term start.
>
> > Since I am not a gdm/kdm user, I cannot tell how it works there, but the
> > idea shoudl be the same, I
Joost Kooij uttered:
> On Mon, Jul 16, 2001 at 08:00:16AM -0700, Greg Wiley wrote:
> >
> > There might be a better way that doesn't
> > require modifying /etc/X11/kdm/Xsession
> > and I'd be happy to hear it.
>
Here's what I'm doing: I installed gdm, then deleted the 'S99gdm'
symlink from /etc/r
Hi,
On Mon, Jul 16, 2001 at 08:00:16AM -0700 or thereabouts, Greg Wiley wrote:
> The problem with ~/.xsession for kdm is that
> you lose the session selection capability of
> the login app. I ended up creating a new
> mechanism that sources a local user init file
> before running the main Xsessio
On Tuesday, July 17, 2001 1:04 PM, [EMAIL PROTECTED] wrote
Subject: Re: .bashrc
> Hi,
>
> On Mon, Jul 16, 2001 at 08:00:16AM -0700 or thereabouts, Greg Wiley wrote:
> > The problem with ~/.xsession for kdm is that
> > you lose the session selection capability of
> >
When I log in to my user account, bash is not reading my .bashrc. I've checked
the permissions and ownership. It's all as it should be. However, when I log
in as root, the /root/.bashrc is getting evaluated.
Does anybody know what's go
In order to get around this problem, I put the following in my ~/.bash_profile:
source $HOME/.bashrc
On 09-Aug-2000 Dale Morris wrote:
> I'm confused as to how debian handles the .bashrc file. In my user
> directory, I have a .bashrc file that reads
># ~/.bashrc: executed by b
Dale wrote:
> I'm confused as to how debian handles the .bashrc file. In my user
> directory, I have a .bashrc file that reads
> # ~/.bashrc: executed by bash(1) for non-login shells.
> ...
> But when I log into X and issue the ls command, it doesn't execute the
> comm
Hello All,
Ghost here. Recently switched from ksh to bash and have a question.
When I open up an Eterm, it does not seem to be reading my .bashrc
properly. For one, I have the lines:
eval `dircolors`
alias ls='ls --color'
# set a fancy prompt
PS1='[EMAI
I have .bashrc set up to support color ls, but .bashrc isn't called when I log
in.
If I subsequently start a new shell, however, or 'source .bashrc' then the file
is read and processed.
What's the best way to handle this so it's done automagically upon logging in?
J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
OK, I'm not quite sure what you're asking here, but there are a number of
possibilities...
"Avinash m Gowda" <[EMAIL PROTECTED]> writes:
>I wanted to knw how to print a file which is
> in text on screen whenever i log in
If you want to pri
Graeme Mathieson wrote:
> OK, I'm not quite sure what you're asking here, but there are a number of
> possibilities...
>
> "Avinash m Gowda" <[EMAIL PROTECTED]> writes:
>
> >I wanted to knw how to print a file which is
> > in text on screen whenever i log in
> > that is printing a quote eve
Or, perhaps it is as simple as Avinash wanting to...
1.) Edit his/her MOTD file to print to screen a set text message at
login. (Edit your /etc/motd file, Avinash, to make it say what you want
it to say.)
and
2.) Attach a signature.txt file to his/her outgoing mail, such as I have
attached to mi
On Mon, May 15, 2000 at 07:40:32PM -0700, montefin wrote:
>
> 2.) Attach a signature.txt file to his/her outgoing mail, such as I have
> attached to mine below. Write one in your home directory
> (~/signature.txt) and point your mail app to it, _but_ only 4 lines,
> Avinash, or you're gonna get ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
montefin <[EMAIL PROTECTED]> writes:
> 1.) Edit his/her MOTD file to print to screen a set text message at
> login. (Edit your /etc/motd file, Avinash, to make it say what you want
> it to say.)
But, as I said before, leave the first line blank.
Graeme Mathieson wrote:
> montefin <[EMAIL PROTECTED]> writes:
> > ALTHILTM,
>
> WTF does that mean? :)
at least, that's how it looks to me.
ALTHILTM. (couldn't resist.)
:)
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Their is five errers in this sentance.
> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> Their is five errers in this sentance.
Took me a while to find the fifth, then my brain briefly rebelled. Think
I'll share your sig with a few friends; pretty cool.
> > -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> > Their is five errers in this sentance.
>
> Took me a while to find the fifth, then my brain briefly rebelled.
>
the error could be, that there are only four (orthographical)
errors. but as it says, that there are five errors, which is correct, we
have
On Wed, May 17, 2000 at 11:29:58AM +0200, Oswald Buddenhagen wrote:
> > > -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> > > Their is five errers in this sentance.
> >
> > Took me a while to find the fifth, then my brain briefly rebelled.
> >
> the error could be, that there are only four (orthographical
Oswald Buddenhagen <[EMAIL PROTECTED]> wrote:
>> > -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
>> > Their is five errers in this sentance.
>>
>> Took me a while to find the fifth, then my brain briefly rebelled.
>>
>the error could be, that there are only four (orthographical)
>errors. but as it says,
Hi
on the standard user's home I use everyday I have the .bashrc file that
is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc/bash.profile the .bashrc is actually never
hi stepehn
put .bashrc in your .profile
.profile
source ~/.bashrc
try /etc/rc.d/boot.local ( wild guess )
c ya
alvin
On Sat, 24 Mar 2001, stephen wrote:
> I've been running Debian for about 3 days now (been running RedHat for 5
> years+). I've read
problems.
>
> 1) When I log in, my .bashrc isn't executed. Here's my ls -al:
>
> -rwx-- 1 stephen stephen694 Mar 24 09:59 .bashrc
.bash_profile is executed rather than .bashrc when entering a login shell.
See 'man bash'.
>
> What do I need to do
:-> "stephen" == stephen <[EMAIL PROTECTED]> writes:
> 1) When I log in, my .bashrc isn't executed. Here's my ls -al:
> -rwx-- 1 stephen stephen694 Mar 24 09:59 .bashrc
> What do I need to do to get this to execute. I've se
> 1) When I log in, my .bashrc isn't executed. Here's my ls -al:
>
> -rwx-- 1 stephen stephen 694 Mar 24 09:59 .bashrc
>
> What do I need to do to get this to execute
Hi, you need only to look at your /home/stephen/.bash_profile. There are
some commands with
>
> Hi all,
> does anyone know which (and where) is the *system-wide* .bashrc file?
Let me quote from the bash man page!
INVOCATION
A login shell is one whose first character of argument
On Fri, 22 Aug 1997, Bruno O. M. Simoes wrote:
> Hi all,
> does anyone know which (and where) is the *system-wide* .bashrc file?
> Thanks in advances
> Bruno
Closest thing I can think of if /etc/profile. You can check for the
correct shell using a case:
case "$0" in
-ba
( Re Message From: E.L. Meijer )
> > Hi all,
> > does anyone know which (and where) is the *system-wide* .bashrc file?
>
> Let me quote from the bash man page!
>
>
Do you mean if .bash_profile exists, .bashrc will be ignored?
Thanks.
On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote:
> * Yamada??? [22-01/12=We 19:49 +0800]:
> > I have a .bashrc file in my home dir, whose content is shown as follows.
> > But every time I log into the sy
* Yamada??? [22-01/12=We 19:49 +0800]:
> I have a .bashrc file in my home dir, whose content is shown as follows.
> But every time I log into the system, I have to source this file by hand.
>
> $ which scala
> /usr/bin/scala
>
> $ cat .bashrc
> #THIS MUST BE AT THE END O
* Yamada??? [22-01/12=We 20:10 +0800]:
> Do you mean if .bash_profile exists, .bashrc will be ignored?
Sometimes. From `man bash`:
When bash is invoked as an interactive login shell, or as a
non-interactive shell with the --login option, it first reads
and executes commands from the f
Thanks a lot @Will Mengarini
On Wed, Jan 12, 2022 at 8:21 PM Will Mengarini wrote:
> * Yamada??? [22-01/12=We 20:10 +0800]:
> > Do you mean if .bash_profile exists, .bashrc will be ignored?
>
> Sometimes. From `man bash`:
> When bash is invoked as an interactive lo
EX_VERSION=8.0.0
export PATH=${PATH}:${HEX_ROOT}/bin
export HEX_CACHE=/home/comp/Apps/Hex/hex_cache
Whie the additional lines are necessary for the execution of HEX they
seem to have wiped oour all of the alias entries I have in .bashrc.
Rebooting the system does not eliminate the problem! B
On Friday 05 April 02:26, Steve Juranich wrote:
> When I log in to my user account, bash is not reading my .bashrc. I've
> checked the permissions and ownership. It's all as it should be. However,
> when I log in as root, the /root/.bashrc is getting evaluated.
>
>
On Fri, 2002-04-05 at 11:26, Steve Juranich wrote:
> When I log in to my user account, bash is not reading my .bashrc. I've
> checked
> the permissions and ownership. It's all as it should be. However, when I
> log
> in as root, the /root/.bashrc is getting evaluate
Works Great!! Thanks
On Wed, Aug 09, 2000 at 01:20:47PM + 26, Pollywog <[EMAIL PROTECTED]> wrote:
> In order to get around this problem, I put the following in my
> ~/.bash_profile:
>
> source $HOME/.bashrc
>
> On 09-Aug-2000 Dale Morris wrote:
> > I'
Put in your user .bash_profile:
source $HOME/.bashrc
On 06-Sep-2000 Debian Ghost wrote:
>
> Also, wish to have my ls = ls --color. Both of these things are not
> working. It almost seems as if my .bashrc is ignored.
>
> Can anyone give bash advice?
>
> Thank$ a l
%% Debian Ghost <[EMAIL PROTECTED]> writes:
dg> Ghost here. Recently switched from ksh to bash and have a question.
dg> When I open up an Eterm, it does not seem to be reading my .bashrc
dg> properly.
dg> Can anyone give bash advice?
The bash man page is _VERY_ comp
On 07-Mar-2001 Colin Cashman wrote:
> I have .bashrc set up to support color ls, but .bashrc isn't called when I
> log in.
>
> If I subsequently start a new shell, however, or 'source .bashrc' then the
> file is read and processed.
>
> What's
On Wed, 07 Mar 2001 16:40:25 EST, "Colin Cashman" writes:
>What's the best way to handle this so it's done automagically upon logging in?
> Just throw "source .bashrc" onto the end of the
>.bash_profile file?
IMHO: yes.
cheers,
&rw
--
/ Ing. Robert W
I had this similar issue on my system. If you look at the bash_profile you
will see some calls to the .bashrc...but they are commented out (why?) just
uncomment them, and you are good to go
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 07
Lo, on Wednesday, March 7, Colin Cashman did write:
> I have .bashrc set up to support color ls, but .bashrc isn't called when
> I log in.
As expected. See bash's man page (specifically the `INVOCATION' section)
for a discussion of the startup sequence.
> If I subseq
On Wed, Mar 07, 2001 at 04:40:25PM -0500, Colin Cashman wrote:
> I have .bashrc set up to support color ls, but .bashrc isn't called when I
> log in.
>
> If I subsequently start a new shell, however, or 'source .bashrc' then the
> file is read and processed.
>
On 07 Mar 2001, ktb wrote:
> On Wed, Mar 07, 2001 at 04:40:25PM -0500, Colin Cashman wrote:
> > I have .bashrc set up to support color ls, but .bashrc isn't called when I
> > log in.
> >
> > If I subsequently start a new shell, however, or 'source .b
Lorenzo Bettini wrote:
Hi
on the standard user's home I use everyday I have the .bashrc file
that is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc/bash.profile the .bash
I remember that the files are read like
/etc/profile - > ~/.bash_profile -> ~/.bashrc -> ~./profile
but the bashrc file should be created by default without you having to
insert it..
On 12/25/06, Lorenzo Bettini <[EMAIL PROTECTED]> wrote:
Hi
on the standard user's home I
Marc Shapiro wrote:
Lorenzo Bettini wrote:
Hi
on the standard user's home I use everyday I have the .bashrc file
that is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
Ali Jawad wrote:
I remember that the files are read like
/etc/profile - > ~/.bash_profile -> ~/.bashrc -> ~./profile
but the bashrc file should be created by default without you having to
insert it..
that's what I thought too, but neither .bashrc nor .bash_profile were
created
On Tue, Dec 26, 2006 at 10:53:27AM +0100, Lorenzo Bettini wrote..
> >I remember that the files are read like
> >
> >/etc/profile - > ~/.bash_profile -> ~/.bashrc -> ~./profile
> >
> >but the bashrc file should be created by default without you
>
What is the best way to set up variables when using xdm/wdm.
I tried to execute my .bashrc from .xsession or to set the
variables in the .xsession, but the X-session refused to start even if
an empty ~/.xsession file exist.
Marc
I made the two following aliases in the .bashrc in my home directory
alias mcd='mount /dev/hdb /cdrom'
alias ucd='umount /cdrom'
They work fine, but I also want to immediately jump to /cdrom when I mount a CD. Thus I ammended the mcd alias to read...
alias mcd='
Hello,
I encountered a trifling problem in my .bashrc:
.
.
# Define some colors:
RED='\e[1;31m'
cyan='\e[0;36m'
CYAN='\e[1;36m'
YELLOW='\e[1;33m
I need to set my locale to en_GB so abiword will boot up with its spelling
checker in GB english mode.
Abiword doc suggests I put
export LANG=en_GB
unset LC_ALL
in either .bashrc or .profile
Typing them on the command line then typing abiword works AOK.
Putting them in .bashrc, .bash_profile
Hello,
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Whie the additional lines are necessary for the execution of HEX they seem
> to have wiped oour all of the alias entries I have in .bashrc. Rebooting
> the system does not eliminate the problem! Bu bumblin
On Wed, 25 Apr 2018 15:34:02 -0400 Stephen P. Molnar said:
> What's going on what is the fix?
It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
directly. However, when ~/.bash_profile did exist, then it is called *instead
of* ~/.bashrc and it is up to ~/.bash_pr
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Bu bumbling about I discovered
> the it is necessary to source .bashrc inorder to recticate the alias lines
> in .bashrc (note: commenting out the added lines in .bash_profile did not
> solve the problem).
>
&g
On Wed, Apr 25, 2018 at 10:49:52PM +0300, Abdullah Ramazanoglu wrote:
> It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
> directly.
That's not correct.
As a LOGIN shell, bash reads ONE file, searching among the following items
in sequence:
a) ~/.bas
Thanks for the reply.
Adding the lines from your .bash_profile to mine restored the
functionality of .bashrc.
I don't have any backups of .bash_profile, but I would guess the the HEX
installation script woped out the origional .bash_profile. ( I try to
never assume anything as we all
, as usual, ~/.bashrc.
I can think that I don't really have a ~/.bashrc (or have a mispelling
on the file name), but if I run bash from the terminal, my configuration
file in ~/.bashrc is loaded.
I add an "echo" on each files before sending you my problem to check
that the
I reconfigured both ~./bash_profile and ~/.bashrc to work properly, and they
do- ls is automatically aliased as --color, etc.
But at login, I still get a '~/.bash_profile: permission denied' error.
When I look at the permissions, I'm listed as the owner. I did these changes
I've just discovered that a stable install (4.0, (with rdiff-backup
pulled from testing)) has a wonky (that's a technical term, you
understand ... ;-) ) /etc/skel/bashrc apparently.
If I ssh in as a freshly-created user and then run the "set" command, I
get pages and pag
On Sun, Aug 01, 1999 at 01:47:37AM +0200, Marc Meier wrote:
> I tried to execute my .bashrc from .xsession or to set the
> variables in the .xsession, but the X-session refused to start even if
> an empty ~/.xsession file exist.
AFAIK, you need to launch your window manager at the en
Hi!
First: Please don't write HTML-Mails. Plain text is smaller files and readable
by everybody.
>
> alias mcd='mount /dev/hdb /cdrom|cd /cdrom'
>
Why do you use the pipe command?
Simply type somthing like:
alias mcd='mount /dev/hdb /cdrom ; cd /cdrom'
and, if your cdrom is mentioned in /etc/fst
> alias mcd='mount /dev/hdb /cdrom|cd /cdrom'
try alias mcd='mount /dev/hdb /cdrom && cd /cdrom'
--
Robert Vollmert [EMAIL PROTECTED]
> Hello all,
>
> I am having a problem with users .bashrc, roots works fine AFAIK, but all the
> user ones do nothing. No matter what I put
> in them it doesn't work. For example in my .bashrc I have the line "l='ls
> --color=auto -als'" but typing
J Horacio MG ([EMAIL PROTECTED]) wrote:
> Not sure whether you already know this, but ~/.bashrc is for interactive
> shell, not for login shell, ie. when you login the config file read is
> ~/.bash_profile or /etc/profile
Oops! In Rat Hat putting things in your .bashrc worked... I guess
Ron Farrer writes:
| J Horacio MG ([EMAIL PROTECTED]) wrote:
|
| > Not sure whether you already know this, but ~/.bashrc is for
| > interactive shell, not for login shell, ie. when you login the
| > config file read is ~/.bash_profile or /etc/profile
|
| Oops! In Rat Hat putting thing
On Wed, Sep 22, 1999 at 10:42:01AM +0200, J Horacio MG wrote:
> shell, not for login shell, ie. when you login the config file read is
> ~/.bash_profile or /etc/profile
Or ~/.profile. I forget the precendence.
Rob
--
MY income is ALL disposable!
On Wed, Sep 22, 1999 at 05:45:21PM +, Martyn Pearce wrote:
>
> | Oops! In Rat Hat putting things in your .bashrc worked... I guess I
> | have a few more things to unlearn from Rat Hat!
>
> The behavoiur of bash w.r.t. .bashrc & .bash_login is fixed. Therefore,
> if
On 23-Sep-99 Eric G . Miller wrote:
> On Wed, Sep 22, 1999 at 05:45:21PM +, Martyn Pearce wrote:
>>
>> | Oops! In Rat Hat putting things in your .bashrc worked... I guess I
>> | have a few more things to unlearn from Rat Hat!
>>
>> The behavoiur of bash w.r.
| On 23-Sep-99 Eric G . Miller wrote:
| > If I remeber correctly, they had .bash_profile sourcing .bashrc. Is
| > there something inherently wrong with doing such a thing?
Most of the time, it's just redundant. There are settings (e.g., PATH),
which only need to be set on
wrong with putting your aliases in
.bashrc. Since that is what I've done, and sourced it in
.bash_profile, I wondered if there was something wrong with that. The
answer seems to be no...
--
+---++-+---++-+---++-+
| YOUR AD HERE1.900.FOO.BARZ |
+-+---++-+---++-+---++
that
| inidicated there was something wrong with putting your aliases in
| .bashrc. Since that is what I've done, and sourced it in
| .bash_profile, I wondered if there was something wrong with that. The
| answer seems to be no...
Oh dear, we're getting confused. My "What ar
s replying to an earlier post that
> inidicated there was something wrong with putting your aliases in
> .bashrc. Since that is what I've done, and sourced it in
> .bash_profile, I wondered if there was something wrong with that. The
> answer seems to be no...
I read in a book tha
'm not trying to do anything. I was replying to an earlier post that
>| inidicated there was something wrong with putting your aliases in
>| .bashrc. Since that is what I've done, and sourced it in
>| .bash_profile, I wondered if there was something wrong with that. The
>
Hello there!
I have just switched to Debian 1.3.1 from Suse 3 Days ago and so far i´m quite
happy with it.
Now i have some trouble with StarOffice:
I included the .sd.sh script in my .bash-profile script:
# Staroffice
source $HOME/.sd.sh
this way it worked in the Suse Distibution.
Why is it that when I switch to a text console with -- that
bash does not read in my ~/.bashrc?
When I pull up a terminal in X it works fine (all my command aliases are
there). And when I log in to a text console, if explicitly type in the
command 'bash' at the bash prompt, the
On Sun, 13 Jul 2003 19:30:10 +0200, Robin Gerard wrote:
> with this PS1 I get:
>
> [18:31 : 0.16]
> [EMAIL PROTECTED] 1] ~$
>
> but if I write a very long command the cursor remains on the same line and
> overlaps the prompt.
>From "man bash":
> \[ begin a sequence of non‐printing chara
On Sun, Jul 13, 2003 at 08:21:34PM +0200, Sebastian Kapfer wrote:
> On Sun, 13 Jul 2003 19:30:10 +0200, Robin Gerard wrote:
Thanks.
PS1="${cyan}[$TIME [EMAIL PROTECTED] \[${YELLOW}\#$NC\]] \[\w\$ "
did the trick.
--
Gerard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
I have changed the files /etc/bash.bashrc and /etc/profile to my liking.
Problem is, when I create new users, the files .bashrc and .bash_profile
are created in their home directory and they are created with elements
that supercede those two previous files.
What generates .bashrc and
Hi.
May be /etc/invironment
I try to put some variables in /etc/bashrc (not /etc/profile - KDE do not use it for
me :( ) then this work.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I am running Debian Woody (3.0r1). The default shell for my user account is
bash, and I can verify this by typing 'ps' once I am logged on. However,
the contents of my .bashrc do not get executed by default. If I explicitely
invoke bash (typing 'bash' at the shell), .bashrc
Hello José,
José Luis Segura Lucas wrote:
> In one (and only one) of then, when I open a terminal or connect by SSH,
> my bash load the default system configuration from /etc/bash.bashrc,
> instead of reading, as usual, ~/.bashrc.
>
> I can think that I don't really have a
y ~/.profile has a section like the following:
>
> # if running bash
> if [ -n "$BASH_VERSION" ]; then
> # include .bashrc if it exists
> if [ -f "$HOME/.bashrc" ]; then
> . "$HOME/.bashrc"
> fi
> fi
>
> which is also in t
On Sat, Jun 23, 2012 at 05:24:59PM +0200, José Luis Segura Lucas wrote:
> You are right: I have the ~/.profile file missing. I don't know how can
> I miss this file, but it didn't exist at all. I copied this from another
> computer and it works.
tal% less .profile
# ~/.profile: executed by the com
Hello José,
José Luis Segura Lucas wrote:
> I don't remember to write or generate "by hand" this ~/.profile. Is it
> created automatically?
It should be created automatically from the files in /etc/skel/ if
you are using useradd or adduser (the former with the --create-home
option).
Best regard
I am setting up a new potato system. I am interested in initializing
environment
variables, in particular PATH. I see as the second line in both .bashrc
and
.bash_profile, the line:
# see /usr/share/doc/bash/examples/startup-files for examples
But on my newly installed system, there is no
On Thu, Mar 01, 2001 at 06:53:16AM -0800, Tom Schuetz wrote:
| I reconfigured both ~./bash_profile and ~/.bashrc to work properly, and they
do- ls is automatically aliased as --color, etc.
|
| But at login, I still get a '~/.bash_profile: permission denied' error.
|
| When I l
1 - 100 of 199 matches
Mail list logo