Felix Miata wrote: > deloptes composed on 2016-12-01 01:17 (UTC+0100): > >> Felix Miata wrote: > >>> deloptes composed on 2016-11-30 07:30 (UTC+0100): > >>>> Felix Miata wrote: > >>>>> xserver > >>>> In your example I don't see how you are passing the display number to >>>> xserver command > >>> I've not been, and adding it doesn't change anything. I'm not trying to >>> start a server. I'm trying to alter the already running server from >>> within the running server. The commands are all run on screen :0 in the >>> instant case. Why does the first instance work as expected (as it has >>> since it was KDE3 and probably KDE2 before) without specifying a screen? > >> I was thinking you want to run xserver on different port/screen > > That I know how to do when it's what I want to do. :-) > The thing is we don't know and above this the "why" is not clear :) >>>> All of the X servers accept the command line options >>>> described >>>> below. Some X servers may have alternative ways of providing the >>>> parameters >>>> described here, but the values provided via the command line >>>> options >>>> should override values specified via other mechanisms. > >>>> :displaynumber >>>> The X server runs as the given displaynumber, which by >>>> default is 0. If multiple X servers are to run simultaneously on a >>>> host, each >>>> must have a unique display number. See the DISPLAY >>>> NAMES >>>> section of the X(7) manual page to learn how to specify which display >>>> number >>>> clients should try to use. > >>> # man X(7) >>> bash: syntax error near unexpected token '('. >>> # man X >>> no manual entry for X > >> Strange I have man for Xorg and for X - perhaps you are missing >> something. > > 'man Xorg' works here. > > I think you are trying to teach me how to do what I already know how to > do, which has nothing to do with the purpose of the exercise. > >> And I have full featured man page for tdecmshell > > On openSUSE, or on a Debian? (sidetracking....) debian (of course) > >>> # tdecmshell --help-all only shows a displayname option, no >>> # displaynumber tdecmshell --help-all >>> Usage: kcmshell [Qt-options] [KDE-options] [options] module... > >>> Says nothing about server options. > >> Qt options: >> --display <displayname> >> Use the X-server display 'displayname' > >>> What is shown in http://fm.no-ip.com/SS/dpi108vs133.jpg is all from a >>> single running instance of starttde, not some cut and paste hocus pocus. > >>> ??? > >> What you show on the image means you change the DPI on display :0 >> (default) and it will impact all programs run there. > > Not exactly. Correct WRT :0. It has no effect on any program already open > on :0, which is one half of the point of the exercise. The xrandr DPI > change only affects programs opened after running it. I want before and > after screenshots, purely for the purpose of showing someone what does and > does not change as a result of a DPI configuration change. I succeeded in > the bulk of reaching my goal, but inelegantly by using xterms instead of > before and after tdecmshells I was expecting to be able to utilize. With > tdecmshell I was expecting its own UI to demonstrate non-text effects on > UI sizing, but most important was the text impact. > Of course you can not change the DPI of already running programs, because they have already got the DPI value when starting. >> I haven't spent too much time with X, but also not too less. AFAIR it was >> 1.GPU -> 1.Screen -> 1..n Display(s) > >> In general I do not understand what you want to achieve > > Clearly. :-) > > - you can not run a >> Xserver from within Xserver and let it bind to the same screen port which >> is already taken by the first Xserver running. In my opinion you can run >> xserver on :1 or :2 from the native console (but it would require more >> work to run applications there ... see session management) > >> man xserver >> ... >> -dpi resolution >> sets the resolution for all screens, in dots per inch. >> To >> be used when the server cannot determine the screen size(s) from the >> hard‐ >> ware. > >> At least AFAIR this is what vnc is doing, where (AFAIR) you specify the >> port example :5 and then can connect from remote to xserver on :5 remote >> via vnc. > > I've been using multiple "screens" on the same display (:0, :1 and/or :2 > running "simultaneously") forcing resolutions and DPIs for roughly a > decade (mostly on test installations, rarely on my 24/7 systems). I only > do it one of two ways though, never according to the man excerpt above, > and never (except very occasionally very temporarily) via a dpi setting > squirreled away in some DE's config file, and very very rarely using > Xft.dpi (see: ). Either I run xrandr in a startup script, or via > DisplaySize and/or PreferredMode in /etc/X11/xorg.conf*. > You are misunderstanding the display term (I think). Display is not your monitor. It is a virtual entity. >  http://fm.no-ip.com/Share/Linux/setup (with a single # removed > [according to > result desired) >  https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 > https://bugs.freedesktop.org/show_bug.cgi?id=98909 I will have to look into the links later, but from what I know it is not possible to set DPI per application on the same screen/server. It could be that you can change the font size (what we actually already have), but this is a different story. regards PS: and I am not teaching, I am just sharing my knowledge and learning something in the same time.