Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename a field in the RIDE-Session dialog box #536

Closed
FionaDyalog opened this issue May 21, 2019 · 1 comment
Closed

Rename a field in the RIDE-Session dialog box #536

FionaDyalog opened this issue May 21, 2019 · 1 comment

Comments

@FionaDyalog
Copy link

Describe the issue you are having

A field in the RIDE-Session dialog box ought to be renamed (occurs in two places)

Did you connect to an already running interpreter or start the interpreter from RIDE?

n/a

How do you reproduce the issue?

Open the RIDE-Session dialog box and select Start from the Type drop-down list. Irrespective of the security protocol setting, there is a fild called "Environment variables". After extensive discussions we decided that these would always be named "Configuration parameters" in the documentation (not fully implemented yet but a work in progress!) – for consistency it would be nice if this ttweak could be made in the UI too. (Sounds petty, but there are numerous possible names and ways of setting these on different operating systems and configuration parameters was the most accurate cover-all that we could come up with! Definitely not environment variables...don't want anything that encourages Windows users to play with those!)

Paste the contents of Help → About (Shift+F1)

IDE:
Version: 4.2.3422
Platform: Win32
Date: 2019-04-01 12:22:09 +0200
Git commit: 0ca7334
Preferences:{
"kbdLocale":"en_GB"
}

@jayfoad
Copy link
Contributor

jayfoad commented May 21, 2019

Yeah but, "environment variables" accurately describes what RIDE is gonna do with the values you put in that box. It's gonna set them in the environment of the spawned process, even on Windows. So at the moment you kinda have to know that on Windows you should put things like "MAXWS=999M" in the Arguments box, and on Linux you should put things like that in the Environment variables box.

Perhaps you'd like the connection page to work at a slightly higher level of abstraction: it could have a single box called Configuration parameters, and it could magically know whether to pass them to the APL process as command line arguments or as environment variables. But that's quite a bold change, and I'm sure some users would still want the ability to explicitly specify some things as either command line arguments or as environment variables.

@abrudz abrudz closed this as completed in 339106e Jul 12, 2022
e9gille pushed a commit that referenced this issue Aug 12, 2022
→ Documentation issue 19941
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants