Bug 753646 - Dictionary not persistent across files/restart
Summary: Dictionary not persistent across files/restart
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gedit
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-13 23:14 UTC by Andrew Ross
Modified: 2017-12-06 12:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:50:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrew Ross 2011-11-13 23:14:50 UTC
Description of problem: The dictionary is not persistent across files/restarts. In Fedora, when I add a word to the dictionary (eg. Virtualization), it is there for all future documents.


Version-Release number of selected component (if applicable):
gedit-2.28.4-3.el6.x86_64

How reproducible:


Steps to Reproduce:
1. Open a text file.
2. Tools -> Autocheck spelling
3. Right click a word (eg. virtualization) -> Spelling suggestions -> Add.
   Red underline will go away.
4. Save the file.
5. Close the file.
6. Open the file.
7. Tools -> Autocheck spelling
8. Red underline will be back for the word :-(
 
Actual results: Dictionary not persistent across files/restart.


Expected results: Dictionary is persistent.


Additional info:

Comment 2 RHEL Program Management 2011-11-13 23:48:34 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 Suzanne Logcher 2012-02-14 23:20:17 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 6 Jan Kurik 2017-12-06 12:50:27 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.