Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
is there a startup script?
5 views
Skip to first unread message
Daniel L Newhouse
Mar 25, 2021, 5:15:23 PM3/25/21
to
I'm looking through the OReilly book. I'm used to the t-shell. Does
this shell have a startup script?
this shell have a startup script?
Grant Taylor
Mar 25, 2021, 5:48:37 PM3/25/21
to
On 3/25/21 3:15 PM, Daniel L Newhouse wrote:
> I'm looking through the OReilly book. I'm used to the t-shell. Does
> this shell have a startup script?
Are you asking about the original Bourne shell or about the newer Bash
> I'm looking through the OReilly book. I'm used to the t-shell. Does
> this shell have a startup script?
shell?
I know that Bash has many different start up files that will be used for
various different things. It's non-trivial and depends on how it's started.
--
Grant. . . .
unix || die
Lewis
Mar 25, 2021, 5:50:18 PM3/25/21
to
In message <09vp5gto0l8kiihh6...@4ax.com> Daniel L Newhouse <dlnew...@gmail.com> wrote:
> I'm looking through the OReilly book. I'm used to the t-shell. Does
> this shell have a startup script?
This seems a strange place to ask about t-shell. Do you, perhaps, mean
> I'm looking through the OReilly book. I'm used to the t-shell. Does
> this shell have a startup script?
tcsh? If so, I seem to recall it uses the same files a csh (.cshrc, et
al) but I haven't run tcsh in many many years.
--
National Socialism is not Socialism, any more than the Black Panthers
were actually cats. @jearl
Michael F. Stemper
Mar 26, 2021, 1:30:20 PM3/26/21
to
On 25/03/2021 16.15, Daniel L Newhouse wrote:
> I'm looking through the OReilly book. I'm used to the t-shell. Does
> this shell have a startup script?
Well, there is ~/.profile, which I mostly use for setting environment
> I'm looking through the OReilly book. I'm used to the t-shell. Does
> this shell have a startup script?
variables. It's only run (as I understand it) for login shells. However,
if you're running in a windowing environment, other windows appear to
inherit all of those variables.
Then, there is ~/.bashrc, which bash runs for non-login shells.
There is also ~/.bash_aliases, which is used to set command aliases in
interactive use. My ~/.bashrc conditionally executes it (the condition
being if ~/.bash_aliases exists). I don't think that this is really
a fundamental part of the bash ecosystem.
--
Michael F. Stemper
If you take cranberries and stew them like applesauce they taste much
more like prunes than rhubarb does.
Daniel L Newhouse
Mar 28, 2021, 4:09:12 PM3/28/21
to
On Fri, 26 Mar 2021 12:30:06 -0500, "Michael F. Stemper"
<mste...@gmail.com> wrote:
Well, they don't have that in cygwin. I remember cygwin being a
little more flexible than it is. Cygwin needs to be based on
OpenSUSE. The only viable alternative would be Darwin.
<mste...@gmail.com> wrote:
Well, they don't have that in cygwin. I remember cygwin being a
little more flexible than it is. Cygwin needs to be based on
OpenSUSE. The only viable alternative would be Darwin.
Daniel L Newhouse
Mar 28, 2021, 4:13:05 PM3/28/21
to
I remember cygwin being more fliexible. Basically, it needs to based
on Darwin. Which means it needs to be like a Macintosh.
on Darwin. Which means it needs to be like a Macintosh.
Daniel L Newhouse
Mar 28, 2021, 4:16:21 PM3/28/21
to
On Sun, 28 Mar 2021 15:12:58 -0500, Daniel L Newhouse
<dlnew...@gmail.com> wrote:
Maybe it should be OpenBSD to avoid the Macintosh association.
<dlnew...@gmail.com> wrote:
Maybe it should be OpenBSD to avoid the Macintosh association.
Daniel L Newhouse
Mar 28, 2021, 5:24:35 PM3/28/21
to
On Sun, 28 Mar 2021 15:16:15 -0500, Daniel L Newhouse
<dlnew...@gmail.com> wrote:
There's another reason to use OpenBSD instead of Darwin. The
nix-Darwin symbol looks like the devil.
<dlnew...@gmail.com> wrote:
There's another reason to use OpenBSD instead of Darwin. The
nix-Darwin symbol looks like the devil.
Daniel L Newhouse
Mar 28, 2021, 8:00:34 PM3/28/21
to
On Sun, 28 Mar 2021 16:24:29 -0500, Daniel L Newhouse
<dlnew...@gmail.com> wrote:
K, I was looking for the following syntax for cygwin
PS1 = "\s-\v\w"
On 4th thought, it should be minix.
<dlnew...@gmail.com> wrote:
K, I was looking for the following syntax for cygwin
PS1 = "\s-\v\w"
On 4th thought, it should be minix.
Lewis
Mar 28, 2021, 11:09:31 PM3/28/21
to
In message <ats16gtvbs6s2uqqt...@4ax.com> Daniel L Newhouse <dlnew...@gmail.com> wrote:
> On Sun, 28 Mar 2021 15:16:15 -0500, Daniel L Newhouse
> <dlnew...@gmail.com> wrote:
> There's another reason to use OpenBSD instead of Darwin. The
> nix-Darwin symbol looks like the devil.
SPOOKY!
> On Sun, 28 Mar 2021 15:16:15 -0500, Daniel L Newhouse
> <dlnew...@gmail.com> wrote:
> There's another reason to use OpenBSD instead of Darwin. The
> nix-Darwin symbol looks like the devil.
The BSD symbol has been a devil for... 40 years?
--
"Those people who think they know everything are a great annoyance to
those of us who do." - Isaac Asimov
Daniel L Newhouse
May 26, 2021, 8:45:52 PM5/26/21
to
On Sun, 28 Mar 2021 16:24:29 -0500, Daniel L Newhouse
<dlnew...@gmail.com> wrote:
From the OReilly book the bash shell
One advantage of bash’s ability to look for either synonym is that you
can retain your .profile if you have been using the Bourne shell. If
you need to add bash-specific commands, you can put them in
.bash_profile followed by the command source .profile. When you log
in, all the bash-specific commands will be executed, and bash will
source .profile, executing the remaining commands. If you decide to
switch to using the Bourne shell you don’t have to modify your
existing files. A similar approach was intended for .bash_login and
the C shell .login, but due to differences in the basic syntax of the
shells, this is not a good idea. .bash_profile is read and executed
only by the login shell. If you start up a new shell (a subshell) by
typing bash on the command line, it will attempt to read commands from
the file .bashrc. This scheme allows you the flexibility to separate
startup commands needed at login time from those you might need when
you run a subshell. If you need to have the same commands run
regardless of whether it is a login shell or a subshell, you can just
use the source command from within .bash_profile to execute .bashrc.
If .bashrc doesn’t exist then no commands are executed when you start
up a subshell.
Cameron Newham. Learning the bash Shell (In a Nutshell (O'Reilly))
(pp. 89-90). O'Reilly Media. Kindle Edition.
<dlnew...@gmail.com> wrote:
From the OReilly book the bash shell
One advantage of bash’s ability to look for either synonym is that you
can retain your .profile if you have been using the Bourne shell. If
you need to add bash-specific commands, you can put them in
.bash_profile followed by the command source .profile. When you log
in, all the bash-specific commands will be executed, and bash will
source .profile, executing the remaining commands. If you decide to
switch to using the Bourne shell you don’t have to modify your
existing files. A similar approach was intended for .bash_login and
the C shell .login, but due to differences in the basic syntax of the
shells, this is not a good idea. .bash_profile is read and executed
only by the login shell. If you start up a new shell (a subshell) by
typing bash on the command line, it will attempt to read commands from
the file .bashrc. This scheme allows you the flexibility to separate
startup commands needed at login time from those you might need when
you run a subshell. If you need to have the same commands run
regardless of whether it is a login shell or a subshell, you can just
use the source command from within .bash_profile to execute .bashrc.
If .bashrc doesn’t exist then no commands are executed when you start
up a subshell.
Cameron Newham. Learning the bash Shell (In a Nutshell (O'Reilly))
(pp. 89-90). O'Reilly Media. Kindle Edition.
0 new messages