GNUstep display glitches

GNUstep display glitches

[Random832]

I have several issues to report about problems in the NS build of Emacs
under GNUstep, and I'm not sure if I should report them as a single bug
or as one bug for each issue.


Brief summary of the issues

- Terrible font display. When the configured font is not found, it
  defaults to some proportional font whose identity I'm not sure of,
  exacerbated by the more serious issue that its display of proportional
  fonts is abysmal.

- Toolbar problems. The toolbar has no background texture, and turning
  off tool-bar-mode simply does not work properly (with results that
  vary depending on if it's done interactively or in an init file, but
  are terrible in both cases)

- Fringe overlaps scrollbar, along with some other scrollbar rendering
  weirdness. (I think that when the whole document is shown, especially
  given the fact that it _can_ be scrolled down, the scrollbar should
  simply be full rather than "blank")

- No Meta key by default. The "Alt" key on my PC keyboard is interpreted
  as "Command" by the GNUstep library, and so becomes Super. The
  "Windows" key becomes Hyper, and is not configurable from within
  Emacs.

Re: GNUstep display glitches

[Eli Zaretskii]

> From: Random832 <random832@fastmail.com>
> Date: Fri, 08 Jan 2016 23:33:08 -0500
> 
> I have several issues to report about problems in the NS build of Emacs
> under GNUstep, and I'm not sure if I should report them as a single bug
> or as one bug for each issue.

Separate bugs, please.

Thanks.

Re: GNUstep display glitches

[John Wiegley]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

>> I have several issues to report about problems in the NS build of Emacs
>> under GNUstep, and I'm not sure if I should report them as a single bug
>> or as one bug for each issue.

> Separate bugs, please.

Definitely as separate bugs. The more specific a bug report can be, the easier
it is for later reviewers to attempt reproduction or make comments. Large bug
reports require commensurately large efforts to comprehend and analyze them.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]