#143 File Browser should show encodings set in recent.xml

Ian Lewis

When right-clicking on a file in the File Browser, the encoding menu should display the encoding that has been saved in the recent.xml file as selected if there is an entry for that file.

Consequently, when opening a file in the file browser, or using file->open, that has an entry in the recent.xml it should be opened with the encoding that is specified in recent.xml. I believe it's intuitive this way since the data is already saved in recent.xml and users will expect that jEdit will open the file in the encoding it was last saved in.

Currently, unless the file is opened from the recent files menu the default encoding is always used (However, unintuitively, caret data that is saved in the recent.xml file is applied to the buffer no matter how the file is opened). With this functionality it is easy to open files in an incorrect encoding. If the user saves the file in an incorrect encoding it can cause corruption of the file.


  • Kazutoshi Satoda

    Logged In: YES
    Originator: NO

    This was extracted from the bug #1524181.

    The problem is caused by unclear "current encoding"
    of File System Browser which precedes over the buffer

    Removing this "current encoding" of the File System
    Browser, and replacing [Encoding] menu of a file with
    [Open with encoding ...] menu (which is already
    implemented in ProjectViwer plugin) may be a solution.

  • Kazutoshi Satoda

    • assigned_to: nobody --> k_satoda
    • summary: File Browser should use encodings set in recent.xml --> File Browser should show encodings set in recent.xml
    • status: open --> pending-fixed
  • Kazutoshi Satoda

    The problem, that the default encoding is always used, is fixed in

    The fix also changed the default behavior of the encoding menu to show
    no one as selected until user explicitly select one.

    It is not the exact change requested by this item, but I think the
    motivation of this request is almost satisfied by the above fix.

  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks