Stop
On Fri, Dec 13, 2024, 7:24 PM Tim via users
wrote:
> Just for the sake of clarity...
>
> On Thu, 2024-12-12 at 13:32 +1030, Tim via users wrote:
> > e.g. stick into one of them an
> >
> > alias grr='echo grr'
> >
> > And something different into the other one. You'll either get a
> > comm
Just for the sake of clarity...
On Thu, 2024-12-12 at 13:32 +1030, Tim via users wrote:
> e.g. stick into one of them an
>
> alias grr='echo grr'
>
> And something different into the other one. You'll either get a
> command not found error, or it'll growl back at you.
If you, then, typed grr
> On 12 Dec 2024, at 16:48, Joe Wulf via users
> wrote:
>
> When logging in, you'd always be at a point where .bash_profile is run
That has not always been the case in recent times.
As I said I have not had time to check if this was fixed in plasma 6.
Barry
--
Hello Will,
On Sun, 1 Dec 2024 17:15:32 + Will McDonald wrote:
> On Sun, 1 Dec 2024 at 17:10, Patrick O'Callaghan
> wrote:
[snip]
>
> Looks like there's a bunch:
>
> https://michurin.github.io/xterm256-color-picker/
> https://colors.sh/
> https://robotmoon.com/bash-prompt-generator/
>
>
On 13/12/24 03:01, Joe Wulf via users wrote:
Konsole is a terminal program out of KDE/Plasma. Similar to 'xterm'
of old. The terminal program of choice along the way invokes bash,
which goes through its initialization routine. .bash_profile is
accomplished upon login, where as opening a termin
That modification to 'konsole' invocation isn't the right way to do things.
I'd recommend undoing that.
When logging in, you'd always be at a point where .bash_profile is run, as part
of logging to the computer; has nothing to do, per se, with plasma regardless
of version. Plasma 6 won't have
Konsole is a terminal program out of KDE/Plasma. Similar to 'xterm' of old.
The terminal program of choice along the way invokes bash, which goes through
its initialization routine. .bash_profile is accomplished upon login, where as
opening a terminal session isn't a 'login' event. There are
> On 11 Dec 2024, at 22:27, Stephen Morris wrote:
>
> Just relative to this, with konsole, which is a bash shell apparently, are
> you saying that when you create a new tab that .bashrc is run in the new tab,
> but .bash_profile is not and is only run at the initial console startup?
I modify
On 12/12/24 14:02, Tim via users wrote:
On Thu, 2024-12-12 at 09:27 +1100, Stephen Morris wrote:
Just relative to this, with konsole, which is a bash shell
apparently, are you saying that when you create a new tab that
.bashrc is run in the new tab, but .bash_profile is not and is only
run at th
On Thu, 2024-12-12 at 09:27 +1100, Stephen Morris wrote:
> Just relative to this, with konsole, which is a bash shell
> apparently, are you saying that when you create a new tab that
> .bashrc is run in the new tab, but .bash_profile is not and is only
> run at the initial console startup?
You can
On 9/12/24 21:25, greg wrote:
On Mon, Dec 2, 2024 at 10:22 AM GianPiero Puccioni
wrote:
On 01/12/2024 19:52, Joe Wulf via users wrote:
For what it is worth, locally changing things like PS1 and environment
variable assignments should be made in .bashrc, not .bash_profile.
When I started
On Mon, Dec 2, 2024 at 10:22 AM GianPiero Puccioni
wrote:
>
> On 01/12/2024 19:52, Joe Wulf via users wrote:
> > For what it is worth, locally changing things like PS1 and environment
> > variable assignments should be made in .bashrc, not .bash_profile.
> >
> When I started with Unix, a long t
On 3/12/24 01:37, Joe Wulf via users wrote:
What you've observed is correct behavior.
Things like PATH enhancements/changes belong in .bash_profile (as that
file has 'generally' replaced the .profile functionality of
yesteryear). Also, putting new things into the PATH variable, should
always
What you've observed is correct behavior.
Things like PATH enhancements/changes belong in .bash_profile (as that file has
'generally' replaced the .profile functionality of yesteryear). Also, putting
new things into the PATH variable, should always be done at the end, not the
beginning.Thus:
On Sun, 2024-12-01 at 18:52 +, Joe Wulf via users wrote:
> For what it is worth, locally changing things like PS1 and
> environment variable assignments should be made in .bashrc, not
> .bash_profile.
Long ago I remember trying to figure out where to put PS1, since it did
work in either one, b
On 01/12/2024 19:52, Joe Wulf via users wrote:
For what it is worth, locally changing things like PS1 and environment
variable assignments should be made in .bashrc, not .bash_profile.
When I started with Unix, a long time ago, it was Env Var in profile and aliases
and other stuff in *rc dep
On Sun, 2024-12-01 at 17:15 +, Will McDonald wrote:
> On Sun, 1 Dec 2024 at 17:10, Patrick O'Callaghan
> wrote:
>
> > On Sun, 2024-12-01 at 11:16 -0500, Todd Zullinger wrote:
> > > One thing which is new is the bash-color-prompt package was
> > > added. This installs /etc/profile.d/bash-colo
On Sun, 2024-12-01 at 12:43 -0500, Todd Zullinger wrote:
> For truecolor terminals, printing all 16 million colors is
> not useful, other than as a test of how well your terminal
> scrolls, perhaps ;).
>
Indeed not, but in case I wasn't clear I meant a colour *picker*, not
just something that pri
For what it is worth, locally changing things like PS1 and environment
variable assignments should be made in .bashrc, not .bash_profile.
On Sunday, December 1, 2024 at 01:38:29 PM EST, GianPiero Puccioni
wrote:
On 01/12/2024 17:16, Todd Zullinger wrote:
>
> One thing which is new
On 01/12/2024 17:16, Todd Zullinger wrote:
One thing which is new is the bash-color-prompt package was
added. This installs /etc/profile.d/bash-color-prompt.sh
which sets PS1. Documentation for how to use it is in
/usr/share/doc/bash-color-prompt/README.md, if you want to
take advantage of it
Will McDonald wrote:
> On Sun, 1 Dec 2024 at 17:10, Patrick O'Callaghan
> wrote:
>
>> On Sun, 2024-12-01 at 11:16 -0500, Todd Zullinger wrote:
>>> One thing which is new is the bash-color-prompt package was
>>> added. This installs /etc/profile.d/bash-color-prompt.sh
>>> which sets PS1. Documen
On Sun, 1 Dec 2024 at 17:10, Patrick O'Callaghan
wrote:
> On Sun, 2024-12-01 at 11:16 -0500, Todd Zullinger wrote:
> > One thing which is new is the bash-color-prompt package was
> > added. This installs /etc/profile.d/bash-color-prompt.sh
> > which sets PS1. Documentation for how to use it is
On Sun, 2024-12-01 at 11:16 -0500, Todd Zullinger wrote:
> One thing which is new is the bash-color-prompt package was
> added. This installs /etc/profile.d/bash-color-prompt.sh
> which sets PS1. Documentation for how to use it is in
> /usr/share/doc/bash-color-prompt/README.md, if you want to
>
Hi,
GianPiero Puccioni wrote:
> I just upgraded to F40 and my bash prompt has changed, I
> have it set up in .bash_profile and it worked before.
>
> I thought that the default config /etc/profile and
> /etc/bashrc were read first and than the user
> .bash_profile and .bashrc so you can change the
Hi,
I just upgraded to F40 and my bash prompt has changed, I have it set up in
.bash_profile and it worked before.
I thought that the default config /etc/profile and /etc/bashrc were read first
and than the user .bash_profile and .bashrc so you can change the defaults; was
it changed or someth
25 matches
Mail list logo
