Easily find issues by searching: #<Issue ID>
Example: #1832
In the documentation it is stated the default profile of fluidshell is fluid
But if we open up a new fluidshell connection and look at the default prompt - it is not that of cli fluid
|
|
24 KB
| Field | Old Value | New Value |
|---|---|---|
| Dev Assignee | NielsGron (Niels Gron) | funfun (Fun Fun) |
cli fluid should match the current default settings when a shell is opened.
| Field | Old Value | New Value |
|---|---|---|
| Fixed Build | trunk/29642 | |
| Resolution | Fixed | |
| Resolved Date | Oct 9, 2012 4:17 AM | |
| Status | New | Resolved |
In your test case, the prompt generated by the 'cli fluid' command is a correct prompt for 'fluid profile'. The problem actually is the prompt displayed after the shell is opened, it is incorrectly set to the prompt associated with the 'shell profile'.
Below are prompt formats used in 3 different profiles:
(1) fluid profile: "PWD$:LINENO> "
(2) shell profile: "USERNAME:PWD$ "
(3) sql profile: "DATABASEUSERNAME:[SERVERNAME]:LINENO> "
where PWD, LINENO, ..., etc. are shell variables.
When a new fluid shell is opened, the default prompt should be (1).
In your test case, the prompt generated by the 'cli fluid' command is a correct prompt for 'fluid profile'. The problem actually is the prompt displayed after the shell is opened, it is incorrectly set to the prompt associated with the 'shell profile'.
Below are prompt formats used in 3 different profiles:
(1) fluid profile: "PWD$:LINENO> "
(2) shell profile: "USERNAME:PWD$ "
(3) sql profile: "DATABASEUSERNAME:[SERVERNAME]:LINENO> "
where PWD, LINENO, ..., etc. are shell variables.
When a new fluid shell is opened, the default prompt should be (1).
| Field | Old Value | New Value |
|---|---|---|
| Status | Resolved | Closed |
Issue #7749 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/29642 |
| No time estimate |
cli fluid should match the current default settings when a shell is opened.