Bug 30463

Summary:	Allow setting environment variables such as EDITOR in systemsettings
Product:	[Applications] systemsettings	Reporter:	Pierre Abbat <phma>
Component:	kcm_componentchooser	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	chaofeng111, g_neeraj, ilovekde, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pierre Abbat 2001-08-09 16:52:40 UTC

(*** This bug was imported into bugs.kde.org ***)

Package:           kcontrol
Version:           KDE 2.1.1 
Severity:          wishlist
Installed from:    Mandrake RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

I'd like to see a way to set arbitrary variables. For instance I set EDITOR=kwrite. I can do that by editing startkde but the proper place for this is kcontrol since different users may want different settings and may want EDITOR to be kwrite in KDE but pico on the console.

(Submitted via bugs.kde.org)

Comment 1 Daniel Molkentin 2001-08-09 17:36:35 UTC

On Thursday 09 August 2001 18:52 you wrote:
>
> I'd like to see a way to set arbitrary variables. For instance I set
> EDITOR=kwrite. I can do that by editing startkde but the proper place for
> this is kcontrol since different users may want different settings and
> may want EDITOR to be kwrite in KDE but pico on the console.
>
> (Submitted via bugs.kde.org)

It is a distributors part to implement it as the permanent setting of 
environment variables is quite different on many system and heavily shell 
dependant.

Cheers

</daniel>

Comment 2 Pierre Abbat 2001-08-10 00:17:45 UTC

On Thursday 09 August 2001 13:36 you wrote:
> On Thursday 09 August 2001 18:52 you wrote:
> > I'd like to see a way to set arbitrary variables. For instance I set
> > EDITOR=kwrite. I can do that by editing startkde but the proper place
> > for this is kcontrol since different users may want different settings
> > and may want EDITOR to be kwrite in KDE but pico on the console.
> >
> > (Submitted via bugs.kde.org)
>
> It is a distributors part to implement it as the permanent setting of
> environment variables is quite different on many system and heavily shell
> dependant.

Did you misunderstand me? I am not asking about permanent setting. I am 
asking that an arbitrary variable can be set as the locale and language 
variables now are.

phma

Comment 3 Daniel Molkentin 2003-09-23 17:28:23 UTC

*** Bug 64700 has been marked as a duplicate of this bug. ***

Comment 4 Daniel Molkentin 2003-09-23 17:34:50 UTC

*** Bug 59344 has been marked as a duplicate of this bug. ***

Comment 5 christian chevalier 2005-01-29 09:23:53 UTC

Yes, for me, the need is to have a the possibility to identify each window when I work on different hosts. A simple solution would be to assign the hostname value to a variable displayed in the title bar for example.

Comment 6 Robert 2006-07-17 23:43:45 UTC

I wanted to set environment variables today (CVSROOT and JAVA_HOME) and learned that this is only possible in KDE by putting a script that has to end in .sh in ~/.kde/env/ .
I think this is kind of cumbersome, especially for the "average user". It would be great if there was a way to do this using the GUI, or in particular, kcontrol, as the original reporter suggested.
Regarding comment #2: ~/.kde/env/*.sh is _not_ in any way distribution or shell specific.

Comment 7 fire f. 2018-11-19 11:03:30 UTC

Whatever happened to KAlternatives and galternatives ?

It used to be helpful for this ! It is gone by now!

Comment 8 soredake 2021-02-10 17:12:09 UTC

Any progress on this?