Konsole in English

[dotancohen]

I need to have KDE in my native language, but I also would like the
terminal in Konsole to be in English. In other words, the "File Edit
... Help" menu and all GUI stuff should be in my native language, but
on the console in Konsole apt-get and other applications should be in
English. I currently run "export LANG=C;" when I first open Konsole,
but is there a way to have this automated? Thanks!


--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On 25/10-2009 23:54 Dotan Cohen <dotancohen@...> wrote:
> I need to have KDE in my native language, but I also would like the
> terminal in Konsole to be in English. In other words, the "File Edit
> ... Help" menu and all GUI stuff should be in my native language, but
> on the console in Konsole apt-get and other applications should be in
> English. I currently run "export LANG=C;" when I first open Konsole,
> but is there a way to have this automated? Thanks!
>

In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you can edit
the environment. You can also choose "Manage Profiles" and do the same for
custom profiles.

--
Best Regards / Med venlig hilsen

  Thomas Olsen

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Monday, 2009-10-26, Thomas Olsen wrote:

> On 25/10-2009 23:54 Dotan Cohen <dotancohen@...> wrote:
> > I need to have KDE in my native language, but I also would like the
> > terminal in Konsole to be in English. In other words, the "File Edit
> > ... Help" menu and all GUI stuff should be in my native language, but
> > on the console in Konsole apt-get and other applications should be in
> > English. I currently run "export LANG=C;" when I first open Konsole,
> > but is there a way to have this automated? Thanks!
>
> In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you can
>  edit the environment. You can also choose "Manage Profiles" and do the
>  same for custom profiles.

Or, since this is basically a setting of the shell, add the adjustment to the
shell's startup file(s).

Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[dotancohen]

2009/10/26 Thomas Olsen <tanghus@...>:

> On 25/10-2009 23:54 Dotan Cohen <dotancohen@...> wrote:
>> I need to have KDE in my native language, but I also would like the
>> terminal in Konsole to be in English. In other words, the "File Edit
>> ... Help" menu and all GUI stuff should be in my native language, but
>> on the console in Konsole apt-get and other applications should be in
>> English. I currently run "export LANG=C;" when I first open Konsole,
>> but is there a way to have this automated? Thanks!
>>
>
> In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you can edit
> the environment. You can also choose "Manage Profiles" and do the same for
> custom profiles.
>

Thanks. Adding the "export LANG=C;" line to the environment page did
not help. Should I be doing something else?


--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[dotancohen]

> Or, since this is basically a setting of the shell, add the adjustment to the
> shell's startup file(s).
>

Which file is that? I know that it is probably .profile or
.bash_profile but I cannot test because this is a work machine. I need
to know which file _only_ affects Konsole and other terminal
emulators, but WILL NOT affect other KDE and non-KDE GUI applications

--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On 26/10-2009 21:48 Dotan Cohen <dotancohen@...> wrote:

> 2009/10/26 Thomas Olsen <tanghus@...>:
> > On 25/10-2009 23:54 Dotan Cohen <dotancohen@...> wrote:
> >> I need to have KDE in my native language, but I also would like the
> >> terminal in Konsole to be in English. In other words, the "File Edit
> >> ... Help" menu and all GUI stuff should be in my native language, but
> >> on the console in Konsole apt-get and other applications should be in
> >> English. I currently run "export LANG=C;" when I first open Konsole,
> >> but is there a way to have this automated? Thanks!
> >
> > In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you can
> > edit the environment. You can also choose "Manage Profiles" and do the
> > same for custom profiles.
>
> Thanks. Adding the "export LANG=C;" line to the environment page did
> not help. Should I be doing something else?
>

You will have to exit all open shells (tabs) and start a new one before the
change takes effect.

--
Best Regards / Med venlig hilsen

  Thomas Olsen

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Boyd Stephen Smith Jr.-3]

On Monday 26 October 2009 15:48:05 Dotan Cohen wrote:
> 2009/10/26 Thomas Olsen <tanghus@...>:
> > In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you can
> > edit the environment. You can also choose "Manage Profiles" and do the
> > same for custom profiles.
>
> Thanks. Adding the "export LANG=C;" line to the environment page did
> not help. Should I be doing something else?

I don't think you want the "export " prefix or the ";" suffix.  Those are for
shells, and konsole is not a shell.  I believe the environment you specify
should simple be NAME=value pairs like /etc/environment.  (The best
documentation for that file appears to be man 8 pam_env).
--
Boyd Stephen Smith Jr.           ,= ,-_-. =.
bss@...             ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/            \_/



___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On 26/10-2009 22:31 "Boyd Stephen Smith Jr." <bss@...> wrote:

> On Monday 26 October 2009 15:48:05 Dotan Cohen wrote:
> > 2009/10/26 Thomas Olsen <tanghus@...>:
> > > In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you
> > > can edit the environment. You can also choose "Manage Profiles" and do
> > > the same for custom profiles.
> >
> > Thanks. Adding the "export LANG=C;" line to the environment page did
> > not help. Should I be doing something else?
>
> I don't think you want the "export " prefix or the ";" suffix.  Those are
>  for shells, and konsole is not a shell.  I believe the environment you
>  specify should simple be NAME=value pairs like /etc/environment.  (The
>  best documentation for that file appears to be man 8 pam_env).
>

Oops, didn't notice that. Boyd is right. Just add LANG=C in the "Edit
Environment" dialog.

--
Best Regards / Med venlig hilsen

  Thomas Olsen

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[James Tyrer]

Dotan Cohen wrote:
>> Or, since this is basically a setting of the shell, add the adjustment to the
>> shell's startup file(s).
>>
>
> Which file is that? I know that it is probably .profile or
> .bash_profile but I cannot test because this is a work machine. I need
> to know which file _only_ affects Konsole and other terminal
> emulators, but WILL NOT affect other KDE and non-KDE GUI applications
>
You are correct that this won't work.

First, it isn't really correct to change the environment in the
".bashrc" file.  The environment should be changed with the
".bash_profile" script.

Second, if you do so (either way), it will affect the whole KDE session
for that user.

What you can do is to start Konsole with a scrip (e.g. konsole_english):

------8<------8<------8<------8<------8<------8<------8<------8<------
#! /bin/bash

LANG="C"
export LANG

exec konsole

------8<------8<------8<------8<------8<------8<------8<------8<------

and modify the:

        $KDEDIR/share/applications/kde4/konsole.desktop

file to read (for example)

        Exec=konsole_english

Then if you find that you need other things in the environment changed,
you can simply add them to the script.

--
James Tyrer

Linux (mostly) From Scratch
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

James and Dotan,

| > Which file is that? I know that it is probably .profile or
| > .bash_profile but I cannot test because this is a work machine. I need
| > to know which file _only_ affects Konsole and other terminal
| > emulators, but WILL NOT affect other KDE and non-KDE GUI applications
| >
| You are correct that this won't work.
|
| First, it isn't really correct to change the environment in the
| ".bashrc" file.

I don't see why.  Remember Dotan's requirements.  The menus of
konsole should be in a different language; the command lines should
be in English.  .bashrc is a very good place to achieve that.

|  The environment should be changed with the
| ".bash_profile" script.

If you want them to be effective everywhere, yes.
But, if you want them to be effective only on the command line of bash
(and its children), then .bashrc is the place.  This is one of the
reasons why we have two files, .bashrc and .bash_profile,
in the first place.

Suppose that we export LANG=C in .bashrc .  There is one problem
remaining.  Env. vars. are inherited by children.  So, if you
invoke konsole from the command line, like so,

   $ konsole &

then it sees LANG=C and its menus will be in English.

To comprehensively solve this problem, you might want to
always invoke konsole as

   $ LANG=your_native_language konsole

or

   $ env LANG=your_native_language konsole

To make this automatic, you can edit your konsole.desktop file and replace

   Exec=konsole

with

   Exec=env LANG=your_native_language konsole

This is an alternative to the following method:

| What you can do is to start Konsole with a scrip (e.g. konsole_english):
|
| ------8<------8<------8<------8<------8<------8<------8<------8<------
| #! /bin/bash
|
| LANG="C"
| export LANG
|
| exec konsole
|
| ------8<------8<------8<------8<------8<------8<------8<------8<------
|
| and modify the:
|
| $KDEDIR/share/applications/kde4/konsole.desktop
|
| file to read (for example)
|
| Exec=konsole_english

Regards,
Ryo
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[James Tyrer]

Ryo Furue wrote:

> James and Dotan,
>
> | > Which file is that? I know that it is probably .profile or
> | > .bash_profile but I cannot test because this is a work machine. I need
> | > to know which file _only_ affects Konsole and other terminal
> | > emulators, but WILL NOT affect other KDE and non-KDE GUI applications
> | >
> | You are correct that this won't work.
> |
> | First, it isn't really correct to change the environment in the
> | ".bashrc" file.
>
> I don't see why.  Remember Dotan's requirements.  The menus of
> konsole should be in a different language; the command lines should
> be in English.  .bashrc is a very good place to achieve that.
>
> |  The environment should be changed with the
> | ".bash_profile" script.
>
> If you want them to be effective everywhere, yes.
> But, if you want them to be effective only on the command line of bash
> (and its children), then .bashrc is the place.  This is one of the
> reasons why we have two files, .bashrc and .bash_profile,
> in the first place.
>
> Suppose that we export LANG=C in .bashrc .  There is one problem
> remaining.  Env. vars. are inherited by children.  So, if you
> invoke konsole from the command line, like so,
>
>    $ konsole &
>
> then it sees LANG=C and its menus will be in English.
>
> To comprehensively solve this problem, you might want to
> always invoke konsole as
>
>    $ LANG=your_native_language konsole
>
> or
>
>    $ env LANG=your_native_language konsole
>
> To make this automatic, you can edit your konsole.desktop file and replace
>
>    Exec=konsole
>
> with
>
>    Exec=env LANG=your_native_language konsole
>

You appear to have snipped out:

"Second, if you do so (either way), it will affect the whole KDE session
for that user."

That is why it won't work (or might not work).  But, it doesn't explain
why that is (or might be) true.

If you read the 'Fine Man Page',

"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 /etc/profile, if that file exists. After
reading that file, it looks for ~/.bash_profile, ~/.bash_login, and
~/.profile, in that order, and reads and executes commands from the
first one that exists and is readable."

"When an interactive shell that is not a login shell is started, bash
reads and executes commands from ~/.bashrc, if that file exists."

You would think that it should work.  However, it is also common
practice for ".bash_profile" to change that.

Fedora 10 "/etc/skel/.bash_profile" (the default):

------8<------8<------8<------8<------8<------8<------8<------8<------

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH

------8<------8<------8<------8<------8<------8<------8<------8<------

It is this that would make it not work.  Now it is possible that your
distro doesn't have the code that sources ".bashrc" from
".bash_profile", but I don't like to suggest that people should make
such changes to their distros.  The script will work for everyone, and
it is really the better way to do it since changing environment
variables in ".bashrc" can cause problems whether or not your distro
does this.

--
James Tyrer

Linux (mostly) From Scratch
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Tuesday, 2009-10-27, James Tyrer wrote:

> "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 /etc/profile, if that file exists. After
> reading that file, it looks for ~/.bash_profile, ~/.bash_login, and
> ~/.profile, in that order, and reads and executes commands from the
> first one that exists and is readable."
>
> "When an interactive shell that is not a login shell is started, bash
> reads and executes commands from ~/.bashrc, if that file exists."
>
> You would think that it should work.  However, it is also common
> practice for ".bash_profile" to change that.
>
> Fedora 10 "/etc/skel/.bash_profile" (the default):
>
> ------8<------8<------8<------8<------8<------8<------8<------8<------
>
> # .bash_profile
>
> # Get the aliases and functions
> if [ -f ~/.bashrc ]; then
> . ~/.bashrc
> fi
>
> # User specific environment and startup programs
>
> PATH=$PATH:$HOME/bin
>
> export PATH
>
> ------8<------8<------8<------8<------8<------8<------8<------8<------
>
> It is this that would make it not work.  Now it is possible that your
> distro doesn't have the code that sources ".bashrc" from
> ".bash_profile", but I don't like to suggest that people should make
> such changes to their distros.  The script will work for everyone, and
> it is really the better way to do it since changing environment
> variables in ".bashrc" can cause problems whether or not your distro
> does this.

Unfortunately this seems to be very common across distributions.

A different approach could be to set the overall environment to what you want
in shells and specifically set the one for KDE and all applications started
from within it, e.g. by using KDE's environment extender mechanism
($HOME/.kde/env), or in the X session setup scripts if other desktop shells
than KDE might be used.

Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[dotancohen]

> You will have to exit all open shells (tabs) and start a new one before the
> change takes effect.
>

Even restarted the computer! No difference.

--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[dotancohen]

>> > In Konsole: "Settings"=>"Edit Current Profile"=>"General". There you can
>> > edit the environment. You can also choose "Manage Profiles" and do the
>> > same for custom profiles.
>>
>> Thanks. Adding the "export LANG=C;" line to the environment page did
>> not help. Should I be doing something else?
>
> I don't think you want the "export " prefix or the ";" suffix.  Those are for
> shells, and konsole is not a shell.  I believe the environment you specify
> should simple be NAME=value pairs like /etc/environment.  (The best
> documentation for that file appears to be man 8 pam_env).

Quite so, thanks Boyd! I just read the manpage that you suggested. I
didn't get much from it, but I suppose that as I get accustomed to
them things will start to clear.

Thanks!

--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[dotancohen]

> You appear to have snipped out:
>
> "Second, if you do so (either way), it will affect the whole KDE session
> for that user."
>
> That is why it won't work (or might not work).  But, it doesn't explain
> why that is (or might be) true.
>
> If you read the 'Fine Man Page',
>
> "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 /etc/profile, if that file exists. After
> reading that file, it looks for ~/.bash_profile, ~/.bash_login, and
> ~/.profile, in that order, and reads and executes commands from the
> first one that exists and is readable."
>
> "When an interactive shell that is not a login shell is started, bash
> reads and executes commands from ~/.bashrc, if that file exists."
>
> You would think that it should work.  However, it is also common
> practice for ".bash_profile" to change that.
>
> Fedora 10 "/etc/skel/.bash_profile" (the default):
>
> ------8<------8<------8<------8<------8<------8<------8<------8<------
>
> # .bash_profile
>
> # Get the aliases and functions
> if [ -f ~/.bashrc ]; then
>        . ~/.bashrc
> fi
>
> # User specific environment and startup programs
>
> PATH=$PATH:$HOME/bin
>
> export PATH
>
> ------8<------8<------8<------8<------8<------8<------8<------8<------
>
> It is this that would make it not work.  Now it is possible that your
> distro doesn't have the code that sources ".bashrc" from
> ".bash_profile", but I don't like to suggest that people should make
> such changes to their distros.  The script will work for everyone, and
> it is really the better way to do it since changing environment
> variables in ".bashrc" can cause problems whether or not your distro
> does this.
>

I have had lots of problems when fiddling with the language settings
in the dofiles, the effects seem to appear in places that I did not
expect them (like Thunderbird). So I am glad for this Konsole-specific
solution.


--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Kurt Sholly]

Do you know how to get off of this email list??????


                                                                           
             Dotan Cohen                                                  
             <dotancohen@gmail                                            
             .com>                                                      To
                                       kde@...                    
             10/27/2009 09:26                                           cc
             AM                                                            
                                                                   Subject
                                       Re: [kde] Konsole in English        
             Please respond to                                            
             kde@...                                              
                                                                           
                                                                           
                                                                           
                                                                           

> You appear to have snipped out:
>
> "Second, if you do so (either way), it will affect the whole KDE session
> for that user."
>
> That is why it won't work (or might not work).  But, it doesn't explain
> why that is (or might be) true.
>
> If you read the 'Fine Man Page',
>
> "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 /etc/profile, if that file exists. After
> reading that file, it looks for ~/.bash_profile, ~/.bash_login, and
> ~/.profile, in that order, and reads and executes commands from the
> first one that exists and is readable."
>
> "When an interactive shell that is not a login shell is started, bash
> reads and executes commands from ~/.bashrc, if that file exists."
>
> You would think that it should work.  However, it is also common
> practice for ".bash_profile" to change that.
>
> Fedora 10 "/etc/skel/.bash_profile" (the default):
>
> ------8<------8<------8<------8<------8<------8<------8<------8<------
>
> # .bash_profile
>
> # Get the aliases and functions
> if [ -f ~/.bashrc ]; then
>        . ~/.bashrc
> fi
>
> # User specific environment and startup programs
>
> PATH=$PATH:$HOME/bin
>
> export PATH
>
> ------8<------8<------8<------8<------8<------8<------8<------8<------
>
> It is this that would make it not work.  Now it is possible that your
> distro doesn't have the code that sources ".bashrc" from
> ".bash_profile", but I don't like to suggest that people should make
> such changes to their distros.  The script will work for everyone, and
> it is really the better way to do it since changing environment
> variables in ".bashrc" can cause problems whether or not your distro
> does this.
>

I have had lots of problems when fiddling with the language settings
in the dofiles, the effects seem to appear in places that I did not
expect them (like Thunderbird). So I am glad for this Konsole-specific
solution.


--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[dotancohen]

> Do you know how to get off of this email list??????
>

Yes, read the footer at the bottom of every message.


--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Billie Erin Walsh]

Kurt Sholly wrote:
> Do you know how to get off of this email list??????
>
>  

Have you ever read the footer at the bottom of every post?

>                                                                            
>              Dotan Cohen                                                  
>              <dotancohen@gmail                                            
>              .com>                                                      To
>                                        kde@...                    
>              10/27/2009 09:26                                           cc
>              AM                                                            
>                                                                    Subject
>                                        Re: [kde] Konsole in English        
>              Please respond to                                            
>              kde@...                                              
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>
>
>
>
>  
>> You appear to have snipped out:
>>
>> "Second, if you do so (either way), it will affect the whole KDE session
>> for that user."
>>
>> That is why it won't work (or might not work).  But, it doesn't explain
>> why that is (or might be) true.
>>
>> If you read the 'Fine Man Page',
>>
>> "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 /etc/profile, if that file exists. After
>> reading that file, it looks for ~/.bash_profile, ~/.bash_login, and
>> ~/.profile, in that order, and reads and executes commands from the
>> first one that exists and is readable."
>>
>> "When an interactive shell that is not a login shell is started, bash
>> reads and executes commands from ~/.bashrc, if that file exists."
>>
>> You would think that it should work.  However, it is also common
>> practice for ".bash_profile" to change that.
>>
>> Fedora 10 "/etc/skel/.bash_profile" (the default):
>>
>> ------8<------8<------8<------8<------8<------8<------8<------8<------
>>
>> # .bash_profile
>>
>> # Get the aliases and functions
>> if [ -f ~/.bashrc ]; then
>>        . ~/.bashrc
>> fi
>>
>> # User specific environment and startup programs
>>
>> PATH=$PATH:$HOME/bin
>>
>> export PATH
>>
>> ------8<------8<------8<------8<------8<------8<------8<------8<------
>>
>> It is this that would make it not work.  Now it is possible that your
>> distro doesn't have the code that sources ".bashrc" from
>> ".bash_profile", but I don't like to suggest that people should make
>> such changes to their distros.  The script will work for everyone, and
>> it is really the better way to do it since changing environment
>> variables in ".bashrc" can cause problems whether or not your distro
>> does this.
>>
>>    
>
> I have had lots of problems when fiddling with the language settings
> in the dofiles, the effects seem to appear in places that I did not
> expect them (like Thunderbird). So I am glad for this Konsole-specific
> solution.
>
>
> --
> Dotan Cohen
>
> http://what-is-what.com
> http://gibberish.co.il
> ___________________________________________________
> This message is from the kde mailing list.
> Account management:  https://mail.kde.org/mailman/listinfo/kde.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.
>
> ___________________________________________________
> This message is from the kde mailing list.
> Account management:  https://mail.kde.org/mailman/listinfo/kde.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.
>
>  

--
Treat all stressful situations like a dog does.
If you can't eat it or play with it,
just pee on it and walk away

Sent with Thunderbird on my Kubuntu Linux Desktop

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Paul Hartman-3]

On Tue, Oct 27, 2009 at 9:30 AM, Dotan Cohen <dotancohen@...> wrote:
>> Do you know how to get off of this email list??????
>>
>
> Yes, read the footer at the bottom of every message.

Or the headers, or the e-mail you got when you signed up, or the
mailing list website you likely visited to sign up (or "Google")... :)

If you use webmail, some (like Gmail) have an easy "Unsubscribe from
this mailing-list" link as well.
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Hi James,

| You appear to have snipped out:
|
| "Second, if you do so (either way), it will affect the whole KDE session
| for that user."

I don't understand why so.  You can change your own .bash_profile and
.bashrc  and you can have your own konsole.desktop in
~/.local/share/applications/ .  I thought we were talking about
per-user settings.

|
| That is why it won't work (or might not work).

Sorry I don't understand what "it" is.  What is not working?

| If you read the 'Fine Man Page',
|
| "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 /etc/profile, if that file exists. After
| reading that file, it looks for ~/.bash_profile, ~/.bash_login, and
| ~/.profile, in that order, and reads and executes commands from the
| first one that exists and is readable."
|
| "When an interactive shell that is not a login shell is started, bash
| reads and executes commands from ~/.bashrc, if that file exists."
|
| You would think that it should work.  However, it is also common
| practice for ".bash_profile" to change that.

Again, I'm afraid I fail to see what's the problem here.
What does "it" refer to in your "You would think that it should work"?

I know all those things you have quoted from the manual.

| # .bash_profile
|
| # Get the aliases and functions
| if [ -f ~/.bashrc ]; then
| . ~/.bashrc
| fi

My ~/.bash_profile does have that clause.

So, in our situation, we want

   <OUR GOAL>
   .bashrc        --- LANG=C
   .bash_profile  --- LANG=your_native_language

Correct?

Then, our ~/.bashrc would read

   LANG=C; export LANG

and our ~/.bash_profile would read

   if [ -f ~/.bashrc ]; then
  . ~/.bashrc
   fi

   # override what's in .bashrc
   LANG=your_native_language; export LANG

Then, OUR GOAL is achieved.  Or am I missing something?

By the way, I've found that most login managers don't source
.bash_profile .  In that case, you have to use your desktop's
(KDE's) autostart feature to load it.  For fortunately,
KDM (KDE's login manager) reads your .bash_profile, at least
on the distro I use (Debian GUN/Linux).

| Fedora 10 "/etc/skel/.bash_profile" (the default):
|
| ------8<------8<------8<------8<------8<------8<------8<------8<------
|
| # .bash_profile
|
| # Get the aliases and functions
| if [ -f ~/.bashrc ]; then
| . ~/.bashrc
| fi
|
| # User specific environment and startup programs
|
| PATH=$PATH:$HOME/bin
|
| export PATH
|
| ------8<------8<------8<------8<------8<------8<------8<------8<------
|
| It is this that would make it not work.  Now it is possible that your
| distro doesn't have the code that sources ".bashrc" from
| ".bash_profile", but I don't like to suggest that people should make
| such changes to their distros.  The script will work for everyone, and
| it is really the better way to do it since changing environment
| variables in ".bashrc" can cause problems whether or not your distro
| does this.

I'm not sure if I understand what you say correctly, but I don't see
why you need a system wide change.  As the manual you quoted say,
your ~/.bash_profile is read after the system wide .bash_profile
is sourced.  So, you have only to make changes to your own
.bash_profile.

| it is really the better way to do it since changing environment
| variables in ".bashrc" can cause problems whether or not your distro
| does this.

"can cause problems"--- What kind of problems do you have in mind?
I've had "export LANG=C" in my ~/.bashrc for years, without having
any problems at all.

Regards,
Ryo
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.