Bug 370225 - [terminal] The Terminal's "encoding" combo should remember values previously entered
Summary: [terminal] The Terminal's "encoding" combo should remember values previously ...
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 4.0   Edit
Assignee: dsdp.tm.core-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 244405
Blocks:
  Show dependency tree
 
Reported: 2012-01-31 10:12 EST by Martin Oberhuber CLA
Modified: 2015-05-07 08:02 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2012-01-31 10:12:50 EST 
+++ This bug was initially created as a clone of Bug #244405 +++

Build ID: 3.4M5 with the new encoding combo from bug 244405

Enhancement Request:
Creating a new terminal connection, the encoding combo suggests 3 default settings (host encoding, UTF-8 and ISO-8859-1). Assume that I want to connect a host with "shift-jis" encoding ... it is likely that I want to connect more similar hosts again.

The encoding combo in the terminal settings dialog should remember encoing strings previously entered (on any connection) and offer these in the combo in a sorted list. That way, having to re-type the encoding name again and again is avoided.
Comment 1 Uwe Stieber CLA 2012-08-14 11:32:31 EDT 
This is fixed in the Target Explorer "Terminals" view coming with TCF/TE 1.1. Once the old "Terminal" view is deprecated and replaced by it's successor (with Kepler?), this bugzilla can be marked as resolved fixed.
Comment 2 Uwe Stieber CLA 2015-05-07 08:02:10 EDT 
Fixed with TM Terminal 4.0