Hi, Please understand, making changes to the English source causes all translations to be broken for some time. Naturally, I am very selective when it comes to changing the paragraph in the English text.
(Adding a new paragraph is much less destructive ... see my patch applied as attached On Wed, Sep 28, 2016 at 11:59:12PM +0100, Brian Potkin wrote: > On Wed 28 Sep 2016 at 23:03:47 +0900, Osamu Aoki wrote: > To be pedantic ~/.xsessionrc can completely override system code > (whatever is meant by that): > > xterm & > exec fvwm OK .... I got your point but you know what I mean. Its a pedantic point but an important one. Let me think how to document it. > The same two lines in ~/.xprofile (mentioned in the patch) or ~/.gnomerc > do the same. I'm not convinced "overriding the system code" is the best > criterion to use. "stealing" ??? (But I need to think a bit more. maybe not worth changing word here.) > new" has also been taken by some users to mean "more modern" or "more > up-to-date", with he outcome that ~/.xsessionrc is seen as replacing > ~/.xsession. (There's a link to that too). Basically, this is more ratinale way. ... > The choice is between using ~/.xsession, a well-documented file > everywhere one looks, and an under-documented ~/.xsessionrc which a > search on the web would reveal is frequently misunderstood. I had rather > hoped debian-reference would rectify this state of affairs. Apparently, > the staus quo is preferable. I did not parse your last sentence. Who "prefere" status quo? > > > So what is the purpose of ~/.xsessionrc? Why does it exist? What does it > > > do better than ~/.xsession? > > > > OK ... design decision on what kind of configuration files to be > > used is not the bug topic for "debian-reference". Please discuss it > > elsewhere. > > It has been discussed and a link to the discussion provided. I have no > wish to re-live it. Excuse me, I had no time to check linked discussion so far. ( I have easier time reading shell script starting X than reading long English text.) > Without knowing what a program, file etc is designed to do makes it > difficult to write about it with any degree of confidence. It will be > noticed that a manual page generally starts by stating the purpose of > the program being used. The sentence you quote was intended to promote > thought, not discussion. True, I am not in position to defend what was done by the maintainer under this bug report. > > > A ~/.xsession must contain a command for a process which does not > > > complete (e.g. 'exec fvwm'). If it doesn't it is not possible to put > > > environment variables (or anything else there) there to be acted on by > > > 50x11-common_determine-startup. This was the thrust of the report in > > > #411639 and the reason ~/.xsessionrc was introduced. (Why 'exec > > > gnome-session' or a similar line could not be put in ~/.xsession as a > > > solution is beyond me). > > > > I totally forgot about this bug report... Hmmmm.... I see changelog > > The report specifies the design considerations and the reasons for > requesting a change. Its purpose is clear. I used it as a basis for > writing part of the submitted patch. OK, ... but your "patch" was more like your proposal in an alternative long sentence. I do not see the diff. I was busy and it was too long for me to digest but now I read it. ... > > "debian-reference" is "a terse user's guide with the focus on the shell > > command line" created and maintained by volumteer. We should not dwell > > too much in this particular issues. > > I might be misunderstanding what you mean it but this comes over to me > as "don't look too deeply at things"; "we state but do not explain"; > "don't rock the boat"; "debian-reference follows the party line". Sorry > for that view. Maybe I did not make myself clear. The text is quotation from the Debian web site. https://www.debian.org/doc/ Please also see to understand my statement "not to dwell" as KISS principle described in: https://www.debian.org/doc/manuals/debian-reference/pr01.en.html#_disclaimer https://www.debian.org/doc/manuals/debian-reference/pr01.en.html#_about_this_document So adding the Xsession(5) pointer is the first thing for me. > The submitted patch has ... > The one thing that cannot be said is that it is inaccurate or incorrect. You are very good on these. (You are missing the fact that "/etc/profile" and "~/.profile" are read now. This is newer feature which I think added following some people wanted to have Fedora like behavior.) But this completely breaks translations. > > As I read my document, I think adding a simple pointer to Xsession(5) in > > at the last part of 7.5. before 7.5.1. may be one solution. > > Maybe. That too leaves more questions unanswered than answered. If we > have Xsession(5) as the only source of information on ~/.xsessionrc it > misrepresents the reality of the role the file plays in starting X. Do > we have to settle for "better than nothing"? Attached is my patch applied to the git repo. I am not touching any paragraph. Just adding new paragraphs. (Its a patch to source written in "asciidoc".) Osamu
diff --git a/asciidoc/07_xwindow.txt b/asciidoc/07_xwindow.txt index 044ad6c..f90a777 100644 --- a/asciidoc/07_xwindow.txt +++ b/asciidoc/07_xwindow.txt @@ -141,6 +141,8 @@ Essentially, all these programs execute the "`/etc/X11/Xsession`" script. Then This process is affected by the content of "`/etc/X11/Xsession.options`". The exact programs to which these "`/usr/bin/x-\*`" commands point, are determined by the Debian alternatives system and changed by "`update-alternatives --config x-session-manager`", etc. +See `Xsession`(5) for details. + ==== Starting X session with gdm3 `gdm3`(1) lets you select the session type (or desktop environment: <<_setting_up_desktop_environment>>), and language (or locale: <<_the_locale>>) of the X session from its menu. It keeps the selected default value in "`\~/.dmrc`" as the following. @@ -155,14 +157,21 @@ Language=ja_JP.UTF-8 On a system where "`/etc/X11/Xsession.options`" contains a line "`allow-user-xsession`" without preceding "`#`" characters, any user who defines "`\~/.xsession`" or "`\~/.Xsession`" is able to customize the action of "`/etc/X11/Xsession`" by completely overriding the system code. The last command in the "`\~/.xsession`" file should use form of "`exec some-window/session-manager`" to start your favorite X window/session managers. +If this feature is used, the selection of the display (or login) manager (DM), session manager or window manager (WM) by the system utility is ignored. + ==== Customizing the X session (new method) Here are new methods to customize the X session without completely overriding the system code as above. - The display manager `gdm3` can select a specific session and set it as the argument of "`/etc/X11/Xsession`". + * "`\/etc\/profile`", "`\~\/.profile`", "`\/etc\/xprofile`", and "`\~\/.xprofile`" files are executed as a part of `gdm3` start up process. - The "`\~/.xsessionrc`" file is executed as a part of start up process. (desktop independent) + * "`#allow-user-xsession`" in "`/etc/X11/Xsession.options`" does not restrict execution of the "`\~/.xsessionrc`" file. - The "`\~/.gnomerc`" file is executed as a part of start up process. (GNOME desktop only) -- The GUI program based session management software may use the "`\~/.gnome2/session`" file etc. + +The selection of the display (or login) manager (DM), session manager or window manager (WM) by the system utility is respected. + +These configuration files should not have "`exec ...`" nor "`exit`" in them. ==== Connecting a remote X client via SSH
