On 26.12.2024 14:03, Greg Wooledge wrote:
On Thu, Dec 26, 2024 at 10:56:31 +, Chris Green wrote:
hen...@privatembox.com wrote:
>
> So, since I am using a login shell, and I have .bashrc created. thus I
> have to create a .profile to include .bashrc? Am I right?
>
Yes, I think that's the righ
On 2024-12-26, hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
> I have to source it by hand to
On Thu, Dec 26, 2024 at 10:56:31 +, Chris Green wrote:
> hen...@privatembox.com wrote:
> >
> > So, since I am using a login shell, and I have .bashrc created. thus I
> > have to create a .profile to include .bashrc? Am I right?
> >
> Yes, I think that's the right way round.
Agreed. Even if
> Sent: Thursday, December 26, 2024 at 5:56 AM
> From: "Chris Green"
> To: debian-user@lists.debian.org
> Subject: Re: bashrc question
>
> hen...@privatembox.com wrote:
> >
> > So, since I am using a login shell, and I have .bashrc created. thus I
hen...@privatembox.com wrote:
>
> So, since I am using a login shell, and I have .bashrc created. thus I
> have to create a .profile to include .bashrc? Am I right?
>
Yes, I think that's the right way round.
I use ssh a lot and have a 'standard' configuration for all the
systems I ssh into.
On
On 26.12.2024 04:52, Greg Wooledge wrote:
On Thu, Dec 26, 2024 at 04:16:17 +0100, hen...@privatembox.com wrote:
Hello
I have these settings in .bashrc of my home dir:
$ cat .bashrc
export TF_CPP_MIN_LOG_LEVEL=3
export CUDA_VISIBLE_DEVICES=-1
but every time after i login the system, the settin
On Thu, Dec 26, 2024 at 04:16:17 +0100, hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
> I h
On Thursday, 26-12-2024 at 14:16 hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
> I have
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 login shell, or as a
> non
* 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 file /
* 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 OF THE FILE FOR SDKMAN TO
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 system, I have to
Pier Paolo writes:
> I guess the /etc/skel debian directory isn't actually empty: try ls
> --all /etc/skel
Uh, yes, of course!!
> You've to restore your fancy-console-files from a previous backup or
> browsing in gentoo svn to find the files (maybe some base-files or
> something)
After I c
Csanyi Pal:
>
> When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME
> directory with it's dot files too.
>
> So, I think the .bashrc and .bash_profile remain in the state in which
> was on Gentoo.
Yes, that's how it should be. Debian package managers must never touch
anything under
¡Warning: bad english here!
I guess the /etc/skel debian directory isn't actually empty: try ls --all
/etc/skel
You've to restore your fancy-console-files from a previous backup or
browsing in gentoo svn to find the files (maybe some base-files or
something)
On Mon, Sep 6, 2010 at 10:29, Csan
On 09/18/2007 10:08 AM, Kent West wrote:
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.
[...]
I don't see anything particularly odd in /etc/skel/bashrc (but th
On Tue, Sep 18, 2007 at 10:08:35 -0500, Kent West wrote:
> 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 r
On Tue, Aug 21, 2007 at 04:14:04PM -0700, Dr. Jennifer Nussbaum wrote:
>
> PS1='\h\w $ '; export PS1
>
> So, nothing fancy. How do i get my coloured "ls" back,
> and my "#" prompt as sudo'ed root?
Use \$ rather than a plain $ to get # as root.
A.
--
Ansgar Esztermann
Researcher & Sysadmin
2007/8/21, Dr. Jennifer Nussbaum <[EMAIL PROTECTED]>:
>
> Im a new Debian Etch user, coming from FreeBSD. When i
> first installed my system, running the "ls" command
> would
> give me coloured output (executables one colour,
> directories another). Also, when I sudo'ed to root, i
> would get the u
On Sun, 04 Jan 2004 08:17:26 -0500, Russ Schneider wrote:
> 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 super
On Sun, Jan 04, 2004 at 08:36:41 -0500, Russ Schneider wrote:
> When the system copies those files for a new user, they're all owned by
> root:root.
That's sounds like a bug. Please file a report using reportbug.
Ray
--
People don't respond to any events as real people facing events would.
Othe
On Sun, 4 Jan 2004, J.H.M. Dassen (Ray) wrote:
> Edit the skeleton files in /etc/skel/ . (They're marked as conffiles so the
> package management system will not accidentally overwrite your changes).
Great! But I noticed something.
When the system copies those files for a new user, they're all
On Sun, Jan 04, 2004 at 08:17:26 -0500, Russ Schneider wrote:
> What generates .bashrc and .bash_profile for each new user?
adduser(1) by copying from /etc/skel/ .
> Is it something I can alter so it writes them the way I want them?
Edit the skeleton files in /etc/skel/ . (They're marked as conf
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 evaluated.
>
> Does anybody know w
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.
>
> Does anybody know what's going
hi
you might want to check out the package sysprofile (apt-get install sysprofile)
but it is only
available for testing and unstable.
generally though you can set PATH in /etc/profile for all users to use when
they log in.
hth
--
M.
On Fri, Jan 04, 2002 at 04:13:10PM -0800, Paul E Condon de
On Fri, Jan 04, 2002 at 04:13:10PM -0800, Paul E Condon wrote:
> But on my newly installed system, there is no "examples/" directory at
> /usr/share/doc/bash/
> there is only some residue from a debian install.
> Where are the examples? Where is other docs about user space
> initialization?
Inst
On Fri, Jan 04, 2002 at 04:13:10PM -0800, Paul E Condon wrote:
>
> # see /usr/share/doc/bash/examples/startup-files for examples
>
> But on my newly installed system, there is no "examples/" directory at
> /usr/share/doc/bash/
> there is only some residue from a debian install.
> Where are the e
On Fri, Jan 04, 2002 at 04:13:10PM -0800, Paul E Condon wrote:
> Where are the examples? Where is other docs about user space
> initialization?
Here is mine:
# ~/.bashrc: executed by bash(1) for non-login shells.
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
On Fri, Jan 04, 2002 at 04:13:10PM -0800, Paul E Condon wrote:
> 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/s
> "Paul" == Paul E Condon <[EMAIL PROTECTED]> writes:
Paul> I am setting up a new potato system. I am interested in
Paul> initializing environment variables, in particular PATH. I
Paul> see as the second line in both .bashrc and .bash_profile,
Paul> the line:
Paul> # see /
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
> >
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
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
On Mon, Jul 16, 2001 at 08:00:16AM -0700, Greg Wiley wrote:
> On Friday, July 13, 2001 1:54 PM, [EMAIL PROTECTED] wrote:
> > If you use xdm, the trick is [...]
> > Since programs in your x session are usually descendants of ~/.xsession,
> > they will automatically be run with the right environment
On Friday, July 13, 2001 1:54 PM, [EMAIL PROTECTED] wrote:
> If you use xdm, the trick is [...]
> Since programs in your x session are usually descendants of ~/.xsession,
> they will automatically be run with the right environment settings.
Right, just make sure your bash-specific com-
mands (like
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
> > > root but does not get executed wh
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 command (the rest
>
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 command (the rest are co
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 you have a .bash_profile file
[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 one alias c
> 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
Hi, you need only to look at your /home/stephen/.bash_profile. There are
some commands with an # at beginnig that you shol
:-> "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 set up a .login which
> executes the file and
On Sat, Mar 24, 2001 at 05:50:19PM -0600, stephen wrote:
> 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
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 through several docs
%% 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_ comprehensive and well-wri
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 lot!
>
> Debian Ghost
>
> 'spa
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'm confused as to how debian handles the
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
> command in color, nor does it do
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 bash(1) for non-login
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,
> From: Justin Megawarne [mailto:[EMAIL PROTECTED]
>
> 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
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
> > -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> > 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
> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> 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.
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.
-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.
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
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
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
-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
On 23-Sep-99 Martyn Pearce wrote:
>
> Eric G . Miller writes:
>| On Thu, Sep 23, 1999 at 07:21:47AM +, Martyn Pearce wrote:
>| > What are you trying to do here? Is there some bash feature being
>| > exploited that I haven't seen before?
>| >
>| I'm not trying to do anything. I was replyin
On 23-Sep-99 Eric G . Miller wrote:
> On Thu, Sep 23, 1999 at 07:21:47AM +, Martyn Pearce wrote:
>> What are you trying to do here? Is there some bash feature being
>> exploited that I haven't seen before?
>>
> I'm not trying to do anything. I was replying to an earlier post that
> inidi
Eric G . Miller writes:
| On Thu, Sep 23, 1999 at 07:21:47AM +, Martyn Pearce wrote:
| > What are you trying to do here? Is there some bash feature being
| > exploited that I haven't seen before?
| >
| I'm not trying to do anything. I was replying to an earlier post that
| inidicated the
On Thu, Sep 23, 1999 at 07:21:47AM +, Martyn Pearce wrote:
> What are you trying to do here? Is there some bash feature being
> exploited that I haven't seen before?
>
I'm not trying to do anything. I was replying to an earlier post that
inidicated there was something wrong with putting y
| 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 once, because they're
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.t. .bashrc & .bash_login is fixed.
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 using .bashrc "worked" wi
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!
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 things in your
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 I have a
> 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 'l' does
> nothing... Also /etc/skel/.aliases a
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 end of your .xse
Brendon Baumgartner wrote:
> I can't seem to find the .bashrc file. I checked all over for it.
> According to the debian package search on their website, its
> suppose to be in the bash package, but I installed that again, and
> its not there! What can I do to find it?? Thanks.
umm.. try "vi .bash
On 28-May-99 Brendon Baumgartner wrote:
> I can't seem to find the .bashrc file. I checked all over for it. According
> to the debian package search on their website, its suppose to be in the bash
> package, but I installed that again, and its not there! What can I do to
> find it?? Thanks.
>
> B
( 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!
>
>
[ snip ]
> --
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
-bash | -sh)
# do stuff h
>
> 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
zero is a -,
On Sun, 10 Aug 1997 [EMAIL PROTECTED] wrote:
> 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
> sour
>
> 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
Hi [EMAIL PROTECTED]; unless Mutt is confused,on Aug 10, you wrote :
>snip<
> I included the .sd.sh script in my .bash-profile script:
> # Staroffice
> source $HOME/.sd.sh
> this way it worked in the Suse Distibution.
> But now it only works if i start i.e. swriter from the initial
81 matches
Mail list logo
