Disabling CLI prompting also disables command history

Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-13-2019 05:35 PM
When you disable CLI prompting in order to get rid of those pesky confirmation prompts, CLI stops recording new commands, and "dis cli p" remains the last command in your history until you just give up and type "en cli p".
I guess this is somewhat related to CLI prompting being a problem for scripts (hence the "disable cli prompting" command), and history not being used in scripts... *sigh*
Is this a known issue ? Is there any hope for a fix in upcoming releases ?
I guess this is somewhat related to CLI prompting being a problem for scripts (hence the "disable cli prompting" command), and history not being used in scripts... *sigh*
Is this a known issue ? Is there any hope for a fix in upcoming releases ?
2 REPLIES 2

Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-13-2019 10:45 PM
Hello Drew, thanks for your answer, and sorry about not being more specific.
The EXOS version I'm currently working on is 16.2.5.4-patch1-7, but I observed the same behavior on previous 16.1 and 16.2 releases.
Both the "up arrow" and the "history" command are affected.
The EXOS version I'm currently working on is 16.2.5.4-patch1-7, but I observed the same behavior on previous 16.1 and 16.2 releases.
Both the "up arrow" and the "history" command are affected.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-13-2019 09:15 PM
