openSUSE X.org January 2011

xorg@lists.opensuse.org

6 participants
6 discussions

[opensuse-xorg] xditview does not show the tilde character
by Krzysztof Żelechowski 31 Jan '11

31 Jan '11

Try this: { groffer -TX100 ls; } You get the following description for option -B: do not list implied entries ending with The displayed text should be: do not list implied entries ending with ~ Please fix, Chris -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

2 2

[opensuse-xorg] xorg & KVM problem
by walter harms 27 Jan '11

27 Jan '11

dear list, i have added a KVM switch (DVI) and run into trouble. Without the switch everything is normal, adding the switch causes a chaos, monitor on/off, unreadable display ,..... The switch itself is ok, it works fine under windows. Restarting X and rescanning does not help. Anyone an idea where to look ? re, wh $ xrandr -display :0 -q Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 DP-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

1 0

[opensuse-xorg] font: None in the first XTextItem
by Krzysztof Żelechowski 17 Jan '11

17 Jan '11

Specifying font: None in the first XTextItem causes a BadFont error. This is contrary to the documentation, which says that font: None has no effect on the GC. Chris -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

2 1

[opensuse-xorg] libX11 documentation complaints
by Krzysztof Żelechowski 17 Jan '11

17 Jan '11

1. Chapters in libX11.html are not in TOC. That makes it hard to identify the chapter of a given section. 2. libX11.ps has no index. It should be on page 485 which does not exist. 3. XGContextFromGC is not described in its manual page. 4. libX11.html is one big document, which makes the scroll bar unreliable in TOC 5. Tables in libX11.html are replaced by missing images (e.g. /Window attribute value mask bits/ ) Please fix, Chris -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

3 3

[opensuse-xorg] syntax colouring in xedit
by Krzysztof Żelechowski 13 Jan '11

13 Jan '11

Since when does *xedit* use syntax colouring? The manual page does not say how to switch it off, and the display is awful. The font used for /code/ is smaller than the font used for /text/ , to the point of being unreadable. -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

3 13

Re: [opensuse-xorg] syntax colouring in xedit
by Egbert Eich 13 Jan '11

13 Jan '11

Matthias Hopf writes: > On Jan 11, 11 19:02:30 +0100, Krzysztof elechowski wrote: > > > the predefined font in my c.lsp is: "*lucidatypewriter-medium-r*-12-*" > > > xlsfonts "*lucidatypewriter-medium-r*-12-*" > > The same at my side, and C language files display neatly as required. The problem is with HTML. > > xedit is using a seriously broken font setup for HTML, that is true. The > "code" font is much too small (still readable in my place, so you have > an additional issue). > > Please report this upstream, we don't do anything special about xedit > (heck, I guess it's the first time I ever actually run it knowingly). > Point is, the patches that went into xedit over the past year were mostly build fixes. Paolo used to maintain it (he also was the author of the lisp interpreter) but he hasn't contributed anything for two years now. So xedit is an x app that is more or less shipped as is. My fear is that if people raise too much hell upstream about it being broken it will become a more likely drop candidate. There are numerous much more powerful and better maintained editors around and and it may not be considered the HTML editor of choice by the vast majority of web developers. I certainly don't think the issue you are seeing has not been introduced recently as there have been no patches going in regarding fonts for quite a while. I suggest you use a different editor for html unless you would like to investigate and fix the issue yourself. I'm sure fixes are welcome upstream. Cheers, Egbert. -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

3 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE X.org January 2011