No underscores on ubuntu with no editor preferences · Issue #42 · SWI-Prolog/issues · GitHub
Skip to content

No underscores on ubuntu with no editor preferences #42

Open

Description

@Anniepoo
  1. Install Ubuntu 16.04

  2. from Bash do
    uname -v
    the answer should be
    GMP Test crash on OpenBSD #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016

    if you're on the right version

  3. swipl

  4. at the query, emacs.

  5. In the editor type this_is_a_test

Expected: Underscores appear
Observed: Underscores don't appear

  1. chose 'editor preferences'
  2. Save what comes up
  3. halt.
  4. swipl
  5. emacs

Observed: Correct behavior, underscores appear

Activity

  1. JanWielemaker commented on Jun 28, 2016

    @JanWielemaker
    Member

    That seems to happen with some fonts, typically with specific scaling. At CWI, I use Fedora, where you get exactly the same issue using the default font. Luckily the screen is a bit too highres for my eyes, so I scaled the font up a little and then the problem disappeared. I did some investigation. First I thought it was caused by xpce computing a too small clipping area, but that doesn't seem to be the problem. You find similar complaints from other applications using specific fonts. It is unclear whether the problem is with the font itself or the font rendering.

    I don't know a good solution. Possibly we should select a different default font as to avoid this buggy one, but how? The current approach is to be as default as possible: just ask for monospace and hope the system finds a nice one.

    I think the above is a lucky shot and will not work for all setups :(

  2. Anniepoo commented on Jun 28, 2016

    @Anniepoo
    MemberAuthor

    Maybe we should file the bug with X or with linux?

  3. Anniepoo commented on Jun 28, 2016

    @Anniepoo
    MemberAuthor

    It's suprising that the default default (the one if you have no prefs file) has different behavior than if you just have a file. That's going to lead somebody into confusion when they create a file for other reasons.

  4. JanWielemaker commented on Jun 28, 2016

    @JanWielemaker
    Member

    Maybe we should file the bug with X or with linux?

    I doubt how useful that is. The bug is either in libXft or in the specific font that is selected by default.
    If I recall well, this has been reported. Our use case is six layers deep and we probably have to make a minimalistic version.

    It's suprising that the default default (the one if you have no prefs file) has different behavior than if you just have a file. That's going to lead somebody into confusion when they create a file for other reasons.

    That is probably something we have to sort out ourselves ... Shouldn't be too hard, but I must admit it is not my priority ....

  5. Anniepoo commented on Jun 28, 2016

    @Anniepoo
    MemberAuthor

    My enthusiasm for tracking it down is also low. 8cD I was just taught when I saw a bug to report it or fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions